User Tools

Site Tools


High availability for OPNFV

  • Proposed name for the project: High availability for OPNFV
  • Proposed name for the repository: availability
  • Project Categories: (Requirements)

Project description:

This project is based on the requirement proposal in “HA requirement-Chinamobile.pptx”, which is proposed in the initial TSC meeting. The proposal is focusing on the high availability requirements of the OPNFV platform regarding the Carrier Grade NFV scenarios. Some possible development of codes to meet the requirement may also be developed.

In the current networks, normally HA is required for the physical hardware, and can be fulfilled by 1:1 backup. When it comes to the NFV case, since VNFs are all virtualized on different VMs, HA problem can become complicated. In this project, we address HA requirements and solutions in 3 different perspectives, the hardware HA, the virtual infrastructure HA and the service HA, to be specific.

The hardware HA can be solved by several legacy HA schemes. However, when considering the NFV scenarios, hardware failure will cause collateral damage to not only virtual infrastructures but also services running on it. Therefore, fault detection and report of HW failure from the hardware to VIM, VNFM and Orchestrator is necessary for the HA approaches in OPNFV.

Virtual infrastructure HA addresses the high availability mechanisms for NFV infrastructures and VIM. The HA schemes Openstack now have, which provides HA for different components for Openstack (such as Nova, Quantum, and etc.), can be categorized into this class. However, considering the Carrier Grade NFV scenarios, current HA schemes may not be enough. Gap analysis for Openstack HA schemes can be done in this project. Based on the analysis, further improvement and development can be done to improve the HA schemes for the virtual infrastructure.

There are several different mechanisms for the service HA. In this project, a white paper concluding these different mechanisms will be accomplished. Based on these mechanisms, we can further study what capability and interfaces OPNFV platform shall provide to the services. Therefore, API provided by the OPNFV platform to the services HA schemes should be well defined.

In this project, we will first work on the HA requirements of Carrier Grade NFV. The requirements will include the hardware HA, the virtual infrastructure HA, and the service HA. HA API will then be well defined according to the requirements. Such API may include not only state update but also capability provision from the hardware and platform to the Orchestrator, the VNFM and different VNFs,

For hardware HA, legacy HA mechanisms will be studied. Considering the NFV scenario, API will be defined for the hardware to inform the up-layers about its states and its capability. Related interfaces may include vl-hw, nf-vi, vi-vnfm, and or-vi.

For the virtual infrastructure HA, gap analyses of HA mechanism will be proposed for the current Openstack. Advance mechanisms of OPNFV HA can be studied and developed. And corresponding Openstack extension can then be developed in the following collaborative development project.

For the service HA, studies about the current service HA schemes can be pulled out. In the meantime, API can be defined for state update and capability provision for the VNFs from the lower layers. Related interfaces may include vn-nf, vi-vnfm and or-vi.

Based on the output of this requirement project, corresponding testing may also be worked out about the HA APIs and possible development in the following integration and testing project.


• Propose high availability requirement for Carrier Grade NFV.

• Define HA API requirements. Related interfaces may include vl-ha, vn-nf, nf-vi, vi-vnfm, or-vi.

• Gap analyses of Openstack HA schemes

• Whitepaper about service HA scheme study

Possible work for the following projects:

• Openstack extension and development on HA

• Testcases of OPNFV HA API and development.


• Identify any open source upstream projects and release timeline.


• Identify any specific development be staged with respect to the upstream project and releases.

• Are there any external fora or standard development organization dependencies. If possible, list and


Committers and Contributors:

• Names and affiliations of the committers:

Qiao Fu (

Palani Chinnakannan (pals) []

Huailin Chen []

Jun Zhang []

Stefan Arntzen []

Yuyijun (Eugene) []

Yifei Xue []

Hellmann, Gil []

Jonas Bjurel []

Maria Toeroe []

Tamas Zsiros []

Murali Birru []

• Any other contributors

Planned deliverables

• HA requirement documents

• HA API specification

• Openstack HA gap analyses

• Whitepaper of service HA schemes

Proposed Release Schedule:

• When is the first release planned?

• Will this align with the current release cadence

May not be as part of the 1st release 
requirements_projects/high_availability_for_vnfs.txt · Last modified: 2014/12/17 06:35 by Murali Birru