User Tools

Site Tools


requirements_projects:nemo

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:nemo [2015/03/13 12:30]
Tianran Zhou [Project description:]
requirements_projects:nemo [2015/07/02 07:43] (current)
Tianran Zhou
Line 1: Line 1:
 +====== This page is outdated. ​ ======
 +====== Please go to the following link for the project proposal ======
 +
 +[[requirements_projects:​vimnbi|Project Name: MOVIE]]
 +
 +
 +
 ==== Project Name: ==== ==== Project Name: ====
  
Line 8: Line 15:
 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 NFV orchestrator. ​ 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 NFV orchestrator. ​
  
-The proposed project is to provide a consistent and intuitive northbound interface for VIM to better fitting the orchestrator,​ and make it easy for resource access, connection generation, flow identification,​ policy operation, etc.+The proposed project is to provide a consistent and intuitive northbound interface for VIM to better fitting the orchestrator,​ and make it easy for resource access, connection generation, flow identification,​ policy operation, etc. This higher level interface gives the upper layer application (e.g. orchestrator) another option in addition to openstack native interfaces.
  
 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 platforms. This 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. 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 platforms. This 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.
  
-{{ :​requirements_projects:​vim_nbi.png?​nolink&​600 |}}+{{ :​requirements_projects:​vim_nbi.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 26:
 **Describe the problem being solved by project** **Describe the problem being solved by project**
  
-This project is to provide a consistent, organized ​and intuitive northbound interface for VIM to better fitting ​the VNF manager and the orchestrator. 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 consistent and intuitive northbound interface for VIM to better fitting the orchestrator. 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):
   * document typical NFV use-cases for high-level functional abstraction,​ and find gaps between OpenStack API and high level applicaitons;​   * document typical NFV use-cases for high-level functional abstraction,​ and find gaps between OpenStack API and high level applicaitons;​
-  * abstract VIM NB models and interfaces, refine existing information models and develop new models;+  * abstract ​the service oriented ​VIM NB models and interfaces, refine existing information models and develop new models;
   * work together with other entities to achieve collaboration and synergy;   * work together with other entities to achieve collaboration and synergy;
-  ​The following figure shows the mapping to ETSI NFV architecture. As the first step, Or-Vnfm interface is beyond the scope of existing OPNFV. So the logical node operation will map to this architecture with secondary priority. +  * provide open source implementation for a shim layer. ​
-{{ :​requirements_projects:​nemo-nfv_arch-mapping.png?​nolink&​600 |}} +
-  ​* provide open source implementation for a shim layer. The northbound API encapsulates higher order operations appropriate in the NFV problem domain, and converts them into collections of calls to cloud platforms.+
   * and coordinate integrated testing and release testing results.   * and coordinate integrated testing and release testing results.
 +
  
 **Specify any interface/​API specification proposed** **Specify any interface/​API specification proposed**
Line 36: Line 42:
  
   * The "​Promise"​ project in OPNFV   * The "​Promise"​ project in OPNFV
 +  * The "​Copper"​ project in OPNFV
 +  * The "​VNFFG"​ project in OPNFV
 +  * The "​Doctor"​ project in OPNFV
   * The "​Nova"​ project in OpenStack   * The "​Nova"​ project in OpenStack
   * The "​Neutron"​ project in OpenStack   * The "​Neutron"​ project in OpenStack
-  * The "​Congress"​ project ​in OpenStack +  * the use cases and messages specified ​in the individual projects 
 +  * new shim layer will consider the interface specifications currently being made by ETSI NFV IFA
 ==== Committers and Contributors:​ ==== ==== Committers and Contributors:​ ====
 **Names and affiliations of the committers:​** **Names and affiliations of the committers:​**
Line 62: Line 71:
  
   * 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
 +  - Gap Analysis for OpenStack API and high level applicaitons
 +  - Blueprint sent to OpenStack, e.g. "​Congress"​ 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/nemo.1426249811.txt.gz · Last modified: 2015/03/13 12:30 by Tianran Zhou