Developers and partners met at the Austin design summit to define early technical goals and plan how compute and storage pieces would fit together. These working sessions helped turn the announcement into a coordinated engineering project with shared priorities. The summit model later became a repeating way OpenStack aligned community work across many companies.
Rackspace and NASA publicly launched OpenStack as an open-source cloud-computing initiative, combining code and ideas from Rackspace’s cloud services and NASA’s Nebula work. The goal was to let organizations build “Amazon-style” clouds in their own data centers using open software and standard hardware. This announcement set the stage for a fast release cycle and a growing multi-company community.
The first coordinated OpenStack release, code-named “Austin,” shipped with two key projects: Nova (compute) and Swift (object storage). This release gave early adopters real code to test and helped establish OpenStack’s pattern of named releases. It also marked the start of OpenStack as deployable software rather than just an idea.
The “Bexar” release expanded OpenStack beyond compute and object storage by including Glance, the image service used to store and manage virtual machine images. With Glance, clouds could standardize how they handled images, which made provisioning more consistent across deployments. This was an early step toward a fuller platform for private and on‑prem clouds.
The “Essex” release brought two foundational services into the core: Keystone for identity/authentication and Horizon for a web-based dashboard. These additions mattered for private cloud adoption because they made access control and administration more practical for enterprise IT teams. Essex also marked the point where OpenStack’s release cadence shifted to a six-month cycle.
Rackspace announced a “production ready” next-generation public cloud powered by OpenStack. This was significant because it demonstrated OpenStack running at large scale in a commercial environment, not only in labs. It also reinforced OpenStack’s positioning as an “open cloud” alternative to proprietary cloud stacks.
Rackspace introduced a packaged “Private Cloud” distribution based on OpenStack (starting with Essex), designed to help organizations deploy OpenStack on their own hardware. This mattered for on‑prem adoption because it lowered the barrier to building a multi-node private cloud with a known bundle and support options. It also signaled how vendors would compete by packaging and hardening upstream OpenStack for enterprise use.
Control of OpenStack’s trademark and stewardship moved to the OpenStack Foundation, a neutral nonprofit created to manage legal, operational, and community governance needs. The project also transitioned from the earlier “policy board” approach toward a foundation-led model with a technical committee. This governance shift aimed to reduce single-vendor influence and support broader vendor and user participation.
OpenStack “Folsom” promoted major capabilities that enterprises needed for private clouds: Cinder as a dedicated block storage service (separating storage from Nova) and Quantum networking (later renamed Neutron) as a core network service. These changes helped OpenStack better match real data center needs like flexible networking and persistent volumes. Folsom also reflected the project’s growing scope beyond the original compute-and-object-storage focus.
The “Havana” coordinated release added Heat (orchestration, meaning template-driven automation of cloud resources) and Ceilometer (telemetry, meaning usage and measurement data). These services supported more advanced private-cloud operations, like automated deployments and metering. The release announcement highlighted the growing number of features and bug fixes delivered each cycle as the community matured.
HP launched the HP Helion portfolio, including OpenStack technology-based products and services, and publicly committed major investment to cloud and OpenStack-related work. This was a notable vendor-adoption moment because HP positioned OpenStack as a foundation for hybrid IT (mixing on‑prem and cloud). It also reflected OpenStack’s shift from community software to a large enterprise platform with major OEM backing.
The “Queens” coordinated release marked OpenStack’s continued six-month cadence and maturity after years of rapid expansion in services, vendors, and governance. By this point, OpenStack had become a standard reference platform for many private-cloud and on‑prem distributions. In the 2010–2018 story arc, Queens serves as a clear end point showing OpenStack operating as a stable, scheduled, foundation-governed ecosystem rather than a startup project.
OpenStack: major releases, vendor adoption, and governance changes (2010–2018)