Page Comparison

Table of Contents

...

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

...

London, i.e. the functional enhancements

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

...

)

...

- Bug fixes for MOD/Helm-gen (log.path setting override)
- 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
- Archival of DCAE MOD repositories and components

* Pending committment (dependent on community contribution/support)

Services Introduction

Following new service will be delivered for Kohnis targetted for London (Supported by Wipro)

- 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 R12 London M2 Release Planning#Scope for more details

Image RemovedImage Added

Deprecation Notice:

- Acumos Adapter

DCAE MOD under assessment for EOL with London release

DCAEMOD will be deprecated from DCAE in London release.

Background : 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.

...

Acumos project has been archived under LF (end of 2021). And with DCAE platform transformation feature, requirement

...

#a and

...

#b are less critical as the onboarding/deployment are easily managed through Helm-Charts and catalog supported through Chartmuseum (or any other registry).

...

As some MOD components are on java8 due to upstream dependency with Apache/Nifi project on java8 and have SECCOM exception currently

...

KOHN Deployment

Image Removed, team had decided to retire MOD.

(TSC Notification : https://lists.onap.org/g/onap-tsc/topic/dcae_mod_eol_with_london/92490689)

Deployment

Image Added

3. New or modified interfaces

New External interfaces

- None

Modified interfaces

...

With REQ-1379 (Improve DCAE PRH to handle Early PNF Registrations) - PRH publish interface will be switched to use Kafka API directly (replacing DMAAP). No change/impact to SO.