From 10502c9bad534d307c6341adfd824e742c4492b9 Mon Sep 17 00:00:00 2001 From: Shannon Mitchell Date: Tue, 2 Oct 2018 12:42:53 -0500 Subject: [PATCH] multi-noda-aio loadbalancer routing issues fix The loadbalancer vm is configured to utilize br-dhcp for the external vip and br-mgmt for the internal vip. Users end up accessing these from various networks depending on the dev/testing going on. For example if you utilize the flat network for vms that need to hit the external api, the calls fail. This is due to traffic coming in on br-dhcp then going back out on br-flat. This change is to remove the unused interfaces to cut down on routing issues in the load balancer. Change-Id: Ic3c3bd18e63943ff288692da20d449852a316b5e Closes-Bug: #1795710 --- .../playbooks/host_vars/loadbalancer1.yml | 20 +------------------ 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/multi-node-aio/playbooks/host_vars/loadbalancer1.yml b/multi-node-aio/playbooks/host_vars/loadbalancer1.yml index 9c4a2ae4..d9b61b1b 100644 --- a/multi-node-aio/playbooks/host_vars/loadbalancer1.yml +++ b/multi-node-aio/playbooks/host_vars/loadbalancer1.yml @@ -27,22 +27,4 @@ server_networks: inet_type: 'static' address: '10.0.236.150/22' vm_int_iface: vm-br-eth1 - flat: - iface: 'eth2' - inet_type: 'static' - address: '10.0.248.150/22' - vm_int_iface: vm-br-eth2 - vlan: - iface: 'eth3' - inet_type: 'manual' - vm_int_iface: vm-br-eth3 - vxlan: - iface: 'eth4' - inet_type: 'static' - address: '10.0.240.150/22' - vm_int_iface: vm-br-eth4 - storage: - iface: 'eth5' - inet_type: 'static' - address: '10.0.244.150/22' - vm_int_iface: vm-br-eth5 +