Does the OpenStack cloud controller need to support the full set of APIs from Amazon Web Services and other public clouds? Randy Bias,Check the following list of cheap dedicated linux dedicated server. the founder and CTO of OpenStack distie Cloudscaling thinks so.
This week, as OpenStack celebrates its third birthday, Bias issued a call to arms to the OpenStack community to do what rival open source cloud controllers Eucalyptus and CloudStack are doing and embrace the full set of AWS APIs, as well as the ones created largely by Rackspace Hosting at the beginning of the OpenStack project that are not compatible with AWS.
If Amazon Web Services had decided to sell its homegrown server virtualization and cloud controller software as a retail product, like a camera or a bottle of soap, as well as its bespoke servers and storage arrays that make up its compute and storage clouds, then it is very likely that the Eucalyptus, CloudStack, and OpenStack alternatives would have never gotten off the ground, or at the very least might not be flying quite so high.
Despite many of the limitations in the AWS infrastructure cloud, and despite the desire to offer different features in a cloud than those offered by AWS, Bias has passionately argued in a blog post that the OpenStack community has to return to the roots of NASA’s original Nova compute controller β created before the space agency aligned with Rackspace to create OpenStack β and get AWS compatibility back into OpenStack.
And, if that were not enough of a tall order, Bias goes on to argue that OpenStack then has to support the full API stacks of Microsoft’s Windows Azure and Google’s Compute Engine public clouds, too β eventually.
For the moment, getting full support for the AWS APIs β in effect, making an OpenStack public or private cloud look operationally and functionally like the AWS EC2 cloud and its related S3 and EBS storage service β is paramount, and a decision that the community must make regardless of Rackspace’s desire to make OpenStack look essentially like its own public cloud’s Cloud Servers and Cloud Files services.
“The community controls the direction of the project, and it’s time we advocate a public cloud compatibility strategy that is in all our best interests, not just those of a single, albeit substantial, contributor,” writes Bias. “Failing to make this change in strategy could ultimately lead to the project’s irrelevance and death.”
With AWS refusing to let go of its server and storage designs and all of the tweaks it has made to the Xen hypervisor, the Linux operating system, and the other components that make up its infrastructure cloud, the way is open for some alternative to dominate the private cloud.
Windows by far prevails in the corporate data center, and the very good support that VMware had for virtualizing Windows made it a powerhouse in the server virtualization era. But it is not a foregone conclusion that VMware’s vCloud can become the cloud controller of choice in the corporate data center β especially not with Microsoft’s Hyper-V 3.0, Windows Server 2012, and System Center 2012 offering a less expensive and more native alternative to those who might prefer to stick with a Redmond stack.
OpenStack, like CloudStack and Eucalyptus, is more aligned to Linux workloads and increasingly the KVM hypervisor for slicing up servers, but the Xen hypervisor is still getting some love and remains popular on the biggest public clouds. No one knows what Google is using for its Google Compute Engine (GCE) infrastructure cloud, but AWS and Rackspace use variants of Xen.
The open source cloud controllers are also able to support and manage virtualized Windows workloads, however, so they have a chance of taking some share away from either VMware or Microsoft as corporations transform their virtualized server farms into clouds by adding orchestration, billing, metering, disaster recovery, and other functions to their pooled server capacity.
In the opinion of Bias, the need to fully embrace the AWS APIs β to make OpenStack look and operate like AWS β is pretty clear-cut. It’s based on an assumption that AWS will continue to dominate the public cloud market, no matter how hard Rackspace and the likes of Hewlett-Packard and IBM try to fluff up OpenStack-based clouds.
“It is clear that AWS (and quite likely GCE) will utterly dominate the public cloud race,” Bias states emphatically. “But more importantly, who cares? Dominance by AWS and GCE does not mean that OpenStack fails. In fact, OpenStack is clearly on a trajectory to ‘win’ the private cloud race, and a rapid embracing of Amazon will put OpenStack in the pole position to dominate hybrid cloud.”
Two and a half years ago, AWS and Rackspace were basically doubling their cloud businesses, according to Bias, but Rackspace’s growth in the cloud has slowed down as Google has jumped in (and Microsoft as well, which Bias did not mention) and AWS has continued more or less on its trajectory.
Rackspace wanted to “control the innovation curve” like Amazon does with its public cloud, Bias argues, and therefore not only started OpenStack with NASA, but also was able, through the acquisition of ANSO Labs, to pick up the NASA people familiar with the Nova compute controller and get them to essentially shift to Rackspace’s own Cloud Files API set. And now, says Bias, it is time to shift back.
“OpenStack can be in control of the innovation curve in private and hybrid cloud, but doing so requires that we support the services that are leading the innovation curve in public cloud,” Bias writes. “For OpenStack to dominate innovation in private and hybrid, it must embrace the public clouds to which enterprises want to federate.”