Spirent presents a survey of today’s NFV MANO landscape and discusses the challenges faced by the ecosystem in their efforts toward mass deployment of NFV. In the on-demand version of this webinar, Spirent shares their best practices for testing MANO components and use cases.
Spirent NFV MANO Report Webinar: MANO a MANO: The Battle for NFV Orchestration
The ETSI NFV architecture defines MANO as the combination of the NFV Orchestrator (NFVO), the VNF Manager (VNFM) and the Virtual Infrastructure Manager (VIM). Dozens of established vendors, startup companies, standards bodies and open source initiatives are in the mix, defining requirements and developing working code. Not surprisingly, the MANO domain is emerging as the biggest battleground in the NFV marketplace and it is widely believed that success of NFV deployments is heavily dependent on the successful integration of the various MANO components from multiple vendors.
The webinar presents a survey of the MANO landscape and highlights the Orchestrator, VNFM and VIM vendors who have participated in recent multi-vendor MANO public tests. The webinar also addresses some of the challenges that can impede the fast deployments of NFV, with a focus on the following:
- Multiple open source initiatives (Open source MANO and ONAP) and their respective ecosystems are attempting to define interfaces and develop reference platforms. Spirent discusses the merits and demerits of having two, potentially competing, open source initiatives.
- The industry has not yet coalesced around a dominant MANO architecture. Some ecosystems and implementations combine NFVO and VNFM, others treat them as separate entities. There are significant user interface and RESTful API differences between MANO vendors. There are even VNFD coding differences between vendors. Is it time to standardize the interfaces? Should the standards bodies stay away from standardizing software interfaces?
Spirent presents unique test methodologies and best practices for validating the MANO components, including VNF and network services lifecycle management. Spirent believes that thorough validation is necessary to ensure reliable NFV deployments. Spirent shares lessons learnt from validation of MANO components in a multi vendor environment and will present a use case validation of the following two VNF lifecycle events: a) VNF instantiation and time need to complete instantiation, and b) VNF autoscaling via instantiation of new VNF components.
Having worked closely with dozens of vendors and service providers, Spirent concludes by providing their perspectives on how to overcome the challenges that the NFV ecosystem is facing today and accelerate deployments.
By clicking the links above, I consent to share my contact information with the sponsor(s) of this content.