<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 30 March 2016 at 17:07, Abhishek Raut <span dir="ltr"><<a href="mailto:rauta@vmware.com" target="_blank">rauta@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>I think what Gary is talking about is BGP and the Border Gateway API spec[1] in L2 GW repo.</div>
<div>[1] <a href="https://review.openstack.org/#/c/270786/" target="_blank">https://review.openstack.org/#/c/270786/</a></div>
<div><span style="font-family:arial,sans-serif;font-size:small;color:rgb(34,34,34)"></span></div></div></blockquote><div><br></div><div>Spec [1] has nothing to do with BGP (the routing protocol) last time I checked (note to self: I should go and have another look). We should probably consider clarify the confusion that stems from the use of the word 'Border' in spec [1].</div><div><br></div><div>A.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><div><span style="font-family:arial,sans-serif;font-size:small;color:rgb(34,34,34)"> </span><br></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><div>
</div>
<div>—Abhishek Raut</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>"Tidwell, Ryan" <<a href="mailto:ryan.tidwell@hpe.com" target="_blank">ryan.tidwell@hpe.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, March 30, 2016 at 4:52 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><span class=""><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Neutron] BGP support<br>
</span></div><div><div class="h5">
<div><br>
</div>
<div>
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Gary,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I’m not sure I understand the relationship you’re drawing between BGP and L2 GW, could you elaborate? The BGP code that landed in Mitaka is mostly geared toward
the use case where you want to directly route your tenant networks without any NAT (ie no floating IP’s, no SNAT). Neutron peers with upstream routers and announces prefixes that tenants allocate dynamically. We have talked about how we could build on what
was merged in Mitaka to support L3 VPN in the future, but to my knowledge no concrete plan has emerged as of yet.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-Ryan<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Gary Kotton [<a href="mailto:gkotton@vmware.com" target="_blank">mailto:gkotton@vmware.com</a>]
<br>
<b>Sent:</b> Sunday, March 27, 2016 11:36 PM<br>
<b>To:</b> OpenStack List<br>
<b>Subject:</b> [openstack-dev] [Neutron] BGP support<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Hi,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">In the M cycle BGP support was added in tree. I have seen specs in the L2 GW project for this support too. Are we planning to consolidate the efforts? Will the
BGP code be moved from the Neutron git to the L2-GW project? Will a new project be created?<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Sorry, a little in the dark here and it would be nice if someone could please provide some clarity here. It would be a pity that there were competing efforts and
my take would be that the Neutron code would be the single source of truth (until we decide otherwise).<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">I think that the L2-GW project would be a very good place for that service code to reside. It can also have MPLS etc. support. So it may be a natural fit.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Thanks<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Gary<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></span>
</div>
<br>__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>