Red Hat's new OpenStack distribution raises concerns

Does Red Hat's impending OpenStack distribution signal maturity for the cloud computing standard, or fragmentation?

There is a growing group of OpenStack distribution providers and some industry watchers who believe fragmentation...

of the cloud standard could negatively impact cloud software providers and customers.

Red Hat Inc. launched its own distribution of OpenStack this week. Rackspace launched public cloud services based on the open source cloud software stack earlier this month, and other companies with OpenStack offerings on the market include Hewlett-Packard Co., Canonical's Ubuntu, Dell Inc., Piston Cloud Computing and Nebula.

OpenStack isn't just a package like other open source tools, said Lydia Leong, research vice president at Gartner Inc., based in Stamford, Conn. It's an entire framework, which means it will be more difficult to keep the different components in lockstep with one another. Also, any given OpenStack product could theoretically contain whatever combination of those components its creator feels like including, along with proprietary extensions.

Red Hat said any changes it makes to the OpenStack standard will be fed back into the community, but according to Leong, "If your distro doesn't have a lot of changes, then it doesn't have a whole lot of differentiation. But if it does have changes, then you have fragmentation."

Fragmentation makes supporting OpenStack difficult for users and for the management tools ecosystem, Leong said.

For other experts, the growing number of distributions is not a sign of fragmentation, but of growing maturity in the OpenStack market -- especially now that there is a Red Hat version.

"Generally speaking, all these multivendor foundations need one or more distros because there are a class of customers who won't take the product without support," said Mike Norman, analyst with The Virtualization Practice LLC, a virtualization and cloud consultancy based in Wrentham, Mass. "It's a sign of maturity that Red Hat is picking up OpenStack, producing a distro and committing to proper enterprise support and product lifetime."

"The important part is that everyone's sticking to the same [application programming interfaces]," said Chris Perry, cloud architect for DreamHost, a hosting provider based in Brea, Calif. "Even if people implement it in a slightly different way on the back end, the APIs are the same pretty much across the board."

Norman is also encouraged by the changes he's seen in the governance of OpenStack over the last year. Previously, OpenStack was too much under Rackspace's thumb for Norman's liking, but with the establishment of the OpenStack Foundation in April, it has become more of an independent organization, he said.

The Foundation will hold its first election next week as part of "the final critical steps toward giving [OpenStack] a final independent home," said Jonathan Bryce, president of the OpenStack Project Policy Board.

The release, dubbed Folsom, will be released in October.

Right now the open source community is on OpenStack's side, but it's important for the Foundation's participants to start seeing revenue soon, said James Staten, analyst for Forrester Research.

"If OpenStack fails by the fall of this year or the first quarter next year to really start driving revenue, there are a lot of companies that are participating in the OpenStack community in an oftentimes passive way who really need revenue from this, [who] could jump ship," he said. "They have a ticking clock [and] they've really got to move fast."

Beth Pariseau is a senior news writer for SearchCloudComputing.com and SearchServerVirtualization.com. Write to her at bpariseau@techtarget.com or follow her on Twitter @PariseauTT.

Dig Deeper on Open source cloud computing

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

12 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Is the OpenStack standard becoming fragmented?
Cancel
This is how Open Source works, and how companies like Red Hat have ensured other open source projects like Linux and JBoss Application Server survive and blossom. You can't have an open source distro and expect a single benign dictator. Diversity is a positive thing. Plus Red Hat do push code back upstream. Wouldn't you want professional coders sending back good code?
Cancel
See ten tenet - always possible but those who fragment / add proprietary extensions allowing lock in will fail. Those who understand open source & pay attention to the right thing to do are much more likely to succeed IMHO.
Cancel
there is a coherent development methodology and framework for releases and feature addition.
Cancel
If it is merely a collation it has no negative impact and may increase user base. If it is a fork it will allow comparisons of various methods and tools and if the fork is better it will eventually merge back. Forks are good things.
Cancel
There will not be one OpenStack but several. To truly leverage this enterprises will need to adopt a top level Cloud Management System (CMS) like CloudBolt to unify the control and management.
Cancel
While there are several suitors vying for distro supremacy... there's insignificant differentiation between them. How is this fragmentation?
Cancel
Sounds no different than any other open source package like Linux. Does that mean the end of Linux (or any of its various distros)?
Cancel
The number of variants and distros will make it extremely difficult for an enterprise to standardize on this platform.
Cancel
Of course it is. That is what always happens eventually with any Open Source Product where money is involved.
Cancel
I think quite the opposite, this isn't fragmentation of a community, this is the community working. The creation of the Open Stack foundation creates an independent body to protect the integrity of the upstream project. Downstream vendors have the rights granted to them by the FOSS license terms, most notably to read, modify, and redistribute the source. Those vendors, and customers of those vendors who stray to far from the upstream risk traditional issues of cost and lock-in associated of going your own way, whether using FOSS or closed source offerings.

Red Hat on the other hand has a history of contributing their code back to the upstream community, and not "going it alone" in terms of forks or fragmentation. In other cases, Rack Space's Public Cloud capabilities offer a strong alternative to Amazon's EC2 . If neither Red Hat or Rack Space, or other commercial providers stray to far from the upstream Open Stack code, customer's would appear to have ongoing flexibility for moving their workloads between Open Stack variants. If either choose to fork their code, they risk loosing a customer base smart enough to not want to take that path.

Cancel
NO: Because in its Core there is NO crucial Tech-CHANGES, just some external "marketing make-ups" by different competing vendors
Cancel

-ADS BY GOOGLE

SearchServerVirtualization

SearchVMware

SearchVirtualDesktop

SearchAWS

SearchDataCenter

SearchWindowsServer

SearchSOA

SearchCRM

Close