Page Status: Updated for Istanbul -
Component Status: Pending PTL updates and ArchCom Review
Last Reviewed on:
Certified by: Vijay Venkatesh Kumar
1. High Level Component Definition and Architectural Relationships
2. Component API definitions
DCAE Component provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities | Protocol | Status | Consumed Models | API Spec (Swagger) |
|---|---|---|---|---|---|---|
| DCAE-EXT1 | VES Collector | An interface to share FM/PM data for VNF FCAPS from the VNFs via the EMS Driver to VES Collector | REST | Available | VES | VES-Collector |
| DCAE-EXT2 | HV-VES Collector | Interface to support GPB over TCP for highvolume VES Events | Proto/TCP | Available | VES | HV-VES (High Volume VES) |
| DCAE-EXT3 | DataFileCollector | Supports bulk/batch datafile collection from xNF | http/sftp/ftpes | Available | 3GPP | NA |
| DCAE-EXT4 | SNMPTrap | Supports SNMP traps collection from SNMP agents deployed in the network | UDP | Available | NA | |
| DCAE-EXT5 | RESTConf | Subscribes to external controllers and retrieves data | restconf | Available | RESTConf | |
| DCAE-EXT6 | OnboardingAPI (MOD) | Used for onboarding MS component spec file and data-format into Design catalog | REST | Available (POC) | Onboarding HTTP API (MOD) | |
| DCAE-EXT7 | Deployment Handler | High-level API for deploying/undeploying composed DCAE services | REST | Available | Deployment-Handler | |
| DCAE-EXT8 | Inventory API | DCAE Inventory is a web service that provides the following:
| REST | Available | Inventory API | |
| DCAE-EXT9 | Data Extraction Service (DES) | Provides basic computation and data retrieval/access from datastorage maintained by DL handlers (Feeder) | REST | Available (Guilin) | des-swagger.json | |
| DCAE-EXT10 | DCAE Openloop/CL Event | Open loop and Control Loop event trigger from DCAE analytics/correlation MS into DMAAP | REST | Available | CL Event Structure | |
| DCAE-EXT11 | PNF Registration Handler | PNF Registration event published through DMAAP | REST | Available | VES | PRH (PNF Registration Handler) |
| DCAE-EXT12 | ConfigBindingService (CBS) | The CBS provides API for all DCAE deployment mS to retrieve configuration from Consul. | REST | Available | CBS API | |
| DCAE-EXT13 | SliceAnalysis MS | Adds API support for Subscription/Filters/Measurement group management | REST | Available | NSI/NSSI Selection based on resource occupancy levels | |
| DCAE-EXT14 | PM Subscription Handler Service | API to provide details of remaining capacity available for queried slice instance (NSI/NSSI) | REST | Available | https://gerrit.onap.org/r/c/dcaegen2/+/121898 |
DCAE Component consumes the following Interfaces:
| Interface Name | Interface Definition | Interface Capabilities | Protocol | Status | Consumed Models | API Spec (Swagger) |
|---|---|---|---|---|---|---|
| POE-1 | Policy update notification via DMAAP | Recieve updates to DCAE MS configuration policies via DMAAP (consumed by DCAE Policy Handler) | REST | Available | tosca.policies.root | |
| POE-5 | PDP - Policy Handler | Fetched policies for DCAE MS from the Policy Framework via PDP query | REST | Available | Defined by policy | POE-5 (Policy Decision API) |
| AAIE-1 | Topology Enrichment | Enrichment query by Correlation/analytics MS | REST | Available | AAI REST API Documentation on readthedocs.io | |
| Acumos-E5 Subscription | Acumos - AA (MOD) | Acumos Adapter - Retrieves models from Acumos using E5 interface and onboard them into DCAE (MOD) using OnboardingAPI and make it available in Catalog | REST | Available (POC) | ||
| SDCE-6 | Artifact Distribution | DCAE Platform (SCH) uses notification to determine if artifact (blueprint) retrieval must be triggered DCAE-VESOpenAPI manager uses notification to retrieve VES schema uploaded and perform validation | REST | Available | https://docs.onap.org/projects/onap-sdc/en/latest/offeredapis.html | |
| SDCE-7 | Artifact Retrieval (Cloudify blueprint) | DCAE Platform (SCH) retrieve MS Blueprint based on service-uuid identified in the distribution message | REST | Available | https://docs.onap.org/projects/onap-sdc/en/latest/offeredapis.html |
3. Component Description:
DCAE R9 M2 Release Planning#Architecture
https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/architecture.html
4. Known system limitations
Architectural Technical Debt
Hardening MOD components (delivered as POC in Honolulu) into mainstream component with redesigned catalog and Helm charts contributions
For Istanbul release, all DCAE component deployment will switch to Helm and Cloudify deployment will be provided for backward compatibility. The platform components (Cloudify & associated handlers) will be deployed using Honolulu release version and no update/enhancement/security fix will be supported.
5. System Deployment Architecture
https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/release-notes.html
6. New Release Capabilities
DCAE R9 M2 Architecture Review
7. References
- DCAE Architecture
- DCAE Onboarding -
2 Comments
Byung-Woo Jun
Vijay Venkatesh Kumar, does DCAE use the SDCE-7 (SDC query) APIs? The SDCE-6 APIs are for getting artifact types list and notification registrations.
The SDCE-7 APIs are for getting artifacts and resource details. I am wondering if DCAE uses SDCE-7...
Thanks.
Vijay Venkatesh Kumar
Byung-Woo Jun - You are right - both SDCE-6 and SDCE-7 should be included. DCAE/ServiceChangeHandler uses /v1/catalog/services/{serviceName}/{serviceVersion}/resourceInstances/{resourceInstanceName}/artifacts/{artifactName} which is tagged as SDCE-7; DCAE (SCH and VESOpenAPI manager) also listens to the DMAAP distribution notification hence SDCE-6 is also valid. I will update th wiki to reflect them accordingly