[Starlingx-discuss] Need input on patch 4ae5a58 & 88b7bc7 upstreaming

[Peters, Matt]

Hi Chenjie,
Thanks for sending this email.  See my responses inline.
I have also added the starlingx-discuss mailing list to this reply so that the community can add additional comments or considerations.

The reply to the RFE’s can be something like the following:

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.

From: "Xu, Chenjie" <chenjie.xu at intel.com>
Date: Thursday, January 10, 2019 at 11:54 AM
To: "Peters, Matt" <Matt.Peters at windriver.com>
Cc: Ghada Khalil <Ghada.Khalil at windriver.com>, "Zhao, Forrest" <forrest.zhao at intel.com>
Subject: Need input on patch 4ae5a58 & 88b7bc7 upstreaming

Hi Matt,
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):
https://bugs.launchpad.net/neutron/+bug/1803494
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.

Another RFE (4ae5a58) https://bugs.launchpad.net/neutron/+bug/1793653 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). 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? 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.
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.

The RFE (88b7bc7) https://bugs.launchpad.net/neutron/+bug/1806316 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. Could you please provide another use case in Neutron to help the community accept this RFE?
MP> At the moment we do not have an alternate use-case for this change.   It should be abandoned also with the same justification.

Best Regards,
Xu, Chenjie

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190110/8a4085dc/attachment-0001.html>