<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div>I opened some time ago a thread about this argument (more in general about HA for OpenStack): <a href="http://www.gossamer-threads.com/lists/openstack/operators/33777">http://www.gossamer-threads.com/lists/openstack/operators/33777</a>.</div><div>Now I'm definitely focusing on making the Neutron's agents highly available.</div><div><br></div><div>As stated in the mentioned thread there's no solution for making L3 agent HA with the active/active paradigm. But I have to use the active/active paradigm.</div><div><br></div><div>In the mentioned thread, Jay suggests to use a tool to replicate l3 agent's status to the other node upon failure of the current node (I haven't used this tool yet).</div><div><br></div><div>Reading the HA guide by Openstack (<a href="http://docs.openstack.org/high-availability-guide/content/_running_neutron_metadata_agent.html">http://docs.openstack.org/high-availability-guide/content/_running_neutron_metadata_agent.html</a>) there's not a solution active/active-based also for the metadata agent.</div><div><br></div><div>I wonder if there's a similar tool to replicate the metadata agent's status on the other node, as for the l3 agent.</div><div><br></div><div>thank you,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Alvise</div></body></html>