Project Overview
DCAE platform includes components collectively fulfilling the role of Data Collection, Analytics, and Events generation for ONAP. The architecture of DCAE targets flexible, plugable, micros-service oriented, model based component deployment and service composition.
DCAE also support multi-site collection and analytics operations which are essential for large ONAP deployments. DCAE components generally fall into two categories: DCAE Platform Components and DCAE Services Components.
DCAE Platform refers the set of controller components which manages the deployment and LCM of the DCAE service components which include all the collectors, analytics and event processor MS.
New component capabilities for Dublin, i.e. the functional enhancements
Following new components introduced for Dublin
Collectors
RESTConf collector
Event Processors
VES/Universal Mapper
3gpp PM-Mapper
BBS Event processorDL Handlers – Feeder and Admin (POC)
Analytics/RCA
SON-Handler (former PCI-Handler)
Heartbeat (STRETCH GOAL)
TCA-Gen2 (STRETCH GOAL)Platform Enhancements
- Support helm chart deployment in DCAE-C using custom helm plugin*
- DCAE Healthcheck enhancement
- Dynamic AAF based topic provisioning (STRETCH GOAL)
- Multisite K8S cluster deployment support (STRETCH GOAL)
- Dashboard (UI for deployment/verification)
New or modified interfaces
Architecture diagram - DCAE R4 Architecture Diagram
New External interfaces
RESTConf collector (DCAE) - Domain Controllers
SON-Handler (DCAE) - OOF (via API), SDNR (via DMaaP), Policy (via DMaaP)
BBS-eventprocessor (DCAE) - Policy (via DMaaP)
Heartbeat Ms (DCAE) - Policy (via DMaaP)
TCA-gen2 (DCAE) - Policy (via DMaaP)
Modified interfaces
Policy Handler (DCAE) - Policy (moving to new LC API)
PRH (DCAE) - AAI (API change based on PNF model update)
Interface naming
Reference to the interfaces
Existing platform API's - https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/offeredapis.html
https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/apis/inventory.htmlhttps://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/apis/dcaecdap.html
https://git.onap.org/dcaegen2/services/prh/tree/swagger.yaml
https://git.onap.org/dcaegen2/collectors/ves/tree/swagger_vescollector_1.3.1.yaml
https://git.onap.org/dcaegen2/platform/configbinding/tree/app/app/swagger.yaml
New R4 APIs to be added into RTD - SON-Handler, RESTConf
DCAE R4 M1 Release Planning#APIOutgoingDependencies
What are the system limits
Relies on k8s for loadbalancing and scaling. DCAE platform handles the control flow and do not carry the data/event; DCAE service components can be scaled and support state management.
Cloudify is 3rd party product; multi-site feature on community version will be available later in 2019; will be incorporated for E release.Involved use cases, architectural capabilities or functional requirements
- Usecases
5G Use Case (Dublin)
5G - Bulk PM
5G - OOF and PCI
BBS Broadband Service Use Case (Dublin)
CCVPN (E-LAN Service (EP-LAN, EVP-LAN) *, https://wiki.onap.org/pages/viewpage.action?pageId=45296665
Model Driven Control Loop RequirementsListing of new or impacted models used by the project (for information only)
Support for new policy model as required by Model driven control loop requirement.
...