On Tue, Jul 21, 2026 at 10:49 PM Han Zhou <[email protected]> wrote: > > This series lets OVN honor a per-route L3 VNI for learned EVPN (type-5) > routes, instead of always encapsulating with the destination logical > switch's dynamic-routing-vni. > > This depends on the OVS route-table library change that parses the LWT > tunnel id (VNI) from kernel routes, which is still under review, so marked as > RFC. > > Han Zhou (2): > features: Detect OVS 32-register support. > dynamic-routing: Support per-route VNI for learned EVPN routes. > > .../topics/dynamic-routing/architecture.rst | 19 +++ > controller/chassis.c | 12 ++ > controller/physical.c | 137 +++++++++++++----- > controller/route-exchange-netlink.c | 2 + > controller/route-exchange-netlink.h | 5 + > controller/route-exchange.c | 40 ++++- > include/ovn/features.h | 6 + > lib/features.c | 75 ++++++++++ > lib/logical-fields.c | 8 + > northd/en-global-config.c | 13 ++ > northd/en-global-config.h | 1 + > northd/en-learned-route-sync.c | 15 +- > northd/en-lflow.c | 3 +- > northd/northd.c | 73 ++++++++-- > northd/northd.h | 9 +- > ovn-sb.xml | 10 ++ > tests/ovn-northd.at | 46 ++++++ > tests/system-ovn.at | 18 +++ > 18 files changed, 434 insertions(+), 58 deletions(-) > > -- > 2.38.1
The approach used in this series depends on OVS 32 registers which is only available after OVS 3.7, so environment with older OVS version would still be broken. I submitted a patch with an alternative approach so that it can work for old OVS versions as well: https://patchwork.ozlabs.org/project/ovn/patch/[email protected]/ Thanks, Han _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
