Versions Compared

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.

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 platform includes components collectively fulfilling the role of Data Collection, Analytics, and Events generation for ONAP. The architecture of DCAE targets flexible, pluggable, micros-service oriented, model based component design and deployment and service composition. DCAE also offers support for multi-site collection and analytics operations which are essential for large ONAP deployments. DCAE components generally fall into two categories: DCAE Platform Components and DCAE Services Components.DCAE Platform refers the set of controller components which manages the deployment and LCM of the DCAE service components which include all the collectors, analytics and event processor MS. 

2. New component capabilities for

...

Frankfurt, i.e. the functional enhancements

Following new components introduced for DublinFrankfurt

Event Processors

Analytics/RCA

Platform Enhancements

  • DCAEGEN2-1852  DCAE MOD (mod/genprocessor, mod/runtimeapi, mod/distributorapi, mod/onboardingapi , mod/webui - NiFI)
  • DCAEGEN2-1893 Acumos-ONAP DCAE adapter (POC)
  • DCAEGEN2-1908 OTI (Phase1) - EventProcessor, Event-Handler

...

https://git.onap.org/dcaegen2/platform/configbinding/tree/app/app/swagger.yaml

https://git.onap.org/dcaegen2/collectors/restconf/tree/swagger_restconfcollector_1.0.0.yaml

New R6 APIs to be added into RTD  - SON-Handler, RESTConfMOD Onboarding API - To be added


DCAE R6 M1 Release Planning#APIOutgoingDependencies

...

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 20192020; will be incorporated for E G release.


7. Involved use cases, architectural capabilities or functional requirements

...

  • Outstanding OJSI Jira (OJSI Tickets Status)
  • Java 11 Upgrade (DCAEGEN2-1918) (stretch goal)
  • Python 2.x EOL migration support (DCAEGEN2-1519)
  • Following additional TSC MUST have requirement will also be worked in this release.
    • Document current upgrade component strategy
    • SECCOM Perform Software Composition Analysis - Vulnerability tables
    • SECCOM Password removal from OOM HELM charts
      • No DCAE impacts identified; will handle new charts contribution for MOD to align with Security needs.
    • SECCOM HTTPS communication vs. HTTP

      config-binding-service30415
      dashboard30418


    • DCAEGEN2-1972 - Password removal from HELM charts (EPIC)
      • DCAEGEN2-1973  DCAE Helm chart updates for password removal 

      • DCAEGEN2-1974  Bootstrap pod updates for sourcing password 

      • DCAEGEN2-1975  Cloudify pod updates for sourcing password   

      • DCAEGEN2-1976  Policy-Handler updates for sourcing password

      • DCAEGEN2-1977  InventoryAPI updates for sourcing password 

      • DCAEGEN2-1978  ServiceChangeHandler updates for sourcing password 

...