Overview
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 | 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 |
Support Guilin use cases, Features and Non Functional requirements.
Explained in detail in the below sections.
Deliver all the need dockers and DB needed to support SO core functionality and the needed scripts for deploying it in OOM.
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.
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.
Hence, Please confirm the contributions in SO.
1. the resource commitment for this requirement for Guilin release
2. the non-functional requirement that would be contributed by them.
Thanks in advance.
| 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. ttps://jira.onap.org/browse/REQ-323 - Wipro |
| REQ-342 | E2E Network Slicing requirements for Guilin release | Swaminathan S | 3 |
| CMCC, Wipro, Huawei Requirement is presented in the 5G slicing weekly meeting and is accepted. Need resource commitment for the non-functional requirement. ttps://jira.onap.org/browse/REQ-358 - Wipro 374 - Tech M 349 - Tech M |
| REQ-325 | MDONS Extension in Guilin Release | Xin Miao | 2 |
| Fujitsu Need clarifications on the new scope. We will have a meeting scheduled next week. 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 reviewed in the SO weekly and is accepted. commitment on the Non functional requirement is required. REQ-364 - Orange |
| 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 | contributor Wipro | |
| RANK #1 - Must Have | Need to check for each of the POD SO seems to be ok - TBD on event basis (OOM and SO) contributor | ||
| RANK #1 - Must Have | OK for SO | ||
| RANK #1 - Must Have | Huawei Seems OK for SO | ||
| RANK #1 - Must Have | Java 11 upgrade is the pending item at the moment for SO. onap/integration-java11:7.0.0 image In nexus to be used. License compliance - to be sure all the containers Contributors : Nokia : SO : Java part (REQ-351) TBC, Fujitsu. Xin Miao so/libs: Nokia (TBC) Orange - Docker part | ||
| RANK #1 - Must Have | NA | ||
| RANK #1 - Must Have | Wrapping the dockers on the deployment scripts (Oom based) OK Contributors : Orange Sylvain Desbureaux , Ericsson Byung-Woo Jun and Huawei Mukesh Paliwal . New pods should be taken care - K8s Adapter, SO-NFVO. | |
| RANK #1 - Must Have | Certificate and ingress (Oom based) passwords and certificates to be cleaned in the oom. Certificate : Https solution will be done through Ingress. (REQ-364) - Orange Sylvain Desbureaux Password : Att (30225 Ramesh Parthasarathy , Ericsson (30227 Byung-Woo Jun Orange, Att, Ericsson and Huawei. | ||
 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 | onap/integration-java11:7.0.0 In nexus Contributors : SO - Att (base work), Fujitsu (Xin Miao ) So/libs - Damian Nowak to get back.. |
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
| RANK #2 – Continuity | This should be OK, Need to check it further with Security (Oom based)
|
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
|
| Multi Tenancy
|
| Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM).
| |
| Gating and daily deployment impact... (Deployment scripts)
| |
|
| |
| REQ-360 - Application config should be fully prepared before starting the application container To Do |
| spring boot based application should be ok, will need to re-check with Kryzstof (Oom based)
|
|
| CII badging improvement
|
| Springboot startup should take care of this, need to check with Kryzstof. (Oom based)
|
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 |
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.
Please fill out the centralized wiki page: Guilin Release Platform Maturity
| Milestone | Description | Date | Comments |
|---|---|---|---|
| M2/M3 | Functionality Freeze / API Freeze | ||
| July 3, 2020 | Last day to submit Guilin swagger / Yang changes to Gerrit | |
| Aug 3, 2020 | Release manager reviews worksheets to assess readiness for M2/M3 milestone | |
| Aug 6, 2020 | ||
| M4 | Code Freeze | ||
| Sept 4, 2020 | Last day to submit Frankfurt code changes to Gerrit | |
| Sept 7, 2020 | Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:
| |
| Sept 7, 2020 | ||
| Sept 10, 2020 | ||
| RC0 | Release Candidate 0 | ||
| Sept 25, 2020 | Last date to submit code fixes for release candidate 0 | |
| Sept 28, 2020 | ||
| Sept 28, 2020 | ||
| Oct 1, 2020 | ||
| RC1 | Release Candidate 1 | ||
| Oct 9, 2020 | Last date to submit code fixes for Frankfurt release candidate 1 | |
| Oct 12, 2020 | ||
| Oct 12, 2020 | ||
| Oct 15, 2020 | ||
| RC2 | Release Candidate 2 | ||
| Oct 23, 2020 | Last date to submit code fixes for final Frankfurt release (RC2) | |
| Oct 26, 2020 | ||
| Oct 26, 2020 | ||
| Oct 29, 2020 | ||
| Release Sign-Off | Final TSC Sign-Off | May 7, 2020 | Frankfurt Release Sign-Off |
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 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 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 SO base images.
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.
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 |
Please refer to Frankfurt Defect Status – To be updated when avail
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
Fill out the Resources Committed to the Release centralized page.
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
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 |
Please update the following centralized wiki: Frankfurt Documentation – To be updated when avail
That includes
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
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.
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.