This patch use "project" to replace "tenant" term in image-guide for cleanup. Partial-Bug: #1475005 Change-Id: I4ef7db5634968da6b8eed14a4b650a43228a18f1
|7 years ago|
|doc||7 years ago|
|releasenotes/source||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|
|bindep.txt||7 years ago|
|doc-test.conf||7 years ago|
|doc-tools-check-languages.conf||7 years ago|
|projects.txt||7 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:
- Administrator Guide
- Architecture Design Guide
- Command-Line Interface Reference
- Configuration Reference
- Documentation Contributor Guide
- End User Guide
- High Availability Guide
- Installation Guide
- Networking Guide
- Operations Guide
- Virtual Machine Image Guide
In addition to the guides, this repository contains:
- docs.openstack.org contents:
Various manuals are in subdirectories of the
All guides are in the RST format. You can use tox to prepare virtual environment and build all 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:
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 linkcheck- to run the tests for working remote URLs
tox -e checkniceness- to run the niceness tests
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.
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:
Refer to http://docs.openstack.org to see where these documents are published and to learn more about the OpenStack project.