OpenStack

OpenStack is an open-source cloud-computing platform rather than a conventional software company or single commercial product. It provides a collection of interoperable services for compute, networking, storage, identity, image management, orchestration, telemetry, and related infrastructure functions. Organizations use it to construct infrastructure-as-a-service environments in their own data centers, at the edge, or through service providers. The project is particularly associated with private and sovereign clouds, telecommunications infrastructure, research computing, and deployments where operators want control over hardware, architecture, data location, and service-provider relationships. The project began in 2010 through collaboration between NASA and Rackspace. NASA contributed technology associated with the Nebula cloud effort, while Rackspace contributed cloud infrastructure technology and operational experience. The initial proposition was to create an openly developed alternative to proprietary cloud platforms and to encourage a broad ecosystem of vendors, integrators, operators, and users. OpenStack was designed around open-source licensing, public development processes, published APIs, and modular services. Its community model allowed companies and independent contributors to influence the roadmap while enabling customers to obtain support and managed services from multiple providers. The early releases established the core architecture. Nova provided compute management, Swift addressed object storage, and later projects expanded the platform into networking, block storage, identity, images, dashboards, orchestration, bare-metal provisioning, containers, and infrastructure lifecycle management. Releases were traditionally issued on a regular cadence and named alphabetically, creating a recognizable sequence that included Essex, Havana, Icehouse, Juno, Kilo, Liberty, Mitaka, Newton, Ocata, Pike, Queens, Rocky, Stein, Train, Ussuri, Victoria, Wallaby, Xena, Yoga, Zed, Antelope, Bobcat, Caracal, Dalmatian, and later releases. OpenStack’s central positioning is freedom of deployment and avoidance of lock-in. Its advocates emphasize the ability to deploy on preferred hardware, combine components from different suppliers, move between operators where compatible implementations exist, and adapt the platform to specialized requirements. That promise has also created an enduring challenge: interoperability depends on disciplined implementation, compatible versions, operational expertise, and standards that extend beyond merely sharing an API name. Running OpenStack at production scale can require substantial engineering, automation, monitoring, and lifecycle-management capability. The OpenStack Foundation was created in 2012 to provide neutral governance, community infrastructure, trademark stewardship, events, and ecosystem coordination. As the foundation supported additional open-source infrastructure projects, its scope expanded beyond the original cloud platform. In 2021 it became the Open Infrastructure Foundation, while OpenStack remained one of its principal projects. The broader ecosystem includes projects and communities concerned with containers, edge infrastructure, continuous integration, bare metal, and secure virtualization. OpenStack is used by large enterprises, telecommunications operators, public cloud providers, governments, universities, and research institutions. Commercial offerings have included supported distributions, managed clouds, consulting, training, certification, and integration services from ecosystem participants such as Canonical, Red Hat, Mirantis, SUSE, and others. OpenStack is often deployed alongside Kubernetes: OpenStack supplies infrastructure and virtualized or bare-metal resources, while Kubernetes manages containerized applications. Its continuing relevance is tied to private-cloud modernization, network-function virtualization, distributed and edge computing, data sovereig…

