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 SO

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

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

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

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

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

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

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Fujitsu

Need clarifications on the new scope.

We will have a meeting scheduled next week.

Resource commitment for the non-functional requirement

REQ-351

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

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Huawei

Requirement is presented in the CNF task force and is accepted

Stories to be updated for the requirement.

Non functional requirement Identified:

REQ-362

REQ-324 - Support xNF Software Upgrade in association to schema updates IN PROGRESS

x

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Ericsson, Orange

This is already reviewed in the SO weekly and is accepted.

commitment on the Non functional requirement is required.

REQ-364 - Orange

REQ-318 - PNF Plug & Play in R7 TO DO

x

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Nokia

SO-2785 - Getting issue details... STATUS

Scope and Resource commitment and the non functional requirement need clarifications.

~~SO-2046 - TBC~~

Lukasz Muszkieta damian.nowak

REQ-341 - ONAP CNF orchestration - Enhancements TO DO

x

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Lumina, Huawei, Att

The requirement is presented in the CNF task force meeting and is accepted.

Non Functional requirement,

REQ-361

REQ-343 - ONAP SO support Dynamic Orchestration IN PROGRESS

x

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Huawei, (Nokia - initial support in the design)

The requirement is presented in the SO weekly meeting and is accepted.

Non-Functional Requirement.

REQ-362

REQ-334 - ETSI-Alignment for Guilin IN PROGRESS

x

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Ericsson, Verizon

The requirement is presented in the ETSI taskforce meeting and is accepted.

Non-Functional Requirement:

REQ-362 - Getting issue details... STATUS

REQ-361 - Getting issue details... STATUS

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
REQ-323 - Each project will update the vulnerable direct dependencies in their code base To Do	RANK #1 - Must Have	SO-2915 - Getting issue details... STATUS	contributor Reshmasree c Wipro
REQ-366 - Containers must crash properly when a failure occurs To Do	RANK #1 - Must Have	SO-3037 - Getting issue details... STATUS	Need to check for each of the POD SO seems to be ok - TBD on event basis (OOM and SO) contributor Seshu Kumar Mudiganti
REQ-365 - Containers must have no more than one main process To Do	RANK #1 - Must Have	SO-3039 - Getting issue details... STATUS	OK for SO
REQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do	RANK #1 - Must Have	SO-3040 - Getting issue details... STATUS	License compliance Huawei Seems OK for SO
REQ-379 - ONAP projects must use only approved and verified base images for their containers To Do	RANK #1 - Must Have	SO-3041 - Getting issue details... STATUS	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 (Unlicensed) so/libs: Nokia (TBC) Orange - Docker part
REQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do	RANK #1 - Must Have		NA
REQ-362 - All containers must run as non-root user To Do	RANK #1 - Must Have	SO-3042 - Getting issue details... STATUS	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.
REQ-361 - Continue hardcoded passwords removal To Do	RANK #1 - Must Have	SO-3043 - Getting issue details... STATUS	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	SO-3038 - Getting issue details... STATUS	OK 63% and 66% Tech Mahindra to support on need basis. Milind Jalwadi (Unlicensed)
REQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do	RANK #1 - Must Have	SO-2046 - Getting issue details... STATUS	onap/integration-java11:7.0.0 In nexus Contributors : SO - Att (base work), Fujitsu (Xin Miao (Unlicensed)) So/libs - damian.nowak to get back..

1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)

REQ-358 - No root (superuser) access to database from application container To Do

RANK #2 – Continuity

SO-3044 - Getting issue details... STATUS

This should be OK, Need to check it further with Security

(Oom based)

Contributors : Wipro
Reshmasree c

7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)

REQ-340 - ONAP to support Multi - tenancy To Do

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

Multi Tenancy

Contributors : Bell, Yoppworks
Olivier Phenix

REQ-374 - ONAP shall use STDOUT for logs collection To Do

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

Pattern of the logging to be standardized.

Append the log4j with the appender ( on OOM).

Contributors : Tech Mahindra
Milind Jalwadi (Unlicensed)

SO-3077 - Getting issue details... STATUS

REQ-369 - Replace nfs share with storage class as a default deployment option To Do

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

Gating and daily deployment impact...

(Deployment scripts)

Contributors : ?

REQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

30227 and 20225 should be

Robot Pod Refactoring

(Oom based)

Contributors : Orange

SO-3078 - Getting issue details... STATUS

REQ-360 - Application config should be fully prepared before starting the application container To Do

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

spring boot based application should be ok, will need to re-check with Kryzstof

(Oom based)

Contributors : ?

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

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

CII badging improvement

Contributors : ?
Seshu Kumar Mudiganti
SO-3079 - Getting issue details... STATUS

REQ-359 - Container rootfs must be mounted readOnly To Do

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

Springboot startup should take care of this, need to check with Kryzstof.

(Oom based)

Contributors : ?

SO Backlog Overview - Not committed for the release (except for stories that have been captured in the above table), best effort

key	summary	type	updated	assignee	priority	status

Loading...

Refresh

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/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

Team Internal Milestone (Tentative)

Milestone	Description	Date	Comments
M2/M3	Functionality Freeze / API Freeze
	Final API definitions (swagger, Yang) due	July 3, 2020	Last day to submit Guilin swagger / Yang changes to Gerrit
	M2/M3 Jiras ready for review	Aug 3, 2020	Release manager reviews worksheets to assess readiness for M2/M3 milestone
	M2/M3 Milestone	Aug 6, 2020
M4	Code Freeze
	Code due for Frankfurt user stories	Sept 4, 2020	Last day to submit Frankfurt code changes to Gerrit
	M4 worksheets ready for review	Sept 7, 2020	Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks: All repos must have >= 55% code (line) coverage in Sonar No failed Jenkins jobs All CSIT tests pass Healthchecks pass
	M4 release builds available	Sept 7, 2020
	M4 Milestone	Sept 10, 2020
RC0	Release Candidate 0
	Code due for RC0 fixes	Sept 25, 2020	Last date to submit code fixes for release candidate 0
	RC0 release artifacts available	Sept 28, 2020
	RC0 Jiras ready for review	Sept 28, 2020
	TSC RC0 approval vote	Oct 1, 2020
RC1	Release Candidate 1
	Code due for RC1 fixes	Oct 9, 2020	Last date to submit code fixes for Frankfurt release candidate 1
	RC1 release artifacts available	Oct 12, 2020
	RC1 Jiras ready for review	Oct 12, 2020
	TSC RC1	Oct 15, 2020
RC2	Release Candidate 2
	Code due for final Frankfurt fixes	Oct 23, 2020	Last date to submit code fixes for final Frankfurt release (RC2)
	RC2 release artifacts available	Oct 26, 2020
	RC2 Jiras ready for review	Oct 26, 2020
	TSC RC2	Oct 29, 2020
Release Sign-Off	Final TSC Sign-Off	May 7, 2020	Frankfurt Release Sign-Off

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

Browser not supported