From 7d62a1c3ba96d7935eaaae1d50d0982a2eb7b2c3 Mon Sep 17 00:00:00 2001 From: octopusZhang Date: Fri, 25 Aug 2017 15:05:37 +0800 Subject: [PATCH] Add enable_haproxy to globals.yml 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 --- etc/kolla/globals.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/etc/kolla/globals.yml b/etc/kolla/globals.yml index 0699b313e4..48d9a9c384 100644 --- a/etc/kolla/globals.yml +++ b/etc/kolla/globals.yml @@ -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 }}"