OpenStack High Availability Guide
Go to file
Tom Fifield dcd8735e31 Liberty release updates
With the release of liberty, some links in this guide
needed to be updated. Where possible, links were updated
to liberty. Since the guide appears to rely on the older
3-node architecture, some links have only been updated to
the kilo release (which is the same as Juno).

Change-Id: Ifc2ea3ea926dff139b9ea93e4919ee0876bace54
2015-10-15 16:15:37 +08:00
doc Liberty release updates 2015-10-15 16:15:37 +08:00
tools Use doc-tools-build-rst 2015-10-12 20:20:31 +02:00
.gitignore Add RST infrastructure for HA Guide 2015-05-02 09:08:43 +02:00
.gitreview Setup ha-guide infrastructure 2014-09-15 19:40:07 +02:00
README.rst Delete XML HA Guide 2015-10-12 12:21:13 +02:00
doc-test.conf Rename doc/ha-guide to doc/high-availability-guide 2014-09-21 07:03:26 +02:00
doc-tools-check-languages.conf Fix language publishing 2015-10-12 14:58:41 +02:00
test-requirements.txt Merge "Update for openstackdocstheme 1.2.3" 2015-10-13 06:38:57 +00:00
tox.ini Use doc-tools-build-rst 2015-10-12 20:20:31 +02:00

README.rst

OpenStack High Availability Guide

This repository contains the OpenStack High Availability Guide.

For more details, see the OpenStack Documentation wiki page.

Building

The root directory of the OpenStack High Availability Guide is doc/ha-guide.

To build the guide, run tox -e docs.

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 checkniceness - to run the niceness tests
  • tox -e checkbuild - to actually build the manual

tox will use the openstack-doc-tools package for execution of these tests.

Contributing

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 #openstack on irc.freenode.net.

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 Documentation HowTo.

Bugs

Bugs should be filed on Launchpad, not GitHub:

https://bugs.launchpad.net/openstack-manuals

Installing

Refer to http://docs.openstack.org to see where these documents are published and to learn more about the OpenStack project.