From 3daa26ab646327098f4ff77ad64e8c0ae67ac11e Mon Sep 17 00:00:00 2001
From: Kevin Carter <kevin.carter@rackspace.com>
Date: Thu, 20 Oct 2016 22:43:22 -0500
Subject: [PATCH] [DOCS] Add note about extra VIP addresses

Change-Id: Icff55b02c6061f9fe250e132c951cd5add8c9caf
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
---
 doc/source/configure-haproxy.rst | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/doc/source/configure-haproxy.rst b/doc/source/configure-haproxy.rst
index 52fcc66..a17c2b5 100644
--- a/doc/source/configure-haproxy.rst
+++ b/doc/source/configure-haproxy.rst
@@ -150,7 +150,7 @@ various formats <https://search.thawte.com/support/ssl-digital-certificates/inde
 .. _Securing services with SSL certificates: configure-sslcertificates.html
 
 Configuring additional services
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Additional haproxy service entries can be configured by setting
 ``haproxy_extra_services`` in ``/etc/openstack_deploy/user_variables.yml``
@@ -169,3 +169,21 @@ An example HTTP service could look like:
           haproxy_ssl: "{{ haproxy_ssl }}"
           haproxy_port: 10000
           haproxy_balance_type: http
+
+
+Adding additional global VIP addresses
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In some cases, you might need to add additional internal VIP addresses
+to the load balancer front end. You can use the HAProxy role to add
+additional VIPs to all front ends by setting them in the
+``extra_lb_vip_addresses`` variable.
+
+The following example shows extra VIP addresses defined in the
+``user_variables.yml`` file:
+
+.. code-block:: yaml
+
+   extra_lb_vip_addresses:
+     - 10.0.0.10
+     - 192.168.0.10