As a OpenStack enthusiast, it would have been easier to dismiss that as a FUD. However, I think it is in the best interests of OpenStack project to consider actionable items. Thanks @cloudpundit (and your recommendations at the end were right on)! Here they are:
1) Publish data on size and stability of large scale deployments:
Concerns about maturity of the OpenStack can only be addressed by sufficient customer feedback. There are at least a handful of ‘large scale’, ‘enterprise’ deployments of OpenStack. Deployment statistics and user feedback from such large deployments would re-affirm OpenStack’s maturity.
2) Publish road map of product features:
Having a road map for the next 18 – 24 months ahead gives good confidence to the customers to take bets on. Moving to OpenStack Foundation is expected to give such clarity; this moves feature planning from project (nova/ swift) level to product (OpenStack) level.
There are a few that appear to unsubstantiated. Lydia, questions to you:
1) What exactly is the ‘hype’?
I couldn’t understand what exactly is the hype is and what is it about – is it the popularity of OpenStack or is it the buzz around OpenStack Foundation? To me, there is no more buzz than any reasonably successful open source product (and the geekiness around it). I also don’t think any CIO will go for OpenStack just by so called ‘hype’.
2) Do you have any data from current large scale users of OpenStack on lack of maturity?
I would be interested in knowing the data points. Obtaining deployment numbers from partners was very difficult – of course they had their business reasons not to reveal. However, if you have come across such data, it would be very helpful.
3) When would you consider a CMP to be matured?
Is it by customer adoption numbers? Sizes of deployments? Feature set? I don’t think one can compare check against AWS features for maturity. While OpenStack feature set can be expanded, I would rate all of the pre-Essex features (nova, swift, keystone) to be mature.
4) Technical Evaluations:
How is evaluating a CMP uniquely applicable to OpenStack? No CIO would consider a CMP without an evaluation; if so why only for OpenStack?
5) Open vs Interoperable:
Where does OpenStack documentation/ marketing claim Interoperability? In fact, one of my hopes is that OpenStack standardizes cloud APIs, rather than aligning with a mess called AWS APIs. Your article seem to consider open and interoperable synonymous.
6) Open vs Vendor:
I do not see the OpenStack community as a cliques of vendor-employees. Particularly after OpenStack Foundation is live, it is an open source project with a lot of participating vendors and an eco-system of vendor offerings around it.