One of the benefits of virtualization is the ability to centrally orchestrate the deployment of service building blocks from a software catalog, as opposed to using proprietary appliances. Instead of sending engineers to a site to install physical devices, Virtual Network Functions (VNFs), also known as service components, are selected from a catalog. By clicking a button, the new service is installed.
To reach this level of simplicity, the NFV platform must support the following:
Quick VNF Onboarding. VNF onboarding is automated using enhanced, policy based vApp templating and declarative abstract resource requirements for underlying compute, storage, and networking resources.
Programmatic VNF Provisioning: The speed and efficiency of VNF deployment is increased through automation, selecting service operations from a catalog of VNFs to deploy specific services.
True Multitenant Isolation. Physical resources abstracted into virtual resource pools are shared between services and customers, referred to as tenants of the platform. The ability to partition the service and VNF from each other is key to ensure performance and quality of service (QoS) across the platform
Service Life Cycle Management. Programmatic service creation and dynamic orchestration of running VNFs are required pieces of an automation framework. Interfaces between the VIM, the VNFM, and the NFV Orchestrator (NFVO) must leverage a robust and open API. Using these interfaces the NFV platform deploys, scales, restarts, and decommissions VNFs as needed
Dynamic Optimization. As more and more VNFs are deployed on the NFVI, NFVI resources must be able to proactively act on specific operations. Since the NFV environment is software based, the system must be able to move VNF components to balance fair and optimized resource utilization. NFVI resiliency is improved with proactive monitoring and automation - from scalability of resource pools to avoid issues, to policy based workload placement