When it comes to the NDR charm we enabled it in the charms (neutron-api- plugin-ovn specifically needed a code change) documenting those limitations in the charm-guide.
https://review.opendev.org/q/topic:2023-enable-ndr https://review.opendev.org/q/topic:2023-ovn-ndr Also we are adding some data plane testing to make sure that the advertised routes are actually possible to reach. https://review.opendev.org/c/openstack/charm-neutron-dynamic- routing/+/886157 ** Also affects: charm-neutron-api-plugin-ovn Importance: Undecided Status: New ** Changed in: charm-neutron-api-plugin-ovn Status: New => Fix Committed ** Changed in: charm-neutron-dynamic-routing Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1959666 Title: Neutron-dynamic-routing does not work with OVN Status in OpenStack Neutron API OVN Plugin Charm: Fix Committed Status in OpenStack Neutron Dynamic Routing charm: In Progress Status in Ubuntu Cloud Archive: New Status in neutron: Fix Released Bug description: When using OVN as Neutron backend, announcing prefixes with neutron- dynamic-routing is currently not working due to changes in the database structure. Some attempt to fix this has been made in https://review.opendev.org/c/openstack/neutron-dynamic- routing/+/814055 but wasn't successful. This is a major stop gap for production deployments which are using BGP to provide connectivity for IPv6 subnets in tenant networks. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-api-plugin-ovn/+bug/1959666/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp