tripleo-docs/doc/source/index.rst
Alex Schultz 984b904733 Update docs with stable/pike repos
The install documentation is currently missing the pike repository
information. This change adds stable/pike into the repository
documentation.

Change-Id: Ia34da03343d726d4796013a816bd5ed53e9d3edf
Closes-Bug: #1723265
2017-10-13 15:12:00 -06:00

2.5 KiB

Welcome to 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

contributor/index

Install Guide

install/index

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

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.