The content of this template is expected to be fill out for M1 Release Planning Milestone.
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Honolulu |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Amdocs, Bell Canada, CMCC, DT, Ericsson, Fujitsu, Huawei, Intel, Lumina Networks, Nokia, Orange, Samsung, Tech Mahindra, Verizon |
Scope
What is this release trying to address?
Improve the platform maturity of SO project and cleanup some of the key technical backlogs.
Requirements
Explained in detail in the below sections.
Minimum Viable Product
Deliver all the needed docker images and DB to support SO core functionality and the needed scripts for deploying it in OOM.
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.
Key Requirements Epics for Honoloulu, impacting SO
SO-3473 - Getting issue details... STATUS
Use Cases :
Greetings, As per the new process set in place, we need to have the TSC must have requirements also to be completed for us to qualify for the release.
Functional Requirements :
| SO Epic(s) / Story(ies) | M1 Scope and clarification |
SO-3493 - Getting issue details... STATUS | Java 11 and Python 3 upgrade of all the SO components, trace elements scanned by Security subcommittee needs to be checked trace elements scanned by Security subcommittee needs to be checked |
SO Backlog Overview - Not committed for the release (except for stories that have been captured in the above table), best effort
Longer term roadmap
SO aims to highest level of orchestration which is model driven and generic enough to both traditional and Cloud Native scenarios alike.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| SO Docker Images | Docker Images, details can be found below |
| SO libs | libs |
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.
- onap/so/api-handler-infra
- onap/so/bpmn-infra
- onap/so/catalog-db-adapter
- onap/so/openstack-adapter
- onap/so/request-db-adapter
- onap/so/sdc-controller
- onap/so/sdnc-adapter
- onap/so/so-monitoring
- onap/so/vfc-adapter
- onap/so/sol003-adapter
- onap/so/nssmf-adapter
- onap/so/mso-cnf-adapter
- onap/so/etsi-nfvo
Architecture
High level architecture diagram
Refactoring modules
Platform Maturity
Please fill out the centralized wiki page: Honolulu Release Platform Maturity
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, Elastic Search, Crystal Reports, ...).
| Name | Description |
|---|---|
| Camunda | Dependency on the camunda engine for processing the workflows |
| MariaDb | Used for all the dependencies on the persistency. |
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.
- validate uses cases and pairwise testing of SO with other components
- enhance CSIT to include more tests
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 release notes of Guilin release – To be updated when avail
Please update any risk on the centralized wiki page - Honolulu Risks
Resources
Please see the INFO.yaml files associated with each repo as the authoritative sources of information - https://gerrit.onap.org/r/admin/repos/q/filter:so
Release Milestone
The milestones are defined at the Release Planning: Honolulu and all the supporting project agreed to comply with these dates.
Team Internal Milestone
Milestone | Description | Date | Comments |
|---|---|---|---|
| M2 | Spec Freeze |
| |
| M3 | Feature Freeze | ||
|
| Last day to submit Honolulu code changes to Gerrit | |
|
|
| |
|
| ||
|
| ||
| | ||
| RC0 | Release Candidate 0 | ||
|
| Last date to submit code fixes for Honolulu RC0 | |
|
| ||
|
| ||
| | ||
| RC1 | Release Candidate 1 | ||
|
| Last date to submit code fixes for Honolulu RC1 | |
|
| ||
|
| ||
|
| ||
| RC2 | Release Candidate 2 | ||
|
| Last date to submit code fixes for final Honolulu release (RC2) | |
|
| ||
|
| ||
| | ||
| Release Sign-Off | Final TSC Sign-Off | | Honolulu Release Sign-Off |
Documentation, Training
Please update the following centralized wiki: Honolulu 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
- ...
Note
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.