Move the HA setup notes to its own page

This moves the guide on setting up high availability from the easily
missed note under Basic deployment to its own page under Advanced
deployment.

HA is an advanced mode of deployment -- one that requires the operators
to learn Pacemaker, deal with more complex configuration of services,
etc.

The page can later be augmented with notes on debugging a HA setup and
talk about pacemaker-lite once that's ready.

Change-Id: If10f00ddebe52d9d19d8c2a1e3b8394115852d60
This commit is contained in:
Tomas Sedovic 2016-06-08 16:29:30 +02:00
parent 02869b84d3
commit dd6dbd5c8e
3 changed files with 16 additions and 9 deletions

View File

@ -17,6 +17,7 @@ In this chapter you will find advanced deployment of various |project| areas.
template_deploy
network_isolation
network_isolation_virt
high_availability
deploy_manila
cinder_netapp
ceph_config
@ -27,4 +28,3 @@ In this chapter you will find advanced deployment of various |project| areas.
# relevant to regular users.
tripleo.sh
in_progress_review

View File

@ -0,0 +1,12 @@
Configuring High Availability
=============================
|project| supports high availability of the controller services using
Pacemaker. To enable this feature, you need at least three controller
nodes, enable Pacemaker as the resource manager and specify an NTP
server.
Adding the following arguments to your `openstack overcloud deploy`
command will do the trick::
--control-scale 3 -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml --ntp-server pool.ntp.org

View File

@ -339,20 +339,15 @@ Run the deploy command, including any additional parameters as necessary::
openstack overcloud deploy --templates [additional parameters]
To deploy an overcloud with multiple controllers and achieve HA,
follow :doc:`../advanced_deployment/high_availability`.
.. admonition:: Virtual
:class: virtual
When deploying the Compute node in a virtual machine, add ``--libvirt-type
qemu`` or launching instances on the deployed overcloud will fail.
.. note::
To deploy an overcloud with multiple controllers and achieve HA
you must provision at least 3 controller nodes, specify an NTP
server and enable Pacemaker as cluster resource manager. To do
so add the following arguments to the deploy command::
--control-scale 3 -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml --ntp-server pool.ntp.org
.. note::
To deploy the overcloud with network isolation, bonds, and/or custom