Comment 38 for bug 1375625

@Alex Shouldn't this bug keep the l3-ha tag?

Also, I just noticed that apparently I never updated this bug with the results from the Atlanta PTG, but they are summarised here:

http://lists.openstack.org/pipermail/openstack-dev/2017-February/112868.html

In particular, this ethercalc summarises how the various failure modes are or aren't covered depending on how L3 HA is set up:

https://ethercalc.openstack.org/Pike-Neutron-L3-HA

Having said that, rereading the comments here makes me wonder if the spreadsheet was 100% accurate - at very least it was missing the possibility that Pacemaker can monitor networks other than the corosync network, and I have a vague memory of Assaf *maybe* mentioning that RH has it set up to do that (although I see no evidence of that in the https://github.com/beekhof/osp-ha-deploy repo).