OpenStack for NFV
As we know, OpenStack is mainly known to be the largest pool of open source projects which collectively form the software platform for cloud computing infrastructure. This infrastructure is used widely in private cloud use cases by many enterprises. After an introduction of NFV by ETSI, OpenStack has emerged as a key infrastructure platform for NFV. In most of the NFV deployments, OpenStack is used at VIM (Virtual Infrastructure Manager) layer to give a standardized interface for managing, monitoring and assessing all resources within NFV infrastructure.
Various OpenStack projects (like Tacker, Neutron, Nova, Astara, Congress, Mistral, Senlin, etc) are capable of managing virtualized infrastructure components of NFV environment. As an example, Tacker is utilized to build generic VNF Manager (VNFM) and NFV Orchestrator (NFVO) which helps in deployment and operation of VNFs within NFV infrastructure. Additionally, integration of OpenStack projects introduces various features to NFV infrastructure. Features include performance features like huge pages, CPU Pinning, NUMA topology and SR-IOV; service function chaining, networking slicing, scalability, high availability, resiliency and multisite enablement.
Telecom service providers and enterprises have implemented their NFV environment with OpenStack: AT&T, China Mobile, SK Telecom, Ericsson, Deutsche Telekom, Comcast, Bloomberg, etc.
Open Source Mano (OSM) for NFV
MANO layer is responsible for orchestration and complete lifecycle management of hardware resources and virtual network functions (VNFs). In other words, MANO layer coordinate NFV Infrastructure (NFVI) resources and map them efﬁciently to various VNFs. There are various options available as three-dimensional software stack for MANO. But ETSI hosted OSM is largely preferred due to large activity at the community level, highly mature framework, production readiness, easy to initiate and constant feeding of use cases by members.
Virtual Network Functions (VNFs), forms a network services may need updates for feature addition or patch for functionalities. OSM provides a method to invoke the VNF upgrade operation with minimal impact in the running network service.
With the continuous community support and involvement for feature innovation, OSM has now evolved to bring CI/CD (Continuous Integration and Continuous Delivery) framework at MANO layer.
The latest release 4 of OSM has brought large set of features and enhancements to OSM framework which has impacted functionality, user experience, and maturity which enables various enhancements for NFV MANO from usability and interoperability perspective.
OSM has steadily adopted the cloud native principles and can be easily deployed in the cloud as installation is container-based and run with the help of container orchestration engine. A new northbound interface is introduced which is aligned with ETSI NFV specification SOL005 provides dedicated control of the OSM system. Monitoring and closed‐loop capabilities have also been enhanced.
The next version of OSM release 5 is expected to be launched in November 2018 and will be bundled with more 5G-related features, like Network Slicing and container-based VNFs.
Why OpenStack + Open Source MANO for MANO layer in NFV?
Both OpenStack and OSM have a large community that have a rapid pace for innovating NFV & higher contribution by all scale companies to enhance current features and develop new capabilities for core projects under it.
For NFV case, OpenStack standardized interfaces between NFV elements and infrastructure. OpenStack is used for commercial solutions offerings by companies like Canonical/Ubuntu, Cisco, Ericsson, Huawei, IBM, Juniper, Mirantis, Red Hat, Suse, VMware and Wind River. A large percentage of VIM deployments are based on OpenStack due to the simplicity in handling and operating various projects targeted towards providing full potential storage, compute and networking for NFVi.
With last 2 releases (3 & 4), OSM has evolved a lot to support integration for cloud-native approach by enabling CI/CD frameworks into orchestration layers. Cloud readiness involvement of OSM is the key benefit along with OpenStack which has proven architecture for private as well as public clouds. OSM deployment into NFV infrastructure has become very lean where one can start with importing docker containers into production. On the other hand, OpenStack is known for enabling simplicity to manage virtualized & containerized infrastructure. Organizations can realize full benefits out of integration as NFV MANO using OSM and OpenStack due to lean and simple management and deployment.
Latest posts by Sagar Nangare (see all)
- Demystifying Persistent Storage Myths for Stateful Workloads in Kubernetes - October 18, 2019
- How is Kubernetes Leading the Game in Enabling NFV for Cloud Native? - September 10, 2019
- Analysis of Kubernetes and OpenStack Combination for Modern Data Centers - September 6, 2019