Blog Post

OpenStack faces the terrible twos

Stay on Top of Enterprise Technology Trends

Get updates impacting your industry from our GigaOm Research Community
Join the Community!

OpenStack turns two this week. That means the open-source project — which fancies itself the Linux of the cloud — is entering a critical stage of its development process.

[company]Rackspace[/company] — which helped give birth to OpenStack in July 2010 — rolled out some stats to show OpenStack momentum and to push its OpenStack-as-Linux comparision. For example,  in the 84th week of the project, there were 166 entities contributing to the effort whereas it took Linux 828 weeks to hit 180 active contributors, according to Rackspace’s tally.

By that count — and the fact that Internap, Hewlett-Packard(s hpq), and Rackspace itself have OpenStack clouds in some degree of production — shows pretty fair momentum going into year three. Whether that’s enough to form a competitive counterweight to Amazon(s amzn) Web Services and VMware(s vmw) vCloud’s heft remains to be seen. And some competitors (most notably Eucalyptus’ CEO Marten Mickos) maintain that OpenStack has too many cooks in the kitchen. At GigaOM Structure last month, Mickos said OpenStack, rather than following in Linux’ footsteps, could become “the Unix of cloud.” The implication was that so many vendors weighing in could lead to a forking or fracturing of the OpenStack standard.

Fear of fracturing

The project is transitioning from an effort largely driven by Rackspace to a broader  OpenStack Foundation with control to be spread among several vendors including Platinum members AT&T(s t), Canonical, HP, IBM(s ibm), Red Hat(s rhat) and SUSE joining Rackspace. (Gold members include Cisco(s csco), ClearPath Networks, Cloudscaling, Dell(s dell), Dreamhost, Morphlabs, NetApp(s ntap)  and Yahoo(s yhoo)). There is precedent for this model succeeding. The Eclipse Java IDE really took off once IBM ceded control to a multi-vendor foundation.

Jim Curry, GM and VP of Rackspace Cloud Builder, one of the early instigators of the OpenStack effort, is clearly bullish on the project’s prospects but acknowledges its challenges as well.  “Any open-source project that is not controlled by one vendor but with lots of folks with their own agendas is at higher risk of fracturing — the advantage of single-vendor or close-to-single-vendor projects is that there is more control in the short term and a shorter time to market,” he told me in a recent interview.

But, in his view,  that dynamic shifts over time. “For continuing, rapid innovation it’s up to the community to determine if standards, interoperability are important. It’s hard to make that judgement now because OpenStack is still really early.”

There has already been agita among the OpenStack alliance with Citrix, an OpenStack backer, reversing course in April, setting up its more mature CloudStack as a rival open source cloud platform.  Now there  is concern in some quarters that even some of the Platinum partners are hedging their bets with OpenStack, while pursuing their own potentially competitive projects. Red Hat’s CloudForms is one example. (For the record, Red Hat paints CloudForms as complementary, not competitive, with OpenStack although some of its own partners said there is deep confusion on that point among customers evaluating cloud options.)

Curry said there have been some vendors — although he stressed that he does not count either HP nor Red Hat among them — that have used the OpenStack brand for its marketing value while not fully buying into the mission.  “Red Hat and its CTO Brian Stevens are big backers  and they’ve contributed a lot of code but large companies like that often have competing solutions. Some of them launched before OpenStack, but I love the contributions from those companies and others.”

Bottom line: Choice is good

Curry holds true to OpenStack’s early mantra: customers need choice in their cloud deployment options.  “Cloud was not this big two years ago. At that time, customers had to choose one technology or another, the choices being Amazon and VMware. It’ s not that they were bad technologies — they’re great technologies with a lot to offer but by choosing one of those you limit the opportunity to go to another,” Curry said

As OpenStack enters its third year — and as Amazon  and VMware face customer fears of vendor lock-in —  everyone agrees that it’s still early  in the cloud game. Most companies have put some projects in the  cloud but have not yet fully bought in. But they all want choices.

Photo courtesy of Flickr user ansik

6 Responses to “OpenStack faces the terrible twos”

  1. Reblogged this on Virtualized Geek and commented:
    Choice is good however too much choice at the cost of fracturing the project itself isn’t very good for the brand. It’s true that it’s too early to tell. I think that OpenStack as a foundation technology can be a great competitor to vCloud and AWS. But, I believe fracturing will be an issue for making a concentrated branding effort against AWS, vCloud or even Eucalyptus. Go to HP’s Cloud site and look for OpenStack. You will have a hard time finding it because HP isn’t interested in the OpenStack brand. Similar to how Amazon isn’t interested in the Android brand or Google with the Java brand for Android.
    It’s all about functionality for these Platinum members. OpenStack is a great foundation to deliver value added consulting services. IBM for example doesn’t care what product you use to meet your organizations goals just as long as you buy their services. At the end of the day it will be an IBM Cloud solution.
    Do IBM and HP really care about having shared API’s and interoperability between their clouds? Building Cloud management is difficult work and open source is a great way to solve that challenge. When they have customer’s that have use cases for interoperability, I bet they won’t bring up that their clouds are based on OpenStack but rather that they are compatible with each other.
    Does it even matter that people may not recognize a single brand? Are the API’s all we really care about in the end as cloud consumers?