Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
==== Project Name: ====

  * Proposed name for the project: ''VIM Northbound Model and Interface''
  * Proposed name for the repository: ''vim_nbi''
  * Project Categories:  ''(Requirements) ''

==== 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). 

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.

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&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.
==== Scope: ====

**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):
  * 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;
  * work together with other entities to achieve collaboration and synergy;
  * provide open source implementation for a shim layer. 
  * and coordinate integrated testing and release testing results.


**Specify any interface/API specification proposed**

Vi-Vnfm, Or-Vi
==== Dependencies: ====

**Identify similar projects is underway or being proposed in OPNFV or upstream project**

  * 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 "Neutron" project in OpenStack
  * the use cases and messages on this interface specified in the individual projects
  * the new shim layer will consider the ETSI NFV IFA specifications 
==== Committers and Contributors: ====
**Names and affiliations of the committers:**
    Tianran Zhou (zhoutianran@huawei.com)
    Lei Zhu (lei.zhu@huawei.com)
    Zhipeng Huang (huangzhipeng@huawei.com)
    Linghui Zeng (linghui.zeng@huawei.com)
    Qiao Fu (fuqiao@chinamobile.com)
    Susan Hares (shares@ndzh.com)
    Zhiying Wang (wang.zhiying1@zte.com.cn)
    Gerald Kunzmann (kunzmann@docomolab-euro.com) 
    Peter Lee (plee@clearpathnet.com)
    David Lenrow (david.lenrow@hp.com)
    Frank Zdarsky (fzdarsky@redhat.com)

**Any other contributors:**
    Julien Zhang (zhang.jun3g@zte.com.cn)
    Rajeev Seth (rseth@sonusnet.com)
    Guofeng Shao (shaoguofeng@huawei.com)
    Yinben Xia (xiayinben@huawei.com)
    Wei Cao (wayne.caowei@huawei.com)
==== Planned deliverables ====

  * 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 upper layer 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.

==== Proposed Release Schedule: ====

  * When is the first release planned?  Q2 2015   
  * Will this align with the current release cadence? Yes
Wiki

User Tools

Site Tools

Page Tools
