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, provides FCAPS (fault, configuration, accounting, gathers performance, security) functionality. DCAE gathers performance, usage, and configuration data about from the OpenECOMP systemmanaged environment. This This data can is then be fed to various analytic programsapplications, and if anomalies or significant events are detected, the results can trigger appropriate actions, such as publishing to other OpenECOMP ONAP components such as Policy, orchestrationMSO, or Controllers.
The primary functions of the data lake. DCAE supports closed-loop control and higher-level correlation for business and operations activities. It also provides the infrastructure for collection of autonomous events from the network and other cloud components, making them available to subscribing applications, including business support system (BSS) and operational support system (OSS) applications.
The DCAE environment forwards usage and other information that can be used by the BSS to generate billable events and other events and records. The BSSs obtain the data from DCAE distribution channels or from the data lake. For example, the billing function in a BSS can support near real-time balance management by receiving streaming analytics from DCAE.
Usage and event management BSSs can be created as applications on top of the DCAE environment as well as applications outside DCAE. These applications can collect customer events and perform mediation of the usage and events to downstream BSSs or OSSs (Operational Support Systems). BSSs can also collect network events such as bill-impacting configuration changes, consumption or any new bill-impacting network product or service which can in turn be used DCAE subsystem are to
- Collect, ingest, transform and store data as necessary for analysis
- Provide a framework for development of analytics
These functions enable closed-loop responses by various ONAP components to events or other conditions in the network.
DCAE provides the ability to detect anomalous conditions in the network. Such conditions, might be, for example, fault conditions that need healing or capacity conditions that require resource scaling. DCAE gathers performance, usage, and configuration data about the managed environment, such as about virtual network functions and their underlying infrastructure. This data is then distributed to various analytic micro-services, and if anomalies or significant events are detected, the results trigger appropriate actions. In addition, the micro-services might persist the data (or some transformations of the data) in the storage lake. In addition to supporting closed-loop control, DCAE also makes the data and events available for higher-level correlation by business and operations activities, including business support systems (BSS) and operational support systems (OSS).
Usage and other event processing applications can be created in the DCAE environment. In addition to real-time processing of events, these applications can perform mediation of the usage and other events to external BSSs or OSSs. For example, events about bill-impacting configuration changes or consumption of any new product or service can be subscribed to by external BSS applications for various purposes such as rating, balance management , and charge calculations.
The following figure shows provides a functional view of the DCAE Platform architecture:.
Figure 1. DCAE Platform high-level architectureA key subset of the DCAE architecture is the DCAE Platform. The DCAE platform consists of the capabilities that help define how data is collected, moved, stored and analyzed within DCAE.
DCAE Platform Components
The DCAE Platform consists of several functional components: Common Collection Framework, Data Movement, Storage Lakes, Analytic Framework, and Analytic Applications.
In large scale deployments, DCAE components are generally distributed in multiple sites that are organized in hierarchical fashionhierarchically. For example, to provide DCAE function for a large scale eCOMP ONAP system covering that covers multiple sites spanning across a large geographical area, there will be edge DCAE sites, central DCAE sites, etc. Edge and so on. Edge sites are physically close to the NFs 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 eCOMP ONAP system. This hierarchical organization offers better flexibility, performance, resilience, and security.
...
Collection Framework
The collection layer provides the various data collectors that are needed to collect the instrumentation that is available from the cloud infrastructure. Included are both physical and virtual elements. For example, collection of the following types of data is supported:
...
Data Movement
This component facilitates (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
...
While there may be detailed data retained at the DCAE edge layer for detailed analysis and trouble-shooting, applications should optimize the use of bandwidth and storage resources by propagating only the required data (for example, reduced, transformed, or aggregated) to the core data lake for other analyses.
...
The following list provides examples of the types of applications that can be built on top of DCAE:
...
Performance surveillance and visualization: Thisclass of application provides a window to an an operations organization, notifying them it of network and service conditions. The notifications could include outages and impacted services or customers based on various dimensions of interest. They provide visual aids ranging from geographic dashboards to virtual information model browsers to detailed drilldown to specific service or customer impacts.
...
Security: Some components of AIC the infrastructure may expose newtargets for security threats. Orchestration and control, decoupled hardware and software, and commodity hardware may be more susceptible to attack than proprietary hardware. However, SDN and virtual networks also offer an opportunity for collecting a rich set of data for security analytics applications to detect anomalies that signal a security threat, such as DDoS attack, and automatically trigger mitigating action.
Other: The applications listed here are by no means exhaustive and the open architecture of DCAE lends itself to integration of additional application capabilities over time.
DCAE System
...
Flows
The following figures show the implemented system architecture and 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.
Figure 2 shows the DCAE configuration flow. The DCAE Controller is “node 0.” The The flow proceeds as follows:
- The DCAE Controller is instantiated from an OpenECOMP ONAP Heat template.
- The 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.
Figure 2. DCAE configuration flow (Control plane)
Figure 3 shows the DCAE data flow. This flow proceeds as follows:
- 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