OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 day ago|
|_custom||2 months ago|
|_templates||1 year ago|
|deploy-guide/source||5 months ago|
|doc/source||2 days ago|
|.gitignore||1 year ago|
|.gitreview||1 day ago|
|.zuul.yaml||7 months ago|
|README.rst||1 year ago|
|requirements.txt||1 year ago|
|setup.cfg||4 months ago|
|setup.py||1 year ago|
|test-requirements.txt||4 months ago|
|tox.ini||4 months ago|
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.
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
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.
Now you have the documentation generated for the various available formats from the local source. The resulting documentation will be available within the