Gartner report throws cold water on uber-hyped OpenStack project

By Brandon Butler, Network World |  Cloud Computing, OpenStack

Leong: "Since the vendors involved want to drive business through the OpenStack ecosystem, there is considerable incentive for proprietary lock-in. There is no significant difference in lock-in for customers adopting OpenStack than for those customers adopting proprietary CMPs. In fact, as OpenStack is not a widely-adopted standard, the number of solution providers is highly limited (whether in hardware, software, or services), restricting overall customer choice far more than adopting VMware's vCloud. Nor are there multiple implementations of an OpenStack CMP. On a practical level, the AWS API has the broadest ecosystem, including multiple CMPs (both open source and proprietary) offering compatible implementations."

OpenStack: While there may be many companies using OpenStack and creating their own products and services based on the code, Bryce says each company has a lowest common denominator of using the same base-level code, which will inherently allow for interoperability compared to if vendors had each created their own cloud management platform. The OpenStack Foundation hopes to control fragmentation by creating rules to ensure that products and services that use the OpenStack brand name include specific components to encourage interoperability. One of the recent goals of the code development within OpenStack has been around improving ease of use, and Collier says he expects a healthy debate about how much focus there should be on management and upgradeability within the code at the upcoming OpenStack foundation.

Leong: "The overall project difficulties are causing many vendors to re-evaluate their OpenStack-related strategies. Vendors, as well as OpenStack customers, often say very different things in public about OpenStack than they do in private. The dissonance between public and private statements stems from customers' desire to associate themselves with a project hyped as the future of the cloud. However, their reservations about the project's ability to produce a stable product within a commercially meaningful time frame run very deep and consequently, many vendors are unwilling to fully commit significant engineering resources to the project at present."

OpenStack: Folsom had a 65% increase in contributions, with a record 330 developers writing 185 new or updated features in the code, Collier says. "Numbers tell the story," he adds. "We have more developers than ever." Rackspace, which some have viewed as steering the project in the past, dropped from contributing about half of the code changes in previous versions to being responsible for 30% of contributions in the newest release. "There are more features, more bug fixes and less of them from Rackspace," Bryce says, noting the additional share of contributions represents more vendors involving themselves in the project.

Originally published on Network World |  Click here to read the original story.
Join us:






Answers - Powered by ITworld

Ask a Question