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.
 
 
 
 
 
Natal Ngétal e017f31915 Add a bindep. 2 years ago
_custom Merge "Modify judgment logic" 2 years ago
_templates Unify undercloud upgrade steps 4 years ago
deploy-guide/source Removed references to tripleo-centos-ceph-jewel.repo 2 years ago
doc Fix tripleo-validations documentation page URL 2 years ago
.gitignore Update .gitignore 4 years ago
.gitreview OpenDev Migration Patch 2 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 PDF documentation build 2 years ago
setup.cfg Use "modern" way of building docs 2 years ago
setup.py Manually sync global-requirements 4 years ago
test-requirements.txt PDF documentation build 2 years ago
tox.ini Add a bindep. 2 years ago

README.rst

Team and repository tags

image

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.