Versions Compared

Key

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

...

The DCAE Platform consists of several functional components: Common Collection Framework, Data Movement, Edge and Central LakeStorage Lakes, Analytic Framework, and Analytic Applications.  

In large scale deployments DCAE components are generally distributed in multiple sites organized in hierarchical fashion.  For example, to provide DCAE function for a large scale eCOMP system covering multiple sites spanning across large geographical area, there will be edge DCAE sites, central DCAE sites, etc.  Edge sites are physically close to the NFs under collection, for reasons such as processing latency, data transport, and security, but often have limited computing and communications resources.  On the other hand central sites generally have more processing capacity and better connectivity to the rest of the eCOMP system.  This hierarchical organization offers better flexibility, performance, resilience, and security.  

Common Collection Framework

...

This component facilitates the movement of messages and data between various publishers and interested subscribers that may reside at different sites. While a key component within DCAE, this is also the component that enables data movement between various OpenECOMP components.

...

The following figures show the implemented system architecture  and flows for the first release of OpenECOMP.  DCAE for this release is "minimalistic" in the sense that it is a single DCAE site with all DCAE functions.

 Figure 2 shows the DCAE configuration flow.  The DCAE Controller is “node 0.”  The flow proceeds as follows:

  1. The controller DCAE Controller is instantiated with from an OpenECOMP Heat template.
  2.  The DCAE Controller instantiates the rest of the DCAE components, including both infrastructure and service/application components.
  3. The DCAE Controller configures service/application components with static configurations, configuration policies fetched at run-time (for example data processing configurations or alert configurations), and any DMaap topics required for communication.

...

  1. VNFs use REST calls to push measurement data to the DCAE VES collector.
  2. The VES collector validates, filters, and packages the received measurement data, and publishes the data to the "measurement data" topic of DMaaP.
  3. The analytics application receives measurement data from the DMaaP "measurement data" topic.
  4. The analytics application analyzes measurement data, and if alert conditions (defined by the alert policy that was installed by the DCAE Controller) are met, publishes an alert event to the DMaaP "event data" topic. 
  5. Other OpenECOMP components, for example the Policy or MSO subsystems, receive alert events from the DMaaP "event data" topic and react accordingly.

...