DCAE R11 Kohn M2 Architecture Review

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.

Since Jakarta release, DCAE Platform component centered around Cloudify has been deprecated; all Microservice orchestration and lifecycle management are 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 offers support for multi-site collection and analytics operations which are essential for large ONAP deployments.

2. New component capabilities for Kohn, i.e. the functional enhancements

Following are the planned scope for Kohn release (more info on the commitment and supporting companies documented under DCAE R11 Kohn M2 Release Planning)

- Address DCAE transformation carry-over items
  - Common Template Enhancement for dcaegen2-services-common (For support for dynamic configuration update via ConfigMap)
  - DR Feed configuration cleanup
  - Bug fixes for MOD/Helm-gen (log.path setting override)
- Support TSC approved ONAP Usecases and Features (details below)
- Alignment with TSC/SECCOM Global requirements & TSC/SECCOM Best Practice
- OpenSSF Best Practice progression (target Gold badging)
- SBOM Report integration with CI and validation*
- Continue AAF certificate dependency removal (by making it a configurable property)
- Microservice enhancements in support for ONAP usecases/features
  - SliceAnalysis Ms (under E2E Slicing/IBN/CCVPN), SON-Handler (5G SON)
- Enable automated static-check code review/scan with CI/verify job
- Improving code coverage across all DCAE components
- DCAE backlog reduction

Services Introduction

Following new service will be delivered for Kohn

- ML MS (REQ-1074)
  - Repository : https://git.onap.org/dcaegen2/services/tree/components/ml-prediction-ms (introduced as new subproject under existing repo)

Refer DCAE R11 Kohn M2 Release Planning#Scope for more details

Deprecation Notice:

- Acumos Adapter

DCAE MOD under assessment for EOL with London release

DCAE MOD was introduced in Frankfurt release to address following requirements:

1. Simplified and streamlined onboarding for DCAE components/microservice and distribute the deployment artifact with DCAE-Core Platform (Cloudify)
2. Provide Common Catalog for reusable DCAE microservices for Designer to leverage
3. Enable automated onboarding for ML microservices from Acumos.

With DCAE platform transformation feature, requirement #1 and #2 are less critical as the onboarding/deployment are easily managed through Helm-Charts and catalog supported through Chartmuseum (or any other registry). Also with Acumos project archived under LF (end of 2021), DCAE team will be assessing the need for continuation/support of DCAE MOD going forward.

Note: Certain MOD components are on java8 due to upstream dependency with Apache/Nifi project on java8 and have SECCOM exception currently.

KOHN Deployment

3. New or modified interfaces

New External interfaces

- None

Modified interfaces

- None

Deprecated interfaces

- With deprecation of Acumos Adapter, interface with Acumos project will no longer be supported

4. Interface naming

DCAE R11 Kohn M2 Release Planning#APIOutgoingDependencies

DCAE R11 Kohn M2 Release Planning#APIIncomingDependencies

5. Reference to the interfaces

DCAE R11 Kohn M2 Release Planning#APIOutgoingDependencies

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

DCAE Platform

- Onboarding HTTP API (MOD)*

DCAE Service Components

Deprecation Notice: Following Platform API's will be deprecated post Kohn release if no new usecase/driver is identified for ONAP releases. For the interim time, MOD component will be retained in deployment using Jakarta version (no new enhancement/updates are planned)

- Onboarding HTTP API (MOD)*

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.

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