Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
outlinetrue

Overview

Project NameEnter the name of the project
Target Release NameGuilin
Project Lifecycle StateIncubation
Participating Company 
Amdocs,
AT&T,
ZTE
Amdocs,
Huawei
Bell Canada,
Intel
CMCC,
Nokia
DT, Ericsson, Fujitsu, Huawei,
Iconectiv
Intel,
Vodafone
Lumina Networks,
IBM
Nokia,
TechM
Orange, Samsung, Tech Mahindra, Verizon

Scope

What is this release trying to address?

Support Guilin 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

Explained in detail in the below sections.

Minimum Viable Product

SDC:

deliver Deliver all the need dockers and DB needed to support sdc SO core functionality and the needed scripts for deploying it in OOM.

WORKFLOW:

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

SDC SDK's:

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 Guilin, impacting

...

1 Use Case :

...

SO

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority

...

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-342

...

,status,resolution
maximumIssues20
jqlQueryproject =

...

SO AND issuetype

...

= Epic AND fixVersion = "Guilin Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

 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.


KeySummaryAssigneeTsc PrioritySO

5 Functional Requirements :

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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-324

RANK #3 – PTL GO / NO GO
M1 Scope Clarifications
REQ-347CCVPN-Transport Slicing for Guilin ReleaseHenry Yu2

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

324

347
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Ercisson, Orange OK

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-334

Huawei, CMCC, Wipro

Scope and Resource commitment for the non-functional requirement is needed.


ttps://jira.onap.org/browse/REQ-323 - Wipro


REQ-342E2E Network Slicing requirements for Guilin releaseSwaminathan S3
RANK #2 – Continuity 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND

text ~ETSI AND fixVersion = "Guilin Release"

("Epic Link" = REQ-342 OR "Epic Name" ~ Slicing ) AND fixVersion = "Guilin Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Ericsson ?

Waiting Component commit

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-335

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-325MDONS Extension in Guilin ReleaseXin Miao2
RANK #3 – PTL GO / NO GO

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

335

325
serverId425b2b0a-557c-3c0c-b515-579789cceedb

China Mobile OK

See discussion in REQ Jira

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 :

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-341

RANK #0  – TSC Special GO JiraserverONAP JIRAcolumns

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 DOx

Jira
serverONAP JIRA
columns

key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

341

339
serverId425b2b0a-557c-3c0c-b515-579789cceedb

SDC (S): Lumina,

Huawei

OK

Waiting assignment on SDC story

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-353

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
RANK #0  – TSC Special GO

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

353

324
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Ericsson,

Nokia OK

18 Non functionals :

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

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
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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

323

318
serverId425b2b0a-557c-3c0c-b515-579789cceedb

  • Contributors : AT&T

Mentee SDC (Amir) supported by AT&T mentor

Nokia

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-2785

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

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

366

341
serverId425b2b0a-557c-3c0c-b515-579789cceedb

  • Contributors : ?
Image RemovedREQ-365 - Containers must have no more than one main process To Do

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
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

365

343
serverId425b2b0a-557c-3c0c-b515-579789cceedb

  • Contributors : ?
Image RemovedREQ-380 - ONAP container repository (nexus) must not contain upstream docker images To Do

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
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "

Epic Link

labels" =

REQ

ETSI-

380

Alignment
serverId425b2b0a-557c-3c0c-b515-579789cceedb

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

Ericsson, Verizon

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

Non-Functional Requirement:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-362

RANK #1 - Must Have

Jira
serverONAP JIRA

columnskey,summary,type,updated,assignee,priority,statusmaximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-379 serverId425b2b0a-557c-3c0c-b515-579789cceedb

serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-361


18 Non functionals :

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

Image RemovedREQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8)
Requirement EpicTSC PrioritySO Epic(s) / 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
serverONAP JIRA

columnskey,summary,type,updated,assignee,priority,statusmaximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link"

serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-2915

contributor

Reshmasree c

Wipro

Image AddedREQ-366 - Containers must crash properly when a failure occurs To Do
RANK #1 - Must Have

Jira
serverONAP JIRA

= REQ-373

serverId425b2b0a-557c-3c0c-b515-579789cceedb

Contributors :user-7f92d others ?

keySO-3037

Need to check for each of the POD

SO seems to be ok - TBD on event basis

(OOM and SO)

contributor

Seshu Kumar Mudiganti

362
365 -
All containers must run as non-root user serverId
Containers must have no more than one main process To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

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

serverId

425b2b0a-557c-3c0c-b515-579789cceedb

Contributors : AT&T

keySO-3039

OK for SO
361 - Continue hardcoded passwords removal
380 - ONAP container repository (nexus) must not contain upstream docker images To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status

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

,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb

  • Contributors : AT&T (Amir if time allows)
Remove certificates from containers

keySO-3040

License compliance

Huawei

Seems OK for SO

349
379 -
Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage
ONAP projects must use only approved and verified base images for their containers To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status

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

,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb

  • Contributors : All (currently at 54.8%)
Image RemovedREQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do
RANK #1 - Must Have

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-351
serverId425b2b0a-557c-3c0c-b515-579789cceedb

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

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

keySO-3041

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

Image AddedREQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8) To Do
RANK #1 - Must Have


NA

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

RANK #1 - Must Have
Image RemovedREQ-358 - No root (superuser) access to database from application container To Do
RANK #2 – Continuity 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status

maximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-358 serverId425b2b0a-557c-3c0c-b515-579789cceedb
  • Contributors : ?

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

