collaborative_development_projects:rescuer
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
collaborative_development_projects:rescuer [2015/04/10 06:40] Zhipeng (Howard) Huang [Project description:] |
collaborative_development_projects:rescuer [2015/04/10 07:18] Zhipeng (Howard) Huang |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ==== Project description: ==== | ==== Project description: ==== | ||
| - | Disaster Recovery (DR) is a very important issue in NFV, as when a VIM instance or even a complete site goes down, we need a strong DR scheme to keep the service continuity to meet the requirement defined by the terms like RPO or RTO. | + | Disaster Recovery (DR) is a very important issue in NFV, for example when dealing with burst hours during holidays , shut down or malfunction of a VIM instance or even a complete site may cause severe service interruption, or a complete service termination. without a strong infrastructure level disaster recovery support. Therefore this project is proposed to develop use cases, requirements, as well as upstream project blue prints, focusing on how to make infrastructure DR-capable to keep the service continuity to meet the requirement defined by the terms like RPO or RTO when extreme scenario strikes. |
| === ETSI NFV Requirements === | === ETSI NFV Requirements === | ||
| Line 46: | Line 46: | ||
| * ''Describe the problem being solved by project'' | * ''Describe the problem being solved by project'' | ||
| - | The project aims to develop the requirements for NFVI and VIM on supporting Telco grade DR implementation which covers : | + | The project aims to develop the requirements and use cases for NFVI and VIM on supporting Telco grade DR implementation : |
| - | * Requirements for VIM and NFVI to support Single Site DR, including both active-active and active-standby design | + | |
| - | * Requirements for VIM and NFVI to support Multisite DR, including both active-active and active-standby design | + | * Requirements for VIM and NFVI to support Multisite DR, including: |
| + | |||
| + | a. For active-active, active-hot standby, active-cold standby design | ||
| + | b. Replication of all configuration and metadata required by an application - Neutron, Cinder, Nova, etc. | ||
| + | c. Ability to ensure consistency of the replicated data & metadata | ||
| + | d. Supporting a wide range of data replication methods: Storage systems based replication, Hypervisor assisted (possibly between heterogeneous storage systems). For example, using DRBD or Qemu based replication, Backup and Restore methods, Pluggable application level replication methods | ||
| + | |||
| + | * DR Use Cases to provide more requirements. | ||
| + | * Formulate BPs that would reflect the requirements, and implement those BPs in the upstream community. | ||
| * .. | * .. | ||
| - | The requirements would cover DR for compute, storage and network. | + | |
| * ''Specify any interface/API specification proposed'' | * ''Specify any interface/API specification proposed'' | ||
| Line 72: | Line 80: | ||
| This project is extendable for future functions. | This project is extendable for future functions. | ||
| - | |||
| ==== Testability: ''(optional, Project Categories: Integration & Testing)'' ==== | ==== Testability: ''(optional, Project Categories: Integration & Testing)'' ==== | ||
| Line 89: | Line 96: | ||
| * ''Identify similar projects is underway or being proposed in OPNFV or upstream project'' | * ''Identify similar projects is underway or being proposed in OPNFV or upstream project'' | ||
| - | OPNFV Multisite. | + | OPNFV: Multisite, HA For VNF, Doctor. |
| * ''Identify any open source upstream projects and release timeline.'' | * ''Identify any open source upstream projects and release timeline.'' | ||
collaborative_development_projects/rescuer.txt · Last modified: 2015/04/10 07:19 by Zhipeng (Howard) Huang
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
