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 Frankfurt, i.e. the functional enhancements

Following new components introduced for Frankfurt

Event Processors

DCAEGEN2-1849 DL Handlers integration (DL-Admin, DL-Feeder) (cont of DataLake POC)

Analytics/RCA

DCAEGEN2-1820 PM-Subscription Handler
DCAEGEN2-1907 TCA-Gen2 (STRETCH GOAL)

Platform Enhancements

DCAEGEN2-1852 DCAE MOD (mod/genprocessor, mod/runtimeapi, mod/distributorapi, mod/onboardingapi , mod/webui - NiFI)
DCAEGEN2-1893 Acumos-ONAP DCAE adapter (POC)
DCAEGEN2-1908 OTI (Phase1) - EventProcessor, Event-Handler

3. New or modified interfaces

Architecture diagram - DCAE R6 M1 Release Planning#Highlevelarchitecturediagram

New External interfaces

MOD (Onboarding API to AcumosAdapter)
Policy Handler (via DMaaP)
PM-Subscription Handler (via DMaaP)
TCA-gen2 (via DMaaP)

Modified interfaces

VES Collector (security)
InventoryAPI (MOD Flow support for CLAMP)

If they are modified, are the backwards compatible?

VESCollector - Yes
InventoryAPI - Yes

4. Interface naming

https://lf-onap.atlassian.net/wiki/display/DW/DCAE+R4+M1+Release+Planning#DCAER4M1ReleasePlanning-APIIncomingDependencies

5. 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/deployment-handler.html

https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/apis/inventory.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

https://git.onap.org/dcaegen2/collectors/restconf/tree/swagger_restconfcollector_1.0.0.yaml

MOD Onboarding API - swagger-onboardingAPI.json

DCAE R6 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.

7. Involved use cases, architectural capabilities or functional requirements

Usecases
- Self Serve Control Loops v2
- Policy Update Notifications
- 5G / OOF SON Enhancement
- 5G / Bulk PM / PM Control
- 5G / Bulk PM / Secure Communication between xNFs and ONAP
- PNF / Plug and Play

8. Platform Maturity Targets

DCAE R6 M1 Release Planning#PlatformMaturity.1

In-addition, following SECCOM activities are being worked for Frankfurt

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.

Browser not supported