Content Comparison

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. 

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

...

• Reducing DCAE backlogs  + security fixes

Refer DCAE R10 M2 Release Planning for more details

Image Modified

Following Platfrom components are deprecated and no longer part of DCAE deployment

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

Image Modified

3. New or modified interfaces

New External interfaces

• • None

Modified interfaces

• • PMSH - Adds new API support for Subscription/Filters/Measurement group management (this will be consumed by Policy)
  • Slice Analysis -  API to provide resource 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

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)

4. Interface naming

DCAE R10 M2 Release Planning

DCAE R10 M2 Release Planning

5. Reference to the interfaces

DCAE R10 M2 Release Planning

Existing platform API's - https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/offeredapis.html

DCAE Platform

• • Config Binding Service*
  • Onboarding HTTP API (MOD)

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
  • DES
  • PMSH
  • Slice-Analysis MS 

Deprecation Notice: Following Platform API's will be deprecated 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) 

• • Config Binding Service

6. What are the system limits

...

PM-Mapper performance baseline

Datafile Collector (DFC) performance baseline results

HV-VES Performance Test

7. Involved use cases, architectural capabilities or functional requirements

...

8. Platform Maturity Targets

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