1. Project Overview
DCAE project provides intelligence for ONAP to support automation (via open-loop and CL) by performing network data collections, analytics & correlation and trigger actionable rootcause events.
DCAE components are classified between platform and service components. DCAE Platform refers to the set of controller components which manages deployment and LCM of DCAE service components. The DCAE services components includes all the microservices - collectors, analytics and event processor which supports active data-flows and processing as required by ONAP usecases.
The architecture of DCAE targets flexible, micros-service oriented, model based component design and deployment. DCAE also offers support for multi-site collection and analytics operations which are essential for large ONAP deployments.
2. New component capabilities for Guilin, i.e. the functional enhancements
Following new components introduced for Guilin part of E2E slicing usecase
Event Processors
- DCAEGEN2-2258 - Data Extraction Service (DES) under DataLake Handlers framework.
Analytics/RCA
- DCAEGEN2-2255 - Slice Analysis mS
Following services are retired for Guilin
- TCA (cdap) - Replaced by TCA-gen2 (introduced in Frankfurt release)
For Guilin, new MOD Front-End and Back-end components is being worked as PoC (tracked under REQ-326 -Self Serve Control Loops). This would eventually replace NiFI based UI/processor in subsequent ONAP release)
3. New or modified interfaces
Architecture diagram - DCAE R7 M1 Release Planning#Highlevelarchitecturediagram
New External interfaces
- Data Extraction Service API - Provides basic computation and data retrieval/access from datastorage maintained by DL handlers (Feeder). This API will be consumed by Slice Analysis MS (DCAE) and UUI
Modified interfaces
- VES Collector (7.2 VES support)
If they are modified, are the backwards compatible?
- VESCollector - Yes
4. Interface naming
5. Reference to the interfaces
Existing platform API's - https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/offeredapis.html
DCAE Platform
- Config Binding Service
- Deployment-Handler
- Inventory API
- Onboarding HTTP API (MOD)
- DCAE Dashboard - https://git.onap.org/ccsdk/dashboard/tree/ccsdk-app-os/src/main/resources/swagger.json
DCAE Service Components
- VES-Collector
- HV-VES (High Volume VES)
- PRH (PNF Registration Handler)
- DFC (DataFile Collector)
- 3GPP PM Mapper
- PM Subscription Handler
- DCAE SDK
- RESTConf - https://git.onap.org/dcaegen2/collectors/restconf/tree/swagger_restconfcollector.yaml
- DES
DCAE R7 M1 Release Planning#APIOutgoingDependencies
6. 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 through external DB and/or K8S state management.
Cloudify is 3rd party product; multi-site feature on community version will be available later in 2020; will be incorporated for G release.
As DCAE collectors are extensively used in all ONAP usecase, performace testing has been done on below collectors
VES Collector Performance Test
PM-Mapper performance baseline
Datafile Collector (DFC) performance baseline results
HV-VES Performance Test
7. Involved use cases, architectural capabilities or functional requirements
- Usecases - DCAE R7 M1 Release Planning#GuilinUsecaseswithDCAEimpact
- Features - DCAE R7 M1 Release Planning#GuilinFeatureswithDCAEImpact
8. Platform Maturity Targets
DCAE R7 M1 Release Planning#PlatformMaturity.1
Non-Functional - DCAE R7 M1 Release Planning#Non-FunctionalRequirement
9. Listing 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.