Chenjie, 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. -Ryan On 12/19/18 2:17 AM, Xu, Chenjie wrote:

Hi Ryan,

Could you please help review the RFE for Neutron (https://bugs.launchpad.net/neutron/+bug/1806316) and leave a comment?

 

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 (*Potential for BGP Dynamic Routing agent*). 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:

https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master...

https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master...

 

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. *Could you leave a comment on the potential use?*

 

Best Regards,

Xu, Chenjie