...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Huawei, Cloudify, Nokia, Tech Mahindra, Ericsson, Cisco |
Scope
What is this release trying to address?
The DCAE Casablanca release has two following primary objectives:
1. improving Improving platform maturity;
2. supporting Supporting use cases . In addition, DCAE will add support for more analytics platform(s): PNDA, Flink, Prometheus; and enhancements for DCAE platform, analytics and collection.identified by ONAP and integration.
3. Adding to mS suite of collectors and event processors
Use Cases
From R1:
R3
TBD
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).
From R1:
Minimum Viable Product
The MVP of DCAE for R2 will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
...
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 Long term roadmap will include support for more analytics platforms (e.g. PDNA, Flink, Prometheus, etc); more collection apparatus.
...
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| DCAE Platform | Include platform components (Containers/packages) updated for R3 | ||
| DCAE Services | Include all services component (Containers/packages) | ||
| Documentation | |||
| Component spec | All ms added into DCAE should provide meta data representation of the component itself; will be used to generate models in SDC and blueprint generation | ||
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.
TBD
IN addition to existing platform/service component
| Deliverable | repo | Files Structure of repo |
| DataFileCollector | dcaegen2/collectors/datafile | dcaegen2/collectors/datafile |
| HV-VESCollector | dcaegen2/collectors/hv-ves | dcaegen2/collectors/hv-ves |
| PM-Mapper | dcaegen2/services/pm-mapper | |
| : | ||
Architecture
High level architecture diagram
...
Anyone reading this section should have a good understanding of all the interacting modules.
TBD (add new R3 arch diagram with new components and interface)
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.
...