<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri",sans-serif;
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
text-indent:21.0pt;
font-size:10.5pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="ZH-CN" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Hi Ryan,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Thank you for your reply! For your questions:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">1. What’s the context for this RFE:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">StarlingX extends Neutron, networking-bgpvpn and neutron-dynamic-routing as stx-neutron, stx-networking-bgpvpn and stx-neutron-dynamic-routing. These extensions enable Neutron network to learn external
MAC/IP information from BGPVPN network and publish the external</span><span lang="EN-US">
</span><span lang="EN-US" style="color:#1F497D">MAC/IP information internally via the L2POP mechanism. Similarly, internal MAC/IP information in Neutron network is published to remote systems via a subscription to L2POP RPC notifications and finally will be
received by the BGP agent.<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></a></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">2. It looks like this RFE is one of several in the neutron space that would be required to achieve this functionality, is that correct?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Yes, it is. To achieve what I describe in question one, 3 RFE has been posted to Neutron.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:26.25pt;mso-para-margin-left:1.0gd;text-indent:-15.75pt">
<span lang="EN-US" style="color:#1F497D">1). RFE “Enable other subprojects to extend l2pop fdb information” (</span><a href="https://bugs.launchpad.net/neutron/+bug/1793653"><span lang="EN-US">https://bugs.launchpad.net/neutron/+bug/1793653</span></a><span lang="EN-US" style="color:#1F497D">)
should be used by networking-bgpvpn to publish the (MAC, IP) information in BGPVPN network to Neutron network.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:26.25pt;mso-para-margin-left:1.0gd;text-indent:-15.75pt">
<span lang="EN-US" style="color:#1F497D">2). RFE “Add l2pop support for floating IP resources” (</span><a href="https://bugs.launchpad.net/neutron/+bug/1803494"><span lang="EN-US">https://bugs.launchpad.net/neutron/+bug/1803494</span></a><span lang="EN-US" style="color:#1F497D">)
extends l2pop FDB information to avoid the broadcast in the scenario that two VMs, residing on different network, communicate by their respective floating IP.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:10.5pt"><span lang="EN-US" style="color:#1F497D">3). This RFE proposes to add an RPC query API to l2pop. This RFE is used by BGP Dynamic Routing agent to pull the l2pop FDB information.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">For the changes in stx-networking-bgpvpn and stx-neutron-dynamic-routing, the plan is to upstream them to networking-bgpvpn and neutron-dynamic-routing. However, in the short term this is not being
prioritized nor has any attempt been made to approach the individual project teams about getting this accepted.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I'm not sure if this is the same idea that using BGPVPN to provide an alternative to the current l2pop implementation or not. Looking forward to your reply!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Xu, Chenjie<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="text-align:left"><a name="_____replyseparator"></a><b><span lang="EN-US" style="font-size:11.0pt;color:windowtext">From:</span></b><span lang="EN-US" style="font-size:11.0pt;color:windowtext"> Ryan Tidwell [mailto:rtidwell@suse.com]
<br>
<b>Sent:</b> Thursday, December 20, 2018 6:08 AM<br>
<b>To:</b> Xu, Chenjie <chenjie.xu@intel.com><br>
<b>Cc:</b> starlingx-discuss@lists.starlingx.io<br>
<b>Subject:</b> Re: [Starlingx-discuss] RFE Review Request for patch 88b7bc7 for StartlingX upstreaming<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US">Chenjie,</span><span lang="EN-US" style="font-size:12.0pt"><o:p></o:p></span></p>
<p><span lang="EN-US">Thanks for reaching out. I've taken a glance over the RFE, it's very detailed but lacks some context. Just to be sure I understand this correctly, is the idea here to use BGP EVPN as a method for providing l2pop functionality? If so, I've
actually been thinking about this for some time now and I think it would be great to provide an alternative to the current l2pop implementation. I could certainly see supporting this functionality in some fashion in neutron-dynamic-routing. It looks like this
RFE is one of several in the neutron space that would be required to achieve this functionaliy, is that correct? If I'm not understanding the use case correctly, could you explain what you have in mind? In the mean time I'll look this over again and leave
some comments.<o:p></o:p></span></p>
<p><span lang="EN-US">-Ryan<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On 12/19/18 2:17 AM, Xu, Chenjie wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Hi Ryan,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Could you please help review the RFE for Neutron (<a href="https://bugs.launchpad.net/neutron/+bug/1806316">https://bugs.launchpad.net/neutron/+bug/1806316</a>) and leave a comment?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This RFE proposes to add an RPC query API to l2pop. The API is used to allow an agent to query the full FDB for a list of network_id values. This is needed by the agents which want to support l2pop but don't have ports
bound to themselves (<b>Potential for BGP Dynamic Routing agent</b>). The project stx-neutron-dynamic-routing is a fork project for neutron-dynamic-routing. The project stx-neutron-dynamic-routing implements the l2pop for BGP Dynamic Routing agent:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1053">https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1053</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1180">https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1180</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The plan is to upstream these changes to neutron-dynamic-routing. However, in the short term this is not being prioritized nor has any attempt been made to approach the individual project teams about getting this accepted.
<b>Could you leave a comment on the potential use?</b><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Xu, Chenjie<o:p></o:p></span></p>
</blockquote>
</div>
</body>
</html>