Welcome to TripleO documentation

TripleO is a project aimed at installing, upgrading and operating OpenStack clouds using OpenStack’s own cloud facilities as the foundation - building on Nova, Ironic, Neutron and Heat to automate cloud management at datacenter scale.

Contents:

• TripleO Introduction
• Environment Setup
  • Virtual Environment
  • Baremetal Environment
  • VirtualBMC
• Undercloud Installation
  • Installing the Undercloud
  • Updating Undercloud Components
• Basic Deployment (CLI)
  • Prepare Your Environment
  • Get Images
  • Upload Images
  • Register Nodes
  • Introspect Nodes
  • Provide Nodes
  • Flavor Details
  • Configure a nameserver for the Overcloud
  • Deploy the Overcloud
  • Post-Deployment
• Containers based OpenStack deployment
  • Containers based Undercloud Deployment
  • Containers based Overcloud Deployment
  • TripleO Containers Architecture
  • Tips and Tricks for containerizing services
• Post Deployment
  • Migrating Workloads from an existing OpenStack cloud
  • Scaling overcloud roles
  • Deleting Overcloud Nodes
  • Quiescing a Compute Node
  • Quiescing a CephStorage Node
  • Import/Export of VM Snapshots
  • Updating Packages on Overcloud Nodes
  • Upgrading to a Next Major Release
  • Building a Single Image
  • Uploading a Single Image
  • Backing up and Restoring your Undercloud
• Feature Configuration
  • Configuring Network Isolation
  • Configuring Network Isolation in Virtualized Environments
  • Deploying with SSL
  • TLS everywhere for the overcloud
  • Controlling Node Placement and IP Assignment
  • Deploying Operational Tools
  • Configuring High Availability
  • Bare Metal Instances in Overcloud
  • Deploying with OVS DPDK Support
  • Using Already Deployed Servers
  • Security Hardening
  • Configuring API access policies
• Baremetal Node Configuration
  • Bare Metal Node States
  • Setting the Root Device for Deployment
  • Introspecting a Single Node
  • Advanced Profile Matching
  • Ready-state configuration
  • Accessing Introspection Data
  • Use whole disk images for overcloud
• Backend Configuration
  • Deploying Manila in the Overcloud
  • Configuring Cinder with a Custom Unmanaged Backend
  • Configuring Cinder with a NetApp Backend
  • Configuring Ceph with Custom Config Settings
  • Use an external Ceph cluster with the Overcloud
  • Configuring MidoNet as a Neutron Backend
  • Domain-specific LDAP Backends
  • Use an external Swift Proxy with the Overcloud
• Custom Configurations
  • Deploying with Composable Services
  • Deploying with Custom Roles
  • Modifying default node configuration
  • Provisioning of node-specific Hieradata
  • Node customization and Third-Party Integration
  • Deploying with Heat Templates
  • Deploy and Scale Swift in the Overcloud
  • Role-Specific Parameters
• Troubleshooting
  • Troubleshooting instack-virt-setup Failures
  • Troubleshooting Image Build
  • Troubleshooting Node Management Failures
  • Troubleshooting a Failed Overcloud Deployment
  • Debugging TripleO Heat Templates
• Validations
  • Running a single validation
  • Running a group of validations
• Mistral API
  • Working with Mistral
  • Creating a Deployment Plan
  • Working with Bare Metal Nodes
  • Parameters
  • Deployment
• Developer Documentation
  • tripleo.sh
  • Using an In-Progress Review
  • Composable services tutorial
  • Release Management
• How to Contribute
  • Contributing Code
  • Contributing to this Documentation
  • Reporting Bugs
  • Requesting Features

Documentation Conventions

Some steps in the following instructions only apply to certain environments, such as deployments to real baremetal and deployments using Red Hat Enterprise Linux (RHEL). These steps are marked as follows:

RHEL

Step that should only be run when using RHEL

RHEL Portal Registration

Step that should only be run when using RHEL Portal Registration

RHEL Satellite Registration

Step that should only be run when using RHEL Satellite Registration

CentOS

Step that should only be run when using CentOS

Baremetal

Step that should only be run when deploying to baremetal

Virtual

Step that should only be run when deploying to virtual machines

Ceph

Step that should only be run when deploying Ceph for use by the Overcloud

Source

Step that should only be run when choosing to use some components directly from their git source code repositories instead of packages.

Stable Branch

Step that should only be run when choosing to use components from their stable branches rather than using packages/source based on current master.

Mitaka

Step that should only be run when installing from the Mitaka stable branch.

Newton

Step that should only be run when installing from the Newton stable branch.

Ocata

Step that should only be run when installing from the Ocata stable branch.

SSL

Step that should only be run when deploying with SSL OpenStack endpoints

Self-Signed SSL

Step that should only be run when deploying with SSL and a self-signed certificate.

Validations

Steps that will run the pre and post-deployment validations

Any such steps should not be run if the target environment does not match the section marking.