User Tools

Site Tools


requirements_projects:multisite

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:multisite [2015/03/25 09:29]
Zhipeng (Howard) Huang [Project Name:]
requirements_projects:multisite [2015/04/21 06:26] (current)
Zhipeng (Howard) Huang
Line 6: Line 6:
  
 ==== Project description:​ ==== ==== Project description:​ ====
 +
 +{{:​requirements_projects:​multisite.png?​200|}}
  
 NFV infrastructure must be distributed across multiple geographical locations. This will require multiple connected OpenStack deployments,​ of different sizes. The infrastructure will also mix physical and virtual infrastructure. NFV infrastructure must be distributed across multiple geographical locations. This will require multiple connected OpenStack deployments,​ of different sizes. The infrastructure will also mix physical and virtual infrastructure.
Line 17: Line 19:
 As shown in the above figure, although Multisite is not a requirement project that only integrates works from other requirement projects, it does have possible inputs from projects like Copper, Promise, VNFFG, Doctor, HA, Paser, and other new project being able to running on multi-site scenario. It should be noted that it is up to the respective project team to decide if they have requirements for such scenario, and what those requirements would be (That'​s why they are all in dotted lines). For projects that do see multi-site scenario is necessary, Multisite project would be more than glad to work together with those projects, through any form it deems fit, to provide common requirements,​ and further feedback to the upstream community for implementation. As shown in the above figure, although Multisite is not a requirement project that only integrates works from other requirement projects, it does have possible inputs from projects like Copper, Promise, VNFFG, Doctor, HA, Paser, and other new project being able to running on multi-site scenario. It should be noted that it is up to the respective project team to decide if they have requirements for such scenario, and what those requirements would be (That'​s why they are all in dotted lines). For projects that do see multi-site scenario is necessary, Multisite project would be more than glad to work together with those projects, through any form it deems fit, to provide common requirements,​ and further feedback to the upstream community for implementation.
  
-For those of which features will be developed only inside one site, for example Qtip, VSPERF, some feature of HA, some feature of Doctor, will not produce dependency on multi-site project. However it should also be noted that there are certain scenarios in a single site deployment that actually deals with the same technical difficualties as in a multisite deployment. These scenarios, if deems necessary, would be included in the Multisite project discussion.+For those of which features will be developed only inside one site, for example Qtip, VSPERF, some feature of HA, some feature of Doctor, will not produce dependency on multi-site project. However it should also be noted that there are certain scenarios in a single site deployment that actually deals with similar ​technical difficualties as in a multisite deployment. These scenarios, if deems necessary, would be included in the Multisite project discussion.
  
 === General High Level Requirements === === General High Level Requirements ===
Line 23: Line 25:
 The Multisite Project would like to drive the following high level requirements to be defined in the process: The Multisite Project would like to drive the following high level requirements to be defined in the process:
  
-1. The requirement of supporting performance and fault management for a multisite ​VIMs deployment ​scenarion.+1. The requirement of supporting performance and fault management for a multisite ​VIM deployment ​scenario.
  
-2. The requirement of supporting vnf software image management for supporting ​a multisite ​VIMs deployment ​scenarion.+2. The requirement of supporting vnf software image management for a multisite ​VIM deployment ​scenario.
  
-3. The requirement of virtualized resource management for a multisite ​VIMs deployment ​scenarion.+3. The requirement of virtualized resource management for a multisite ​VIM deployment ​scenario.
  
-4. The requirement of supporting identity management for a multisite ​VIMs deployment ​scenarion.+4. The requirement of supporting identity management for a multisite ​VIM deployment ​scenario.
  
-5. The requirement of supporting policy management for a multisite VIM deployment ​scenarion.+5. The requirement of supporting policy management for a multisite VIM deployment ​scenario.
  
-6. The requirement of message bus enhancement for a multisite VIM deployment ​scenarion.+6. The requirement of message bus enhancement for a multisite VIM deployment ​scenario.
  
-7. The requirement of defining/​utilizing NFVI Descriptor/​Record for a multisite VIM deployment ​scenarion.+7. The requirement of defining/​utilizing NFVI Descriptor/​Record for a multisite VIM deployment ​scenario.
  
-8. ...+8. The requirement of supporting High Availability for a multisite VIM deployment scenario.
  
 +9. The requirement of supporting Disaster Recovery for a multisite VIM deployment scenario.
 +
 +10. ...
  
 More requirements would be added afterwards. More requirements would be added afterwards.
