...
| 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, Cisco, Tech Mahindra, |
...
The DCAE Beijing release has two primary objectives: 1. improving deliverable quality addressing "carrier grade"; 2. supporting R2 use cases.
In addition, DCAE will add support for more analytics platform(s): PNDA, Flink, Prometheus; and enhancements for DCAE platform and collection.
Use Cases
From R1:
From R2:
VNF Scale Out (TBD)
Use case proposal: 5G- RAN deployment, Slicing, SON (TBD)
Hardware Platform Enablement In ONAP (TBD)Describe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
Describe the The MVP for this release.of DCAE for R2 will include the necessary subcomponents supporting the primary objectives.
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 server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox and issuetype in (story) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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, 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)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...) of this release.
...
| 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 Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||
|---|---|---|---|---|---|---|
| VES Ingestion | API for VNFs to send VES data | 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 description |
| DCAE Deployment Handler | NB API for |
API Outgoing Dependencies
...