 Chapter 7) for closed-loop automation as shown in Figure 14.6. It provides dynamic auto-recovery and auto-scaling capabilities for virtual services. The flow for closed-loop automation is as follows: 1. Virtual functions send fault and performance data to Data Collection Analytics and Events (DCAE). 2. DCAE performs correlation and analytics on data received at both the virtual function level as well as the service level. For example, at the virtual function level, it may detect that a VM needs to be rebooted. At the service level, it may detect that the rate of incoming registrations is much higher and is exceeding a threshold for a service. 3. Policy is consulted for events generated by DCAE as needed and includes recommended actions for specific events. 4. The controller may be requested to perform auto-recovery actions, for example, reboot a virtual function. 5. The orchestrator is requested to perform an action if an instantiation needs to be performed in real-time for auto-recovery (e.g., a new virtual function needs to be instantiated) or for auto-scaling (e.g., to expand a service footprint). Orchestration may be requested to expand a Service footprint, increase e2e bandwidth or move a Service/Network due to a planned or unforeseen outage or stress point Orchestrator Controllers may be requested to Policy is consulted reboot/restart a Virtual Function DCAE may determine that when events occur Controller the event or analytics to determine the warrant the creation of action. Policy could additional resources in the direct request to Storage Network resource layer or an the Orchestration or Policy additional order Control Layers based Compute Applications opportunity on the scope of the resolution DCAE receives events and data for analytics to make adjustments outside of the Controller's domain or where Policy must be interrogated to determine appropriate action. FIGURE 14.6 Closed-Loop Automation. Service Platforms When a control loop action is taken, an event is sent to the ONAP portal for operations vis