the creation of bifurcated cloud offerings that are built for specific business purposes. NFVI depends on physical components to provide a platform to operate VNFs. The three main physical components of NFVI are compute, network, and storage. Beyond the physical components of NFVI, a complete NFVI solution also needs an NFV orchestrator and a set of VIMs. Service providers interested in open source options may use ONAP as the NFV orches- tration component of NFVI; many network clouds use OpenStack, an open-source cloud solution, as the underlying technology for the VIM. Fundamental operational changes and new strategic philosophies need to be established to suc- cessfully build and deploy an NFVI solution that lowers cost and increases flexibility. Implementing Agile development principles and a DevOps methodology to emphasize collaboration between soft- ware developers and other IT professionals to automate software delivery processes and infrastruc- ture changes helps in keeping up with rapid technology changes. NFVI solution deployment strategies should provide the resiliency needed to guarantee a con- stantly accessible network. NFVI deployment requires the physical infrastructure to be deployed in close proximity to customers to ensure the best network experience with the lowest latency. The VNFs are also deployed with an active-active-active configuration across zones to provide enhanced resiliency. Near real-time network performance expectations require NFVI solutions to include scaling options that deliver carrier grade performance. To facilitate this, some service providers have defined standard NFVI configurations called "Flavor Series" to provide enhanced performance for Building the Network of the Future VNFs. Example Flavor Series include SR-IOV and DPDK and CPU pinning techniques to deliver the throughput needed for carrier grade networks. REFERENCES 1. n.d. Retrieved from http://searchsdn.techtarget.com/definition/virtual-network-functions 2. n.d. Retrieved fromhttp://searchsdn.techtarget.com/tip/N