This series adds support to run multiple ovn-controller instances using the same vswitchd instance. This may be used to reuse a single host level vswitchd installation to run multiple CMS (e.g. k8s and openstack), each having its own OVN stack running on a separate integration bridge.
This setup may, in some instances, simplify administration of the system, since the admin no longer needs to maintain separate vswitchd installations (e.g. in separate containers). This is also helpful when running different datapath types for the mixed setup. Ihar Hrachyshka (6): Rename tunnel ports to include source chassis name Support ovn-...-<chassis> specific global ovsdb options Allow to override system-id via file Support passing chassis name via CLI Don't touch tunnel ports from a different br-int Add connectivity test for 2 controllers on the same host controller/chassis.c | 162 ++++++++----- controller/chassis.h | 9 +- controller/encaps.c | 58 ++--- controller/encaps.h | 1 - controller/ovn-controller.c | 167 ++++++++----- controller/patch.c | 5 +- controller/physical.c | 2 +- lib/ovn-util.c | 87 +++++++ lib/ovn-util.h | 26 ++ tests/automake.mk | 1 + tests/ovn-controller.at | 22 +- tests/ovn-ipsec.at | 16 +- tests/ovn-macros.at | 6 +- tests/ovn-performance.at | 4 +- tests/ovn.at | 463 ++++++++++++++++++++++++++++++------ tests/ovs-macros.at | 2 + 16 files changed, 790 insertions(+), 241 deletions(-) -- 2.34.1 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
