DRAFT PROPOSAL FOR COMMENTS
...
| Project Name | Enter the name of the project | ||
|---|---|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverDublin | ||
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information | Participating Company | List the company participating in this release. At least 3-4 organizations, including an operator are recommended. |
| Participating Company | Amdocs, AT&T, ZTE, Huawei, Intel, Nokia, Ericsson, Iconectiv, Vodafone, IBM, TechM |
Scope
What is this release trying to address?
...
Describe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
...
SDC:
deliver all the need dockers and DB needed to support sdc functionality and the needed scripts for deploying it in HEAT heat and in OOM.
WORKFLOW:
deliver all the need dockers needed to support workflow designer functionality and the needed scripts for deploying it in HEAT heat and in OOM.
DCAE-DS:
deliver all the need dockers needed to support dcae-ds functionality and the needed scripts for deploying it in HEAT heat and 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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox SDC and issuetype in (epic) AND fixversion="Dublin Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox SDC and issuetype in (story) AND fixversion="Dublin Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspectiveSDC 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...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| SDC Docker Images | To fill outTo fill out |
| SDC TOSCA SDK | JAR file |
| SDC | |
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 titan cassandra
- SDC workflow designer
- DCAE-DS
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 0 | 0 |
| |
| Stability | 1 | 1 |
| |
| Resiliency | 1 | 1 +AAF integration and https support |
| |
| Security | 1 | 1 |
| |
| Scalability | 0 | 0 |
| |
| Manageability | 1 | 1 |
| |
| Usability | 1 | 1 |
|
...
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.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out |
|---|---|---|---|---|---|---|---|---|
| Link toward the detailed API descriptionPortal | user management APIs | api for user management | delivered | exposed by portal sdk | ||||
| Destribution client | apis for retriving artifacts from catalog | download artifacts | delivered | exposed by sdc part of external apis. |
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||||
|---|---|---|---|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API descriptiondmaap | 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 | To fill out | To fill out | To fill out|
|---|---|---|---|---|---|
| Cassandra | Open-source distributed storage system | 2.1.19 | |||
| Docker | VM container | ||||
| ElasticSearch | Search framework | 2.4.6 | |||
| titan | Open-source, distributed graph database | 1.0.0 | |||
| Jetty | Open-source application server | | |||
| Ubuntu | Open-source software operating system | 16.0.4-LTS | |||
| kibana | analytic disply server | | |||
| vnc | vnc server used for ui testing | |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
- validate uses cases and pairwise testing of SDC with other components
- enhance CSIT to include more tests
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 outN/A | N/A |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...