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.
Contributor Guide¶
Install Guide¶
- TripleO Install Guide
- TripleO Introduction
- Environment Setup
- Undercloud Installation
- Basic Deployment (CLI)
- Basic Deployment (UI)
- Tempest
- Tempest Plugins
- Containers based OpenStack deployment
- 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 Content on Overcloud Nodes
- Upgrading to a Next Major Release
- Understanding undercloud/standalone stack updates
- Building a Single Image
- Uploading a Single Image
- Updating undercloud user’s ssh key
- Rotation Keystone Fernet Keys from the Overcloud
- Feature Configuration
- Configuring Network Isolation
- Configuring Network Isolation in Virtualized Environments
- Deploying with SSL
- Deploying with IPSec
- Controlling Node Placement and IP Assignment
- Deploying Operational Tools
- Configuring High Availability
- Configuring Instance High Availability
- Configuring Messaging RPC and Notifications
- Bare Metal Instances in Overcloud
- Container Image Preparation
- Deploying with OVS DPDK Support
- Using Already Deployed Servers
- Keystone Security Compliance
- Security Hardening
- Configuring API access policies
- Disable Telemetry
- Disabling updates to certain nodes
- Splitting the Overcloud stack into multiple independent Heat stacks
- Ansible config-download differences
- Deploying with RHSM
- TripleO config-download User’s Guide: Deploying with Ansible
- Baremetal Node Configuration
- 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
- Deploying with Custom Networks
- 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
- Exporting Deployment Plans
- Deploying Overcloud with L3 routed networking
- TripleO backup and restore (Undercloud and Overcloud control plane)
- Troubleshooting
- Validations
- Mistral API
- Developer Documentation
Fast Forward Upgrade Guide¶
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
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
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.
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.
Pike
Step that should only be run when installing from the Pike stable branch.
Validations
Steps that will run the pre and post-deployment validations
Optional Feature
Step that is optional. A deployment can be done without these steps, but they may provide useful additional functionality.
Any such steps should not be run if the target environment does not match the section marking.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.