Line 47: Line 52:
  
 === Uses Cases ===  === Uses Cases === 
 +
 +Sample Use Cases dealing with HA, GR:
 +
 +  - 1. HA: High Availability cross VIMs ( in one site, but not limited to). Requirements for such use case would relate to how Neutron establish the networks to support HA or how Keystone maintains HA features, for instances.
 +
 + 
 +
 +  - 2. GR: Geo-site Redundancy, with/​without application level data/​configuration replication (Cross-site disaster recovery would be one classic use case of this type). Requirements for such use case would relate to for example, how Cinder supports cross-site data replication.
 +
 + 
 +
 +  - 3. GLB: Geo-site Load Balancing, DNS based, or non-DNS based. GLB can work as the front-end for HA and GR, HA and GR can work without GLB.
 +
 +In the above exemplary use cases, VNF may run in active-active or active-standby mode, according to the VNF management setup, which is out of the scope of this project. This project only concerns with how VIM should support the VNF in multi-site scenario.
 + 
 +It should be noted that these are non-exhaustive exemplary use cases which aim to serve the purpose of the clarification of the project, in certain aspects that may have confusions .
 + 
 +More detailed use cases are among the targeted deliverables of phase 1 of this project, which won’t be available during the proposal period, and more sophisticated ​ use cases like migration across VIM could be discussed in the later phase.
  
 Currently there are several high level use cases already defined by ETSI NFV documents: Currently there are several high level use cases already defined by ETSI NFV documents:
Line 121: Line 144:
     ''​OpenStack''​     ''​OpenStack''​
   * Identify any open source upstream projects and release timeline. ​   * Identify any open source upstream projects and release timeline. ​
-    ''​based on OpenStack Liberty Release which is available by the middle of Oct.2015''​+    ''​OpenStack ​as upstream project, and target ​Liberty Release which is available by the middle of Oct.2015''​
   * 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.
-    ''​based on OpenStack Liberty Release which is available by the middle of Oct.2015''​+    ''​OpenStack ​as upstream project, and target ​Liberty Release which is available by the middle of Oct.2015''​
   * Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.   * Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.
-    ''​ETSI NFV''​+    ''​ETSI NFV: GS MANO,GS INF, GS IFA005, GS IFA006, GS IFA010, and future Phase 3 work''​
   * If project is an integration and test, identify hardware dependency.   * If project is an integration and test, identify hardware dependency.
     ''​None''​     ''​None''​
Line 135: Line 158:
   * Xiaolong Kong, Orange (xiaolong.kong@orange.com)   * Xiaolong Kong, Orange (xiaolong.kong@orange.com)
   * Gerald Kunzmann (kunzmann@docomolab-euro.com)   * Gerald Kunzmann (kunzmann@docomolab-euro.com)
 +  * Ulrich Kleber (Ulrich.Kleber@huawei.com)
 +  * Colin Tregenza Dancer (ctd@metaswitch.com)
  
 Names and affiliations of any other contributors Names and affiliations of any other contributors
  
   * Morgan Richomme, Orange (morgan.richomme@orange.com)   * Morgan Richomme, Orange (morgan.richomme@orange.com)
 +  * Daniel Smith, Ericsson (daniel.smith@ericsson.com)
 +  * Dimitri Mazmanov, Ericsson (dimitri.mazmanov@ericsson.com)
   * Ashiq Khan (khan@nttdocomo.com)   * Ashiq Khan (khan@nttdocomo.com)
   * Zhipeng Huang, Huawei (huangzhipeng@huawei.com)   * Zhipeng Huang, Huawei (huangzhipeng@huawei.com)
Line 144: Line 171:
   * Ray, Smartscale Systems (rnugent@smartscalesystems.com)   * Ray, Smartscale Systems (rnugent@smartscalesystems.com)
   * Mike Godley, Intel (michael.godley@intel.com)   * Mike Godley, Intel (michael.godley@intel.com)
- +  * Jie Hu, ZTE (hu.jie@zte.com.cn)
 ==== Planned deliverable ==== ==== Planned deliverable ====
  
requirements_projects/multisite.1427275765.txt.gz · Last modified: 2015/03/25 09:29 by Zhipeng (Howard) Huang