Steve Clayton, a blogger working in the Software + Service field at Microsoft, criticizes the term "private cloud" in his latest post. He cites Joe Weinman, who claims in his article 6 Half-Truths About the Cloud:
- Poll: How reliable are ChatGPT and Bing Chat? - Tue, May 23 2023
- Pip install Boto3 - Thu, Mar 24 2022
- Install Boto3 (AWS SDK for Python) in Visual Studio Code (VS Code) on Windows - Wed, Feb 23 2022
By analogy then, a “private cloud” makes as much sense as would be something like a “personal hotel". This is more than semantics — it’s economics.
I am not sure if the term "personal hotel" makes sense, but "private hotel" does. Some organizations own hotels at which only their members can stay.
I think that Joe Weinman and Steve Clayton made the mistake of interpreting "cloud computing" as an economic term. In their view, cloud computing is a new kind of business that provides a certain service to the public. Therefore, private clouds seem to make no sense at all.
However, "cloud computing" is most often used as a technical term. It is a new technology that can be used for different purposes. You can make a business out of it, companies can use it in their data centers, and you can also have it in your garage.
This doesn't mean that the term "cloud computing" is always used in the same way. It is a relatively new technical concept, so it is only natural that people aren’t using it consistently and often disagree as to its meaning.
In my view, cloud computing introduces a new virtualization level in IT. In the beginning, there was only hardware virtualization. For example, the virtualization of a hard disk is a virtual disk. Hardware virtualization allows you to run multiple operating systems on a computer. The point about hardware virtualization is that multiple operating systems share a certain piece of hardware.
The next step is what could be called location virtualization. If you only do hardware virtualization, you still know on which computer the guest operating system is running. But if the virtual machines location is virtualized, it doesn't matter anymore on which host the guest OS resides. This doesn't mean that the OS isn't actually running on a specific computer. The point is that the system administrator doesn't have to care about the location of a virtual server.
For me, cloud computing is nothing more than "location virtualization". This kind of virtualization is not only about the operating system. You can also run a specific application in the cloud, say Internet Information Server. The main point about Windows Azure is that it doesn't really matter on which machine your web server is running. Virtualized servers in the cloud don't just share a piece of hardware, they share multiple machines or a whole data center.
The advantage of cloud computing is that it scales much better than hardware virtualization. With hardware virtualization, the administrator still has to move a virtual server manually from one computer to another if performance problems arise. Some server virtualization solutions can do this more or less automatically, but the admin is still aware of the location of a specific server. In cloud computing, the location of the guest OS or virtual application becomes totally unimportant. Scalability here means that you only have to add a new server to extend resources and let the cloud OS do the rest.
Subscribe to 4sysops newsletter!
Therefore, private cloud computing makes a lot of sense. It even makes sense for small businesses with only a couple of servers. Rest assured that Microsoft and others will soon offer the corresponding technology for private businesses. Perhaps one of the successors of Virtual Machine Manager will just be called Cloud Manager.
Maybe the private cloud equivalent of the hotel is the “corporate dormitory” — on-demand, highly configurable, pay-as-you-go resource for the business.
I think cloud will end up being about more than location virtualization. I think it also implies some of these things as well — from Surgient CTO via Mike D: http://www.mikedipetrillo.com/mikedvirtualization/2009/04/the-five-defining-characteristics-of-cloud-computing.html#more-524
And what’s wrong with the idea of a personal hotel? Hotels are defined by the services they provide, not to whom they provide them. Even that analogy is in agreement with you, as the “cloud” is defined by what it does, not for whom.
Thanks for answering a question I’ve had for a while, in Cloud computing a server image can span multiple hardware servers.
How much overhead, network/disk/cpu would setting up an in-house cloud to run on unused cycles on the “average” users desktop outside of the data center. In theory that way you could have a resource available to handle peak loads.
John, thanks for the link. I don’t agree with the author of this post though. I think all the characteristics he names are not defining, but just typical features of cloud computing. For example, this consumption-based billing (or pay-as-you-go pricing as I call it) is certainly not a defining. We will soon see cloud providers that will offer flat rates. Shall we stop calling it cloud computing just because they changed their pricing model? In my view, location virtualization of guest operating systems is the only feature that is unique to cloud computing and it can’t be replaced by another feature. Therefore, it qualifies as a real defining feature.
Adam, you are right. A hotel that hosts only one person is still a hotel. I just never heard of such a hotel whereas private hotels, i.e. hotels that are not for the public, do certainly exist.
ron, that applies also to other technologies that improve scalability. The new thing about cloud computing is the way it virtualizes resources.