...

What is this release trying to address?

Describe the problem being solved by this releaseThe scope for this release will be deploy DCAE Platform using the new controller platform components leveraging the common SDK framework, OOM and in supporting the approved use cases for R1.

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

Use Case: vFW/vDNS (Approved)

Use Case: Residential Broadband vCPE (Approved)

Use Case: VoLTE(approved)

Minimum Viable Product

Describe the MVP for this release.

All core DCAE Platform components

-       Cloudify Manager

-       Consul

-       DeploymentHander

-       Policy-Handler

-       ServiceChangeHandler

-       Inventory-API

-       Postgres

-       Registrator

-       ConfigBinding Service

-       CDAP Broker

       DCAE Service specific components

-       VESCollector

-       TCA (Analytics application)

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.

...

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Once the platform components are stabilized, newer mS and application can be onboarded into DCAE platform to support additional usescases. DCAE controller integration with MultiVM project would allow support into multi-cloud environment.

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Sub-Components

List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

DCAE Platform encompasses following sub-components.

• Cloudify-manager (blueprints/plugins)
• Consuls
• cdapbroker
• deployment-handler
• servicechange-handler
• inventory-api
• policy-handler
• configbinding
• registrator
• ves
• Postgres

Below is the interaction/flow between these components.

ONAP Dependencies

List the other ONAP projects your depends on.

VNF’s –  The VNF supporting the R1 usecase should comply with VES specification or be able to send SNMP Traps to DCAE

Policy – For sending dynamic configuration and rules for analytics into DCAE. Policy-hander also uses policy-engine client-lib provided in PolicyEngine-0.9.win32.tar file.

CLAMP – For create/update DCAE collector, analytic and micro service configuration Policies.

DMAAP - We are dependent on Dmaap for pub/sub of events/Control Loop messages (to Policy and APP-C)

OOM – For instantiating the DCAE controller

CCSDK – For deploying database as a service for DCAE.

MSB -   Integration with MSB (stretch)

Multi-VM - Integration with Mutli-VM project to leverage infrastructure api  (stretch)

Architecture

High level architecture diagram

...