ration and control framework (MSO and controllers) that is recipe/policy driven to provide automated instantiation of the service when needed and managing service demands in an elastic manner. 3. An analytic framework that closely monitors the service behavior during the service life- cycle based on the specified design, analytics, and policies to enable response as required from the control framework, to deal with situations ranging from those that require healing to those that require scaling of the resources to elastically adjust to demand variations. The Network Operating System Instantiate Service based on customer request or Monitor Monitor service by listening to events; computing infrastructure needs: set up monitoring controls: Service analytics based on data collection: publish test and turn-up service events that require healing or scaling based on defined policies Distribute design templates and policies to various actors Actor(s) perform the required Actions Automated to implement the changes; verify changes restore the service to needed levels Service Define analytics governing service/resource behavior: ensure analytic applications are in place to Lifecycle manage behavior Actor(s) publish events to record changes made for the the required Specify policies governing conditions. service/resource behavior; adapt policy changes based on service lifecycle Recommend Analyze behavior over time to identify changes Design Service based on resource models and needs: changes needed in design. policies, analytics design/define analytics & thresholds needed to monitor or thresholds governing response service; incorporate design changes based on service lifecycle FIGURE 7.14 ONAP closed-loop automation. The following sections describe the ONAP frameworks designed to address these major require- ments. The key pattern that these frameworks help automate is the following: "Design Create Collect Analyze Detect Publish Respond" This automation pattern is referred to as "closed-loop automation" in that it provides t