On 02/08/14 02:22, Assaf Muller wrote: > Hey Marios, comments inline. > > ----- Original Message ----- >> Hi all, >> >> I have been asked by a colleague about the status of A/A HA for >> neutron-* processes. From the 'HA guide' [1], l3-agent and >> metadata-agent are the only neutron components that can't be deployed in >> A/A HA (corosync/pacemaker for a/p is documented as available 'out of >> the box' for both). >> >> The l3-agent work is approved for J3 [4] but I am unaware of any work on >> the metadata-agent and can't see any mention in [2][3]. Is this someone >> has looked at, or is planning to (though ultimately K would be the >> earliest right?)? >> > > With L3 HA turned on you can run the metadata agent on all network nodes. > The active instance of each router will have the proxy up in its namespace > and it will forward it to the agent as expected. perfect thanks Assaf as well as for the follow up clarifications on irc, I didn't realise this was the case, all the best, marios > >> thanks! marios >> >> [1] http://docs.openstack.org/high-availability-guide/content/index.html >> [2] https://wiki.openstack.org/wiki/NeutronJunoProjectPlan >> [3] https://launchpad.net/neutron/+milestone/juno-3 >> [4] >> http://git.openstack.org/cgit/openstack/neutron-specs/tree/specs/juno/l3-high-availability.rst >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >