Overview

Scope

What is this release trying to address?

In this release we will address the need for improving automation, permissions and instantiation flows of VNFs.

Use Cases

VID will contribute to the following use cases:

Use Case: Residential Broadband vCPE (Approved)

Use Case: VoLTE(approved)

VID will continue to support to the following use case:

Use Case: vFW/vDNS (Approved)

Minimum Viable Product

• Read only "ONAP global role" permission for VID users
• Specific role assignment for components instantiations 
• Change management for selected work flows (Upgrade and Configuration)
• PNF support

Functionalities

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.

Epics

Stories

Longer term roadmap

• Fully automated deployment of new VNFs without the need of manual intervention or configuration.
• Support workflows for change management by using the SDC as a provider of workflows capabilities 
• Dashboarding scheduled and ongoing change management

Release Deliverables

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

Sub-Components

ONAP Dependencies

Portal - Our application is compiled with the Portal SDK and is accessed as a "tab" in the Portal web application. Any changes to this sdk may require re-compilation on our end.

A&AI - We are dependent on A&AI apis so that we can retrieve instances of already exist Services,VNFs and Modules.

AAF - We are dependent on AAF so that our new roles are managed through the Portal and role cased permissions of VID.

SDC - We are dependent on being able to integrate with the SDC API in order to receive service catalog and models

(m)SO - We are dependent on SO (MSO) so that VID will invoke creation and modification of services, VNFs and modules.

Architecture

High level architecture diagram

API Incoming Dependencies

Not applicable for this release

API Outgoing Dependencies

API this release is delivering to other releases.

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, RabbitMQ, ElasticSearch,Crystal Reports, ...).

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 tests are run automatically as part of every code merge.
• Once the final Docker image is compiled, it will be installed onto a Docker host and will be checked to ensure no errors occur during start-up.
• Functional testing will occur to ensure that the use cases are functioning correctly.

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.

Known Defects and Issues

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

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

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.

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

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.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.