openstack/kolla-ansible
Code Issues Proposed changes

Add enable_haproxy to globals.yml

Browse Source 
Update comments and add enable_haproxy to let helpinners know how
to set kolla_internal_vip_address and deploy AIO OpenStack without
haproxy correctly.

As a beginner in kolla-ansible, current comments for
kolla_internal_vip_address let me belive that if I set it to my eth0 ip,
kolla-ansible will help deploy an AIO OpenStack without haproxy. But in
fact it throws an error, I get the right way after searching IRC log.

Change-Id: I1ba1ffe774ad0cf29543523a56854b9d7caa680a
This commit is contained in:
octopusZhang 2017-08-25 15:05:37 +08:00 committed by octopuszhang
parent 7716497d1e
commit 7d62a1c3ba
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
etc/kolla/globals.yml
View File

@ -24,8 +24,9 @@
#node_custom_config: "/etc/kolla/config"
# This should be a VIP, an unused IP on your network that will float between
# the hosts running keepalived for high-availability. When running an All-In-One
# without haproxy and keepalived, this should be the first IP on your
# the hosts running keepalived for high-availability. If you want to run an
# All-In-One without haproxy and keepalived, you can set enable_haproxy to no
# in "OpenStack options" section, and set this value to the first IP on your
# 'network_interface' as set in the Networking section below.
kolla_internal_vip_address: "10.10.10.254"
@ -147,6 +148,7 @@ kolla_internal_vip_address: "10.10.10.254"
#enable_freezer: "no"
#enable_gnocchi: "no"
#enable_grafana: "no"
#enable_haproxy: "yes"
#enable_heat: "yes"
#enable_horizon: "yes"
#enable_horizon_cloudkitty: "{{ enable_cloudkitty | bool }}"