Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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


Overview

Project NameEnter the name of the project
Target Release NameJakarta
Project Lifecycle StateMature
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 EpicStatusSDC EpicCommitted Contribututors

REQ-1044 - Getting issue details... STATUS



Ericsson

REQ-993 - Getting issue details... STATUS


SDC-3777 - Getting issue details... STATUS


Global Requirements:

Requirement EpicStatusSDC EpicCommitted Contribututors

REQ-1070 - Getting issue details... STATUS




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

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Stories

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh


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 NameDeliverable Description
SDC Docker ImagesDocker images for running SDC
SDC ToscaTosca library
SDC Distribution ClientLibrary 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, ...).

NameDescriptionVersion
Cassandra

Open-source distributed storage system

3.1
DockerVM container18 and above
JanusGraphOpen-source, distributed graph database
0.3.1
JettyOpen-source application server
9.4.18
UbuntuOpen-source software operating system20.0.4-LTS
vncvnc 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.

  • No labels