OpenStack emerged in 2010 from a collaboration between NASA and Rackspace. NASA’s Nebula work supplied an important cloud-computing foundation, while Rackspace contributed technology and experience from its public cloud operations. The project was introduced as an open-source effort intended to make cloud infrastructure deployable and extensible outside a single proprietary vendor’s control. Its initial architecture was modular. Nova managed compute resources and virtual machines, while Swift supplied object storage. Subsequent projects added authentication and authorization through Keystone, machine-image management through Glance, persistent block storage through Cinder, software-defined networking through Neutron, and a browser-based management interface through Horizon. Additional services addressed orchestration, telemetry, bare-metal provisioning, containers, shared filesystems, and high-availability operations. OpenStack’s growth was driven by a broad contributor base of technology companies, cloud operators, hardware manufacturers, systems integrators, researchers, and individual developers. Its release process, public specifications, project teams, user groups, summits, and technical gatherings created a governance model in which no single commercial distributor formally owned the software roadmap. The project’s regularly named releases helped coordinate compatibility and communicate major development cycles. The OpenStack Foundation was established in 2012. It provided legal and organizational infrastructure for the community, administered trademarks and project resources, organized major events, and promoted adoption. Marketing during the early years focused on freedom, credibility, provider choice, deployment flexibility, and protection against software and service-provider lock-in. At the same time, the community recognized that a common API alone would not guarantee that workloads could move seamlessly among every OpenStack deployment. Compatibility expectations therefore became an important part of branding, release management, and ecosystem guidance. OpenStack became a foundation for commercial distributions and managed services. Companies including Canonical, Red Hat, Mirantis, SUSE, Rackspace, and other ecosystem participants built products, support programs, hosted clouds, consulting practices, or operational tooling around it. HPE’s OpenStack-related assets and personnel were acquired by SUSE in 2017, demonstrating the degree to which enterprise vendors were consolidating and repositioning their cloud portfolios. The platform also expanded beyond conventional centralized private clouds. Telecommunications operators adopted it for network-function virtualization and carrier infrastructure; public-sector and research organizations used it where data control and specialized hardware mattered; and the community pursued edge and distributed-cloud use cases. OpenStack increasingly appeared alongside Kubernetes rather than as a direct substitute for it: OpenStack could provide virtual machines, bare metal, networking, and storage, while Kubernetes coordinated containerized workloads. In 2021 the OpenStack Foundation changed its name to the Open Infrastructure Foundation. The change reflected the foundation’s support for a wider family of infrastructure projects and communities, including work related to containers, continuous integration, edge computing, and secure virtualization. OpenStack remained an active project within that broader structure. Its long-term position is shaped by the operational complexity of large-scale private cloud, competition from public-cloud services and proprietary virtualization, and continued demand for open, controllable infrastructure in telecommunications, regulated industries, sovereign-cloud programs, and edge environments.

1. 2021OpenStack Foundation becomes Open Infrastructure Foundation

   The governing foundation adopts a broader name and mission while continuing to support OpenStack as its best-known project.

   Source
2. 2017SUSE acquires HPE OpenStack assets

   SUSE completes the acquisition of relevant HPE OpenStack technology and talent and integrates the assets into its enterprise cloud portfolio.

   Source
3. 2016Marketing and brand modernization work expands

   Foundation marketing materials document work on refreshed visual assets, release communications, events, user stories, and ecosystem campaigns.

   Source
4. 2012OpenStack Foundation is formed

   A nonprofit foundation is established to provide neutral governance, community infrastructure, trademark administration, and ecosystem coordination.

   Source
5. 2010OpenStack launches

   NASA and Rackspace launch an open-source cloud infrastructure project combining NASA cloud technology with Rackspace operational experience.

   Source

An open, modular, community-governed alternative to proprietary cloud and virtualization stacks, focused on operator control, infrastructure choice, interoperability, private cloud, telecommunications, and distributed computing.

• NovaCompute2010

  Nova is OpenStack’s compute service. It schedules and manages virtual-machine instances across available hosts and integrates with networking, image, identity, and storage services. Deployments can use different hypervisors and hardware arrangements, allowing operators to build compute clouds suited to their infrastructure and workload requirements.

• NeutronNetworking

  Neutron provides networking services for OpenStack clouds, including tenant networks, routing, security groups, floating addresses, and integration with physical or virtual network technologies. Its extensible architecture supports advanced use cases such as multi-homing, dynamic routing, and telecommunications networking.

• SwiftObject storage2010

  Swift is OpenStack’s distributed object-storage system. It is designed to store large collections of unstructured data with replication and scalable access across storage nodes. Swift is distinct from block storage and is commonly used for objects, archives, media, backups, and other data accessed through object-storage interfaces.

• CinderBlock storage

  Cinder supplies persistent block volumes that can be attached to compute instances. It abstracts storage systems from multiple vendors and supports use cases requiring durable disks, snapshots, volume management, and storage back ends with different performance characteristics.

