For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Id83308f29eb3dc23b20253b54735e529a9bd16d3
|7 years ago|
|doc||7 years ago|
|tools||7 years ago|
|www||7 years ago|
|.gitignore||7 years ago|
|.gitreview||12 years ago|
|LICENSE||11 years ago|
|README.rst||7 years ago|
|RELEASENOTES.rst||8 years ago|
|doc-test.conf||8 years ago|
|doc-tools-check-languages.conf||7 years ago|
|projects.txt||8 years ago|
|test-requirements.txt||7 years ago|
|tox.ini||7 years ago|
This repository contains documentation for the OpenStack project.
For more details, see the OpenStack Documentation Contributor Guide.
It includes these manuals:
- Admin User Guide
- Architecture Design Guide
- Cloud Administrator Guide
- Command-Line Interface Reference
- Configuration Reference
- Documentation Contributor Guide
- End User Guide
- Installation Guides
- Networking Guide
- Virtual Machine Image Guide
In addition to the guides, this repository contains:
- docs.openstack.org contents:
Various manuals are in subdirectories of the
Various guides are in the RST format. You can use tox to prepare virtual environment and build all RST based guides:
tox -e docs
You can also build a specific guide. For example, to build OpenStack End User Guide, use the following command:
tox -e build -- user-guide
You can find the root of the generated HTML documentation at:
Apache Maven must be installed to build the glossary.
To install Maven 3 for Ubuntu 12.04 and later, and Debian wheezy and later:
apt-get install maven
On Fedora 20 and later:
yum install maven
On openSUSE 13.1 and later:
zypper ar http://download.opensuse.org/repositories/devel:/tools:/building/openSUSE_13.1/devel:tools:building.repo zypper install maven
To build the glossary, move to
doc/glossary, then run the
mvn command in that directory:
cd doc/glossary mvn clean generate-sources
The generated PDF documentation file is:
The root of the generated HTML documentation is:
Testing of changes and building of the manual
Install the python tox package and run
tox from the top-level directory to use the same tests that are done as part of our Jenkins gating jobs.
If you like to run individual tests, run:
tox -e checklinks- to run the tests for working remote URLs
tox -e checkniceness- to run the niceness tests
tox -e checksyntax- to run syntax checks
tox -e checkdeletions- to check that no deleted files are referenced
tox -e checkbuild- to actually build the manual
tox -e checklang- to build translated manuals
tox will use the openstack-doc-tools package for execution of these tests.
Our community welcomes all people interested in open source cloud computing, and encourages you to join the OpenStack Foundation.
The best way to get involved with the community is to talk with others online or at a meet up and offer contributions through our processes, the OpenStack wiki, blogs, or on IRC at
We welcome all types of contributions, from blueprint designs to documentation to testing to deployment scripts.
If you would like to contribute to the documents, please see the OpenStack Documentation contributor guide.
Bugs should be filed on Launchpad, not GitHub:
Refer to http://docs.openstack.org to see where these documents are published and to learn more about the OpenStack project.