Use separate interfaces for lb traffic

Currently, deploying a multi-node AIO results in
internal_lb_vip_address and external_lb_vip_address being set to the
same IP (10.0.236.150), which results in services having issues
communicating with the lb.

This commit simply sets external_lb_vip_address to use the
load balancer's dhcp address, which is fixed to 10.0.2.150.

Change-Id: I6faabd641c0559a0381e559f364cc76c49293014
This commit is contained in:
Matt Thompson 2017-08-29 12:12:47 -04:00 committed by weezer su
parent ee85d37ce9
commit 33fb2d2ffa

View File

@ -12,8 +12,8 @@ used_ips:
- "10.0.248.0,10.0.248.200" - "10.0.248.0,10.0.248.200"
global_overrides: global_overrides:
internal_lb_vip_address: "{{ external_lb_vip_address | default(hostvars[groups['loadbalancer_hosts'][0]]['server_networks']['mgmt']['address'].split('/')[0]) }}" internal_lb_vip_address: "{{ internal_lb_vip_address | default(hostvars[groups['loadbalancer_hosts'][0]]['server_networks']['mgmt']['address'].split('/')[0]) }}"
external_lb_vip_address: "{{ external_lb_vip_address | default(hostvars[groups['loadbalancer_hosts'][0]]['ansible_host'].split('/')[0]) }}" external_lb_vip_address: "{{ external_lb_vip_address | default(hostvars[groups['loadbalancer_hosts'][0]]['server_vm_fixed_addr']) }}"
tunnel_bridge: "br-vxlan" tunnel_bridge: "br-vxlan"
management_bridge: "br-mgmt" management_bridge: "br-mgmt"
provider_networks: provider_networks: