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 14:04]
Tianran Zhou [Scope:]
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.
Line 40: Line 47:
   * 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 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 66: Line 73:
   - 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 OpenStack API and high level applicaitons
-  - Blueprint sent to OpenStack "​Congress"​ and more.+  - 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.1426255495.txt.gz · Last modified: 2015/03/13 14:04 by Tianran Zhou