Microservices Expo Authors: Dalibor Siroky, Elizabeth White, Pat Romanski, John Katrick, Liz McMillan

Related Topics: @DevOpsSummit, Microservices Expo, Containers Expo Blog, @CloudExpo

@DevOpsSummit: Blog Post

Virtualization, an Implementation Detail By @bcferrycoder | @CloudExpo #DevOps #Microservices

Nowhere has virtualization made more of an impact than in Cloud Computing

In the Cloud, Virtualization Is an Implementation Detail

Virtualization is everywhere. Enormous and highly profitable companies have been built on nothing but virtualization. And nowhere has virtualization made more of an impact than in Cloud Computing, the rampant and unprecedented adoption of which has been the direct result of the wide availability of virtualization software and techniques that enabled it. But does the cloud actually require virtualization?

I think not.

What Makes Cloud Computing Cloud Computing?
According to NIST Cloud Computing has a handful of defining characteristics including on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured services. Nowhere does this say anything about virtualization, and all of these features can be obtained without a hypervisor in site.

Why Virtualization?
Without a doubt, virtualization is the fastest track to enable these cloud features. Virtualization provides:

  • Resource pooling
  • Isolation
  • multitenancy
  • Mostly instant availability
  • snapshots
  • Over-provisioning of resources
  • Server consolidation
  • Efficient disaster recovery responses
  • Reduced hardware vendor lock-in

and a host of other capabilities that ease the burden of providing cloud capabilities.

Importantly, the time-consuming and clunky manual tasks of building, installing, loading, booting, configuring, and connecting a physical server can be fully accomplished in software, which means the entire process can be encapsulated and served behind an API. This results in major gains in productivity for ops and developers and is, as discussed above, the reason that virtualization is the enabling technology for cloud.

Why Not Virtualization?
Virtualization does come at a cost, mostly in the areas of agility, performance and security. VMs are beefy, with large memory footprint, and they're not exactly quick to start up.

Performance necessarily takes a hit. Fundamentally, a virtual machine or hypervisor will allow "user" code to execute unimpeded, but when "privileged" operations are invoked, the VM must intercept and intervene, making sure these operations behave and do not interfere with the rest of the system. This interception and intervention introduces overhead.

More generally, virtualization enables multi-tenancy where several workloads or tenants share a single physical host. The process of sharing and swapping between these tenants necessarily introduces inefficiencies.

I recently had a discussion with a DevOps engineer from a significant player in the cloud security industry. He told me that their cloud-based security application services hundreds of millions of requests a day, and that by eliminating the virtualization layer they were able to realize a 5% performance increase.

Virtualization also changes the security landscape. Security architects often take advantage of hardware acceleration and other bare-metal features for encryption, entropy, and performance, and these are obscured or unavailable in a virtual environment. Also physical isolation is always more secure than anything a hypervisor can provide.

Additional downsides include potentially inconsistent performance, unpredictable behavior due to the noisy neighbor problem, and increased complexity of failure analysis due to the additional VM layer.

However, for most applications and workloads the benefits of virtualization far outweigh these downsides. But workloads with very high throughput, or those that deal with highly sensitive data, might benefit from running on a stack where virtualization isn't present.

Metal-as-a-Service: Virtual Private Cloud without the Virtual
MaaS, or Metal-as-a-Service, is basically cloud sans virtualization, and allows the delivery of cloud solutions without some of the disadvantages that virtualization brings to the table. Many cloud providers are diving into bare-metal cloud offerings.

Take a look at Canonical's MaaS which treats compute, storage, and network as commodities, much like virtualization does, but without the overhead of the virtualization layer. From their site: Metal-as-a-Service lets you treat farms of servers as a malleable resource for allocation to specific problems, and re-allocation on a dynamic basis. No virtualization here.

This is a powerful concept that allows complex full-stack apps to be deployed to the cloud, with all the above-mentioned cloud features (on demand, self-service, etc.) yet avoiding many of the downsides of virtualization.

Other IaaS Providers Joining the Metal Party
Other infrastructure providers are taking the leap into MaaS. Sign up for Mirantis OpenStack and you can instantly access a dedicated cluster of bare-metal hosts guaranteed to be yours and yours alone, with no noisy neighbors to keep you awake at night.

Other bare metal offerings are coming into play including Rackspace OnMetal single-tenant bare-metal IaaS, IBM Softlayer Bare Metal Servers, and Internap.

And you might find it Ironic that the OpenStack project, mostly focused on provisioning VMs, also has a bare-metal component well underway.

