Where are you using WebAssembly?
Wasm promises to let developers build once and run anywhere. Are you using it yet?
At work, for production apps
At work, but not for production apps
I don’t use WebAssembly but expect to when the technology matures
I have no plans to use WebAssembly
No plans and I get mad whenever I see the buzzword
Cloud Native Ecosystem

A Code Contribution Analysis Of OpenStack And The Trends It Uncovers

May 15th, 2014 12:29pm by
Featued image for: A Code Contribution Analysis Of OpenStack And The Trends It Uncovers
Editor’s note: The New Stack Founder Alex Williams will be at a Fireside Chat hosted by Pivotal with Greylock Ventures on May 29. Registration is now open. He plans to discuss the OpenStack report as part of the discussion that will cover a variety of topics related to open source and the enterprise. Interested in the report and the data behind it? Please contact us for consultation.

With more than 100 companies contributing to OpenStack code, it is interesting to see the trends in the way they contribute. Metrics around commits have been tracked for a while now and Stackalytics has great visualizations around them. We set to find trends in code contributions over multiple releases across multiple projects.

We analyzed the data from Github, Stackalytics and interviewed scores of developers from different companies. We tracked overall contribution trends over past 4 releases of OpenStack (Folsom (Sept 2012), Grizzly (Apr 2013), Havana (Oct 2013) and the most recent Icehouse (Apr 2014)). Please note that ‘Overall’ here includes all the projects OpenStack Gihub, but doesn’t include OpenStack Infra projects. We also drilled down contribution trends in the following projects of OpenStack : Nova (compute), Swift (Object storage), Cinder (Block Storage), Neutron (Networking), Horizon (Dashboard), Heat (Orchestration), Keystone (Identity) and Glance (Image service).

We presented our findings during our The New Stack Analysts show on Tuesday. Here are some of the trends we observed. While some are as expected, there were some interesting outliers.

Standard Trends

Top 5 Contributors

Over all top contributors have been Red Hat, HP, IBM, Rackspace and Mirantis for the past two releases. They are also viewed to be top contributors by developers, with the exception of IBM. Almost all non-IBM (and even an IBM) developers ranked Rackspace or Mirantis among Top 3, but not IBM. May be it has got to do with the low profile they maintain when compared to others. Looking at their overall contributions, we also get a vibe that they are very close to announcing their own OpenStack distro.

It is also very interesting to observe Mirantis moving into top 5 from 28 during the Folsom release in less than two years.

Code = Commitment

OpenStack community is a developer driven one.  Only code speaks internally. It is clear that if one needs to be taken seriously, one needs to code. This is well understood by the participating companies, as reflected in their contribution trends.

Soon after Red Hat joined the OpenStack community, they have been steadily increasing its participation. They had been #1 contributor for the past 4 releases, continuing the trend for the next release too. This pattern is also demonstrated by Mirantis (#5) and eNovance (#8). Mirantis, the darling of SIs, has always been viewed as OpenStack experts. With their ramped up code contributions, they are allround experts now (also we wonder why the big players haven’t just acquired them yet:)).

Niche Players

Each projects has niche players who are dominant in that project, but might be virtually unknown in other projects. Startups exhibit this trend, such as SwiftStack for Swift, Big Switch Networks for Neutron, SolidFire for Cinder.

Decreasing Gaps

We tracked the total number of commits and calculated the percentage contribution from each company overall and also in these individual projects. The % gap between #1 and #2 contributors is decreasing overall (with the exception of Neutron and Keystone projects). For example, in Nova, it was 8% for the Havana release, whereas only 6% for the Icehouse release. In Heat, this is pattern is more prominent with the gap decreasing from 49% to 24% during the same period.

Another interesting trend is the number of contributors contributing to Top 80% of contribution has also increased (from just 3 in Folsom to 8 in Icehouse), with the long tail of contributors also increasing.


Two outliers that have rapidly shot up high in their overall contribution ranking are Huawei (from #69 for Grizzly to #18 in Havana to #12 in Icehouse), Samsung (from #102 in Havana to #13 in Icehouse). For Huawei, it is largely attributed to their rapid growth in APAC. For Samsung, it is possibly related to ARM related porting work on Nova. Almost all developers didn’t see this until we showed them the data, but were able to correlate once data was presented.

Another unique trend we observed was with Intel, with them never in Top 3 and never below Top 15. They have maintained consistent contributions to features strategically important to them (such as smarter scheduling in Nova, reducing storage footprint in Swift etc). While they tend to trend upwards overall, they go up and down between releases.

High Trenders

Almost each project has unique players trending high, mostly reflective of their product strategy or offerings. For example, in Neutron, Big Switch Networks have risen from #14 in Grizzly to #6 for Icehouse. In Keystone, Metacloud has shot up from non-contributor to #4 during the same period.

Low Riders

We also have contributors trending low. When we analyzed their patterns, we found out the trend in decreasing contributions are threefold:

Other contributors ramping high

Some companies exhibit this trend of consistent contribution, but others have ramped higher significantly. DreamHost is a very good example for this trend. While their code contribution has been always between 2 – 3% overall, but their ranking has trended down considerably (from #5 in Folsom to #15 in IceHouse)

Product completion/ Product Change

Typically small companies exhibit this pattern. When they achieve the goal of what they wanted to do, or if there is a change in their product strategy, their contribution trend reversely drastically.  For example, Nexenta stopped contributing to Swift after Havana release once the code related to their offering is complete. InkTank exhibited the same in Cinder after Havana. More interestingly, Nebula, who had been top contributor for Horizon in Folsom and Grizzly, tapered down after Havana once they decided to use their in-house dashboard for their product.

Decreasing Contributions

Some companies have really decreased their code contributions, justified by reasons that we are yet to find. For example, Canonical is contributing lesser and lesser overall, from 1.8% overall in Folsom to 0.5% overall in Icehouse. Rackspace has been trending down in the projects we are tracking, but also have increased in other newer projects, manuals and infrastructure related projects. SUSE has been trending low in Heat, and Yahoo in Glance.

About the Author: Sriram is founder and cloud specialist at Cloud Don LLC, a cloud consulting firm. He is an OpenStack enthusiast, an individual member of the OpenStack Foundation, passionate about OpenStack’s success overall, and in India particularly. Prior to Cloud Don, he was a lead developer at ComputeNext, building a Federated Cloud Marketplace, where he gained expertise in multiple cloud platforms, including OpenStack. Prior to ComputeNext, he was with various companies like Microsoft, Intel, Hitachi, working on a wide spectrum of technologies like cloud computing, virtualization, compilers, and low power design. He is passionate about cloud computing, green/clean technology, and holistic living.

Group Created with Sketch.
TNS owner Insight Partners is an investor in: Mirantis.
THE NEW STACK UPDATE A newsletter digest of the week’s most important stories & analyses.