openstack/openstack-ansible
Code Issues Proposed changes

Updated hostlayout to fix some wording

Browse Source 
The change removes the documented "HARD" requirement to have
a physical load balancer which is absolutly not true when deploying
the project.

Change-Id: I9832a1f8fd67c148800a0062bbf8f264920cba5c
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
Kevin Carter 2015-10-14 21:00:22 -05:00
parent 8b91ad32f7
commit 7d8ca7ad02
No known key found for this signature in database
GPG Key ID: 69FEFFC5E2D9273F
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/install-guide/overview-hostlayout.rst
View File

@ -22,8 +22,11 @@ environment within these hosts. The OSA environment also recommends a
*deployment host* from which Ansible orchestrates the deployment
process. One of the target hosts can function as the deployment host.
At least one hardware load balancer **must** be included to manage the
traffic among the target hosts.
At least one load balancer **must** be used to manage the traffic among
the target hosts. This can be any load balance of any type (hardware, haproxy,
etc). While OpenStack-Ansible has playbooks and roles for deploying haproxy
it's recommended for deployers to use physical load balancers when moving to
production.
Infrastructure Control Plane target hosts contain the following
services: