work of the Future template-based hardware allocation and rack arrangement, automated naming, automated IP address allocation, and automated cabling instructions, among others things. 4.3.2.2 Build Once automating the design is complete, a network cloud service provider needs to effectively and efficiently virtualize OpenStack, enable the control plane to be dynamic, and reduce its physical footprint. This leads to the creation of virtual LCP (vLCP). With vLCP, one can build and automate under the cloud that is entirely virtualized, SO that the OpenStack control plane runs inside VMs. This allows the operator to be able to easily move around, snapshot, rollback, and redeploy or upgrade AIC zones when needed. 4.3.2.3 Manage Once built, AIC needs to be managed at scale. By engineering "day 2" operations into fuel, and the automation framework, capabilities ranging from minor setting changes, to deploying new plugins and enabling new features across 100 S of AIC zones, are rapidly enabled. 4.3.2.4 Integrate In order to fully and effectively transform OpenStack environments into a Network Cloud, a few key gaps need to be filled. A VNF automation system is required to build carrier grade network functions and integrate with OpenStack Neutron APIs. Capabilities to enable and manage high-end commu- nication services across the wide area network and integrate them with existing systems while fully automating the lifecycle of the VNF in a network cloud ecosystem, are also required. This VNF automation system is created via ONAP (see Chapter 7). ONAP provides a design time and execution time framework that tightly integrates all of the systems within the Network Cloud. ONAP is inten- tionally separated from AIC to create a layered software approach. ONAP provides the full lifecycle of VNF automation to an AIC, as well as enables and manages the wide area network. 4.3.2.5 Operate The massive scale of a service provider's zone deployments calls for a management frame- work. This is provided by the OpenStack resource manager 