<div dir="ltr">Hello,<div><br></div><div>Thank you for your answer. I'm looking now in "multiple l3 agent". </div><div><br></div><div>Really, what we like, is : bare metal => layer 2 ; virtual machine => layer 3. </div>
<div>So network node works on layer 2 (external vlan and gre tunnel) and we have virtual machine for layer 3 (IP, firewall, loadBalancer, ....).</div><div>At least I didn't see how openstack can deploy a tenant/project/full featured plate-forme with layer 3 located on a VM ?</div>
<div><br></div><div>Robert, can you tell me more about new function ? and "not hard-wire" ? </div><div><br></div><div>Thank you.</div><div><br></div><div>Regards,</div><div><br></div><div><br></div><div><br></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-28 20:03 GMT+02:00 Robert Kukura <span dir="ltr"><<a href="mailto:kukura@noironetworks.com" target="_blank">kukura@noironetworks.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Also, note that the Modular L2 (ML2) plugin does not hard-wire a particular implementation of the L3 router API. There is a service plugin that implements this via Neutron's l3-agent, but other options are possible as well (and are being developed).<br>
<br>
-Bob<div class="HOEnZb"><div class="h5"><br>
<br>
On 5/28/14, 9:02 AM, Jasper Capel wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You are also free to not use the L3 agent at all and just patch a few virtual routers into the L2 segments you want them to route (obviously this will result in floating IPs, routing, etc not being managed by Neutron).<br>
<br>
Jasper<br>
<br>
<br>
On 28 May 2014, at 14:14, Ageeleshwar Kandavelu <<a href="mailto:Ageeleshwar.Kandavelu@csscorp.com" target="_blank">Ageeleshwar.Kandavelu@<u></u>csscorp.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think you are looking for multiple neutron-l3-agent. It is possible and has been discussed many times before in mailing lists. Just do a google search 'multiple l3 agent in openstack' you should be able to find some link to start with.<br>
From: Benoit ML [<a href="mailto:ben42ml@gmail.com" target="_blank">ben42ml@gmail.com</a>]<br>
Sent: Wednesday, May 28, 2014 2:15 PM<br>
To: <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a>; Benoit ML<br>
Subject: [Openstack] Network Architecture - Separate Layer 2 and Layer 3 - neutron/network node only l2<br>
<br>
Hello,<br>
<br>
<br>
I'm writing to you because I'd like to discute about the separation of layer 2 and layer 3.<br>
<br>
Can openstack network node only work on layer 2 with a dedicated server ? and all layer 3 configuration done elsewere ?<br>
<br>
The idea is : netowk node manage layer 2 topologie (openvswitch/gre tunnel) and Layer 3 is dedicacted to virtual machine/application.<br>
For evry tenant i'm thinking about a VM doing all L3 jobs (router, firewall, loadbalancing, ....)<br>
<br>
Did you see what i mean ? Is it possible ?<br>
<br>
Thank you in advance !<br>
<br>
Regads,<br>
<br>
ps : sorry for my english ;)<br>
<br>
--<br>
Benoit<br>
<a href="http://www.csscorp.com/common/email-disclaimer.php" target="_blank">http://www.csscorp.com/common/<u></u>email-disclaimer.php</a> ______________________________<u></u>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>--<br>Benoit<br>
</div>