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?
Originally posted on Gigaom:
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.
Rackspace(a rax) — 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.