Comment 8 for bug 1508575

James, in your comments above, it seems we are mixing physical host network setup (juju-br0) with lxc network setup. The lxcs should not have juju-br0 in them.

juju-br0 is used on the physical host to bridge traffic for itself and all of its lxcs.

We can apply a vip (an alias) to eth0 *inside* the lxc. We are doing that for ServerStack and I just stood up an independent test in another MAAS environment.

On the physcial host there are several bridges that allow the virtual networking. But notice that eth0 is a member of juju-br0 and that the IP for the physical host is on juju-br0. This is by design and works.

Example lxc eth0
sudo ip addr

43330: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:16:3e:b0:31:b1 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.50/24 brd 10.245.167.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 10.0.0.200/24 brd 10.245.167.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:feb0:31b1/64 scope link
       valid_lft forever preferred_lft forever

In this example 10.0.0.200 is the vip and .50 is the main ip for the lxc. Corosync decides which node has the alias for the vip.

So, we have not yet been able to recreate failure to distribute keystones vip. We still need to figure out what is different in your environment.