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

Table of Contents
outline true

Overview

Scope

What is this release trying to address?

Support Honolulu use cases, Features and Non Functional requirements.

Requirements

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

REQ-342 - E2E Network Slicing requirements for Guilin release

...

see tables below for content related to this 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 OOM.

...

sdc-destribution-client

sdc-tosca

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

...

Honolulu, impacting SDC

1 No Use Case :

No use case impacting SDC planned for this Release

5 Functional Requirements :

5 Functional Requirements :

Requirement EpicTSC PrioritySDC Epic(s) and/or SDC Story(ies)Committed Contributors

Image RemovedREQ-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 RemovedREQ-366 - Containers must crash properly when a failure occurs To Do

RANK #1 - Must HaveCommitted Contributors

China Mobile OK

See discussion in REQ Jira

SDC (S): Lumina, Huawei Orange

stories created and assigned

Requirement Epic	TSC Priority	SDC Epic(s) and/or SDC Story(ies)	SDC : Bell, Amdocs (S) Arch Review OK No story avail yet
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-324 RANK #3 – PTL GO / NO GO columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-400	ETSI Modeling update	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 text ~ETSI AND fixVersion = "Epic Link" = REQ-324 Honolulu Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Ercisson, Orange OK	Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-334	RANK #2 – Continuity	SDC (S) - Ericsson Arch review To Do Stories Created and assigned
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project = SDC AND issuetype in (Epic, Story, Task, bug) AND text ~ETSI AND fixVersion = "Guilin Release"
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
Ericsson support on SDC see Req Jira for details	Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-335	RANK #3 – PTL GO / NO GO	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-335 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-341	RANK #0  – TSC Special GO	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-341 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-353	RANK #0  – TSC Special GO	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-353 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Ericsson, Nokia OK Ericsson contributing to 349 NF

18 Non functionals :

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

serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-458

Continuation of CNF support, presented by Luckasz at SDC weekly

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

458 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

• Contributors : ?

Image RemovedREQ-365 - Containers must have no more than one main process To Do

RANK #1 - Must Have

SDC (P): Nokia, Huawei Arch Review OK Stories Created and assigned

Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status

maximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-365

,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

Contributors : ?

key

Image Removed

REQ-

380 - ONAP container repository (nexus) must not contain upstream docker images To DoRANK #1 - Must Have

446

PNF SW update continuation

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

446 serverId 4733707d-2057-

3a0f-ae5e-4fd8aff50176

• Contributors : AT&T
• Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions

Image RemovedREQ-379 - ONAP projects must use only approved and verified base images for their containers To Do

RANK #1 - Must Have

3a0f-ae5e-4fd8aff50176	SDC (S): Ericsson stories created and assigned
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status

maximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-379

Image RemovedREQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do

RANK #1 - Must Have

,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

• Contributors : AT&T
• Align all containers to Database, Java, Python, Docker, Kubernetes, and Image Versions

key REQ-433

Distribution improvements

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

433 serverId 4733707d-2057-3a0f-ae5e

-4fd8aff50176

• Contributors :Former user (Deleted) others ?

Image RemovedREQ-362 - All containers must run as non-root user To Do

RANK #1 - Must Have

-4fd8aff50176

(S) SDC - Nokia stories created and assigned

Global Requirements/Best Practices :

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

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

RANK #2 – Continuity ,priority,statusproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-362 Image Removed361 - Continue hardcoded passwords removal To DoRANK #1 - Must HaveRANK #1 - Must Havepriority,statusproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-349 RANK #1 - Must HaveFrancis Toth (Deactivated) others ?

• Java 11 - need to update many dependencies, very challenging

Requirement Epic	TSC Status	SDC Epic(s) and/or SDC Story(ies)	Committed Contributors
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee
maximumIssues	20
jqlQuery	,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 Contributors : AT&T key	REQ-	443	Best Practice for New code - approved by TSC	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 443 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : AT&T (Amir if time allows) Remove certificates from containers	Image RemovedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do	all from SDC Ensure to enforce proper crypto when committing new code
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,
maximumIssues	20
jqlQuery	reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors : All (currently at 54.8%)	Image RemovedREQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do	key REQ-439	Best Practice for New code - approved by TSC	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 439 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	Contributors :

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

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

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

key REQ-438

Global Requirement - all code must comply

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

438 serverId

4733707d-2057-3a0f-ae5e-4fd8aff50176

• Contributors : YoppWorks, Amdocs

Agreed as a Stretch goal

Image RemovedREQ-374 - ONAP shall use STDOUT for logs collection To Do

4733707d-2057-3a0f-ae5e-4fd8aff50176	SDC code is compiled with Java11 All code compliant already May need to revisit base image to ensure proper setup
Jira Legacy server System Jira columns key,summary,type,created,updated,

assignee,priority,statusmaximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-374

due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

Contributors : ?

key

Image Removed

REQ-

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

437

Global Requirement - all code must comply

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

437 serverId 4733707d-2057-3a0f

-ae5e-4fd8aff50176

• Contributors : ?

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

-ae5e-4fd8aff50176	SDC code is already using Python 3.6 All code compliant already May need to revisit base image to ensure proper setup
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee

,priority,statusmaximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-364

,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

Contributors : ?

key

Image Removed

REQ-

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

442

Best Practice for New code - approved by TSC

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

442 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

• Contributors : ?

Image RemovedREQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. To Do

No impact on SDC but OOM charts must be compliant Will follow OOM team guidelines and rules

POC - Proof of Concept

assignee,priority,statusproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350 Contributors : ?Image Removed359 - Container rootfs must be mounted readOnly To Do359 Contributors : ?

Jira Legacy server System Jira columns key,summary,type,created,updated,
maximumIssues	20
jqlQuery	due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176	key	REQ-	478	POC - waiting stories/info to be provided	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-	478 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176		Company Engagement OK : Ericsson Arch Review OK Need more info, no stories attached yet

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

Longer term roadmap

SDC aims to position itself as the main design IDE in ONAP. SDC works towards creating a fully model-driven design experience.

...

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

...

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

Architecture

High level architecture diagram

Platform Maturity

Please fill out the centralized wiki page: Guilin Honolulu 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 Outgoing Dependencies

API this project is delivering to other projects.

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

0.

3.

1

9.34.X18

ubuntu-xfce-vnc:1.3.0

...

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.

...

• validate uses cases and pairwise testing of SDC with other components
• enhance CSIT to include more tests (now integrated in SDC main build)

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

• Known Defects and Issues

Please refer to Frankfurt Defect Status  – To be updated when availSDC Release notes when available

• 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 Honolulu Risks – To be updated when avail

• Resources

Fill out the Resources Committed to the Release centralized page.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:sdc

• Release Milestone

The milestones are defined at the Release LevelPlanning: Honolulu 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.

...

• Documentation, Training

Please update the following centralized wiki: Frankfurt Honolulu Documentation – To be updated when avail

...

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.

...