This document provides an overview of DCAE functionality and APIs planned for ONAP R1.
DCAE Functionalities
...
DCAE supports two methods for configuring service components deployed by DCAE. The first is via default (static) configurations that is provided as part of the service component on-boarding process. The second is via Policy. Configurations via either method will become available on Consul through DCAE platform, and for service components to fetch via service discovery mechanism.
Service Component Functions
DCAE service components will support the CLAMP control loops for the approved use cases for ONAP R1.
DCAE APIs
Primary APIs
Primary APIs are the designed methods of interaction with DCAE Platform. They are stable, and intended as the entry points into DCAE platform functionalities
...
C3 interface is the interface from CLAMP to DCAE. When CLAMP performs lifecycle management on any control loop, it invoke the C3 API into DCAE to trigger corresponding workflows being executed on DCAE service components.
C4 is the interface that DCAE depends on for deploying its virtual resources to cloud infrastructure. For R1 it is the standard Open Stack API, provided by either the cloud infrastructure or MultiVIM.
D1 is the FCAPS data ingestion API provided by DCAE service component (VES collector) for supporting all three approved use cases, i.e. vFW/vDNS, vCPE, vVoLTE.
...
- Instantiation tests: deploying DCAE platform, then verifying component status via T1. Deploying service components based on CLAMP blueprints from C3, then verifying component status via T1.
- Functional tests: injecting synthetic FCAPS data via D1, observing data being accepted and forwarded by VES via T2, observing alters any alerts generated by analytics (TCA or Holmes) via T2.
...