The content of this template is expected to be fill out for M1 Release Planning Milestone.

...

Scope

What is this release trying to address?

Support Frankfurt Guilin use cases, Sonar and security improvementsFeatures and Non Functional requirements.

Requirements

Describe the use case this release is targeted for (better if reference to customer requirements).

PNG WF upgrade

Third-party Operational Domain Manager

Multi-domain optical networks

(5G) FM/PMREQ-342 - E2E Network Slicing requirements for Guilin release

Minimum Viable Product

SDC:

deliver all the need dockers and DB needed to support sdc functionality and the needed scripts for deploying it in HEAT heat and in OOM.

WORKFLOW:

deliver all the need dockers needed to support workflow designer functionality and the needed scripts for deploying it in HEAT heat and in OOM.

SDC SDK's:

sdc-destribution-client

...

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

1 Use Case :

5 Functional Requirements :

...

18 Non functionals :

10 - TSC MUST HAVE (please indicate where you plan to contribute)

Requirement Epic	TSC Priority	SDC Epic(s) and/or SDC Story(ies)	Committed Contributors
Image AddedREQ-323 - Each project will update the vulnerable direct dependencies in their code base To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-323 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : AT&T Mentee SDC (Amir) supported by AT&T mentor  https://jenkins.onap.org/view/CLM/job/sdc-catalog-maven-clm-master/      https://jenkins.onap.org/view/CLM/job/sdc-onboarding-maven-clm-master/
Image AddedREQ-366 - Containers must crash properly when a failure occurs To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-366 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?
Image AddedREQ-365 - Containers must have no more than one main process To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-365 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?
Image AddedREQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-380 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : AT&T Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions
Image AddedREQ-379 - ONAP projects must use only approved and verified base images for their containers To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-379 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : AT&T Align all containers to Database, Java, Python, Docker, Kubernetes, and

...

Image Versions
Image AddedREQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-373 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors :Former user (Deleted) others ?
Image AddedREQ-362 - All containers must run as non-root user To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-362 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : AT&T
Image AddedREQ-361 - Continue hardcoded passwords removal To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-361 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : AT&T (Amir if time allows) Remove certificates from containers
Image AddedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-349 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : All (currently at 54.8%)
Image AddedREQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do	RANK #1 - Must Have	Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-351 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors :Francis Toth (Deactivated) others ? Java 11 - need to update many dependencies, very challenging

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

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

RANK #2 – Continuity

Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-358 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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

Image AddedREQ-340 - ONAP to support Multi - tenancy To Do

Jira Legacy server System Jira columns key,summary,type,

...

updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-340 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : YoppWorks, Amdocs Agreed as a Stretch goal
Image AddedREQ-374 - ONAP shall use STDOUT for logs collection To Do		Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-374 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?
Image AddedREQ-369 - Replace nfs share with storage class as a default deployment option To Do		Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-369 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?
Image AddedREQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do		Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-364 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?
Image AddedREQ-360 - Application config should be fully prepared before starting the application container To Do		Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-360 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?
Image AddedREQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and

...

documenting it in their CII Badging site. To Do		Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?
Image AddedREQ-359 - Container rootfs must be mounted readOnly To Do		Jira Legacy server System Jira columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-359 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : ?

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

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

• Jtosca
• SDC Tosca
• SDC Distribution Client
• SDC base docker
  
• SDC titan cassandra
  SDC workflow designer 

Architecture

...

Please fill out the centralized wiki page: Frankfurt 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.

...

9.3.X

ubuntu-xfce-vnc:1.3.0

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

...

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

...

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

...