ONAP

Virtual Network Function Orchestration (VNFO) Market Overview: VMs vs Containers

Posted on by Alan Weissberger

by Kaustubha Parkhi, edited by Alan J Weissberger

Cloud-native network functions (CNF) promise to change the dynamic of telecommunications network function engineering. The advent of 5G has added impetus to this change. Insight Research is at the cutting edge of CNF market analysis.  Here are a few excerpts from our new report on the Virtualized Network Function Orchestrator (VNFO) market

Insight Research considers Virtual Machines (VMs) and Containers to be the major Virtual Network Function Orchestration (VNFO) methodologies.  Network functions synthesized using VMs and Containers qualify as Virtual Network Functions (VNFs), in our opinion.  That latter term has taken on much broader context since it was first introduced in the context of Network Function Virtualization (NFV) at the OpenFlow World Congress in 2012.

VNFs orchestrated by Containers are sometimes referred to as cloud-native NFs (CNFs).  Insight Research has also employed this term as early as 2020. Over time however, we have observed that the usage of CNFs is neither consistent nor uniform.

Most ‘traditional’ Management and Orchestration (MANO) schemes such as ONAP, OSM and all proprietary offerings now support Containers and Kubernetes [1.]. Containers are thus one more mean towards achieving the end-objective of VNFs.   As such, Insight Research finds it more appropriate to use VNF as an umbrella term and refer to VM or Container as the specific virtualization methodology.

Note 1.  Kubernetes, also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications.

The question then arises – where would we slot network functions (NFs) orchestrated by containers encapsulated in VMs? Answer is containers. Similarly, NFs orchestrated by VMs encapsulated in containers are slotted under VMs.

The table below breaks down the VNFO market by virtualization methodology.

We see Containers gaining major market share from VMs such that they are running away with the VNFO market.  The advantages of containers over VMs are all well known. Containers are sleeker and when employed with optimal microservice granularity – considerably faster as well.

Additionally, VMs have a head start over containers and have established a solid legacy which will hold good for near to midterm future.  However, barriers surrounding container adoption are gradually dissolving with differing momentums across end-applications. The greater the performance differential, the greater is the adoption potential for Containers in end-applications.

Initiatives such Nephio have placed Kubernetes in the center of the VNFO universe. In short, it’s a matter of time before Containers push VMs to be the dominant VNFO virtualization vehicle.  However, many question arise.

Here are a few questions for starters:

 Is the NFVO the same as service orchestrator?
 Is the NFVO the same as SDN controller?
 Is Kubernetes an orchestrator?
 Since containers and VMs can be embedded inside one another, how do we stamp which virtualization methodology they are using?
 If a proprietary MANO uses portions of open source code, should it be considered proprietary?

After picking the brains of numerous experts who were unfailingly patient in unravelling their thinking, Insight Research has been able to arrive at a set of clearcut definitions and assumptions that address the above queries and more.

To buy the report or download an executive summary, please visit:

https://www.insight-corp.com/product/vnfo-ripe-for-change/

OCP – Linux Foundation Partnership Accelerates Megatrend of Open Software running on Open Hardware

Posted on by

“From 1876 to 2013 telecom and network equipment design was proprietary….We are now in the 3rd phase of open networking transformation,” said Arpit Joshipura, Linux Foundation GM of Networking at the 2018 OCP Summit.   The network equipment design  transformation is shown in the figure below:

During his OCP Summit keynote speech, Arpit announced a partnership between OCP and the Linux Foundation to further the development of software and hardware-based open source networking. The organizations will work together to create stronger integration and testing, new open networking features, more scalability, a reduction in CAPEX/OPEX, greater harmonization with switch network operating systems, and increased interoperability for network functions virtualization (NFV) network transformation.

Virtualization of network functions and the resulting disaggregation of hardware and software have created interest in open source at both layers. OCP provides an open source option for the hardware layer, and The Linux Foundation’s OPNFV project integrates OCP along with other open source software projects into relevant NFV reference architectures. Given this alignment, OCP and OPNFV already have been collaborating on activities such as plugfests and joint demos. Now they have committed to expanded collaborative efforts which will accelerate the megatrend of totally open networking.

“It’s exciting to see the principles of open source software development come to hardware, and OCP has already made a substantial contribution to some Linux Foundation project plugfests and demos,” said Arpit Joshipura in the referenced press release. “We see OCP as an integral partner as we explore new opportunities for NFV deployments, performance, features, and footprint. Global network operators agree and ranked OCP very high on a list of the most important projects for OPNFV in a recent survey. We look forward to continued and intensified collaboration across ecosystems.”

The key market disruptors- virtualization of equipment functions, software defined networking and disaggregation of equipment are shown below with the applicable software and hardware entities on the left, and sample open source projects on the right of the figure below.

Arpit said the drivers behind this huge move to open source software running on open source hardware are 5G and the Internet of Things (IoT).  Mandatory automation of functions (e.g. provisioning and configuration) are (and will be) required to support the high speeds/low latency of 5G and the huge number of IoT endpoints.

The Linux Foundation Networking (LNF) group’s vision includes automating cloud services, network infrastructure, and IoT services as shown in this illustration:

The Linux Foundation Open Source Networking activities include participants from telecom carriers, cloud computing, and enterprises. As shown in the illustration below, 9 out of 10 of the most important projects of participants will use open source software with all 10 of the largest network equipment vendors actively involved and 60% of global subscribers represented.  Shared innovation and a 15 minute “new service creation time” are selected goals of the LFN projects.

