Page Comparison

...

The following figures show the implemented system architecture  and flows for the first release of OpenECOMP.

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

1. The controller is instantiated with an OpenECOMP Heat template.
2.  The DCAE Controller instantiates the rest of the DCAE

...

1. components, including both infrastructure and service/application components.
2. 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.

Image Added

Figure 2. DCAE configuration flow (Control plane)

Figure 3 shows the DCAE configuration data flow.

Image Removed

Figure 2. DCAE configuration flow (Control plane)This flow proceeds as follows:

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.