From dd6dbd5c8e00ad5cc992c3b24dea52428f33a144 Mon Sep 17 00:00:00 2001 From: Tomas Sedovic Date: Wed, 8 Jun 2016 16:29:30 +0200 Subject: [PATCH] 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 --- .../advanced_deployment/advanced_deployment.rst | 2 +- doc/source/advanced_deployment/high_availability.rst | 12 ++++++++++++ doc/source/basic_deployment/basic_deployment_cli.rst | 11 +++-------- 3 files changed, 16 insertions(+), 9 deletions(-) create mode 100644 doc/source/advanced_deployment/high_availability.rst diff --git a/doc/source/advanced_deployment/advanced_deployment.rst b/doc/source/advanced_deployment/advanced_deployment.rst index 24e649ae..4f2d5c69 100644 --- a/doc/source/advanced_deployment/advanced_deployment.rst +++ b/doc/source/advanced_deployment/advanced_deployment.rst @@ -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 - diff --git a/doc/source/advanced_deployment/high_availability.rst b/doc/source/advanced_deployment/high_availability.rst new file mode 100644 index 00000000..3069995b --- /dev/null +++ b/doc/source/advanced_deployment/high_availability.rst @@ -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 diff --git a/doc/source/basic_deployment/basic_deployment_cli.rst b/doc/source/basic_deployment/basic_deployment_cli.rst index 7d95b204..3bc762e4 100644 --- a/doc/source/basic_deployment/basic_deployment_cli.rst +++ b/doc/source/basic_deployment/basic_deployment_cli.rst @@ -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