Google and Virtualization
If virtualization incurs a 5% overhead, then Google, with their gazillions of servers, could probably unplug an entire datacenter by eliminating the virtualization layer. Obviously Google is more forward thinking than this and has been building non-virtualized infrastructure for ages. The secretive Borg project and, more recently, the Omega cluster management system, provide a unified view of compute resources without the need for a virtualization layer.

Apache Mesos provides similar functionality and its adoption by Twitter shows that they too see the value of a non-virtualized infrastructure.

Containers vs. Virtualization
Containerization is like virtualization off steroids. Containers provide a homogeneous and isolated environment in which applications can safely run, much like virtualization does. But containers are less bulky, more nimble, more lightweight. Instead of the several minutes it takes to boot a VM, a fully equipped container can "boot" in under a second.

Today most container-based applications run in virtual environments, but this seems almost redundant: containerization on top of virtualization. Why not eliminate the VM layer altogether and provision the containers on bare metal?

Joshua McKenty from Pivotal has strong opinions on this matter. At a recent Cloud Foundry meetup he said: "Containers on bare metal is like having unprotected sex with the Internet."

I wouldn't go quite that far, at least not until the third date, but Josh clearly has more experience in these activities than I do. And he does have a point. Docker, for example, does not provide the full isolation between different "guests" that hypervisors do. Just ask Google: they run containers everywhere, but when they need true isolation (for example, in Google Compute Engine) they run their containers on VMs.

Naysayers aside, there's considerable work being done by Joyant and others building powerful platforms that provision and manage containers directly on the hardware.

What About Stackato?
Does Stackato run on bare metal? The short answer is yes but we don't officially support it.

A slightly longer answer: Stackato is delivered as a VM appliance, intended to be provisioned from within a hypervisor. But Stackato at its essence is a bootable Ubuntu image, highly evolved and enhanced to support all the things that make it an enterprise hardened PaaS suitable for any production workload. But it's a bootable Ubuntu image none-the-less, and Ubuntu images can be booted on physical hardware just as easily as from a hypervisor.

We don't officially support bare-metal Stackato...yet. But we could: all you have to do is ask.

In the Cloud, Virtualization Is an Implementation Detail
But really, the bare-metal vs. virtualization shouldn't matter. Virtualization is just an implementation detail. For the vast majority of applications, services, and workloads running in the cloud, the specifics of the underlying infrastructure just don't matter. Unless you're in the .0001% of applications that need crazy high performance or have security requirements that aren't acceptable to the rest of the world, then what's under the hood makes no difference.

The other 99.9999% should not be concerned with such matters. If you are, as I'm fond of saying, then you're in the weeds. Let's step back and look at the big picture. What are we really trying to achieve?

The Big Picture
This quote, from Gigaom, sums it up nicely:

We believe the simpler path for the New Stack is to give power to developers to write modern data center-scale applications against an aggregation of all of the resources in the data center, to build operational support into apps as they are created, and to avoid management of individual machines and other low-level infrastructure.

That's it! Application teams should not get mired in the complexities of the infrastructure. Instead they should be free to define their platform in terms of resource requirements, policies, SLAs, and high level security constraints, independent of the underlying architecture of the infrastructure. And this precisely is what PaaS, and other modern deployment platforms like Apache Mesos, provide.

Mesos says pretty much the same thing:

...we are also using commodity hardware. So, today, this VM model doesn't make as much sense any more. Rather than splitting up the applications onto multiple machines, we have to aggregate all the machines and present them to the application as a pool of resources.

The Bottom Line
The panacea here is to allow an app team to deliver and provision software to the data center just as easily as it can be provisioned to a laptop. The interface exposed to the development team has nothing to do with VMs, instead providing a unified view that looks the same whether deploying to a laptop or to multiple datacenters.

If you want to experience it today, in less time than it took you to read this blog, download the Stackato microcloud right now, and see for yourself what's it's like to program to your data center from the comfort of your own laptop.

The post In the Cloud, Virtualization Is an Implementation Detail appeared first on ActiveState.

More Stories By John Wetherill

Originally from Canada, John has spent much of his career designing and building software at a handful of startups, at Sun Microsystems, NeXT Inc., and more recently in the smart grid and energy space. His biggest passion is for developer tools, or more generally any tool, language, process, or system that improves developer productivity and quality of life. Without question, Stackato is one such tool and the reason why he is here. No stranger to technology evangelism, John spent several years in the late 1990's on Sun's Technology Evangelism Team spreading the Java Gospel across the globe and focusing on the prolific number of Java technologies. Now John is now returning to his roots, as a technology evangelist working for a Canadian company, albeit remotely from Santa Cruz.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.