<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
font-size:10.5pt;
font-family:"Calibri",sans-serif;}
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.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 lang="EN-CA" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Chenjie,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks for sending this email. See my responses inline.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I have also added the starlingx-discuss mailing list to this reply so that the community can add additional comments or considerations.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The reply to the RFE’s can be something like the following:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This RFE is specific to the Neutron BGP-EVPN use-case which is currently not being pursued for upstreaming from the corresponding starlingx-staging projects (stx-neutron-dynamic-routing and stx-networking-bgpvpn).
Therefore, until this feature is required, and an attempt is made to have it accepted by the OpenStack community, this feature cannot be used as a justification for this RFE. This RFE is being abandoned and can be revived if the BGP-EVPN feature becomes a
priority.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Xu, Chenjie" <chenjie.xu@intel.com><br>
<b>Date: </b>Thursday, January 10, 2019 at 11:54 AM<br>
<b>To: </b>"Peters, Matt" <Matt.Peters@windriver.com><br>
<b>Cc: </b>Ghada Khalil <Ghada.Khalil@windriver.com>, "Zhao, Forrest" <forrest.zhao@intel.com><br>
<b>Subject: </b>Need input on patch 4ae5a58 & 88b7bc7 upstreaming<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Hi Matt,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">There are 3 RFEs related to BGPVPN and one of them has been abandoned by today’s meeting. The abandoned RFE’s (9f926a5) link is below (we can call it RFE floatingIP):</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://bugs.launchpad.net/neutron/+bug/1803494">https://bugs.launchpad.net/neutron/+bug/1803494</a></span><o:p></o:p></p>
<p class="MsoNormal"><i><span lang="EN-US" style="color:red">MP> As discussed, we should abandon this RFE. We also need to ensure that we respond to the launchpad with the reasoning for the abandonment.<o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Another RFE (4ae5a58) <a href="https://bugs.launchpad.net/neutron/+bug/1793653">
https://bugs.launchpad.net/neutron/+bug/1793653</a> we can call it RFE l2pop. RFE l2pop has been discussed on Neutron Driver Meeting for several times, and they think RFE l2pop lacks approved use cases. There are two potential use cases: BGPVPN and RFE floatingIP.
The community of BGPVPN is not active and RFE l2pop has been pending on Thomas Morin’s input for a long time (Thomas leads the networking-bgpvpn project).
<b>Because RFE floatingIP has been abandoned and BGPVPN got no input, could you please provide another use case in Neutron to help the community accept this RFE?</b>
<b>What’s more, another concern of community is that it’s hard to test the feature related to BGPVPN and I don’t have a BGPVPN environment to test this RFE either.<o:p></o:p></b></span></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt;color:red">MP> I agree that this is related and is only valid within the BGP-EVPN use-case. It should be abandoned also with the same justification.<o:p></o:p></span></i></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">The RFE (88b7bc7) <a href="https://bugs.launchpad.net/neutron/+bug/1806316">
https://bugs.launchpad.net/neutron/+bug/1806316</a> we can call it RFE BgpDrAgent. Though RFE BgpDrAgent has not been triaged by Neutron team, I think it will face the same problem as RFE l2pop. Neutron team may think this RFE lacks approved use case. This
RFE only has one use case which is neutron-dynamic-routing. I asked Ryan Tidwell who leads the neutron-dynamic-routing project to review this RFE and for now pending on his input.
<b>Could you please provide another use case in Neutron to help the community accept this RFE?
</b></span><o:p></o:p></p>
<p class="MsoNormal"><i><span lang="EN-US" style="color:red">MP> At the moment we do not have an alternate use-case for this change.
</span></i><i><span lang="EN-US"> </span></i><i><span style="font-size:11.0pt;color:red">It should be abandoned also with the same justification.</span></i><i><span lang="EN-US" style="color:red"><o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Xu, Chenjie</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
</div>
</body>
</html>