1.1 (R1)
Dependencies
https://docs.openstack.org/designate/pike/index.html
TBD
https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/blueprints/DockerHost.html
https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/blueprints/deploymenthandler.html
https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/blueprints/centos_vm.html
https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/blueprints/ves.html
http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/installation.html
1.0.0 (Feb 2017)
The Data Collection, Analytics, and Events (DCAE) subsystem, in conjunction with other OpenECOMP ONAP components, gathers performance, usage, and configuration data from the managed environment. This data is then fed to various analytic applications, and if anomalies or significant events are detected, the results trigger appropriate actions, such as publishing to other OpenECOMP ONAP components such as Policy, MSO, or Controllers.
...
These functions enable closed-loop responses by various OpenECOMP ONAP components to events or other conditions in the network.
...
In large scale deployments, DCAE components are generally distributed in multiple sites that are organized hierarchically. For example, to provide DCAE function for a large scale OpenECOMP ONAP system that covers multiple sites spanning across a large geographical area, there will be edge DCAE sites, central DCAE sites, and so on. Edge sites are physically close to the network functions 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 OpenECOMP ONAP system. This hierarchical organization offers better flexibility, performance, resilience, and security.
...
This component (known as DMaaP) 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 ONAP components.
Edge and Central Lake
...
The following figures show the implemented system architecture and flows for the first release of OpenECOMPONAP. DCAE for this release is "minimalistic" in the sense that it is a single DCAE site with all DCAE functions.
...
- The DCAE Controller is instantiated from an OpenECOMP ONAP Heat template.
- The DCAE Controller instantiates the rest of the DCAE components, including both infrastructure and service/application components.
- 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.
...
- VNFs use REST calls to push measurement data to the DCAE VES collector.
- The VES collector validates, filters, and packages the received measurement data, and publishes the data to the "measurement data" topic of DMaaP.
- The analytics application receives measurement data from the DMaaP "measurement data" topic.
- 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.
- Other OpenECOMP ONAP components, for example the Policy or MSO subsystems, receive alert events from the DMaaP "event data" topic and react accordingly.
...
Figure 3. DCAE data flow (Data plane)
References