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.

–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:

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.

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

Name

Description

Version

To fill out

To fill out

To 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.

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.

Gaps

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 identified

Impact

To fill out

To fill out

Known Defects and Issues

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

Risks

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 identified

Mitigation Plan

Contingency Plan

To fill out

To fill out

To fill out

Resources

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.

Date

Project

Deliverable

To fill out

To fill out

To 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.

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

Note

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