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

Overview

Scope

What is this release trying to address?

The main focus of this release is on Security and transferring Helm Chart ownership back to project teams.

Securing access to ONAP applications running in Kubernetes is the highest priority. Which will introduce an Ingress Controller to remove the exposure of 100+ node ports.

Second priority will be on ensuring Helm Charts are consistent in their structure, allowing for flexible configuration (ie. choice of ingress) and then moving them to repositories under the project team's control. 

Requirements

Non-functional requirements for enhanced security and manageability of ONAP are driving OOM release deliverables.

Minimum Viable Product

Deliver a reference integration of ONAP with an Ingress Controller (with the flexibility to integrate alternative Ingress Controller implementations).

Providing secure access to ONAP applications via ingress or node ports (deprecated - to be removed in future release).

Deliver generation (include common .tpls) and enforcement (via schema) mechanism for standardized Helm Charts. This ensures consistency and ease of configuration (ie. ingress controller impl.).

Converting a subset of Helm Charts to standardized generation and validation mechanism before transferring them out of the OOM repository and into ONAP project team repositories.

Focus will be on transferring ownership for a handful (approximately 6) of project teams in this release.

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

Areas of focus for current and future releases:

• security - as we move towards service mesh

• usability - to simplify configuration and deployment of ONAP

• lower barrier to entry - by reducing the resource footprint required to deploy and run ONAP 

Release Deliverables

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

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

Architecture

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.

No OOM-related architectural changes planned for this release.

Platform Maturity

Please fill out the centralized wiki page: Frankfurt Release Platform Maturity

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

OOM does not consume application APIs.

• API Outgoing Dependencies

OOM does not produce application APIs.

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

OOM does not consume third party libraries. However, it has dependencies on infrastructure product versions for this release (listed below).

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.

OOM testing is performed directly by the Integration Team as ONAP itself is validated.

• 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

Please refer to Frankfurt Defect Status

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

Please update any risk on the centralized wiki page - Frankfurt Risks

• 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

Please update the following centralized wiki: Frankfurt Documentation

That includes

• Team contributions to the specific document related to he project (Config guide, installation guide...).

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