With respect to the previous implementation, OVN is now tracking and flushing ECMP next-hop ct entries with the next-hop mac address instead of using an identification number committed by ovn-northd since the previous approach had some limitations when the traffic is initialized from outside the ovn cluster. This series is introducing a way to periodically resolve L2 address of the configured next-hops. Please note IPv6 is not currently supported and it will be added before posting a formal series. The goal of this series is just to collect feedbacks about the proposed approach.
Lorenzo Bianconi (4): northd: Introduce ECMP_Nexthop table in SB db. pinctrl: Send periodic arp-request to ecmp next-hops. pinctrl: update ecmp-nexthop mac resolving L2 address ofctrl: Introduce ecmp_nexthop_monitor. controller/ofctrl.c | 73 ++++++++ controller/ofctrl.h | 2 + controller/ovn-controller.8.xml | 11 ++ controller/ovn-controller.c | 8 + controller/pinctrl.c | 298 ++++++++++++++++++++++++++++---- controller/pinctrl.h | 3 + northd/en-northd.c | 31 ++++ northd/en-northd.h | 4 + northd/inc-proc-northd.c | 14 +- northd/northd.c | 70 +++++++- northd/northd.h | 5 + ovn-sb.ovsschema | 17 +- ovn-sb.xml | 34 ++++ tests/ovn-northd.at | 18 +- tests/system-ovn.at | 185 ++++++++++++++++++++ 15 files changed, 729 insertions(+), 44 deletions(-) -- 2.46.0 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
