 interval, to a model where we can accelerate field deployments by pivoting test VMs and VNFs into produc- tion VMs and VNFs once laboratory testing on those VMs has completed. Using production VMs also enables parallel field testing. Using service orchestration, we will also be able to significantly reduce field deployment intervals. Upgrades and configuration changes are automated and can be fully deployed in a matter of hours or days once the code has been proven to be stable in production. In the PMO, testing progresses in a serial or "water-fall" fashion and field testing (network val- idation testing, operational readiness testing, Service First Field Application [FFA]) follows the completion of laboratory testing. In the future mode of operation (FMO), field testing substantively overlaps laboratory approval for use (AFU) testing on the same set of VNFs, resulting in a dramatic reduction in cycle time. Once laboratory AFU testing on VMs and VNFs completes, those VMs and VNFs are "pivoted" into production and a much smaller amount of additional field testing is required. Figure 14.11 depicts this. Transitioning to a fully virtualized network will take time to realize. During the transition to an all virtualized network, PNFs that have not yet been virtualized will need to interconnect with newer VNFs to provide an end-to-end test environment. The goal is to leverage existing PNF labora- tory equipment, and not to replicate those PNFs, in order to minimize laboratory costs. Since testing is done in a production cloud environment, laboratory certified VM/VNF templates or Snapshots can be directly applied to instantiate production VMs/VNFs. OpenStack supports sharing Glance Lab Platform Test Lab SVT Service FFA Orchestration/Virtualization Operations/Maintenance/Security Reliability Pivot to Field Testing Start of AFU Testing FIGURE 14.11 Pivot from lab to production to reduce cycle time. Building the Network of the Future images across cloud sites. This minimizes human error associated with network-wide deplo