The content of this template is expected to be fill out for M1 Release Planning M2 Milestone.
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Honolulu |
| Project Lifecycle State | Mature |
| Participating Company | Amdocs, AT&T, ZTE, Huawei, Intel, Nokia, Ericsson, Iconectiv, Vodafone, IBM, TechM, Samsung, CMCC |
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 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 :
| Requirement Epic | TSC PriorityStatus | SDC Epic(s) and/or SDC Story(ies) | Committed Contributors | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 342RANK #3 – PTL GO/NO GO
| Waiting presentation from involved parties and/or stories creation |
| ,resolution
| 342
|
5 Functional Requirements :
SDC : Bell, Amdocs (S) Arch Review OK No story avail yet | |||||||||||||||||||||||||||||
| Requirement Epic | TSC Priority | SDC Epic(s) and/or SDC Story(ies) | Committed Contributors | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ETSI Modeling updateRANK #3 – PTL GO / NO GO |
| SDC (S) - Ericsson Arch review To Do Stories Created and assigned Ercisson, Orange OK | ||||||||||||||||||||||||||
| Continuation of CNF support, presented by Luckasz at SDC weeklyRANK #2 – Continuity |
| SDC (P): Nokia, Huawei Arch Review OK Stories Created and assigned Ericsson support on SDC see Req Jira for details | ||||||||||||||||||||||||||
| RANK #3 – PTL GO / NO GO |
| PNF SW update continuation |
| SDC (S): Ericsson stories created and assigned China Mobile OK See discussion in REQ Jira | ||||||||||||||||||||||||
| Distribution improvementsRANK #0 – TSC Special GO |
| SDC (S) : Lumina, Huawei OrangeSDC - Nokia stories created and assigned | ||||||||||||||||||||||||||
| RANK #0 – TSC Special GO |
| Ericsson, Nokia OK Ericsson contributing to 349 NF |
18 Non functionals :
10 - TSC MUST HAVE (please indicate where you plan to contribute)
Global Requirements/Best Practices :
10 - TSC MUST HAVE (please indicate where you plan to contribute)
| Requirement Epic | TSC Status | SDC Epic(s) and/or SDC Story(ies) | Committed Contributors | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Requirement Epic | TSC Priority | SDC Epic(s) and/or SDC Story(ies) | Committed Contributors | ||||||||||||
| RANK #1 - Must Have |
|
Mentee SDC (Amir) supported by AT&T mentor | ||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
|
| |||||||||||||
| RANK #1 - Must Have |
| ,priority,status||||||||||||||
| maximumIssues | 20 | jqlQuery | project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-362
|
| 361 - Continue hardcoded passwords removal To Do
| Best Practice for New code - approved by TSC | RANK #1 - Must Have
|
|
| ||||||
 REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do | RANK #1 - Must Have |
| ,priority,status|||||||||||||
| maximumIssues | 20 | jqlQuery | project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-349
|
| RANK #1 - Must Have |
| Best Practice for New code - approved by TSC |
|
| Francis Toth others ?
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
|
|
|
- Not applicable to SDC, as SDC is already using ONAP user on shared Cassandra DB
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
| Global Requirement - all code must comply |
REQ-340 - ONAP to support Multi - tenancy To Do
|
|
- Contributors : YoppWorks, Amdocs
Agreed as a Stretch goal
REQ-374 - ONAP shall use STDOUT for logs collection To Do
|
| |||||
|
|
|
|
| Global Requirement - all code must comply |
|
|
- Contributors : ?
REQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do
|
| |||||
|
|
|
|
| Best Practice for New code - approved by TSC |
|
|
- Contributors : ?
REQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. To DoNo impact on SDC but OOM charts must be compliant Will follow OOM team guidelines and rules |
POC - Proof of Concept
| assignee,priority,status||||||||
| maximumIssues | 20 | jqlQuery | project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350
| Contributors : ?
|
| 359 - Container rootfs must be mounted readOnly To Do
| POC - waiting stories/info to be provided |
| 359
| Contributors : ?
|
|---|
SDC Backlog Overview - Not committed for the release (except for stories that have been captured in the above table), best effort
Jira server ONAP JIRA columns key,summary,type,updated,assignee,priority,status maximumIssues 20 jqlQuery project = SDC AND issuetype in (Epic, Story, Task, bug) AND fixVersion = "Guilin Honolulu Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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.
...
| Deliverable Name | Deliverable Description |
|---|---|
| SDC Docker Images | To fill outContainers running SDC |
| SDC TOSCA | Tosca library |
| SDC distribution client | Distribution client runtime for other apps to use |
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.
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| Portal | user management APIs | api for user management | delivered | exposed by portal sdk |
| Destribution Distribution client | apis for retriving artifacts from catalog | download artifacts | delivered | exposed by sdc part of external apis. |
API Outgoing Dependencies
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| dmaap | using Cambria client | api for pushing and retrieving notifications | delivered | sdk |
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 | 10.0 3.0 1 |
| Jetty | Open-source application server | |
| Ubuntu | Open-source software operating system | 1620.0.4-LTS |
| vnc | vnc server used for ui testing | |
...
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.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
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.
...
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
Documentation, Training
Please update the following centralized wiki: Frankfurt Honolulu Documentation – To be updated when avail
...
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
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.
...