Documentation for TripleO
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Ben Nemec 1e731bd201 Stop services only on upgrade to Ocata or later
The undercloud upgrade process is now able to stop services itself,
so there is no need for the user to do so (and they should not, in
case part of the upgrade expects the services to be running).

This moves the service stop into a stable admonition and leaves an
explanation as to why it should not be done on Pike+.

bp undercloud-upgrade

Change-Id: Ifc52866d7f22427ec41e6ac616710e3e431dffe3
6 years ago
_custom Clean up admonition problems 6 years ago
_templates Clean up admonition problems 6 years ago
deploy-guide/source Update docs structure 6 years ago
doc/source Stop services only on upgrade to Ocata or later 6 years ago
.gitignore Ignore both the AUTHORS and ChangeLog files 7 years ago
.gitreview Add .gitreview 8 years ago
README.rst Show team and repo badges on README 7 years ago
requirements.txt Switch to openstackdocstheme 6 years ago
setup.cfg Enable warning-is-error for docs job 6 years ago Manually sync global-requirements 6 years ago
test-requirements.txt Update docs structure 6 years ago
tox.ini Basic structure of TripleO Deployment Guide 6 years ago


Team and repository tags


TripleO Documentation

This is the documentation source for the TripleO project. You can read the generated documentation at TripleO Docs.

You can find out more about TripleO at the TripleO Wiki.

Getting Started

Documentation for the TripleO project is hosted on the OpenStack Gerrit site. You can view all open and resolved issues in the openstack/tripleo-docs project at TripleO Reviews.

General information about contributing to the OpenStack documentation available at OpenStack Documentation Contributor Guide

Quick Start

The following is a quick set of instructions to get you up and running by building the TripleO documentation locally. The first step is to get your Python environment configured. Information on configuring is available at Python Project Guide

Next you can generate the documentation using the following command. Be sure to run all the commands from within the recently checked out repository.

tox -edocs

Now you have the documentation generated for the various available formats from the local source. The resulting documentation will be available within the doc/build/ directory.