• KeystoneIdentity

  Keystone is OpenStack’s identity service. It handles authentication, authorization-related policy integration, service catalogs, projects, domains, roles, and credentials. It provides the common identity layer through which users and services discover and access other components of an OpenStack deployment.

• GlanceImage management

  Glance manages virtual-machine images and related metadata. It provides a catalog and delivery mechanism for operating-system images and templates used to create instances, while integrating with storage and compute services.

• HorizonCloud dashboard

  Horizon is a web-based dashboard for administering and using OpenStack resources. It presents common operations for projects, instances, networks, volumes, images, and identity settings, while APIs and command-line tools remain available for automation and advanced administration.

• IronicBare-metal provisioning

  Ironic provisions and manages physical servers as cloud resources. It extends OpenStack beyond virtual machines for workloads that need direct hardware access, specialized accelerators, predictable performance, or isolation from virtualization layers.

• 2016Release and ecosystem marketing program

  Worldwide

  Foundation marketing teams coordinated release previews, user stories, event communications, collateral, website work, and community messaging around releases including Mitaka.

  Outcome. The program provided a repeatable communications structure for a large, multi-company open-source ecosystem.

  Source
• 2016Winning Marketing Strategies for OpenStack

  Worldwide

  An Open Infrastructure Summit session brought together marketers from different ecosystem organizations to discuss integrating OpenStack into corporate narratives, content strategies, product cycles, and social channels.

  Outcome. The event promoted coordinated ecosystem marketing rather than a single-vendor advertising model.

  Source
• 2012Open infrastructure freedom and interoperability campaign

  Worldwide

  Early OpenStack marketing emphasized deployment freedom, provider choice, interoperability, and protection against software and service-provider lock-in. Campaign guidance also encouraged community use of the brand and logo under published rules.

  Outcome. The campaign established the conceptual positioning that continues to distinguish OpenStack from proprietary cloud platforms, while highlighting the need for stronger compatibility standards.

  Source

• 2021Broaden the foundation’s mission to open infrastructureStrategy

  The foundation had become a home for projects and communities extending beyond the original cloud platform.

  What changed. The OpenStack Foundation adopted the Open Infrastructure Foundation identity while retaining OpenStack as a core project.

  Aftermath. The change positioned OpenStack within a wider portfolio spanning cloud, edge, containers, continuous integration, and related infrastructure technologies.

  Source
• 2012Promote interoperability as a brand obligationStrategy

  Community messaging identified a gap between the promise of open APIs and the practical ability to move workloads among different OpenStack clouds.

  What changed. The project and foundation promoted compatibility expectations, including use of recent APIs and recent code for products using the OpenStack name.

  Aftermath. Interoperability and release compatibility became recurring themes in OpenStack governance, technical work, and marketing.

  Source

• 2021OpenStack Foundation becomes the Open Infrastructure Foundation

  The foundation broadened its identity and mission to support OpenStack and additional open-source infrastructure projects, while retaining OpenStack as a central community project.

  Other
  Source
• 2017SUSE completes acquisition of HPE OpenStack and Cloud Foundry assets

  SUSE completed its purchase of relevant HPE technology and talent, incorporating the OpenStack assets into SUSE OpenStack Cloud and expanding its enterprise infrastructure portfolio.

  M&A
  Source
• OpenStack gains renewed attention as private-cloud demand increases

  Industry coverage has linked renewed interest in OpenStack with private-cloud modernization, edge deployments, telecommunications infrastructure, and customer concerns about proprietary virtualization economics.

  Other
  Source
• Red Hat makes OpenStack services available on OpenShift

  Red Hat presented an integration of OpenStack services with OpenShift, reflecting the ecosystem’s growing emphasis on combining infrastructure management with cloud-native application platforms.

  Product launch
  Source

1. OpenStack
2. The evolution of OpenStack
3. OpenStack Branding and Marketing
4. Open Infrastructure Foundation marketing governance
5. SUSE completes acquisition of OpenStack IaaS assets from HPE
6. OpenStack launches
7. Winning Marketing Strategies for OpenStack
8. OpenStack gains renewed attention as private-cloud demand increases
9. Red Hat makes OpenStack services available on OpenShift