& cplSiteName &

From Virtualization to Cloudification

James Crawshaw
5/5/2017
50%
50%

A recent article in The Economist (Cloudification will mean upheaval in telecoms) describes the cloudification of telecom as the softwarization of networks. It references the ambition of Alex Choi, SK Telecom's CTO, to make radio the fourth component of cloud, after computing, storage and networking. It also refers to AT&T's ECOMP project which was recently folded into the Chinese-led OPEN-O initiative to create ONAP. The Economist also speculates on the terrifying (for operators) prospect of an Amazon Telecom Services.

Virtualization and cloudification (or cloud computing) are often used interchangeably but they are different concepts. Virtualization increases the utilization of hardware resources, running more software on a given amount of physical infrastructure. The virtualization could be at an operating system level or a network, compute or storage resource level.

Cloud computing, on the other hand, refers to the delivery of shared computing resources on demand through the Internet (public cloud) or enterprise private networks (private cloud). The beauty of public cloud services such as AWS is that they are self-serve (a credit card is all you need), highly automated, elastic/scalable and pay-as-you-go (I mentioned the credit card, right?). Cloud computing makes use of virtualization to enable the elasticity and achieve economies of scale.

So, in an NFV context, all equipment vendors need to do is port their applications that currently run on ASICs and FPGAs to run on virtual machines (VMs) running on x86 processors, right? Er, no. Most physical network functions are stateful applications, that expect to have local storage and a custom ASIC for packet processing, and are designed to scale up. Cloud-native applications have a clear separation between application processing and the associated data. The application is stateless and the states (data) are stored in "the cloud." Unless we re-architect the application to be stateless we gain few of the benefits of cloud computing. With enhanced performance of CPU, network and storage I/O, stateless applications can now achieve high performance while being easier to scale out and recover from failure.

Where these re-architected VNFs run in the network will depend on their latency and reliability requirements. Certain BSS and OSS elements could be centralized in a core data center with strong disaster recovery capability if they are critical but not latency-sensitive. Conversely, video CDN or IoT applications might be deployed closer to the users in edge data centers to ensure low latency.

Huawei Technologies Co. Ltd. sees four key challenges to building a telco cloud architecture: 1) interoperability; 2) automation; 3) reliability; and 4) adaptability.

Interoperability
Current telecom networks comprise multiple network functions from myriad vendors. Interoperability tests, such as those of the NIA, are important to verify VNFs work together nicely in a cloud environment. Even if different vendors say their products are based on standard platforms such as OpenStack, they might not necessarily interoperate well with each other. The TriCircle project is an initiative to drive greater interoperability between OpenStack participants with the aim of enabling greater automation.

Automation
To be useful, cloudification should increase the efficiency of operations and make telcos more agile in the deployment of new services. A key part of this is a culture change to DevOps which enables more regular updates of applications and easy roll back should an update have unexpected consequences. DevOps introduces new tools for IT maintenance including technologies such as containers which enable greater utilization of hardware resources and therefore greater operational efficiency.

Reliability
As much as we all love the cloud, there is still an expectation of high reliability and availability of telco services. This requires DC-level and system-level reliability design, including concepts such as active-standby and active-active disaster recovery (yes, active-active is a thing). A hierarchical solution can ensure every layer has its availability design. For example, in the VM layer, OpenStack has tools to enable high availability without a single point of failure.

Adaptability
Cloud networks must adapt to the diverse workloads of CSPs such as high forwarding, high throughput, or low latency. One size does not fit all. For some applications, VMs running on x86 chips are simply not going to meet all requirements and may require the use of physical network appliances (hybrid NFV) such as core routers. In some cases, such as DPI, a VNF might run on a VM but offload some workload onto an FPGA. Of course, some techniques, like DPDK-accelerated Open vSwitch, can enhance the packet forwarding power of a VM. And the capability of ARM-based servers is increasing all the time. As such, not only do telco cloud networks need to be adaptable, so too do telco cloud architects.

