Documentation for TripleO
You can not 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
Natal Ngétal 03e4013b9f
Update stable version.
4 years ago
_custom Update stable version. 4 years ago
_templates Unify undercloud upgrade steps 6 years ago
deploy-guide/source Upgrade hacking fixed linting 4 years ago
doc/source Update stable version. 4 years ago
.gitignore Update .gitignore 6 years ago
.gitreview Add .gitreview 8 years ago
.zuul.yaml Cleanup zuul.yaml 5 years ago
README.rst Replace the old links in docs 5 years ago
requirements.txt Switch to openstackdocstheme 6 years ago
setup.cfg Change openstack-dev to openstack-discuss 4 years ago Manually sync global-requirements 6 years ago
test-requirements.txt Add simple diagram for contributor guide promotion stages 4 years ago
tox.ini [Configuration] Update min tox version. 4 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.