User Tools

Site Tools


requirements_projects:high_availability_for_vnfs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
requirements_projects:high_availability_for_vnfs [2014/11/28 06:51]
Qiao Fu
requirements_projects:high_availability_for_vnfs [2014/12/17 06:35] (current)
Murali Birru [Committers and Contributors:]
Line 1: Line 1:
-====High availability for VNFs====+====High availability for OPNFV====
  
   * Proposed name for the project: ''​High availability for OPNFV''​   * Proposed name for the project: ''​High availability for OPNFV''​
-  * Proposed name for the repository: ''​HA''​ +  * Proposed name for the repository: ''​availability''​ 
-  * Project Categories: ''​(Requirements),​(Integration & Testing)''​+  * Project Categories: ''​(Requirements) ''​
  
 ====Project description:​ ==== ====Project description:​ ====
Line 15: Line 15:
 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. 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. ​In the meantime, API provided by the OPNFV platform to the services HA schemes should be well defined.+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,  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, 
Line 21: Line 21:
 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 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. ​+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. ​ 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. ​
  
-Corresponding ​testing may also be worked ​on about the HA APIs and possible development. ​+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
  
 ====Scope:​==== ====Scope:​====
Line 31: Line 31:
 • Propose high availability requirement for Carrier Grade NFV. • Propose high availability requirement for Carrier Grade NFV.
  
-• Define HA API. Related interfaces may include vl-ha, vn-nf, nf-vi, vi-vnfm, or-vi.+• Define HA API requirements. Related interfaces may include vl-ha, vn-nf, nf-vi, vi-vnfm, or-vi.
  
-• Gap analyses ​and possible extension and development ​of Openstack HA schemes+• Gap analyses of Openstack HA schemes
  
 • Whitepaper about service HA scheme study • 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. • Testcases of OPNFV HA API and development.
Line 42: Line 46:
 • Identify any open source upstream projects and release timeline. ​ • Identify any open source upstream projects and release timeline. ​
  
-Related with Openstack+  ​Openstack 
 +  OpenDaylight
  
 • Identify any specific development be staged with respect to the upstream project and releases. • Identify any specific development be staged with respect to the upstream project and releases.
Line 48: Line 53:
 • Are there any external fora or standard development organization dependencies. If possible, list and  • Are there any external fora or standard development organization dependencies. If possible, list and 
  
-None + None 
  
 ====Committers and Contributors:​==== ====Committers and Contributors:​====
-Name of and affiliation ​of the maintainer:  +Names and affiliations ​of the committers
 +
 Qiao Fu (fuqiao@chinamobile.com) Qiao Fu (fuqiao@chinamobile.com)
  
-• Names and affiliations of the committers: 
-  
 Palani Chinnakannan (pals) [pals@cisco.com] Palani Chinnakannan (pals) [pals@cisco.com]
   
Line 62: Line 65:
  
 Jun Zhang [zhang.jun3g@zte.com.cn] Jun Zhang [zhang.jun3g@zte.com.cn]
- 
-Yuyijun (Eugene) [yuyijun@huawei.com] 
   
 Stefan Arntzen [Stefan.Arntzen@huawei.com] Stefan Arntzen [Stefan.Arntzen@huawei.com]
 +
 +Yuyijun (Eugene) [yuyijun@huawei.com]
 +
 +Yifei Xue [xueyifei@huawei.com]
  
 Hellmann, Gil [gil.hellmann@windriver.com] Hellmann, Gil [gil.hellmann@windriver.com]
 +
 +Jonas Bjurel [jonas.bjurel@ericsson.com]
 +
 +Maria Toeroe [maria.toeroe@ericsson.com]
 +
 +Tamas Zsiros [tamas.zsiros@ericsson.com]
 +
 +Murali Birru [murali.yadav@calsoftlabs.com]
   
 • Any other contributors • Any other contributors
Line 79: Line 92:
 • Openstack HA gap analyses • Openstack HA gap analyses
  
-• Whitepaper of service HA schemes ​ +• Whitepaper of service HA schemes ​ 
- +
-• Openstack extension for HA +
- +
-• Test cases and test reports for HA API and extensions ​+
  
 ====Proposed Release Schedule:​==== ====Proposed Release Schedule:​====
Line 89: Line 98:
  
 • Will this align with the current release cadence • Will this align with the current release cadence
-  + May not be as part of the 1st release ​
-May not be as part of the 1st release ​+
requirements_projects/high_availability_for_vnfs.1417157495.txt.gz · Last modified: 2014/11/28 06:51 by Qiao Fu