User Tools

Site Tools


requirements_projects:vimnbi

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
Last revision Both sides next revision
requirements_projects:vimnbi [2015/03/17 05:58]
Tianran Zhou [Scope:]
requirements_projects:vimnbi [2015/04/08 07:10]
Tianran Zhou [Committers and Contributors:]
Line 1: Line 1:
 ==== Project Name: ==== ==== Project Name: ====
  
-  * Proposed name for the project: ''​VIM Northbound ​Model and Interface''​ +  * Proposed name for the project: ''​Model ​Oriented Virtualization ​Interface''​ 
-  * Proposed name for the repository: ''​vim_nbi''​+  * Proposed name for the repository: ''​movie''​
   * Project Categories: ​ ''​(Requirements) ''​   * Project Categories: ​ ''​(Requirements) ''​
  
 ==== Project description:​ ==== ==== Project description:​ ====
-While OpenStack is a competitive candidate for VIM, existing interfaces provided by OpenStack include three major parts: compute, storage, and network. ​However, OpenStack as a general cloud platform is not customized for NFV scenario, leaving ​a lot of detailed work for the upper layer applications (e.g. orchestrator). ​+While OpenStack is a competitive candidate for VIM, existing interfaces provided by OpenStack include three major parts: compute, storage, and network. ​The IaaS service oriented NBI leaves ​a lot of detailed work for the upper layer applications (e.g. orchestrator). ​
  
-The proposed project is to provide a consistent and intuitive northbound interface for VIM to better fitting ​the orchestrator and VNF manager, and make it easy for resource access, connection generation, flow identification,​ policy operation, etc. This higher level interface ​gives the upper layer applications another option in addition to openstack ​native ​interfaces.+The proposed project is to provide a more abstract ​VIM NBI alternative by extending the general cloud platform to to simplify ​the orchestrator and VNF manager, and make it easy for resource access, connection generation, flow identification,​ policy operation, etc. This higher level abstraction ​gives the upper layer applications another option in addition to the combination of openstack ​existing ​interfaces ​and extentions developed by other OPNFV projects.
  
-There will be a shim layer to encapsulate higher order operations appropriately in the NFV problem domain, and convert them into collections of calls to cloud platformsThis project ​will use existing projects, like promise, copper, VNFFG, and so on, to implement the NBI and find gaps when the NBI cannot be implemented by existing projects.+The service oriented NBI extension ​encapsulate higher order operations appropriately in the NFV problem domain. ​It will build upon existing projects, like promise, copper, VNFFG, and so on, and their APIs to implement the NBI and find gaps when the NBI cannot be implemented by existing projects.
  
-{{ :​requirements_projects:​vim_nbi.png?​nolink&​500 |}}+{{ :​requirements_projects:​vim_nbi_extension.png?​nolink&​500 |}}
  
 To achieve the NBI consistency,​ we can use the Model Driven Architecture (MDA) approach and define system functionality using platform-independent models. Interfaces can be generated automatically with well defined models. To achieve the NBI consistency,​ we can use the Model Driven Architecture (MDA) approach and define system functionality using platform-independent models. Interfaces can be generated automatically with well defined models.
Line 19: Line 19:
 **Describe the problem being solved by project** **Describe the problem being solved by project**
  
-This project is to provide a consistent and intuitive northbound interface for VIM to better fitting the upper layer applications. With a set of information models and interfaces, we can address most use-cases in a systematical way. The proposed project is intended to (tentatively scheduled):+This project is to provide a more abstract ​VIM NBI alternative ​to better fitting the upper layer applications. With a set of higher level information models and interfaces, we can address most use-cases in a systematical way. The proposed project is intended to (tentatively scheduled):
   * document typical NFV use-cases for high-level functional abstraction,​ and find gaps between OpenStack API and applicaitons;​   * document typical NFV use-cases for high-level functional abstraction,​ and find gaps between OpenStack API and applicaitons;​
-  * abstract the service oriented VIM NB models and interfaces, refine existing information models and develop new models;+  * abstract the service oriented VIM NB models and interfaces;
   * work together with other entities to achieve collaboration and synergy;   * work together with other entities to achieve collaboration and synergy;
-  * provide open source implementation for a shim layer+  * provide ​an open source implementation for the NBI extension
   * and coordinate integrated testing and release testing results.   * and coordinate integrated testing and release testing results.
  
Line 40: Line 40:
   * The "​Nova"​ project in OpenStack   * The "​Nova"​ project in OpenStack
   * The "​Neutron"​ project in OpenStack   * The "​Neutron"​ project in OpenStack
-  * ETSI IFA005,006 +  * the use cases and messages on this interface specified in the individual projects 
 +  * the new abstraction layer will consider the ETSI NFV IFA specifications ​
 ==== Committers and Contributors:​ ==== ==== Committers and Contributors:​ ====
 **Names and affiliations of the committers:​** **Names and affiliations of the committers:​**
     Tianran Zhou (zhoutianran@huawei.com)     Tianran Zhou (zhoutianran@huawei.com)
 +    Yinben Xia (xiayinben@huawei.com)
 +    Wei Cao (wayne.caowei@huawei.com)
     Lei Zhu (lei.zhu@huawei.com)     Lei Zhu (lei.zhu@huawei.com)
     Zhipeng Huang (huangzhipeng@huawei.com)     Zhipeng Huang (huangzhipeng@huawei.com)
Line 54: Line 56:
     Peter Lee (plee@clearpathnet.com)     Peter Lee (plee@clearpathnet.com)
     David Lenrow (david.lenrow@hp.com)     David Lenrow (david.lenrow@hp.com)
 +    Frank Zdarsky (fzdarsky@redhat.com)
  
 **Any other contributors:​** **Any other contributors:​**
Line 59: Line 62:
     Rajeev Seth (rseth@sonusnet.com)     Rajeev Seth (rseth@sonusnet.com)
     Guofeng Shao (shaoguofeng@huawei.com)     Guofeng Shao (shaoguofeng@huawei.com)
-    ​Yinben Xia (xiayinben@huawei.com) +    ​Parviz Yegani ​(pyegani@juniper.net)
-    Wei Cao (wayne.caowei@huawei.com)+
 ==== Planned deliverables ==== ==== Planned deliverables ====
  
   * Described the project release package as OPNFV or open source upstream projects.   * Described the project release package as OPNFV or open source upstream projects.
   - Document on typical NFV use-cases for high-level functional abstraction   - Document on typical NFV use-cases for high-level functional abstraction
-  - Gap Analysis for OpenStack API and high level applicaitons +  - Gap Analysis for existing ​OpenStack API and upper layer applicaitons 
-  - Blueprint sent to OpenStack "​Congress"​ and more.+  - Blueprint sent to OpenStack, e.g. "​Congress", "​Neutron" and more.
  
   * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.   * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.
requirements_projects/vimnbi.txt · Last modified: 2015/04/27 05:43 by Tianran Zhou