Page History

1.

...

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.

With Jakarta release, DCAE Platform component centered around Cloudify will be deprecated. All Microservice orchestration and lifecycle management will be handled through Helm/Kubernetes. 

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.

Under new DCAE transformation project, DCAE platform components will be replaced by cloud native functions supported via sidecar/init containers through Helm deployment.

2. New component capabilities for

...

Jakarta, i.e. the functional enhancements

...

• Complete DCAE

...

• transformation

...

• to Helm
  • Common Template

...

• CMPv2 Certificate
• Policy Sidecar
• PG credentials management through K8S secret
• ConfigMap Support
• DMaap Config Support (dynamic)

...

• Bulk PM flow - DataFile, PM-Mapper, PMSH
• E2E Slicing - KPI-MS, Slice-Analysis, DL Handlers (Feeder, Admin, DES)
• Son-Handler, Heartbeat, VES-Mapper, RESTCOnf, SNMPTrap, BBS-Ep

...

• Helm charts generation through MOD  (POC)
• ONAP Internal Helm Registry support

• • Enhancement for dcaegen2-services-common (filebeat removal + general add-on capabilities)
  • Continue removal of Consul dependency & application config standardization via configmap
  • MOD Support for Helm chart generation/distribution
  • Deprecate Cloudify and related Handlers from ONAP deployment
  • Integration Testsuite migration to use helm chart

• TSC/SECCOM Global requirements 
  • STDIO complaince for Heartbeat and SNMPTRap MS
• TSC/SECCOM Best Practice
  • Integration base image alignment for VES/RESTConf/SliceAnalysis MS

...

• Reducing DCAE backlogs  + security fixes

Refer DCAE R10 M2 Release Planning for more details

Image RemovedImage Added

Following Platfrom components are marked for archival post Istanbul; they will be RO only.deprecated and no longer part of DCAE deployment

• Cloudify
• Dashboard
• ServiceChange Handler
• Policy-Handler
• Deployment-Handler
• InventoryAPI

Image RemovedImage Added

3. New or modified interfaces

New External interfaces

• None

Modified interfaces

• PMSH - Adds Adds new API support for Subscription/Filters/Measurement group management ; (this will be invoked by CLAMP. https://gerrit.onap.org/r/c/dcaegen2/+/121898consumed by Policy)
• Slice Analysis -  API to provide details of remaining capacity available for queried sliceresource availability for existing slice/subslice. OOF is consumer of the API and will use this data to determine reusability of slice. -   NSI/NSSI Selection based on resource occupancy levels

Modified interfaces

Deprecated interfaces

• Cloudify API (used for LCM of DCAE MS)
• InventoryAPI (used for saving/retreving DCAE blueprints)
• DeploymentHandler API (used by CLAMP for triggering MS deployment)NA

4. Interface naming

DCAE R10 M2 Release Planning

...

DCAE Platform

• Config Binding Service*
• Deployment-Handler
• Inventory API
• Onboarding HTTP API (MOD)

DCAE

...

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.yamldes-swagger.json
• DES
• PMSH
• Slice-Analysis MS 

Deprecation Notice: Following Platform API's will be deprecated immediately after Istanbul. For Istanbul release - once all MS migration to new SDK is completed in Jakarta release. For the interim time, the component will be retained in deployment using Jakarta version (no new enhancement/updates are planned for these component (Istanbul deployment will continue using Honolulu version). 

• Deployment-Handler
• Inventory API
• DCAE Dashboard - https://git.onap.org/ccsdk/dashboard/tree/ccsdk-app-os/src/main/resources/swagger.json

• Config Binding Service

6. What are the system limits

...

7. Involved use cases, architectural capabilities or functional requirements

• Usecases -   DCAE R9 R10 M2 Release Planning#IstanbulUsecaseswithDCAEimpactPlanning
• Features -  DCAE R9 M2Release Planning#IstanbulFeatureswithDCAEImpact DCAE R10 M2 Release Planning

8. Platform Maturity Targets

Istanbul Jakarta Release Platform Maturity

Global Requirement and Best Practices -   DCAE R10 M2 Release Planning

9. Listing of new or impacted models used by the project (for information only)

No model changes planned for J release