TripleO

• Uses one OpenStack environment (the undercloud) to deploy and manage another OpenStack environment (the overcloud) for production use (cloud deployment orchestration).
• Provides tooling and workflows for provisioning bare metal, configuring services, and managing OpenStack lifecycle operations (infrastructure automation).
• Integrates with OpenStack components such as Ironic for bare metal management and Heat for template-driven orchestration (cloud infrastructure management).
• Supports template-based customization of OpenStack services and roles through Heat templates and environment files (configuration management).
• Targets operator-focused deployment processes for repeatable, automated OpenStack cloud installation and upgrades (platform operations tooling).

More About TripleO

TripleO is an OpenStack community project that focuses on deploying and operating OpenStack clouds by using OpenStack itself as the deployment and management toolchain (cloud deployment orchestration). The project uses the concept of an “undercloud” OpenStack environment, installed for operators, to provision and manage a separate “overcloud” environment, which serves as the production OpenStack cloud for tenant workloads. This OpenStack-on-OpenStack model is designed to provide a unified way to manage the entire lifecycle of an OpenStack deployment on bare metal infrastructure (infrastructure automation).

In TripleO, the undercloud acts as the control plane for installation and ongoing operations. It typically runs services such as Ironic for bare metal provisioning, Heat for orchestration, and other core OpenStack components that coordinate deployment tasks (cloud infrastructure management). Operators interact with the undercloud to define the architecture and configuration of the overcloud, including controller, compute, storage, and network roles. The undercloud then provisions bare metal nodes, configures operating systems, and deploys OpenStack services onto those nodes according to templates and environment definitions (configuration management).

TripleO relies heavily on Heat templates, environment files, and roles data to describe the target overcloud topology and service layout (infrastructure-as-code tooling). These templates allow operators to adjust parameters such as network configurations, high availability options, storage backends, and service-specific settings. By encoding deployment logic and configuration into versionable templates, TripleO supports repeatable deployments and controlled change management across environments such as test, staging, and production.

In enterprise environments, TripleO is used to install and manage OpenStack clouds on bare metal data center hardware, including scale-out controller and compute clusters (private cloud infrastructure). Typical use cases include initial OpenStack installation, node expansion, hardware replacement, configuration changes, and upgrade workflows. The project’s tooling coordinates Operating System (OS) image provisioning, service configuration, and orchestration of rolling changes, which can reduce manual steps in complex OpenStack operations (platform operations tooling).

TripleO fits within the broader OpenInfra and OpenStack ecosystem as a deployment and operations framework focused on bare metal OpenStack clouds (cloud deployment tooling). It interacts with core OpenStack APIs and services, and its model aligns with environments that require operator-controlled, on-premises (on-prem) cloud infrastructure. For directory and taxonomy purposes, TripleO can be categorized under OpenStack cloud deployment, bare metal provisioning, infrastructure-as-code-based orchestration, and private cloud lifecycle management.