Page tree
Skip to end of metadata
Go to start of metadata

The content of this template is expected to be fill out for Release Planning review.


Project NameEnter the name of the project
Target Release NameMercury
Project Lifecycle StateIncubation
Participating Company China Mobile, Huawei, Intel, VMware, Wind River, ZTE


What is this release trying to address?

Provide VIM broker as a single access point to multiple VIM instances of various VIM types
Provide plugin framework of VIM drivers to add/remove VIM instances of various VIM types
Implement VIM drivers for VIM instances of OpenStack Kilo, Newton(or Mitaka) and VMWare VIO

Use Cases

Deploy VIM instance of OpenStack Kilo to deploy VNF without EPA features
Deploy VIM instance of OpenStack Newton(or Mitaka) to deploy VNF with EPA features
Deploy VIM instance of VMware VIO to deploy VNF (with/without EPA feature)

Minimum Viable Product

Northbound Interfaces
VIM Broker
VIM Driver for OpenStack Kilo
VIM Driver for OpenStack Mitaka
VIM Driver for VMware VIO


List the functionalities that this release is committing to deliver.

Functionality NameIn or OutPriorityStretch
NBI exposingINMProvide northbound interfaces for gVNFM and NFVO LCM and NFVO Resource Manager, and expose them via Swagger.json
VIM resource reportINHCollect VIM resources (cpu,memery, disk, network, etc.) to Resource Manager
EPA capability reportINMCollect EPA resources (NUMA, Hugepages, etc.) and report to Resource Manager 
Image managementINH

Create/Query/Delete images

Network and subnet managementINHCreat/Query/Delete networks and subnets
Port managementINHCreate/Query/Delete ports
Server managementINHCreate/Query/Delete servers
Volumn managementINMCreate/Query/Delete volumns
Flavor managementINH

Create/Query/Delete flavors

gVNFM integrationINH

integrate Multi-VIM driver with gVNFM

NFVO LCM and Resource Manager integrationINH

Integrate Multi-VIM driver with Resource Manager



List the functionalities proposed for this release.
Add one row for each functionality.
In Scope column, indicate if the functionality is IN (for sure it will be delivered) or OUT (the functionality has been discussed, and decision was to NOT deliver the functionality in this release).

In the Priority column, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Longer term roadmap

VIM driver for more Openstack version

VIM driver for more VIM types

Enhancement to EPA capability reporting

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable NameDeliverable Description
VIM brokerVIM broker to redict API calls to VIM types
VIM driver for OpenStack KiloVIM driver translate NBI call to SBI to VIM instance of OpenStack Kilo
VIM driver for OpenStack Newton(or Mitaka)VIM driver translate NBI call to SBI to VIM instance of OpenStack Newton(or Mitaka)
VIM driver for VMware VIOVIM driver translate NBI call to SBI to VIM instance of VMware VIO
VIM driver plugin frameworkFramework to enable develop/deploy new VIM drivers
NBI in swagger.jsondescription of Nourbound Interfaces of Multi-VIM driver


List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.

Sub-components are repositories are consolidate in a single centralized place. Edit the repository table for your project.


Key components:


•VIM instance


  –VIM instance is the VIM which is running somewhere and belong to some VIM type, e.g. OpenStack Kilo.


  –There may be multiple VIM instance with the same VIM type.


•VIM driver


  –VIM driver implements Southbound Interface from Multi VIM driver to specific VIM instances.


  –One VIM driver for a specific VIM type enables OPEN-O access to all VIM instance of that VIM type


  –It does not decide which VIM instance it is trying to access, but it is instructed to access the specific instance.


•VIM broker


  –VIM broker redirects the access request to specific VIM instance to the corresponding VIM driver by looking up the VIM type of that VIM instance.


  –VIM broker provides the single access point to VIM drivers and encapsulate the variations of different VIM drivers, which make it possible keeping Res. Mgr. and gVNFM intact while performing following operations:


         a) Update VIM instance, e.g. update VIM instance 1 from OpenStack Kilo to OpenStack Mitaka


         b) Update the existing VIM driver to enable new capability for VIM instance

API Incoming Dependencies

List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release Functionality Freeze date.

Prior to the delivery date, it is a good practice to organize an API review.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
Micro-services bus APIAPI for registration and use of micro-services bus
Log APIAPI to write log
External System APIAPI to retrieve VIM instance metadata
Driver Manager APIAPI to retrieve VIM driver for VIM instances

API Outgoing Dependencies

API this release is delivering to other releases.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
MultiVimDriver NBIAPI which is used by Resource Manager and gVNFM to interact with VIM instance Feb. 20th 2017MultiVIMDriverAPISpecification-v0.5.doc 
MultiVim Driver SBI for OpenStack Kiloprovide APIs to integrate to OpenStack Kilo   
MultiVim Driver SBI for OpenStack Newton(or Mitaka)provide APIs to integrate to OpenStack Newton (or Mitaka)   
MultiVim Driver SBI for VMware VIOprovide APIs to integrate to VMware VIO   

Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (RabbitMQ, ElasticSearch,Crystal Reports, ODL, OPNFV...).

To fill outTo fill outTo fill out

Testing and Integration Plans

Describe the plan to integrate and test the release deliverables with the overall OPEN-O system.
Confirm that resources have been allocated to perform such activities.
The Release lifecycle accounts for an Testing and Integration Review where detailed plan are expected.

This activity must be in sync with Release Integration Review milestone (RC0).

Projects may apply for a system test waiver if they think they have top-level features not requiring system test or covered by other top-level features test.

Projects must specify whether they plan to use Open-O CI infrastructure for system test. It is recommended to use the Open-O CI infrastructure unless there is some HW or SW resource that cannot be installed there. Projects running system test in external Labs are required to report system test results in a timely fashion after release creations, e.g., weekly, RC, and formal releases.


This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in the future.
List identified release gaps (if any), and its impact.

Gaps identifiedImpact
To fill outTo fill out

Known Defects and Issues

Provide a link toward the list of all known project defects.


List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out


Resources assigned to project are consolidated in a single place. Edit all the table with the ALL information, that helps to expedite Linux Foundation operations.

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

Team Internal Milestone

This section may be used to document internal milestones that the team agreed on.

Also, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

To fill outTo fill outTo fill out

Other Information

Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All OPEN-O deliverables must comply with this rule and be agnostic of any proprietary symbols.

Free and Open Source Software

FOSS activities are critical to the delivery of the whole OPEN-O initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its table within the FOSS Multi VIM.

Documentation, Training, Tutorial

  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide


It is expected all materials to be published directly either in the wiki or in OPEN-O website. Do not provide deliverable in PDF, powerpoint or word documents (these format are not easy to edit and lead to versioning issues).

Board policy (including IPR)

Indicate if the release meets the Board policy.

Release key facts

Link to Multi VIM Release Key Facts