Source: Flickr user arnemontanus
Rackspace this week joined the ranks of those companies offering virtual machines that are hosted on a pool of dedicated servers. What’s curious, however, is that Rackspace refers to these setups as private clouds, yet lists them under its managed hosting offerings, not its cloud hosting products. Such a move once again raises the question of what, exactly, is meant by “cloud computing.”
If Rackspace’s Private Cloud offering is, indeed, a cloud offering, why does it fall under the managed hosting banner? Similar offerings by hosting veterans Savvis and Terremark are marketed as cloud computing solutions only. Layered Technologies clearly distinguishes between VMs housed on its multitenant architecture (virtual private data centers) and those housed on dedicated servers. GoGrid only crosses paths with its dedicated hosting parent company, ServePath, for a hybrid cloud-dedicated offering called Cloud Connect.
Rackspace’s approach, by comparison, could prove confusing to potential customers. Those who think they need a cloud offering but really want something more managed might not, for example, make the connection between the company’s Cloud Servers, a public cloud option, and its Private Cloud managed hosting offering. And those fearful of cloud computing might not be able to separate in their minds the dedicated nature of Rackspace’s new offering from its cloud label. Private Cloud also features a pricing model that is far more complex than most pay-for-what-you-use public cloud services.
At this point, it may be foolish to expect members of the highly competitive managed hosting market to agree on standard definitions of what is and is not cloud computing, but they should at least set forth clear features that differentiate one from the other (e.g., multitenant vs. dedicated, automated provisioning vs. manual provision, automatic load-balancing, etc.). If there must be delineation, prudence dictates making it as clear as possible.