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 | Guilin |
| 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?
Support Guilin use cases, Features and Non Functional requirements.
Requirements
Explained in detail in the below sections.
Minimum Viable Product
Deliver all the need dockers and DB needed 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.
Requirements Epics for Guilin, impacting SDC
Use Cases :
| Key | Summary | Assignee | Tsc Priority | SO Epic(s) / Story(ies) | M1 Scope Clarifications |
|---|---|---|---|---|---|
| REQ-347 | CCVPN-Transport Slicing for Guilin Release | Henry Yu | 2 |
| Huawei, CMCC, Wipro Scope and Resource commitment for the non-functional requirement is needed. |
| REQ-342 | E2E Network Slicing requirements for Guilin release | Swaminathan S | 3 |
| CMCC, Wipro, Huawei Requirement is presented in the 5G slicing weekly meeting, need resource commitment for the non-functional requirement. |
| REQ-325 | MDONS Extension in Guilin Release | Xin Miao | 2 |
| Fujitsu Need clarifications on the new scope, Resource commitment for the non-functional requirement |
Functional Requirements :
Requirement | SO | SO Epic(s) / Story(ies) | M1 Scope and clarification |
| REQ-339 - Container Network Function Test Platform (CNTP): OVP 2.0 support and Enable Network Service testing TO DO | x |
| Huawei Requirement is presented in the CNF task force and is accepted Stories to be updated for the requirement. Non functional requirement Identified: |
REQ-324 - Support xNF Software Upgrade in association to schema updates IN PROGRESS | x |
| Ericsson, Orange This is already review in the SO weekly and is accepted. commitment on the Non functional requirement is required. |
| x |
| Nokia? Scope and Resource commitment and the non functional requirement need clarifications. | |
| x |
| Lumina, Huawei, Att The requirement is presented in the CNF task force meeting and is accepted. Non Functional requirement, | |
| x |
| Huawei, (Nokia - initial support in the design) The requirement is presented in the SO weekly meeting and is accepted. Non-Functional Requirement. | |
| x |
| Ericsson, Verizon The requirement is presented in the ETSI taskforce meeting and is accepted. Non functional requirement?? |
18 Non functionals :
10 - TSC MUST HAVE (please indicate where you plan to contribute)
| Requirement Epic | TSC Priority | SO Epic(s) / Story(ies) | Committed Contributors |
|---|---|---|---|
| RANK #1 - Must Have |
| |
| RANK #1 - Must Have |
| ||
| RANK #1 - Must Have |
| ||
| RANK #1 - Must Have |
| ||
| RANK #1 - Must Have |
| ||
| RANK #1 - Must Have |
| ||
| RANK #1 - Must Have |
| ||
| RANK #1 - Must Have |
| ||
 REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do | RANK #1 - Must Have |
| |
| RANK #1 - Must Have |
|
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
| RANK #2 – Continuity |
|
|
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
|
| ||
|
| ||
|
| ||
|
| ||
| REQ-360 - Application config should be fully prepared before starting the application container To Do |
|
| |
| REQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. To Do |
|
| |
|
|
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 | To fill out |
| SO 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/sol02-adapter
- onap/so/nssmf-adapter
- onap/so/appc-orchestrator
- onap/so/k8s-adapter
Architecture
High level architecture diagram
Platform Maturity
Please fill out the centralized wiki page: Guilin 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.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
API Outgoing Dependencies
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
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, ...).
| Name | Description | Version |
|---|---|---|
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Base docker images with approved set of License to be used to construct SDC base images.
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 SDC 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 Frankfurt Defect Status – To be updated when avail
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 – To be updated when avail
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.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation – To be updated when avail
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.