The vSphere Cloud Operating System: Extra Layer, Extra Cost?

The vSphere Cloud Operating System: Extra Layer, Extra Cost?

  • Comments 3
  • Likes

Hi, I’m David Greschler, director of Microsoft virtualization and management. Today VMware announced their new “Cloud OS,” called vSphere.  It’s an interesting announcement in that it points out more clearly than ever that VMware adds an extra layer to the computing stack.

 

This extra layer, a virtualization “substrate” (VMware CEO Paul Maritz’s words), is inserted by VMware between hardware and the OS.  But is it really necessary to add an extra layer just to do virtualization and the cloud? Do we really need another operating system to effectively just host other operating systems?

 

I can see how initially this made sense when the industry was first experimenting with virtualization. But virtualization has now become mainstream, and as such it’s just another feature we should have as part of our computing process. As a result, Microsoft chose to take a more streamlined approach to virtualization. Instead of adding an additional layer of complexity, we’ve put the virtualization component inside the OS. We think this is a better approach as it means you have one less layer to manage, secure and pay for. (And at the cost of $3,495 per processor for vSphere Enterprise Plus, that’s a pretty expensive layer!).

 

But what about cloud? There’s a lot of talk about how vSphere lets enterprises build “private clouds.” This concept, of a dynamic datacenter where additional compute power can be provisioned on-demand, is something Microsoft has already been talking about for over six years with our Dynamic IT initiative. But does it need an extra layer? We have been developing Windows Server 2008 with System Center, as well as development tools and an application platform, with the Dynamic IT vision all along. The industry terms may have changed from “dynamic datacenter” to “private cloud” but the fact remains that these products today already provide the foundation for building a private – and hosted – cloud infrastructure. After all, the cloud isn’t about throwing away your old applications; it’s partly about taking your existing applications and making them more flexible, extensible and distributed. That’s what Windows Server 2008 and System Center are all about. And customers agree. Take a look at what Kroll Factual Data did with the two products to build their own private cloud. Check out what Lionbridge Technologies did with their Virtual Cloud Lab.

 

In other words, you don’t need an extra “cloud operating system” to build a cloud running Windows Server. Just use Windows Server.

 

If you’re an existing VMware 3.x customer who’s considering migrating to VMware’s new Cloud OS, try the combination of Windows Server 2008 Hyper-V and System Center first. You’ll see that System Center can manage both your VMware and Hyper-V deployments from the same console, as well as both your virtual and physical infrastructure. And compare costs: VMware vSphere’s extra layer is approximately three to five times the cost of Microsoft’s solution, while just yesterday Zane Adam announced in this blog that Microsoft Hyper-V Server R2, which includes live migration and high availability, will be free of charge.

 

vSphere may be the best reason yet to move to Microsoft’s virtualization solution.

 

David Greschler

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • <p>Today, David Greschler, director of Microsoft virtualization and management, commented on the announcement</p>

  • <p>Pessoal, Essa semana um dos maiores players de mercado em Virtualiza&#231;&#227;o (VMWare) fez alguns an&#250;ncios</p>

  • <p>237 Microsoft Team blogs searched, 103 blogs have new articles in the past 7 days. 273 new articles found</p>