e request, the infrastructure controller may obtain its resource recipe from SDC. The infrastructure controller will then begin orchestrating the request. For infrastructure controllers, this typically involves execution of OpenStack requests for the creation of VMs and for the loading of the VF software into the new VM container. The resource recipe will define VM sizing, including compute, storage, and memory. If the resource-level recipe requires mul- tiple VMs, the MSO will repeat the process, requesting each infrastructure controller to spin up one or more VMs and load the appropriate VFs, again driven by the resource recipe of the infrastructure controller. When the infrastructure controller completes the request, it will pass the virtual resource identifier and access (VRID) information back to the MSO to provide to the network and application controllers. During the process, the MSO writes identifier information to A&AI for inventory tracking. 7.4.3 NETWORK CONTROLLER ORCHESTRATION Network controllers are constructed and operate in much the same manner as application and infra- structure controllers. New service requests will be associated with an overall recipe for instantiation of that service. The MSO will obtain compatible network controller information from A&AI and will in turn request LAN or WAN connectivity and configuration to be performed. This may be done by requesting the network controller to obtain its resource recipe from SDC. It is the responsi- bility of the MSO to request (virtual) network connectivity between the components and to ensure that the selected network controller successfully completes the network configuration workflow. A service may have LAN, WAN, and access requirements, each of which will be included in the recipe and configured to meet the instance specific customer or service requirements at each level. Physical access might need to be provisioned in the legacy provisioning systems prior to requesting the MSO to instantiate the service. 7.4.4 APPLICATION CONTROLLER ORCH