1 Introduction
2 Coopetition and Free/Libre/Open Source software ecosystems
Project | Project domain | Competing firms collaborating in the project |
---|---|---|
WebKit | Web-browsing technologies | Apple, Nokia, Google, Samsung, Intel, RIM among others. |
Blink | Web-browsing technologies | Google, Opera, Intel, Samsung among others. |
OpenStack | Cloud computing infrastructure | Rackspace, Canonical, IBM, HP, Vmware, Citrix among others. |
Cloud Foundry | Platform as a Service (PaaS) | Cisco, Canonical, IBM, EMC, VMware, SAP among others. |
Xen | Virtualization | Citrix, IBM, Intel, HP, Novell, Red Hat, Oracle among others. |
Open Handset Alliance | Mobile devices platform | Asus, LG, Samsung, HTC, Acer, Huawei, ZTE among others. |
Tizen | Operating System | Fujitsu, Huawei, NEC, Casio, Panasonic, Samsung among others. |
GENIVI Alliance | In-Vehicle Infotainment | Volvo, BMW, Honda, Hyundai, Renault, PSA among others. |
3 Research questions
-
What is the software development process used to develop the OpenStack high-networked open source cloud computing infrastructure?
-
Are developers affiliated with different firms collaborating with each other in the project? How does the collaboration evolve over time? How is collaboration affected by exogenous events in the market?
-
Is there a tendency towards sub-grouping in the project? Are there different sub-communities within the OpenStack ecosystem-community? Which ones? How do developers cluster into different groups? Do developer clusters correspond to firms?
-
Do firms that compete in the same revenue model collaborate less in the ecosystem?
4 Case Study: OpenStack
Revenue model | Exemplar competitive dyad | Brief description |
---|---|---|
Complementary services | HP vs. Mirantis | Both firms compete for Open-Stack related IT projects. Both provide consultancy, integration, customization, testing, deployment, among other IT services. The “body shopping” businesses model is often employed (i.e., the practice of providing technology workers for a contracted short-term project). Price is often determined on a project basis involving long vendor/client negotiations. |
Complementary software | VMware vs. Cisco | Neutron, the OpenStack cloud networking controller includes a list of plugins that enable interoperability with various commercial and open source network technologies, including routers, switches, virtual switches and software-defined networking (SDN) controllers. Both VMware and Cisco provided such complementary commercial software plugins. By offering this complementary commercial software, VMware also leveraged its visualization technologies while Cisco also leveraged its physical network solutions. |
Complementary hardware | IBM vs. Intel | OpenStack real-life deployments often require costly hardware capabilities. OpenStack is most often deployed in multiple-processor computer systems at specialized data center facilities. By September 2014, IBM was marketing its new POWER8 CPU architecture as OpenStack-friendly. Meanwhile, Intel marketed its Atom C-2750 and Xeon E5-265x-class processors as optimized of OpenStack deployments. |
Distribution & support | Red Hat vs. Canonical | Both Red Hat and Canonical designed business models around the commercial support of Linux distributions: e.g., Red Hat Enterprise Linux vs. Ubuntu Advantage. The same applies to OpenStack distributions: By September 2014, Red Hat commercially distributes and supports the Red Hat Enterprise Linux OpenStack Platform vs. Canonical’s distribution of Ubuntu OpenStack. Even if OpenStack is freely distributed in an open source way, many enterprise customers opt by a commercially supported distribution with legal contracted service level agreements. |
Public clouds hosting | HP vs. Rackspace | Similarly to Amazon, HP and Rackspace also provide public cloud services. Unlike Amazon, the offering of HP and Rackspace relies on OpenStack technologies. Any third part actor can contract OpenStack based cloud services both from HP (HP Helion Public Cloud) or Rackspace (Rackspace Public Cloud). The price of cloud computing services are often determined as a function of renting time multiplied by needed capacity (number of CPU nodes, storage and network requirements). |
5 Methodology
Employed approach | Discipline(s) | Seminal works |
---|---|---|
Case study rooted on archival data | Multidisciplinary | Yin [10] |
Eisenhardt [138] | ||
Mockus et al. [139] | ||
Runeson and Höst [11] | ||
Mining software repositories | Software-Engineering | Madey et al. [140] |
López et al. [141] | ||
Kagdi et al. [142] | ||
Network analysis of digital trace data | Software-Engineering | Robles et al. [143] |
Information-Systems | Hahn et al. [144] | |
Howison et al. [145] | ||
Network analysis with emphasis on the visualization of collaborative activities | Biomedicine | Lundvall [146] |
Bibliometrics | Cambrosio et al. [147] | |
Innovation-Studie | Glänzel and Schubert [148] | |
Network analysis of massive networked data. Use of clustering and sub-community detection algorithms. | Physics | Zachary [149] |
Mathematics | Kleinberg [150] | |
Computer-Science | Newman and Girvan [151] | |
Medicine | Adamcsek et al. [152] | |
Anthropology | Brohee and van Helden [153] | |
Neurology | Fortunato [154] | |
Bioinformatics | Nick et al. [155] |
5.1 Data collection
WWW Internet site | WWW Internet site correspondent title |
---|---|
OpenStack Open Source Cloud Computing Software | |
Stackalytics | OpenStack community contribution... | |
Software development analytics for Open Source projects.. | |
Musings On Cloud Computing and IT-as-a-Service | |
Datacenter Dynamics | |
Slashdot: News for nerds, stuff that matters | |
Technology News, Analysis, Comments... for IT Professionals | |
Technology News - CNET News | |
IT news, features, blogs, tech reviews, career advice | |
The latest technology news and information on startups | |
British Broadcasting Corporation | |
The New York Times - Breaking News, World News | |
Comprehensive Singapore and international news and analysis | |
The Korea Times | |
Breaking News, Kenya, Africa, Politics, Business | |
EL PAÍS: el periódico global | |
Folha de S.Paulo - Jornal on-line com notícias, fotos e vídeos |
dev1@gmail.com
instead of dev1@hp.com
, while actually affiliated with HP). This problem was tackled by manually triangulating our automatically-retrieved affiliation results with data from the Foundation affiliation database using two external data sources [74, 75].5.2 Data analysis
Cactus
release (April 15th 2011), OpenStack abandoned the 3-month time-based release cycle for a coordinated 6-month release cycle with frequent development milestones [76‐78]. Thus, we opted to take a longitudinal approach and to construct SNA visualizations that depict collaborative behaviors release after release. Table 5 lists the 9 releases of OpenStack addressed by this study.
Release date | Release name |
---|---|
Oct 21st, 2010 | Austin
|
Feb 3rd, 2011 | Bexar
|
Apr 15th, 2011 | Cactus
|
Sep 22nd, 2011 | Diablo
|
Apr 5th, 2012 | Essex
|
Sep 27th, 2012 | Folsom
|
Apr 4th, 2013 | Grizzly
|
Oct 17th, 2013 | Havana
|
Apr 17th, 2014 | Icehouse
|
Firm | Firm description |
---|---|
Canonical | The makers of Ubuntu. Provider of support services for Ubuntu deployments in the enterprise. |
Citrix | Multinational software company that provides virtualization, networking, software-as-a-service (SaaS), and cloud computing technologies. |
Cloudscaling | Services and open source products company selling custom cloud infrastructure for large service providers, chiefly telecom service providers. |
HP | Multinational IT company. Provides hardware, software and services to consumers, small- and medium-sized businesses (SMBs) and large enterprises. |
IBM | Multinational technology and consulting corporation. |
Mirantis | North California software company specialized on OpenStack. |
Nebula | North California hardware and software company specialized on cloud computing. |
Rackspace | Multinational IT hosting company. |
VMware | Software company that provides cloud and virtualization software and services. |
Red Hat | Multinational software company providing open source software products to enterprises. |
-
V is the set of nodes representing the developers ∈T O P T E N contributing to the OpenStack Nova open source software project. All other developers not affiliated with the top 10 contributing firms are not considered in this study.
-
A v is the set of nodes-attributes, capturing the company affiliation of a developer.
-
E is the set of edges, identifying the connections between two developers if they have worked on the same software source code file. An edge will exist iff two developers have modified the same file during the release under study. Edges are both unweighted and undirected.
6 Results
6.1 A overview of the software development process
stable/*
branch from the current state of the master branch and introduces any new release-critical fix discovered until the release day. Between the RC1 and the final release, OpenStack looks for regression and integration issues. RC1 may be used as is for the final release, unless new release-critical issues are found that warrant a RC respinning. If this happens, a new milestone will be open (RC2), with bugs attached to it. Those RC bug fixes need to be merged in the master branch before they are allowed to land in the stable/*
branch. Once all release-critical bugs are fixed, the new RC is published. This process is repeated as many times as necessary before the final release. As it gets closer to the final release date, to avoid introducing last-minute regressions, the release team limits the number of changes and their impact: only extremely-critical and non-invasive bug fixes can get merged. All the other bugs are documented as known issues in the Release Notes instead.6.2 Longitudinal description of collaborative and competitive issues
“What is OpenStack? Well, our mission statement says this:To produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.That is a big ambition. The good news is that OpenStack is starting with code contributions from two organizations that know how to build and run massively scalable clouds - Rackspace and NASA. Rackspace has been in the cloud business for 4 years and now serves tens of thousands of customers on its cloud platform. Likewise, NASA began building their Nebula cloud platform 2 years ago to meet the needs of their scientific community” — Jim Curry, OpenStack Lead, 19 July 2010 [103]
Austin
to the Bexar
release, from October 21st 2010 to February 3rd 2011. From it, we can derive the collaboration between software developers affiliated with companies; so, Citrix had three developers working on the project together with Rackspace.
“OpenStack provides a solid foundation for promoting the emergence of cloud standards and interoperability.”.... “As a longtime technology partner with Rackspace, Citrix will collaborate closely with the community to provide full support for the XenServer platform and our other cloud-enabling products.” — Peter Levine, SVP and GM, Citrix, 19 July 2010 [107]
“The project is exhibiting the key benefits that the industry derives from successful open source collaboration: rapid development, faster testing, feedback and project turn around, broader industry adoption and learning through implementation and de-facto standardization whilst avoiding the prospect of commoditization.It has been rewarding to work with the OpenStack crew, and to have experienced first hand the dedication to an open, code-rules, community-first approach taken by the project leaders. OpenStack has shown that it is possible to rally the community around the development of “management” software - as opposed to the Linux kernel or Xen - and it is definitely the case that OpenStack is breaking new ground for the industry at large. With the release behind us, our team will head in force to San Antonio for the next Design Summit.” — Simon Crosby, CTO, Citrix 21 October 2010 [108]
Bexar
to the Cactus
release (from February 3rd 2011 to April 15th 2011). From this visualization we can observe a new node, a developer affiliated with Cloudscaling. Cloudscaling was founded in 2006 by the cloud architect and open source software advocate Randy Bias, and the co-founder Adam Waters. It started as a professional services company selling custom cloud infrastructure for large service providers, chiefly telecom service providers. They had KT (formerly Korea Telecom) as an early customer, for which the company in 2010 designed and deployed the first OpenStack-based storage cloud outside Rackspace.
“Earlier this week, one of our clients, a Tier 1 ISP, launched an object storage cloud based on OpenStack, an open source compute and storage framework created by Rackspace and NASA. The new storage cloud is the first commercial OpenStack-based storage offering in the market after Rackspace itself, which is based on the same technology. Cloudscaling assisted in developingthis solution for the new product, including hardware, networking, configuration, systems integration, monitoring and management.” – Joe Arnold, Director of engineering, Cloudscaling, 31 of January 2011 [109]
Cactus
to the Diablo
release (from April 15th 2011 to September 22nd 2011). HP (a well-known IT multinational company), Mirantis (an OpenStack startup), and Red Hat (the company behind the Red Hat Enterprise Linux and sponsor of the Fedora Linux distributions) joined the coopetitive software development efforts.“Our internal infrastructure is running on Fedora, instead of migrating the full infrastructure to Ubuntu, we decided to make OpenStack Fedora-friendly.” – Maxim Lvov, Senior deployment engineer, Mirantis, 18 of May 2011 [110]“Are you aware of the upstream effort to create packages for Fedora?”... “would you be willing to contribute your specs if you really build your rpms from the sources?” – Fabian Deutsch, Contributor to the Fedora project, 20 of May 2011 [110]“I’ve had a conversation with David Nalley about contributing to Fedora. Sure, we are willing to contribute. We are under refactoring, and we’ll show them soon.” – Mike Scherbakov, OpenStack architect, 20 of May 2011 [110]
Diablo
to the Essex
release (from September 22nd 2011 to April 5th 2012). Although the graph becomes more dense, we can visualize new nodes representing early contributions of Intel (interested in making OpenStack deployments work well on Intel micro-processors) and IBM. IBM has a long history of working with open standards and open source initiatives such as in the Apache and Eclipse projects, and has been able to sell complementary solutions (i.e., hardware, software and services) from open source projects. It expects the same business model to work well with OpenStack.
“Our goal is to accelerate the rate and pace of both functional and non-functional (performance, scalability, reliability, etc.) enhancements to the OpenStack code base. In that vein, IBM will be a very active participant in the next OpenStack Design Summit scheduled for October 15–19 in San Diego. The time has come to establish a de-facto base implementation for IaaS and related open interfaces. Without this, the industry risks fragmentation and complexity that will only serve to slow down the adoption of cloud technology and innovation. Support for OpenStack and the OpenStack Foundation is an effective way to achieve this goal. In a Wired.com blog I wrote back in April, I highlighted three initial focus areas for IBM: 1) Establish the OpenStack Foundation, 2) Support and expand the OpenStack Ecosystem and 3) Contribute to the OpenStack Development.” – Angel Diaz, Vice President of Open Standards, IBM, 19 of September 2012 [113]
Essex
and the Folsom
release (from April 5th 2012 to September 27th 2012). We can observe that the network becomes more dense, as there are more developers working with each other. Even if some of their developers continued contributing to the project, Citrix had by then abandoned its Olympus OpenStack distribution in order to focus instead on the competing CloudStack cloud computing FLOSS ecosystem. Citrix decided to contribute to the competing CloudStack software ecosystem under the umbrella of the Apache Software Foundation, with a codebase resulting from the acquisition of Cloud.com in July 2011. This turn of strategy from Citrix is related with the OpenStack lack of integration with the Amazon’s APIs (Application Programming Interfaces). Amazon is currently the leader of cloud services, and the migration costs to another cloud computing infrastructure are very high, specially if the APIs do not resemble each other.
“Amazon has in many ways invented and created this market, and with what is projected to be $1 billion in ecosystem and customer revenue attached to Amazon cloud, we believe the winning cloud platform will have to have a high degree of interoperability with Amazon” – Sameer Dholakia, GM Cloud Platforms Group, Citrix, 3 of April 2012 [114]
Folsom
to the Grizzly
release (from September 27th 2012 to April 4th 2013). As expected, Citrix reduced its commitment to OpenStack as we observe little activity from Citrix developers. Canonical continued investing increasingly in the development of OpenStack, interested in keeping its Linux Distribution Ubuntu as the leading Linux distribution for OpenStack clouds [115].“(OpenStack Summit) Canonical and VMware, Inc. (NYSE: VMW), the global leader in virtualization and cloud infrastructure, today announced a collaboration that will enable organizations to deploy VMware technologies, including VMware vSphere and Nicira NVP, with Canonical’s OpenStack distribution. Canonical’s Ubuntu Cloud Infrastructure, the most widely used OpenStack distribution, will now include the plugins required to use OpenStack with vSphere and NVP. Canonical will provide commercial support for OpenStack and will collaborate with VMware on issues related to vSphere or NVP running with OpenStack. In addition, VMware reaffirms its support of Ubuntu as a fully supported guest operating system (OS) on vSphere. This agreement will enable customers the flexibility to deploy and reliably run OpenStack clouds with Ubuntu Cloud Infrastructure on VMware vSphere while receiving commercial support.” – Joint press release from VMware and Canonical, Acquire Media, 16 of April 2013 [116]
Grizzly
to the Havana
release (from April 4th 2013 to October 17th 2013). We can see that VMware took its commitment to OpenStack seriously, as six new developers engaged in developing with other OpenStack developers affiliated with TOPTEN firms. Mirantis, in yellow on the right of Fig. 10, invested heavily in collaborative activities with IBM, Rackspace and Red Hat. Mirantis counted on financial support from Dell Ventures and Intel Capital (representing the interests of hardware manufacturers betting on OpenStack) [117] and additional investment by Ericsson, Red Hat, and SAP Ventures [118], turning it into one of the biggest code contributors to the OpenStack software ecosystem in just a few months as reported by Bitergia [82]; the number of developers from Mirantis increased from 1 to 17 in this time period.Havana
to the Icehouse
release (from October 17th 2013 to April 17th 2014). In this visualization, the number of network nodes (i.e., software developers affiliated with TOPTEN firms in the OpenStack Nova) decreased, while retaining a similar density. This fact must be interpreted carefully, as it does not mean that the number of software developers contributing to the OpenStack Nova is now lower. There were currently 313 developers contributing with code, and 483 developers reviewing code during this period. The community contributing to the OpenStack Nova project increased significantly, while the role of the TOPTEN firms decreased. As of this release, Intel, NEC, Huawei and the rest of the non-affiliated developers grouped together would belong to the TOP 10 contributors of the Icehouse
release – although considering the whole lifespan of OpenStack the project, we have considered them to be out of the TOP 10.6.3 Ecosystem and its sub-communities
Grizzly
, Havana
and Icehouse
) because of higher project maturity and a steady diminution of group cohesion (i.e., tendency for subgrouping) as “plotted” in Fig. 12. The figure includes three basic social network metrics that capture the evolution of the collaborative network over time/release: number of nodes, number of edges and network density, all correspondent measures of community-size, collaborative behavior and community cohesion.
6.4 Exploring the relationship between revenue-models and collaboration
Competing revenue stream | Revenue stream description | Competing firms |
\(\frac {\stackrel {\text {DO}}{\mathrm {n}(\alpha _{i})}}{\text {den}(\alpha _{i})}\)
|
\(\frac {\stackrel {\text {DO NOT}}{\mathrm {n}(\beta _{i})}}{\text {den}(\beta _{i})}\)
|
---|---|---|---|---|
Complementary services | Firms providing specialized support, maintenance, integration, customization, testing, consulting, etc. | ALL TOPTEN |
\(\frac {136}{1}\)
|
\(\frac {0}{\text {UND}}\)
|
Complementary software | Firms providing software embedding OpenStack or complementary drivers and plug-ins. | IBM, VMware, Nebula, Cloudscaling, Red Hat, Citrix, Canonical | ||
Complementary hardware | Firms providing hardware targeting OpenStack installations. | IBM, HP, Nebula | ||
Distribution and support | Firms distributing OpenStack with enterprise support (for a fee). | Red Hat, IBM, HP, VMware, Canonical | ||
Public cloud services | Firms providing OpenStack based public cloud services such as hosting. | HP, Rackspace, Canonical |
-
Companies providing complementary software collaborate more than companies not providing complementary software.
-
Companies providing complementary hardware collaborate more than companies not providing complementary hardware.
-
Companies providing distribution and support collaborate more than companies not providing complementary distribution and support.
-
Companies providing public clouds collaborate less than companies not providing public clouds.
7 Discussion, including further research
7.1 Homophily
7.2 Coopetition theories and business models
7.3 Understanding the dynamics of industrial FLOSS projects
7.4 Mixed method approach
Grizzly
to the Havana
release, either by summing the centrality measures of the developers affiliated to Mirantis or by interpreting Fig. 10, we could easily make wrong judgments about the importance or influence of Mirantis within the OpenStack Nova project. Thanks to complementary ethnographic knowledge we know that Mirantis has been in contractual supply relationships with AT&T, Cisco, Red Hat and NASA. Moreover, other companies contributing to the project (e. g., Intel, Ericsson, Red Hat and SAP) have equity participation within Mirantis. Hence, pure repository-driven quantitative judgments about the centrality, importance or influence of actors within a software ecosystem setting must be interpreted very carefully.