Comment 4 for bug 2017889

Yes, for 2), it is a new addition, not a replacement of the EVPN/VRF driver. This is more to address https://bugs.launchpad.net/ovn-bgp-agent/+bug/2017890. Regarding the provider network limitations, not really, if we add this support to the BGP driver, we could expose tenant IPs (through the cr-lrp), but on the same vni as the provider they are associated to. This is the actual use case/testing on 2017890

For 3), yes, it is for EVPN type 5 (VRF + l3vni). Idea is to have exactly what we have in the EVPN driver, but instead of creating a VNI/VRF per cr-lrp, we would create one per provider network, and then expose both IPs on the provider and (optionally) IPs on the tenant networks associated to that provider on the same VRF/VNI

As for the NB driver, note right now only cares about IPs on the provider network since we require an extra feature in core OVN so that the chassis associated to the cr-lrp can be checked from NB. At the moment that information is only available in the SB. Once that is done we'll add also support for tenant networks (as in the BGP driver that uses the SB)