You are currently browsing the monthly archive for July 2009.
I keep thinking about VMware’s vCloud initiative. The idea seems pretty straightforward. Companies will build private clouds in their datacenters using VMware’s vSphere technologies. Those companies will then move applications into the cloud (vCloud Service Providers) when they need more capacity. Okay, I get that. But here’s the question. Why would those companies move their applications back? Why not just leave those applications running in the cloud? The cloud will provide cost savings and scale that only the largest enterprises could hope to achieve.
The cloud is a trojan horse for VMware. They must realize that a mass move to the cloud is inevitable. So their vCloud hybrid is just a step in that direction. When you think of it this way it makes sense why VMware would invest in a service provider like Terremark. They need service providers to start buying vSphere licenses because the license volume from enterprises will eventually dwindle. Right now VMware is getting killed in the cloud. For every cloud server running on VMware’s hypervisor there are probably a hundred others running on Xen or some other virtualization platform.
Peter Laird has maintained a Cloud Computing Taxonomy for the past year or so on his blog. I find this useful to look at as I try to explain how certain companies and their platforms fit into the cloud space.
Reuven Cohen writes about the roles of the CTO and CIO with respect to the growth of cloud computing in a recent blog posting. A CTO develops new technology and a CIO implements technology. So in a world that embraces cloud computing is the CTO role necessary?
My sense is yes. The CTO should be evangelizing and socializing cloud computing within the organization. She should discuss cloud computing strategy with customers and business partners. The CIO should operationalize cloud computing and direct the migration of services from legacy infrastructure.
A successful cloud computing architecture requires strategy, planning, and execution.
Some vendors, like VMware, will tell you it’s really easy to build a cloud. Just grab a couple servers, install hypervisors, slice off a storage LUN and you are off to the races. What was called a virtualized infrastructure yesterday is now called a cloud. I guess clouds sell more licenses. It just ain’t that easy folks.
Vendors are confused. They think cloud computing is a technology. It isn’t. It’s a business methodology that leverages technology and business process. You can’t buy it in a box. Trust me; I’ve looked at a lot of boxes lately.
So how do you go about building a cloud computing platform? Well a cloud has four basic components:
The virtualization layer, data storage, and computing components are fairly straightforward. You can buy most of these commodity pieces off the shelf. The management system is the most difficult component to build or purchase. Let’s look at these cloud components in more detail.
It seems like virtualization and clouds are almost synonymous these days. Virtualization is a technology and cloud computing is a business methodology. I’m going to keep hammering that point home so bear with me. The reason these terms are confused is because pretty much every cloud computing platform uses some form of virtualization technology. Can you build a cloud without using virtualization? I guess. Heck service providers are calling almost anything they sell a cloud these days. In reality it’s hard to build a cloud without using some form of virtualization. One of the main features of a cloud is infrastructure abstraction — or the virtualization of the infrastructure from the perspective of the cloud user. Virtualization technologies are simply the easiest, cheapest, and most efficient way to provide this type of abstraction layer.
So which virtualization technology should you use to build a cloud? The first thing to understand is that from the perspective of the user the virtualization layer does not matter. It really doesn’t. Cloud users could care less whether your cloud employs VMware, Xen, or Hyper-V virtualization technology. The users only care about service availability and performance. So don’t pick a virtualization technology based on market share or public awareness. Ultimately the cloud virtualization technology should be based on your cloud management platform. The management platform will manage the provisioning and configuration of infrastructure within your virtualization layer. So it’s critical that the management platform and virtualization technology work together.
You could pick VMware as the virtualization layer because you plan to build a cloud management platform around vCenter and the VMWare APIs. The same goes for Hyper-V and Microsoft Systen Center Virtualization Manager. Or maybe you want to build a management platform around Xen and the Citrix C3 doohickey. The key point is that the cloud management platform really drives the virtualization technology decision. I’ll talk more about the management platform in a bit.
(To Be Continued)
