...
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Beijing |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Huawei, Cloudify, Cisco, Tech Mahindra, Netcracker, ZTE |
Scope
What is this release trying to address?
The DCAE Beijing release has two primary objectives: 1. improving deliverable quality addressing "carrier grade"platform maturity; 2. supporting R2 use cases.
In addition, DCAE will add support for more analytics platform(s): PNDA, Flink, Prometheus; and enhancements for DCAE platform, analytics and collection.
Use Cases
...
From R1:
From R2:
- VNF Scale Out: Reuse capability/components for R1 use cases. No additional impact.
- Hardware Platform Enablement In ONAP No DCAE impact needed for supporting this use case. Will follow and plan how to use in future release (e.g. additional collection and analytic).
Minimum Viable Product
Describe the The MVP for this releaseof DCAE for R2 will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
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
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox dcaegen2 and issuetype in (epic) and fixversion='Beijing Release' serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Stories
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox dcaegen2 and issuetype in (story) and fixversion = 'Beijing Release' serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Longer term roadmap
...
DCAE is the collection and analytics platform serving ONAP. The value of DCAE lies in the number of types of data being collected, the number of analytics algorithms, the number of open/close control loops, and how well/easy they are supported for ONAP uses.
After the initial R1 deliverables, starting from R2, DCAE will focus more on this long term roadmap by starting to add support for more analytics platforms (e.g. PDNA, Flink, Prometheus, etc); more collection apparatus.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | To fill out|
|---|---|---|
| To fill out |
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.
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.
...
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 | 1 | 1 |
| |
| Stability | 1 | 2 |
| |
| Resiliency | 1 | 1+ |
| |
| Security | 0 | 1 |
| |
| Scalability | 0 | 1 |
| |
| Manageability | 0 | 1 |
| |
| Usability | 1 | 1 |
|
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.
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) |
|---|
| SDC model distribution API | API for retrieving TOSCA model of close loop | To fill out | Link toward the detailed API description | |
| Policy Engine | API for retrieving configuration policy updates | |||
| A&AI | API invoked for information enhancements | |||
| DMaaP Message Router | API for topic publish / subscribe | |||
| DMaaP Bus Controller | DMaaP Bus Controller is a part of DMaaP that provides topic provisioning; this is the API for topic provisioning. (TBD based on AAF availability) |
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) |
|---|
| VES Ingestion | API for VNFs to send VES data | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
| DCAE Deployment Handler | NB API for invoking the deployment of DCAE subcomponents | |||
| DCAE Inventory | API for Add/Delete DCAE copy's TOSCA models |
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|
|---|---|---|---|---|---|
| OpenStack | |||||
| Cloudify Manager | |||||
| Consul | |||||
| CDAP | |||||
| Hadoop | |||||
| PNDA | |||||
| Flink | |||||
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
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.
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.
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
Provide a link toward the list of all known project bugs.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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).
| 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
The milestones are defined at the Release Level 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
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
| 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.
...