As far as I understood neutron L3 HA is done by having scheduled more than one L3 agent per virtual router. When ODL is used to manage L3 traffic, I still can check the option neutron L3 HA, but as far as I know there are no L3 agents anymore (only DHCP and metadata agents).
Now to my questions:
Has checking the neutron L3 HA option in fuel gui network setup any effect when using ODL to manage L3 traffic ? Does ODL have something like L3 HA, and if so is it enabled when checking the L3 HA setup ?
ODL is only deployed on one controller node. so for the ODL part this setup is not HA. What are the effects when this particular controller node is down and some requests hit the neutron API northbound of ODL? does ODL sync with the actual neutron database state when coming back online, and setup ovs bridges accordingly ?
IP consumption in the public network: I understand each node needs access to public network physically in ODL (or also in DVR) setups. However I dont understand why compute nodes are needing an IP address on this link. In my former DVR based setups this was not the case. Has anybody an explanation for this? In my understanding every controller node needs an IP in the public network plus the VIP for HAproxy. (publicvip) In my deplyoment I see another IP allocated in the public network: (publicvroutervip) What is this IP (publicvrouter_vip) used for ?
Thanks in advance. D