<div dir="ltr">I'm also very interested to hear about this. From the looks of it, there won't be an Active/Active solution for the L3 agent without intervention.<div><br></div><div>If you look back through the thread, you'll see a couple links to bugs/bps which are in place for Havana. The DHCP agent is now Active/Active.</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 12, 2013 at 6:00 AM, Kevin Jackson <span dir="ltr"><<a href="mailto:kevin@linuxservices.co.uk" target="_blank">kevin@linuxservices.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi all,<div>What is the current development status of Neutron and HA. We all should know by now some of the issues we have and have to workaround with the likes of the L3 agent, and it's routes being available on a single node that luckily got the request to create it. If it fails, routing fails.</div>
<div><br></div><div>In order for Neutron to be feature-parity with Nova Network, I expect this to be a solved solution in Havana? Is that a fair assumption or would we still need to make decisions around Neutron to include/exclude L3 agents and put some workarounds in place still?</div>
<div><br></div><div>Thanks!</div><div><br></div><div>Kev</div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On 16 August 2013 10:19, PREMSUDHAN CHRISTOPHER.J <span dir="ltr"><<a href="mailto:premedge@gmail.com" target="_blank">premedge@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Simon/Roman/Jacob,<br></div> I was reading your thread about Network node HA and even i wanted the same thing to setup in our environment,But Am little confused as you guys were talking about only three components (i.e quantum-dhcp-agent, quantum-ovs-plugin-agent (i believe this is referred as L2 agent in the thread), Quantum-L3-agent). There is one more daemon running "quantum-metadata-agent" in network node, How do we achieve HA for it?<br>
<br>Apart from DHCP and L3 agent, can we have keepalived or pacemaker (just switching the VIP or active/passive) for quantum-ovs-plugin-agent & quantum-metadata-agent.? <br><br></div>Also for "Quantum L3 agent" will the telekomcloud solution work with Openvswitch along with Vlan ? Also apart from VM internet connectivity what are the other impacts when we do not have HA for L3 agent (i hope VM instance will be accessible over the LAN even if L3 agent is down and if we have the gateway of VM instance pointing to physical router or firewall still we can achieve internet connectivity ) ?<br>
<br></div>Thanks & Regards,<br></div>Premsudhan Christopher.<br></div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On Tue, Jul 23, 2013 at 5:24 PM, Jacob Godin <span dir="ltr"><<a href="mailto:jacobgodin@gmail.com" target="_blank">jacobgodin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Not specifically to Neutron HA, but a great video none the less: <a href="http://www.youtube.com/watch?v=N9mPepfxm-4" target="_blank">http://www.youtube.com/watch?v=N9mPepfxm-4</a></div>
<div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Jul 19, 2013 at 11:09 AM, Roman Podolyaka <span dir="ltr"><<a href="mailto:rpodolyaka@mirantis.com" target="_blank">rpodolyaka@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,<div><br></div><div>Thanks, Akihiro and Simon! I didn't know we had such option.</div><div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
>> Regarding 1, the configuration option "dhcp_agents_per_network" is introduced. This options specifies the number of DHCP agents scheduled to host a network.</div><div style="font-family:arial,sans-serif;font-size:13px">
>> If you set this option to the number of dhcp agents, you can do this.</div></div><div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
>> It already exists in Havana by setting the dhcp_agents_per_network parameter in neutron.conf .</div>
<span style="font-family:arial,sans-serif;font-size:13px">>> Check this commit for details: </span><a href="https://github.com/openstack/neutron/commit/c95e58b70796eae6bbc8bac283f81df9aa1d1894" style="font-family:arial,sans-serif;font-size:13px" target="_blank">https://github.com/openstack/neutron/commit/c95e58b70796eae6bbc8bac283f81df9aa1d1894</a></div>
</div><div><div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 19, 2013 at 4:35 PM, Simon Pasquier <span dir="ltr"><<a href="mailto:simon.pasquier@bull.net" target="_blank">simon.pasquier@bull.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Le 19/07/2013 15:07, Roman Podolyaka a
écrit :<br>
</div><div>
<blockquote type="cite">
<div dir="ltr">Hi Jacob, all
<div><br>
</div>
<div>1. When a new Neutron network is created, it is
automatically scheduled to one of DHCP-agents running in a
cluster (actually, it's done lazily, when the first port on
this network is created, but that's an implementation detail).
Though, you have to manually schedule it to additional
DHCP-agents to provide HA. I haven't seen any BPs adding such
an option, but I agree, that it would be useful to have one.</div>
</div>
</blockquote>
<br></div>
It already exists in Havana by setting the dhcp_agents_per_network
parameter in neutron.conf
.<br>
Check this commit for details:<br>
<a href="https://github.com/openstack/neutron/commit/c95e58b70796eae6bbc8bac283f81df9aa1d1894" target="_blank">https://github.com/openstack/neutron/commit/c95e58b70796eae6bbc8bac283f81df9aa1d1894</a><br>
<br>
<blockquote type="cite"><div>
<div dir="ltr">
<div><br>
</div>
<div>2. Not sure we have one :( The solution from TelekomCloud
guys seems to be the only way to go to provide HA for L3
agents in Active/Active mode currently. </div>
<div><br>
</div>
<div>3. Every network or compute node in a cluster runs an
L2-agent, which allows one to create L2 tenant networks and
plug VMs/routers/DHCP-servers into network ports (the
underlying implementation depends on the core plugin you use,
e.g. OVS can use VLANs or GRE tunnels to provide tenant
isolation). So L2 networking is ready to use when you've
started an L2-agent and provided it with a correct
configuration file.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Roman</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div><div><pre>_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</div></blockquote><span><font color="#888888">
<br>
<br>
<pre cols="72">--
Simon Pasquier
Software Engineer
Bull, Architect of an Open World
Phone: <a href="tel:%2B%2033%204%2076%2029%2071%2049" value="+33476297149" target="_blank">+ 33 4 76 29 71 49</a>
<a href="http://www.bull.com" target="_blank">http://www.bull.com</a></pre>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br></div></div>Warm Regards ,<br><br>Premsudhan.J
</div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br></div></div><span class="HOEnZb"><font color="#888888"><div dir="ltr">Kevin Jackson<br><a href="http://about.me/kevjackson" target="_blank">http://about.me/kevjackson</a><br>
@itarchitectkev</div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>