,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3042

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.

Image AddedREQ-361 - Continue hardcoded passwords removal To Do
RANK #1 - Must Have
Image RemovedREQ-340 - ONAP to support Multi - tenancy To Do

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status

maximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-340 serverId425b2b0a-557c-3c0c-b515-579789cceedb

,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3043

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.

Image AddedREQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do
RANK #1 - Must Have
  • Contributors : ?
Image RemovedREQ-374 - ONAP shall use STDOUT for logs collection To Do

Jira
serverONAP JIRA

columnskey,summary,type,updated,assignee,priority,statusmaximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-374 serverId425b2b0a-557c-3c0c-b515-579789cceedb
  • Contributors : ?

serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3038

OK

63% and 66%

Tech Mahindra to support on need basis.  Milind Jalwadi

Image AddedREQ-351 - ONAP must complete update of the java language (from v8 -> v11) To Do
RANK #1 - Must Have
Image RemovedREQ-369 - Replace nfs share with storage class as a default deployment option To Do

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-2046

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)

Image AddedREQ-358 - No root (superuser) access to database from application container To Do
RANK #2 – Continuity 
columnskey,summary,type,updated,assignee,priority,statusmaximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-369 serverId425b2b0a-557c-3c0c-b515-579789cceedb
  • Contributors : ?
Image RemovedREQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

maximumIssues20jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-364 serverId425b2b0a-557c-3c0c-

serverId425b2b0a-557c-3c0c-b515-579789cceedb

  • Contributors : ?
Image RemovedREQ-360 - Application config should be fully prepared before starting the application container To Do
Jiraserver

keySO-3044

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)

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

360

340
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Multi Tenancy

  • Contributors :
?
350
374 -
Each
ONAP
project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site.
shall use STDOUT for logs collection To Do

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

350

374
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Pattern of the logging to be standardized.

Append the log4j with the appender ( on OOM).

  • Contributors :
?
Image RemovedREQ-359 - Container rootfs must be mounted readOnly To Do

Jira
serverONAP JIRA

columnskey

serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3077

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject =

SDC

SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-

359

369
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Gating and daily deployment impact...

(Deployment scripts)

  • Contributors : ?

...

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject =

...

SO AND issuetype in (Epic, Story, Task, bug) AND

...

"

...

Epic Link" = REQ-364
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

30227 and 20225 should be

Robot Pod Refactoring

(Oom based)

  • Contributors : Orange

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3078

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-360
serverId425b2b0a-557c-3c0c-b515-579789cceedb

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

(Oom based)

  • 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
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350
serverId425b2b0a-557c-3c0c-b515-579789cceedb

CII badging improvement

  • Contributors : ?
  • Seshu Kumar Mudiganti
  • Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keySO-3079
Image AddedREQ-359 - Container rootfs must be mounted readOnly To Do

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-359
serverId425b2b0a-557c-3c0c-b515-579789cceedb

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

Jira
serverONAP JIRA
columnskey,summary,type,updated,assignee,priority,status
maximumIssues20
jqlQueryproject = SO AND issuetype in (Epic, Story, Task, bug) AND fixVersion = "Guilin Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

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 NameDeliverable Description
SO Docker ImagesDocker Images, details  can be found below
SO libslibs


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

Image Added

Platform Maturity

Please fill out the centralized wiki page: Guilin Release Platform Maturity


Team Internal Milestone (Tentative)

MilestoneDescription DateComments
M2/M3Functionality Freeze / API Freeze


  • Final API definitions (swagger, Yang) due
July 3, 2020Last day to submit Guilin swagger / Yang changes to Gerrit

  • M2/M3 Jiras ready for review
Aug 3, 2020Release manager reviews worksheets to assess readiness for M2/M3 milestone

  • M2/M3 Milestone
Aug 6, 2020


M4Code Freeze


  • Code due for Frankfurt user stories
Sept 4, 2020Last 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


RC0Release Candidate 0


  • Code due for RC0 fixes
Sept 25, 2020Last 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


RC1Release Candidate 1


  • Code due for RC1 fixes
Oct 9, 2020Last 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


RC2Release Candidate 2


  • Code due for final Frankfurt fixes
Oct 23, 2020Last 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-OffFinal TSC Sign-OffMay 7, 2020
Frankfurt Release Sign-Off

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.

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

...

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.

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

Architecture

High level architecture diagram

Image Removed

Platform Maturity

...


  • API Incoming Dependencies

...

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
Portaluser management APIsapi for user managementdeliveredexposed by portal sdkDestribution clientapis for retriving artifacts from catalogdownload artifactsdeliveredexposed by sdc part of external apis.










  • API Outgoing Dependencies

API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger
)dmaapusing Cambria clientapi for pushing and retrieving notificationsdeliveredsdk
)





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

...

Open-source distributed storage system

...

.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

NameDescriptionVersion
0JettyOpen-source application server
9.3.X
UbuntuOpen-source software operating system16.0.4-LTSvncvnc server used for ui testingubuntu-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 SO base images.


  • Testing and Integration Plans

...

  • validate uses cases and pairwise testing of SDC with SO with other components
  • enhance CSIT to include more tests

...

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 identifiedImpact
To fill outTo fill out
  • Known Defects and Issues

Please refer to Frankfurt Defect Status  – To be updated when avail

...

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

...

It is not expected to have a detailed project plan.

DateProjectDeliverable
To fill outTo fill outTo fill out
  • Documentation, Training

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

...