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


Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.


Project NameEnter the name of the project
Target Release NameGuilin
Project Lifecycle StateIncubation
Participating Company ATT, China Mobile, Intel, VMware, Wind River


What is this release trying to address?

1, Align to S3P and security requirements and Architecture.

2, Enhance MultiCloud support to StarlingX 4.0.

3, Enhance MultiCloud support to Wind River Cloud Platform which is based on StarlingX 4.0


Functional requirements

REQ-341 - Getting issue details... STATUS

Non-functional requirements (TSC must have)

REQ-380 - Getting issue details... STATUS

REQ-379 - Getting issue details... STATUS

REQ-374 - Getting issue details... STATUS

REQ-370 - Getting issue details... STATUS

REQ-366 - Getting issue details... STATUS

REQ-365 - Getting issue details... STATUS

REQ-362 - Getting issue details... STATUS

REQ-361 - Getting issue details... STATUS

REQ-323 - Getting issue details... STATUS

Requirement with risk:

REQ-373 - Getting issue details... STATUS

REQ-363 - Getting issue details... STATUS

REQ-351 - Getting issue details... STATUS

REQ-349 - Getting issue details... STATUS

Minimum Viable Product

Enhanced MultiCloud Plugin for StarlingX

Enhanced MultiCloud Plugin for Wind River

Enhanced MultiCloud Plugin for k8s


List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, 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.


Key Summary T Created Updated Due Assignee Reporter P Status Resolution


Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Longer term roadmap

Provide a mediation layer between ONAP and underlying infrastrucutres, including openstack, k8s, public clouds, etc..

Release Deliverables

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

Deliverable NameDeliverable Description
Docker ImagesDocker images for all Multi-VIM/Cloud components
DocumentationsDeveloper and user documentations for all Multi-VIM/Cloud components
Maven ArtifactsMaven Artifacts for all Multi-VIM/Cloud components
Release NoteRelease Note cover all Multi-VIM/Cloud components
Source CodeSource code for all Multi-VIM/Cloud components


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

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.


High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Architecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.

The Diagram below shows how Multi-VIM/Cloud fits into ONAP architecture in a high level view


The Diagram below depicts the interaction between Multi-VIM/Cloud and related ONAP components

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

  • API Incoming Dependencies

List the API this project is expecting from other projects.
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 API Freeze date.

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

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
eventListener/v5VES collector event publish APIsN/A since It is ready nowN/A since It is ready now

API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
OpenStack Proxy endpointOpenStack APIs (align to newton release) with proxied endpoints exposed by each plugin (OpenStack, VIO)Ready Since Amsterdam ReleaseReady Since Amsterdam Release

VFC orientied APIsabstract APIs for VFC which is inherited from OPENO for each plugin (OpenStack, VIO)Ready Since Amsterdam ReleaseReady Since Amsterdam Release
OOF oriented APIsCapacity check to filter out those underlying VIM/Cloud without adequate resources for VNF placementReady Since Beijing ReleaseReady Since Beijing Release

Registry API is used to discover infrastructure's resources, including HPA and register them into AAI

Ready Since Amsterdam ReleaseReady Since Amsterdam Release
FCAPS configuration APIFCAPS configuration API is to provision VESagent with VES collector endpoint, metric to collect, event to report, etc.Ready Since Beijing ReleaseReady Since Beijing Release

SO oriented APIsGeneric API for SO to adapt to various VIM/Cloud type with MultiCloud pluginReady Since Dublin ReleaseReady Since Dublin Release
  • 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 (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).


Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects)

RabbitMQ is an implementation of AMQP, the emerging standard for high performance enterprise messaging. The RabbitMQ server is a robust and scalable implementation of an AMQP broker3.6.6-1
uWSGI is a fast, self-healing and developer/sysadmin-friendly application container server2.0.17
Celery is an asynchronous task queue based on distributed message passing
library for authenticating to an OpenStack-based cloud
A high-level Python Web framework that encourages rapid development and clean, pragmatic design.
A powerful and flexible toolkit for building Web APIs

A comprehensive HTTP client library, httplib2 supports many features left out of other HTTP libraries.

a Python interface to the memcached memory cache daemon1.59
onap python logging library

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

  • Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

  • Unit Test: 50% above coverage
  • Functional test: CSIT to cover major functionalities
  • Integration test: Support integration team to provide the end to end integration test.
  • All the above should be automation tests run on the LF Jenkins Infrastructure.
  • 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 a future Release.
List identified release gaps (if any), and its impact.

Gaps identifiedImpact
  • Known Defects and Issues

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

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  • 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 identifiedMitigation PlanContingency Plan
Lack committed resource for MultiClod Azure component Call for contributor from communityrequest waiver or de-scope this component from Guilin Release
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • 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 is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, 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, it is erecommended to 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
  • Documentation, Training

  • Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  • Highlight the team contributions to the overall Release Documentation and training asset
  • 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
    • ...


The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

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 ONAP 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 ONAP 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 project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.