
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
13 lines
502 B
ReStructuredText
13 lines
502 B
ReStructuredText
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
|