Clarify HAProxy configuration necessity

This was a little roadblock that I ran into when deploying
using openstack-ansible recently. The documentation doesn't
indicate that configuration of a load balancer is explicitly
required, and since the HAProxy installation playbook didn't
run automatically on setup-everything.yml the errors that I
got didn't lead me to figuring out that HAProxy was the
missing piece.

Change-Id: I8c15910f19e2be8ece3bac98bcbf82eb49045bf8
Partial-bug: #1552362
This commit is contained in:
Nate Potter 2016-03-02 14:01:32 -08:00 committed by Jesse Pretorius
parent aa0be5a88b
commit 267c49e135
1 changed files with 11 additions and 5 deletions

View File

@ -3,11 +3,17 @@
Configuring HAProxy (optional)
------------------------------
For evaluation, testing, and development, HAProxy can temporarily
provide load balancing services in lieu of hardware load balancers. The
default HAProxy configuration does not provide highly-available load
balancing services. For production deployments, deploy a hardware load
balancer prior to deploying OSA.
HAProxy provides load balancing for high availability architectures deployed by
OpenStack-Ansible. The default HAProxy configuration provides highly-available
load balancing services via keepalived if there are more than one hosts in the
``haproxy_hosts`` group.
.. note::
A load balancer is required for a successful installation. Deployers may
prefer to make use of hardware load balancers instead of haproxy. If hardware
load balancers are used then the load balancing configuration for services must
be implemented prior to executing the deployment.
To deploy HAProxy within your OpenStack-Ansible environment, define target
hosts which should run HAProxy: