Consider three facts that demonstrate the rapid iterations driving OpenStack skyward:
1. Technology is Keeping Up With Hype
There’s no shortage of hype in the OpenStack community. Vendors, pundits and competitive ecosystems are all vying to see who can deliver the greatest OpenStack hyperbole or invective.
Hype is deadly when it *consistently* writes checks that the technology can’t cash. And in the case of OpenStack, the technology is evolving as rapidly as the hype. We know this by simple observation: if it wasn’t the case, we’d all be screwed.
2. The SLDC Has Greatly Matured
The leadership of people like Thierry Carrez, Release Manager of OpenStack, and Monty Taylor of HP has resulted in a continuous integration (CI) process that has greatly improved the reliability of the OpenStack code base and allowed for maintaining momentum, all while the software has grown from two projects (Nova and Swift) to nine. The CI system depends heavily on the Tempest integration tests in OpenStack that have grown from just over 70 integration tests in January 2012 to over 700 integration tests last month. (More at SimplicityScales)
Check out jenkins.openstack.org to get an example of the magnitude of OpenStack’s automated testing system. Over 700 test clouds are deployed every day. Awesome stuff, and it helps assure the quality of the code pushed with each release.
No other competing open source cloud project has this scale of testing.
3. Interest is High. And Growing
The Grizzly release of OpenStack has 230 new features and 7,620 patches from 517 contributors. Developer growth, diverse corporate support and accumulated community have all surpassed Eucalyptus, CloudStack and OpenNebula, and not even close. Check out Qingye (John) Jiang’s compilation and analysis of community contribution statistics for more on this.
Also, consider the growing number of production clouds. They run the gamut from big service providers (AT&T, Comcast, Rackspace) to SaaS providers (PayPal, Living Social, Ubisoft) and enterprises (Fidelity).
Awhile back, Charlie Babcock of Informationweek said, “OpenStack appears to be a more advanced or more modern open source project than some of its predecessors because it’s a highly coordinated effort.”
True. And in the time since he wrote it (last November), it’s only become more coordinated.
The Next Three Years
We’ve advocated adoption of OpenStack since it was launched and were responsible for some of it’s earliest public cloud wins. Having designed and deployed open source IaaS (CloudStack, Eucalyptus, OpenNebula) and closed source IaaS (GoGrid, VMware, DynamicOps), we saw great promise in OpenStack. It was one of the first open source IaaS solutions that was a distributed scale-out software system and showed promise for creating a vibrant community. The right architecture with the right community is the killer combination for success.
We wanted something that would be as compatible as possible with Amazon Web Services (AWS) and our version of OpenStack delivers on this promise.
Looking ahead to the next three years, there are significant threats to the ability of OpenStack to continue on the route to AWS compatibility. We cannot let that happen.
Simon Wardley, a Cloudscaling advisor and prominent thought leader in elastic cloud computing, is fond of saying that OpenStack’s only chance of survival is to immediately embrace the AWS API set, supported by architectural configurations that allow the infrastructure to deliver services that are behaviorally consistent with their AWS counterparts.
Simon and I agree on this. By its sixth birthday, OpenStack needs to have accomplished this objective if not as an exclusive path then as a fully supported alternative to a differentiated API set.
But more on that later.
For today, happy birthday, OpenStack. Congratulations on a job well done.
(JOIN US in Portland at OSCON for the OpenStack 3rd birthday bash.)