SDC Jakarta R10 Release Planning
- Michael Morris
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 | Jakarta |
Project Lifecycle State | Mature |
Participating Company | Ericsson |
Scope
What is this release trying to address?
Support Jakarta Features, Specs and Global Requirements.
Requirements
Use Cases:
N/A
Features:
N/A
Specs:
Requirement Epic | Status | SDC Epic | Committed Contribututors |
|---|---|---|---|
Ericsson | |||
SDC-3777: SDC Shall Support Application Package onboarding and distributionClosed |
Global Requirements:
Requirement Epic | Status | SDC Epic | Committed Contribututors |
|---|---|---|---|
REQ-1070: LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - JAKARTA RELEASETo Do |
Minimum Viable Product
Deliver all the docker images needed to support sdc functionality and the needed scripts for setting up the DB and 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.
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
Please fill out the centralized wiki page: Jakarta Release Platform Maturity
API Incoming Dependencies
No new incoming API dependencies.
API Outgoing Dependencies
No new incoming API dependencies.
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 |
|---|---|---|
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
-
KNOWN DEFECTS AND ISSUES
Please refer to SDC JIRA bugs
RISKS
See Jakarta 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 Jakarta Release Milestones which SDC complies with.
TEAM INTERNAL MILESTONE
N/A
DOCUMENTATION, TRAINING
See the following centralized wiki: Jakarta 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.