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.
John Fulton ac11884704 Document ApplyCephConfigOverridesOnUpdate 2 weeks ago
_custom Introduce new TLS-e guide 1 year ago
_templates Unify undercloud upgrade steps 4 years ago
deploy-guide/source Document ApplyCephConfigOverridesOnUpdate 2 weeks ago
doc Update irc server references in docs to new network 5 months ago
.gitignore Update 3rd party container build with new tooling 1 year ago
.gitreview OpenDev Migration Patch 3 years ago
.zuul.yaml Run deploy guide jobs 2 years ago
README.rst PDF documentation build 2 years ago
bindep.txt Add a bindep. 2 years ago
requirements.txt Switch to newer openstackdocstheme and reno versions 1 year ago
setup.cfg setup.cfg: Replace dashes with underscores 6 months ago Cleanup py27 support and docs 2 years ago
tox.ini Update tox.ini for tripleo-docs 6 months 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,pdf-docs,deploy-guide

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.