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


Project NameEnter the name of the project
Target Release NameAmsterdam
Project Lifecycle StateIncubation
Participating Company Huawei, Intel, AT&T, Gigaspaces, China Mobile, Wind River, Orange, Amdocs, Nokia, ZTE, IBM, VMWare, Cisco, ARM


What is this release trying to address?

  1. Align with VNF Requirements
  2. Develop ONAP packaging model (combining OPEN-O and ECOMP)
  3. Align VNF packaging and validation tools with new model
  4. Align VNF SDK tools (from OPEN-O) with ICE tools (from ECOMP)
  5. Support VNF Validation project tooling requirements
  6. Support handoff to SDC for VNF onboarding

Use Cases

  1. In Amsterdam, we will target packaging of the vCPE and VoLTE VNFs
    1. MVP is to package open source VNFs included in the above

Minimum Viable Product

The MVP for Amsterdam will create an ONAP VNF packaging model and align the OPEN-O and ICE tools with that model.


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

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

To Be Discussed:

  • NS Onboarding Consideration

Release Deliverables

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

Deliverable NameDeliverable Description
Compliance ToolExecutable
ModelUML info model and TOSCA model
Packaging toolExecutable
Reference Repo/MarketplaceExecutable

API : Deliver API for external Project. The API will deliver such as uploading/downloading/Updating/etc functionality
Validation ToolsExecutable
Lifecycle Test FrameworkExecutable/Library
Function Test FrameworkExecutable/Library


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 Release Components name for your project in the centralized page.

ONAP Dependencies

  • VNF Validation Program: responsible for developing a validation program to provide assurance of VNF interoperability with ONAP. It will document governance and processes.
  • VNF Requriement : responsible for documenting VNF guidelines and requirements. It will produce requirements documents
  • Modeling: align information model and TOSCA model
  • Microservices Bus: register microservices
  • SDC: handoff for VNF onboarding


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.

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.

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

API Outgoing Dependencies

API this release is delivering to other releases.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
Upload APIAPI for vendors to upload VNF packages to marketplaceDate for which the API is reviewed and agreedTo fill outAPI Documentation
Download APIAPI for downloading VNF Package from marketplace

API Documentation
Query VNF informationAPI to query information on VNFs uploaded to the marketplace

API Documentation

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

To fill outTo fill outTo fill out

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.

We will provide unit tests and CSIT tests for validation tools, packaging tools, and certification tools.


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
To fill outTo fill out

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


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


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 FOSS VNF SDK.

Charter Compliance

The project team comply with the ONAP Charter.