The .Linux Foundation is leading the way forward to harmonize open source software efforts and get them into the community. In the figure below, the services, software and infrastructure are shown on the left, the various open source projects are shown in the center, and the various standards organizations (but not the actual standards) are shown on the right.  It should be duly noted that there are no official standards bodies working on open networking specifications to provide multi-vendor interoperability of exposed interfaces or even APIs within a single piece of equipment.

To clarify that point, Arpit wrote via email:  “LFN (which hosts ONAP), is working on de-facto automation open source aspects independent of 5G/4G. The 5G services mandate automation due to IOT and new services that are coming up. The specific specs of 5G are out of scope for Networking Automation. OCP and LFN partnership is limited to what I spoke at the OCP Summit keynote.”

Note:  There are more than 20 open source projects for networking currently active at the Linux Foundation (see above illustration).  LF also has expanded lately into areas as diverse as software for IoT devices, storage and blockchain.  It remains to be seen if the OCP – LNF partnership will create defacto standards (e.g. for virtualization of functions in 5G or IoT) or try to enforce interoperability through certification programs. The current motivation seems to come from carriers like AT&T which are demanding open source software on open source hardware to lower their CAPEX/OPEX and to improve automation of network functions.

…………………………………………………………………………………………………………………………………………………………………………………………………………………

Mr. Joshipura asserted that the LFN+OCP partnership would produce the very best of Open Source Software & Hardware.  The total community collaboration will include: Hardware Vendors + Silicon Vendors + OEM/Manufacturers + Software Vendors, Systems Integrators + End Users.

…………………………………………………………………………………………………………………………………………………………………………………………………….

Arpit provided a strong conclusion via email:

“Open source networking software is creating de-facto platforms that result in faster innovation across many IT communities. Collaboration between the leaders in open hardware (OCP) and Open Source Software (Linux Foundation Networking) will help propel this even further and broaden the scope of true open networking. This industry collaboration allows faster deployment, but still offers innovation on top.”

 

Windstream Joins ONAP & Open Source Telco Movement Led by AT&T/ China

Posted on by

Windstream Communications has become a corporate member of the Open Network Automation Platform (ONAP) Linux Foundation project, joining an open-source technology initiative for the first time.

ONAP was formed through the merger of open source ECOMP (contributed by AT&T) and Open Orchestrator Project (OPEN-O), two of the largest open source networking initiatives.  It was the big hit of the 2017 Open Networking Summit as we reported in this blog post.

The ONAP Project is focused on creating a harmonized and comprehensive framework for real-time, policy-driven software automation of virtual network functions. ONAP includes participation by prominent networking suppliers and industry-leading service providers from around the world. It’s primary objective is to enable software, network, IT, and cloud providers and developers to rapidly create new services which can be monetized.

The ONAP draft architectural principles, presented at their May 2017 meeting at AT&T Bell Labs in NJ, can be read here.

……………………………………………………………………………………………….

“Combined with our rapid advances in SDN, Windstream’s participation in ONAP increases the value of our network for all of our customers, as we move to virtualization and cloud-based technologies that offer affordable and efficient next-generation services,” said Art Nichols, vice president of network architecture and technology for Windstream.

“For example, not only does our SDNow solution offer automation and accelerated service delivery, but it forges the path that will allow us to deliver flexible, on-demand services across our multi-vendor network ecosystem.”

“Traditionally, we have always worked with engineering groups and maybe a little bit with IT on the back side” in planning this kind of transition, Windstream’s Jeff Brown told Light Reading in an interview.

“In this new world, you are blending IT and engineering and a lot of crossover resources. So, from the IT perspective, [ONAP] was called out as a group that was taking the leadership role as far as developing open standard work with other companies we have similarities with and with some of our vendors as well.”

Windstream has been informally monitoring multiple open source efforts and supporting the concept of open source for some time now, Brown told Light Reading.  The move to more actively engage in orchestration through ONAP was driven by the growing influence of Windstream’s IT department in its transition to software-defined networking, he added.

“In any type of industry forum, whether standards-based or not, you have to make the determination of what kind of resources you can dedicate to it,” Brown notes. Having just come out of meetings around MEF and proofs-of-concept for its 2017 event, he says the same discussions come up there. “We don’t have groups allocated that can do that type of thing and work with vendors,” he says.

Windstream is the third North American service provider to join, after AT&T and Bell Canada Enterprises. ONAP now has 17 platinum and 22 silver members. The other service providers signed onto this Linux Foundation project include China Mobile, China Telecom, Orange, China Unicom and PCCW.
Carol Wilson of Light Reading opined that Windstream is likely to start off with ONAP as more of an observer than a leader. “Although that may change over time,” Brown said.  The next ONAP meeting is being held in China, and Brown is unsure whether the company will send a representative as a result.
“That [long distance travel] would be highly unusual for us.” Brown added that joining ONAP and getting more involved over time is nonetheless important because of the need to speed up the process of getting to industry consensus, moving faster than the traditional telecom standards process.
“It’s no doubt that waiting for standards to develop in the traditional telecom community can be quite painstaking….We have seen other greenfield entrants, hyperscale companies, come in with an open source approach with no standards and make a huge commercial presence, impacting markets in a big way very quickly.  That is the kind of agility and nimbleness we need to thrive in the industry.”
In the long run, open source “is just a means to an end to be able to provide our solutions,” he told Light Reading, enabling the telecom industry to coalesce “around things similar to what we are seeing [with] all the web-scale providers.”
……………………………………………………………………….
References:

Archives