THE 2000S

OpenStack

By the end of the 2000s, hardware and software resources were gradually shifting toward cloud computing, promising enhanced security and centralized management. In 2009, NASA was looking for a platform for its internal web services. The market only offered proprietary solutions, locked in by a few industry giants.

The American space agency’s developers believed that an open-source alternative would better serve a broad community: academic researchers, government institutions, and various businesses. Nothing like this existed. So they decided to create this solution themselves. The initiative attracted Rackspace, whose engineers were working on a similar project to support their hardware and services sales business.

In early 2010, Rackspace representatives contacted NASA. The two teams met in a Thai restaurant, and this modest collaboration gave birth to OpenStack. The official launch took place in July 2010, with the ambition of helping organizations deploy cloud services on standard hardware. Four months later, the first version, named Austin, was released. It provided cloud computing and object storage for Infrastructure as a Service.

The initial projects enabled control of resource pools: compute, storage, and networking, all through a centralized dashboard in data centers. Administrators had fine-grained control, while users obtained their resources instantly. The community then committed to releasing new versions every six months.

The OpenStack Foundation was established in 2012. This independent nonprofit organization had the mission of promoting the development and adoption of the software. The structure ensured neutral management of intellectual property and resource sharing, creating a level playing field for all participants.

The governance model rested on three pillars: a board of directors set the vision and governance, a technical committee managed releases and cross-project requirements, and a user committee gathered field feedback and advocated for their interests. The community operated according to four principles: open source code under the Apache 2.0 license, an open community producing an active ecosystem, transparent development with public code reviews, and open design with biannual summits accessible to all.

Contributors came from diverse backgrounds. Software engineers contributing to the code, writers providing documentation and translations, application developers creating solutions on the infrastructure, and operators and users deploying and managing their clouds. Working groups gathered requirements from specific segments such as telecommunications or the enterprise world. The commercial ecosystem included cloud providers and vendors adding their value to the base software.

Adoption accelerated across different sectors. BMW, Disney, and Walmart proved the solution’s viability in production. PayPal adopted it for the agility and availability demanded by its flagship products. Time Warner Cable relied on this flexibility to manage significant data volumes in its centers.

The technology expanded far beyond its initially intended uses. CERN employed it to analyze data from its Large Hadron Collider, managing over 115,000 compute cores. Adobe Digital Marketing used it to transform its virtualization environment into self-service computing. Australia’s NeCTAR university adopted it for national collaborative research, supporting over 6,000 researchers.

In 2024, Rackspace reaffirmed its commitment with OpenStack Enterprise, a fully managed cloud solution for mission-critical workloads. The company had contributed over 5.6 million lines of code and ranked among the world’s largest OpenStack cloud providers. Its expertise included over one billion server-hours of production experience.

The impact on the IT industry was considerable. The platform enabled organizations of all sizes to deploy their own cloud infrastructures, thus escaping the dominance of proprietary services. Its open-source nature fostered collaborative innovation and reduced infrastructure costs. The open APIs and support from virtually all major IT vendors gave users the freedom to move their workloads between private and public clouds according to their needs.

The benefits included accelerated time to market through a self-service portal, an API-based platform for developing cloud-native applications, and drastically reduced provisioning times. Interoperability and hybrid cloud capability allowed businesses to choose the best environment for their applications without depending on a single vendor.

Evolution continued with the integration of new technologies such as containers, virtual machines, and bare metal servers. The global community now counts over 56,000 individual members in more than 180 countries and over 600 companies. This growth testifies to the platform’s continued relevance in a constantly changing technological landscape, where demand for flexible and open cloud solutions continues to grow.