Comment 3 for bug 2017888
Revision history for this message
| Maximilian Sesterhenn (msnatepg) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Yes, we created a newer patch as we had to do some modifications to be able to load it.
The OVN BGPVPN service driver adds some config options which are already defined in neutron itself and it seems that Oslo doesn't like that.
Not sure if that was the reason for the Zuul jobs to fail.
Regarding 2017890, yes, BGPVPN allows the user to choose between L2 and L3, in the abandoned patch L2 is blocked and L3 is only allowed on non-provider networks if I remember correctly.
Using our patch you can:
- Associate routers, to allow for exposing non-provider networks connected to the router using L3 routes. (this was already there)
- Associate networks, to allow for exposing provider networks either in L2 or L3.
In all cases, the VNI information gets added to the external_ids field in NB DB, to differentiate between L2 and L3 we added another field into external_ids that carries this information.