Versions Compared

Version Old Version 1 New Version Current
Changes made by

Vijay Kumar

Vijay Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

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.

...

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


DCAE Focus for R7 R8 is on following

  • Address ONAP R7 R8 Usecase & Functional Feature requirement 
  • Address TSC/SECCOM MUST-HAVE non-functional requirementsGeneral platform optimization 
  • DCAE Bootstrap/CM Manager optimization 
  • MOD catalog/UI redesign (POC)
    • Addressing DCAE back logs Global requirements
  • DCAE Transformation to support Helm deployment for services
  • General platform optimization (Cloudify upgrade for python 3.6)
  • Reducing DCAE backlogs  + security fixes


Refer DCAE Honolulu Scope R8 M2 Release Planning#Scope for more details


Following new services will be delivered in R8 

...

Event Processors

Analytics/RCA

Following service is retired for Honolulu

  • TCA (cdap)  - Replaced by TCA-gen2 (introduced in Frankfurt release)

...


In Honolulu, POC for new MOD Front-End and Back-end components is being worked as PoCtracked under REQ-326 -Self Serve Control Loops will continue  - DCAEGEN2-2313 (this would eventually replace NiFI based UI/processor in subsequent ONAP release)


Image RemovedImage Added

3. New or modified interfaces

Architecture diagram - DCAE R7 M1 R8 M2 Release Planning#Highlevelarchitecturediagram

New External interfaces

  • Data Extraction Service API  - Provides basic computation and data retrieval/access from datastorage maintained by DL handlers (Feeder). This API will be consumed by Slice Analysis MS (DCAE) and UUINone for H release

Modified interfaces

  • VES Collector (7.2.1 VES support)

If they are modified, are the backwards compatible?

  • VESCollector - Yes

4. Interface naming

https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/DCAE+R4+M1+Release+Planning#DCAER4M1ReleasePlanning-APIIncomingDependencies

5. Reference to the interfaces


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

...


DCAE R7 M1 R8 M2 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.


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


7. Involved use cases, architectural capabilities or functional requirements

8. Platform Maturity Targets

DCAE R7 M1 R8 M2 Release Planning#PlatformMaturity.1Non-Functional - DCAE R7 M1 Release Planning#Non-FunctionalRequirement

Global Requirement and Best Practices 

DCAE R8 M2 Release Planning#BestPracticeCandidates

DCAE R8 M2 Release Planning#GlobalRequirements

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.VES Mode updates tracked under REQ-433 - ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Honolulu)