SDC R9 Release Planning
- Michael Morris
- 1 Overview
- 2 Scope
- 2.1 What is this release trying to address?
- 2.2 Requirements
- 2.2.1 Use Cases:
- 2.2.2 Features:
- 2.2.3 Specs:
- 2.2.4 Global Requirements:
- 2.2.5 POCs:
- 2.3 Minimum Viable Product
- 2.4 Functionalities
- 2.5 Longer term roadmap
- 3 Release Deliverables
- 4 Sub-Components
- 5 Architecture
- 6 Other Information
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Istanbul |
Project Lifecycle State | Mature |
Participating Company | Ericsson, AT&T, Nokia, Amdocs. |
Scope
What is this release trying to address?
Support Istanbul Features, Specs and Global Requirements.
Requirements
Use Cases:
N/A
Features:
Requirement Epic | Status | SDC Epic | Committed Contribututors |
|---|---|---|---|
Nokia |
Specs:
Requirement Epic | Status | SDC Epic | Committed Contribututors |
|---|---|---|---|
Ericsson |
Global Requirements:
Requirement Epic | Status | SDC Epic | Committed Contribututors |
|---|---|---|---|
REQ-443: CONTINUATION OF BEST PRACTICES BADGING SCORE IMPROVEMENTS FOR SILVER LEVELIn Progress | |||
REQ-439: CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIESIn Progress |
POCs:
N/A
Minimum Viable Product
SDC:
deliver all the docker images needed to support sdc functionality and the needed scripts for setting up the DB and deploying it in OOM.
WORKFLOW:
deliver all the docker images 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.
Epics
Stories
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
|---|---|
SDC Docker Images | Docker images for running SDC |
SDC Tosca | Tosca library |
SDC Distribution Client | Library for other apps to use for SDC distribution handling |
Sub-Components
Jtosca
SDC Tosca
SDC Distribution Client
SDC base docker
SDC workflow designer
Architecture
High level architecture diagram
Platform Maturity
See Istanbul Release Platform Maturity
API Incoming Dependencies
No new incoming API dependencies.
API Outgoing Dependencies
No new outgoing API dependencies.
Third Party Products Dependencies
Name | Description | Version |
|---|---|---|
Cassandra | Open-source distributed storage system | 3.1 |
Docker | VM container | 18 and above |
JanusGraph | Open-source, distributed graph database | 0.3.1 |
Jetty | Open-source application server | 9.4.18 |
Ubuntu | Open-source software operating system | 20.0.4-LTS |
vnc | vnc server used for ui testing | ubuntu-xfce-vnc:1.3.0 |
TESTING AND INTEGRATION PLANS
Unit tests to be added for all new functionality
CSIT tests to be added for new functionality
GAPS
Gaps identified | Impact |
|---|---|
SDC-3510: SDC needs to support CSAR with large-size software/container image filesClosed | Cannot handle csars larger than ~ 8MB |
KNOWN DEFECTS AND ISSUES
Please refer to SDC JIRA
RISKS
See Istanbul Risks
RESOURCES
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
See ONAP Istanbul Release Milestones which SDC complies with.
TEAM INTERNAL MILESTONE
N/A
DOCUMENTATION, TRAINING
See the following centralized wiki: Istanbul Documentation
Other Information
Vendor Neutral
All proprietary trademarks, logos, product names, etc. have been removed.
Free and Open Source Software
See SDC Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.