<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 4 April 2017 at 07:53, Saverio Proto <span dir="ltr"><<a href="mailto:saverio.proto@switch.ch" target="_blank">saverio.proto@switch.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Armando,<br>
<br>
I managed to implement the L2GW setup purely in software, without an<br>
hardware appliance.<br>
<br>
I documented in the README file, please look at this review<br>
<a href="https://review.openstack.org/453209" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>453209</a></blockquote><div><br></div><div>Nice job!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
I have a question: do we have a name for this node where the actually<br>
bridging happens between a VXLAN tenant network and a physical L2 network ?<br>
Is it okay to call it the l2gw agent ?<br></blockquote><div><br></div><div>Historically this was called l2gw agent (node). You can find references in [1,2]</div><div>  </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The l2gw plugin it self runs on the controller, so also the<br>
neutron-l2gw-plugin agent runs on the controller.<br>
<br>
I think it necessary to clarify this naming, because before trying the<br>
software I did the mistake of thinking that the neutron-l2gw-agent had<br>
to run on the switch where the actual briding happens.<br></blockquote><div><br></div><div>The l2gw agent uses solely OVSDB to interact to the server and as such it can run anywhere. In fact, in Arista's POC video [3] (credit to Sukhdev), the demo setup shows this in more details.</div><div><br></div><div>Cheers,</div><div>Armando</div><div><br></div><div><div>[1] <a href="https://github.com/openstack/networking-l2gw/blob/master/doc/source/images/L2GW_deployment.png">https://github.com/openstack/networking-l2gw/blob/master/doc/source/images/L2GW_deployment.png</a></div><div>[2] <a href="https://github.com/openstack/networking-l2gw/blob/master/specs/kilo/l2-gateway-api-implementation.rst">https://github.com/openstack/networking-l2gw/blob/master/specs/kilo/l2-gateway-api-implementation.rst</a></div></div><div>[3] <a href="https://www.youtube.com/watch?v=WpilpgPnYrE">https://www.youtube.com/watch?v=WpilpgPnYrE</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
thank you<br>
<span class="gmail-"><br>
Saverio<br>
<br>
<br>
<br>
<br>
On 30/03/17 18:40, Armando M. wrote:<br>
><br>
><br>
</span><span class="gmail-">> On 30 March 2017 at 08:47, Saverio Proto <<a href="mailto:saverio.proto@switch.ch">saverio.proto@switch.ch</a><br>
</span><div><div class="gmail-h5">> <mailto:<a href="mailto:saverio.proto@switch.ch">saverio.proto@switch.<wbr>ch</a>>> wrote:<br>
><br>
>     Hello,<br>
><br>
>     I am trying to use the neutron l2gw plugin, but I am not using a bare<br>
>     metal switch to bridge.<br>
><br>
>     I am using a server with Openvswitch.<br>
><br>
><br>
> I am not aware of any effort to implement L2GW purely in software, in<br>
> fact this was one key missing pieces that prevented the project to have<br>
> CI solely dealt with the upstream infra resources. Perhaps OVN may come<br>
> to the rescue here, I recall at some point the team was looking at the<br>
> L2GW API.<br>
><br>
> Thanks,<br>
> Armando<br>
><br>
><br>
><br>
>     Following this documentation:<br>
><br>
>     <a href="http://networkop.co.uk/blog/2016/05/21/neutron-l2gw/" rel="noreferrer" target="_blank">http://networkop.co.uk/blog/<wbr>2016/05/21/neutron-l2gw/</a><br>
>     <<a href="http://networkop.co.uk/blog/2016/05/21/neutron-l2gw/" rel="noreferrer" target="_blank">http://networkop.co.uk/blog/<wbr>2016/05/21/neutron-l2gw/</a>><br>
><br>
>     At one point there is this command:<br>
><br>
>     sudo vtep-bootstrap L5 10.0.0.5 192.168.91.21 --no_encryption<br>
><br>
>     This vtep-bootstrap is specific for Cumulux Linux<br>
><br>
>     Anybody has documentation with normal vtep-ctl commands ?<br>
><br>
>     So far on the Ubuntu server I did the following:<br>
><br>
>     apt-get install openvswitch-vtep<br>
>     ovsdb-tool create /etc/openvswitch/vtep.db<br>
>     /usr/share/openvswitch/vtep.<wbr>ovsschema<br>
><br>
>     Anyone has more complete documentation ?<br>
><br>
>     I did not understand if the vtep-openvswitch controlled by the l2gw<br>
>     plugin will make vxlan tunnels to all the compute nodes, to bridge the<br>
>     tenant network with a physical l2 network ? Or all this traffic has to<br>
>     pass to the network node also because the vtep openvswitch is not able<br>
>     to talk to the compute nodes ?<br>
><br>
>     thank you<br>
><br>
>     Saverio<br>
><br>
><br>
>     --<br>
>     SWITCH<br>
>     Saverio Proto, Peta Solutions<br>
>     Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland<br>
>     phone +41 44 268 15 15, direct +41 44 268 1573<br>
</div></div>>     <a href="mailto:saverio.proto@switch.ch">saverio.proto@switch.ch</a> <mailto:<a href="mailto:saverio.proto@switch.ch">saverio.proto@switch.<wbr>ch</a>>,<br>
<span class="gmail-im gmail-HOEnZb">>     <a href="http://www.switch.ch" rel="noreferrer" target="_blank">http://www.switch.ch</a><br>
><br>
>     <a href="http://www.switch.ch/stories" rel="noreferrer" target="_blank">http://www.switch.ch/stories</a><br>
><br>
>     ______________________________<wbr>______________________________<wbr>______________<br>
>     OpenStack Development Mailing List (not for usage questions)<br>
>     Unsubscribe:<br>
>     <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
</span><span class="gmail-im gmail-HOEnZb">>     <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:<wbr>unsubscribe</a>><br>
>     <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
>     <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a>><br>
><br>
><br>
><br>
><br>
</span><div class="gmail-HOEnZb"><div class="gmail-h5">> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
<br>
--<br>
SWITCH<br>
Saverio Proto, Peta Solutions<br>
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland<br>
phone <a href="tel:%2B41%2044%20268%2015%2015" value="+41442681515">+41 44 268 15 15</a>, direct <a href="tel:%2B41%2044%20268%201573" value="+41442681573">+41 44 268 1573</a><br>
<a href="mailto:saverio.proto@switch.ch">saverio.proto@switch.ch</a>, <a href="http://www.switch.ch" rel="noreferrer" target="_blank">http://www.switch.ch</a><br>
<br>
<a href="http://www.switch.ch/stories" rel="noreferrer" target="_blank">http://www.switch.ch/stories</a><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>