Skip to content
OpenStack Manuals
HTML CSS Python JavaScript Shell
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc Merge "Update the VM Image Guide" Sep 12, 2019
releasenotes/source Imported Translations from Zanata Jul 26, 2019
tools Simplify publishdocs et al Aug 16, 2019
www Add adjutant to index pages Aug 28, 2019
.gitignore cache expensive repo/project metadata to disk Jan 4, 2019
.gitreview OpenDev Migration Patch Apr 19, 2019
.pydevproject [config-ref] Update api-paste.ini of manila Apr 13, 2017
.zuul.yaml Zuul: Remove success-url Aug 24, 2019
CONTRIBUTING.rst [contrib-guide] Updating url to doc-contrib-guide Sep 22, 2017
LICENSE bug 944097 adding apache license to openstack-manuals repo Mar 9, 2012
README.rst Cleanup jobs and config Aug 16, 2019
bindep.txt Add missing fonts for pdf build in Sphinx 2.0 Apr 6, 2019
doc-tools-check-languages.conf Add api-quick-start translations Jul 24, 2019
test-requirements.txt Update for openstack-doc-tools 2.0 Aug 22, 2019
tox.ini Update for openstack-doc-tools 2.0 Aug 22, 2019


Team and repository tags

OpenStack Manuals

This repository contains documentation for the OpenStack project.

For more details, see the OpenStack Documentation Contributor Guide.

It includes these manuals:

  • Architecture Design Guide
  • Documentation Contributor Guide
  • High Availability Guide
  • Installation Guide
  • Virtual Machine Image Guide

In addition to the guides, this repository contains:

  • contents: www


Various manuals are in subdirectories of the doc/ directory.


Some pre-requisites are needed to build the guides. If you are using a Linux operating system you can generate a report of missing local requirements with the bindep command:

$ tox -e bindep

All guides are in the RST format. You can use tox to prepare virtual environment and build all guides (HTML only):

$ tox -e docs

You can also build a specific guide.

For example, to build OpenStack Virtual Machine Image Guide, use the following command:

$ tox -e build -- image-guide

You can find the root of the generated HTML documentation at:


To build a specific guide with a PDF file, add a -pdf option like:

$ tox -e build -- image-guide --pdf

The generated PDF file will be copied to the root directory of the generated HTML documentation.

PDF builds are accomplished using LaTeX as an intermediate format. Currently, you can generate a PDF file for a limited number of guides. The supported list is maintained in the tools/ file.

If you get the error message make: xelatex: No such file or directory, it means your local environment does not have LaTeX installed. Read Getting LaTeX and Install dependencies for building documentation for instructions.

Testing of changes and building of all manuals

Install the Python tox package and run tox from the top-level directory to use the same tests that are done as part of the OpenStack CI jobs.

If you like to run individual tests, run:

  • tox -e publishdocs - to actually build the manual; this also generates a directory publish-docs that contains the built files for inspection
  • tox -e publishlang - to build translated manuals
  • tox -e linters - to run the niceness tests, for example, to see extra whitespaces
  • tox -e linkcheck - to run the tests for working remote URLs

The tox command uses the openstack-doc-tools package to run the tests.

Generated files

Some documentation files are generated using tools. These files include a do not edit header and should not be modified by hand. Please see Generated files.


Bugs should be filed on Launchpad, not GitHub:

Release Notes


Refer to to see where these documents are published and to learn more about the OpenStack project.

You can’t perform that action at this time.