Today's move by Citrix to put its CloudStack IaaS solution into the Apache Foundation says more about the state of the cloud market than it does about OpenStack. As our Fall 2011 Forrsights Hardware Survey shows, about 36% of enterprise IT leaders are prioritizing and planning to invest in IaaS this year. That means they need solutions today and thus service providers and cloud software vendors need answers they can take to market now. OpenStack, while progressing well, simply isn't at this point yet.
Second, Citrix needed to clarify the position of its current open source–based solution. Ever since Citrix joined OpenStack, its core technology has been in somewhat of a limbo state. The code in cloudstack.org overlaps with a lot of the OpenStack code base, and Citrix's official stance had been that when OpenStack was ready, it would incorporate it. This made it hard for a service provider or enterprise to bet on CloudStack today, under fear that they would have to migrate to OpenStack over time. That might still happen, as Citrix has kept the pledge to incorporate OpenStack software if and when the time is right but they are clearly betting their fortunes on cloudstack.org's success.
There are myriad other benefits that come from this move. Two of the biggest are:
Amazon Web Services (AWS) is great, but many of our enterprise clients want those cloud services and values delivered on premise, behind their firewall, which may feel more comfortable for protecting their intellectual property (even if it isn't). AWS isn't very interested in providing an on-premise version of its solution (and I don't blame them). Today's partnership announcement with Eucalyptus Systems doesn't address this customer demand but does give some degree of assurance that your private cloud can be AWS compatible.
This partnership is a key value for organizations who have already seen significant adoption of AWS by their developers, as those empowered employees have established programmatic best practices for using these cloud services — procedures that call AWS' APIs directly. Getting them to switch to your private cloud (or use both) would mean a significant change for them. And winning over your developers to use your cloud is key to a successful private cloud strategy. It also could double your work to design and deploy cloud management solutions that span the two environments.
In the IaaS market the open source torch has officially been passed from Eucalyptus to OpenStack, a community effort that is showing strong momentum in both vendor participation and end user interest. But now it needs to start showing staying power, and that's just what I expect to see at this week's OpenStack Design Summit in Boston. What started as an effort to leverage the open community to help advance the technologies started by Rackspace and NASA has now turned into a vibrant community advancing IaaS technologies at a rapid pace. What it was lacking up until this summer was solid go-to-market momentum. But now:
Having attended the OpenStack Design Summit this week and at the same time fielding calls from Forrester clients affected by the Amazon Web Services (AWS) outage, an interesting contrast in approaches bore out. You could boil it down to closed versus open but there’s more to this contrast that should be part of your consideration when selecting your Infrastructure as a Service (IaaS) providers.
The obvious comparison is that AWS’ architecture and operational procedures are very much their own and few outside the company know how it works. Not even close partners like RightScale or those behind the open source derivative Eucalyptus know it well enough to do more than deduce what happened based on their experience and what they could observe. OpenStack, on the other hand, is fully open source so if you want to know how it works you can download the code. At the Design Summit here in Santa Clara, Calif. this week, developers and infrastructure & operations professionals had ample opportunity to dig into the design and suggest and submit changes right there. And there were plenty of conversations this week about how CloudFiles and other storage services worked and how to ensure an AWS Elastic Block Store (EBS) mirror storm could be avoided.