within ONAP. Figure 7.15 illustrates a runtime execution of a service instantiation high-level use case. As requests come into ONAP (1), whether they are customer requests, orders, or an internal operation triggering a network build out, the orchestration framework will first decompose the request and retrieve the necessary recipe(s) for execution. The initial steps of the recipes include a homing and placement task (2) using constraints speci- fied in the requests. "Homing and placement" are micro-services involving orchestration, inventory, and controllers responsible for infrastructure, network, and application. The goal is to allow algo- rithms to use real-time network data and determine the most efficient use of available infrastructure capacity. Micro-services are policy-driven. Examples of policy categories may include geographic server area, serving area/regulatory restrictions, application latency, network resource and band- width, infrastructure and VNF capacity, as well as cost and rating parameters. When a location is recommended and the assignment of resources are done, orchestration then triggers the various controllers (3) to create the internal datacenter and WAN networks (L2 VLANs or L3 virtual private network [VPNs]), spin up the VMs (4), load the appropriate VNF software images, connect them to the designated data plane and control plane networks. Orchestration may also instruct the controllers to further configure the VFs for additional layer 3 features and layer 4 and above capabilities (5). When the controllers make the changes in the network, autonomous events from the controllers and the networks themselves are emitted for updating the active inven- tory (6). Orchestration (MSO) completes the instantiation process by triggering the "test and turn-up tasks" (7); this includes the ability for ONAP to collect service-related events (8) and policy-driven analytics that trigger the appropriate closed-loop automation functions. Similar orchestration/con- troller recipes and templates as well as 