RETIRED, Documentation for TripleO
Go to file
Jiri Podivin d288ff2332 Documentation reflects current state of VF
Documentation previously referenced mistral.
Which has been deprecated and removed some time ago.

Added references to the VF docs and information about
how validations should be run.

Relinked the docs.

Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: Iea6d1f818dc3a80ff60621575fe27b7c47d5ea77
2021-05-05 09:49:04 +02:00
_custom Introduce new TLS-e guide 2020-08-04 10:56:21 -05:00
_templates Unify undercloud upgrade steps 2017-10-17 15:25:38 +02:00
deploy-guide/source Documentation reflects current state of VF 2021-05-05 09:49:04 +02:00
doc Add some docs for pre_deploy_step_tasks 2021-04-02 18:53:24 +02:00
.gitignore Update 3rd party container build with new tooling 2020-06-05 19:58:30 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:43:03 +00:00
.zuul.yaml Run deploy guide jobs 2019-08-21 13:41:28 +05:30
README.rst PDF documentation build 2019-09-17 17:20:48 +02:00
bindep.txt Add a bindep. 2019-10-04 15:57:20 +02:00
requirements.txt Switch to newer openstackdocstheme and reno versions 2020-05-28 14:42:29 +02:00
setup.cfg Cleanup py27 support and docs 2020-04-11 16:32:11 +02:00
setup.py Cleanup py27 support and docs 2020-04-11 16:32:11 +02:00
tox.ini Merge "Remove install unnecessary packages" 2020-09-25 14:34:09 +00:00

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.