In order to have transit router we have to allow peer port connection between LR patch port l3gateway types. This allows direct connection of two LRs, one of the being transit router and the second one being GW router. This is taken care of commit 3/6. To be fair this can change can be useful in general even without transit router.
The 2/4 and 4/4 is the actual work needed for transit router. First is the way to define remote ports for logical router which on it's own is the main component that results in the transit router. The LRP can be set remote by setting options:requested-chassis to chassis that has is-remote=true. Only one chassis is supported at time. The 6/6 is needed in cases when one AZ ARPs port in other AZ, without this the ARP wouldn't be delivered to the original AZ, which would result in dropped traffic. Ales Musil (4): physical: Allow l3gateway and patch port to be peers. northd: Introduce the concept of transit routers. actions, physical: Make the MC split action generic. northd, controller: Flood ARP and NA packet on transit router. NEWS | 3 + controller/lflow.c | 1 + controller/lflow.h | 4 + controller/physical.c | 283 ++++++++++++++++++++++++++++++++------ controller/pinctrl.c | 21 +-- include/ovn/actions.h | 7 +- lib/actions.c | 19 ++- lib/ovn-util.c | 2 +- northd/northd.c | 52 +++++-- northd/northd.h | 4 + ovn-nb.xml | 43 ++++++ tests/multinode-macros.at | 48 +++++++ tests/multinode.at | 201 +++++++++++++++++++++++++++ tests/ovn-controller.at | 157 +++++++++++++++++++++ tests/ovn-macros.at | 1 + tests/ovn-northd.at | 51 +++++++ tests/ovn.at | 10 +- tests/test-ovn.c | 1 + tutorial/ovn-sandbox | 24 ++-- utilities/ovn-trace.c | 3 + 20 files changed, 857 insertions(+), 78 deletions(-) -- 2.48.1 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
