requirements_projects:high_availability_for_opnfv
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
requirements_projects:high_availability_for_opnfv [2014/12/04 09:26] Qiao Fu |
requirements_projects:high_availability_for_opnfv [2015/03/17 06:42] (current) Qiao Fu |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| * 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) '' | * Project Categories: ''(Requirements) '' | ||
| 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 in OpenStack is possibly not efficient. However before enhancing the HA schemes in OpenStack, the Gap analysis for Openstack HA schemes to meet with OPNFV requirements (e.g. the Carrier Grade HA) should be studied in this project. Based on the analysis, further improvement and development can be done to improve the HA schemes for the virtual infrastructure in the scope of 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 in OpenStack is possibly not efficient. However before enhancing the HA schemes in OpenStack, the Gap analysis for Openstack HA schemes to meet with OPNFV requirements (e.g. the Carrier Grade HA) should be studied in this project. Based on the analysis, further improvement and development can be done to improve the HA schemes for the virtual infrastructure in the scope of OPNFV. | ||
| - | 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. | + | There are several different mechanisms for the service HA. In this project, a report 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 27: | Line 27: | ||
| ====Scope:==== | ====Scope:==== | ||
| - | • Propose high availability requirement for Carrier Grade NFV. | + | * Propose high availability requirement for Carrier Grade NFV. |
| - | + | * Define requirements for HA API. Related interfaces may include vl-ha, vn-nf, nf-vi, vi-vnfm, or-vi. | |
| - | • Define HA API. Related interfaces may include vl-ha, vn-nf, nf-vi, vi-vnfm, or-vi. | + | * Define the supporting key performance indicators (KPIs) for measuring the HA |
| - | + | * Gap analyses of Openstack HA schemes | |
| - | • Define the supporting KPIs for measuring the HA | + | * Report about service HA scheme study |
| - | + | * HA requirements for the SDN controller | |
| - | • Gap analyses of Openstack HA schemes | + | |
| - | + | ||
| - | • Report about service HA scheme study | + | |
| ====Possible work for the following projects==== | ====Possible work for the following projects==== | ||
| Line 46: | Line 43: | ||
| • Identify any open source upstream projects and release timeline. | • Identify any open source upstream projects and release timeline. | ||
| - | Related with Openstack | + | Related with 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 54: | Line 51: | ||
| • 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 | + | The ETSI NFV REL GS (e.g. Draft ETSI GS NFV-REL 001 V1.0.0 (2014-11)) and the ongoing discussion in NFV REL field |
| ====Committers and Contributors:==== | ====Committers and Contributors:==== | ||
| - | • Name of and affiliation of the maintainer: | ||
| - | Qiao Fu (fuqiao@chinamobile.com) | + | Names and affiliations of the committers: |
| - | • Names and affiliations of the committers: | + | * Qiao Fu (fuqiao@chinamobile.com) |
| - | + | * Palani Chinnakannan (pals) [pals@cisco.com] | |
| - | Palani Chinnakannan (pals) [pals@cisco.com] | + | * Huailin Chen [huailin@arraynetworks.net] |
| - | + | * Jun Zhang [zhang.jun3g@zte.com.cn] | |
| - | Huailin Chen [huailin@arraynetworks.net] | + | * Stefan Arntzen [Stefan.Arntzen@huawei.com] |
| + | * Yuyijun (Eugene) [yuyijun@huawei.com] | ||
| + | * xueyifei [xueyifei@huawei.com] | ||
| + | * Hellmann, Gil [gil.hellmann@windriver.com] | ||
| + | * Mario Cho [hephaex@gmail.com] | ||
| + | * Jonas Bjurel [jonas.bjurel@ericsson.com] | ||
| + | * Maria Toeroe [maria.toeroe@ericsson.com] | ||
| + | * Tamas Zsiros [tamas.zsiros@ericsson.com] | ||
| - | Jun Zhang [zhang.jun3g@zte.com.cn] | + | Names and affiliations of the contributers: |
| - | + | ||
| - | Stefan Arntzen [Stefan.Arntzen@huawei.com] | + | |
| - | + | ||
| - | Yuyijun (Eugene) [yuyijun@huawei.com] | + | |
| - | + | ||
| - | xueyifei [xueyifei@huawei.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] | + | |
| - | + | ||
| - | • Any other contributors | + | |
| + | * Ian Jolliffe[Ian.Jolliffe@windriver.com] | ||
| + | * 'Hans Feldt'[hans.feldt@ericsson.com] | ||
| + | * Yao Cheng LIANG [ycliang@astri.org] | ||
| ====Planned deliverables==== | ====Planned deliverables==== | ||
| Line 103: | Line 93: | ||
| May not be as part of the 1st release | May not be as part of the 1st release | ||
| - | |||
requirements_projects/high_availability_for_opnfv.1417685171.txt.gz · Last modified: 2014/12/04 09:26 by Qiao Fu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