This blog is sponsored by Huawei.

— James Crawshaw, Senior Analyst, OSS/BSS Transformation, Heavy Reading

(3)  | 
Comment  | 
Print  | 
Newest First  |  Oldest First  |  Threaded View        ADD A COMMENT
SeniorCo80666
100%
0%
SeniorCo80666,
User Rank: Lightning
5/9/2017 | 4:44:11 AM
Virtualization to Cloudification
Good article. No doubt that network function virtualization is the basic evolution step service providers want to go through, but to benifit most from it, they must gradually adopt network function cloudification. Decoupling software from hardware only, surely not enough, the software or network functions should be rearchitected or recoded so that carrier class reliability can be ensured over general purpose IT hardwares. Presumably, rearchitecting the network functions into 3 different layers and ensure stateless process layer is the basic requirement for the cloud native/cloudification phase.    
t.bogataj
50%
50%
t.bogataj,
User Rank: Light Sabre
5/8/2017 | 1:52:59 AM
Re: Different
"It is good to make sure people do know the difference though."

Not to mention it is vital people hear what Huawei has to say about it.

T.
danielcawrey
50%
50%
danielcawrey,
User Rank: Light Sabre
5/7/2017 | 12:35:52 PM
Different
Totally agree. Virtualization and cloud are quite different, although they can be used together to create some pretty useful technology. 

It is good to make sure people do know the difference though. 
More Blogs from Heavy Lifting Analyst Notes
Three strategic initiatives &ndash Novitas, Stratus and Sentio &ndash have powered Colt's move into on-demand services.
Next week at BCE, we'll look at some of the ways machine learning and AI will help operators make the customer experience better, without driving up the cost of network operations.
The Aussie operator is trying to reinvent itself, and its network-as-a-service is a vital piece of the transformation puzzle.
Every network operators business case is different but what remains true is that combining the disciplines needed to get value from data requires a very collaborative organization.
Universal customer premises equipment (uCPE) systems are growing rapidly, paving the way for new opportunities, lowered costs and increased performance overall.
Featured Video
From The Founder
Light Reading founder Steve Saunders talks with VMware's Shekar Ayyar, who explains why cloud architectures are becoming more distributed, what that means for workloads, and why telcos can still be significant cloud services players.
Flash Poll
Upcoming Live Events
June 26, 2018, Nice, France
September 12, 2018, Los Angeles, CA
September 24-26, 2018, Westin Westminster, Denver
October 9, 2018, The Westin Times Square, New York
October 17, 2018, Chicago, Illinois
October 23, 2018, Georgia World Congress Centre, Atlanta, GA
November 7-8, 2018, London, United Kingdom
November 8, 2018, The Montcalm by Marble Arch, London
November 15, 2018, The Westin Times Square, New York
December 4-6, 2018, Lisbon, Portugal
All Upcoming Live Events
Hot Topics
What VeloCloud Cost VMware
Phil Harvey, US News Editor, 5/21/2018
NFV Is Down but Not Out
Iain Morris, News Editor, 5/22/2018
TM Forum Sea-Change Overcomes That Sinking Feeling
Iain Morris, News Editor, 5/17/2018
Has AT&T Inked a Deal With Google for TV?
Mari Silbey, Senior Editor, Cable/Video, 5/18/2018
Animals with Phones
Live Digital Audio

A CSP's digital transformation involves so much more than technology. Crucial – and often most challenging – is the cultural transformation that goes along with it. As Sigma's Chief Technology Officer, Catherine Michel has extensive experience with technology as she leads the company's entire product portfolio and strategy. But she's also no stranger to merging technology and culture, having taken a company — Tribold — from inception to acquisition (by Sigma in 2013), and she continues to advise service providers on how to drive their own transformations. This impressive female leader and vocal advocate for other women in the industry will join Women in Comms for a live radio show to discuss all things digital transformation, including the cultural transformation that goes along with it.

Like Us on Facebook
Twitter Feed