The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Frankfurt |
| Project Lifecycle State | Core |
| Participating Company | Amdocs, AT&T, Bell Canada, Orange, Samsung |
Scope
What is this release trying to address?
...
Non-functional requirements for enhanced security and manageability of ONAP are driving OOM release deliverables.
Minimum Viable Product
Reference Deliver a reference integration of ONAP with an Ingress Controller . Providing (with the flexibility to integrate with alternative Ingress Controller implementations).
Providing secure access to ONAP applications via ingress or node ports (deprecated - to be removed in future release).
Generation Deliver generation (include common .tpls) and enforcement (via schema) of mechanism for standardized Helm Charts. Transfer This ensures consistency and ease of configuration (ie. ingress controller impl.).
Converting a subset of Helm Charts (standardized) to standardized generation and validation mechanism before transferring them out of the OOM repository and into a subset of the ONAP project teamsteam repositories.
Focus will be on transferring ownership for a handful (approximately 6) of project teams for in this release.
Functionalities
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=oom AND type = story AND fixversion = "Frankfurt Release" ORDER BY priority DESC serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
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 are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
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
...
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 Outgoing Dependencies
API this project is delivering to other projects.
...
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).
| Name | Description | Version | To fill out | To fill out | To fill out|
|---|---|---|---|---|---|
| Kubernetes | Container Orchestrator | 1.15.x | |||
| Helm | Kubernetes Package Manager | 2.14.x |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
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.
| Gaps identified | Impact | |
|---|---|---|
| To fill out | To fill out- | - |
Known Defects and Issues
Please refer to Frankfurt Defect Status
...
Please update any risk on the centralized wiki page - Frankfurt Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
It is not expected to have a detailed project plan.
| Date | Project | Deliverable | ||
|---|---|---|---|---|
| To fill out | To fill out | To fill out- | - | - |
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation
...