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.
v1: initial series
v2: change tunnel port naming scheme: include "chassis index" instead of
its name for source chassis.
v2: formatting adjustments.
Ihar Hrachyshka (6):
Include "chassis index" into tunnel port 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 | 164 +++++++++++++------
controller/chassis.h | 9 +-
controller/encaps.c | 83 ++++++----
controller/encaps.h | 3 +-
controller/ovn-controller.c | 225 ++++++++++++++++++-------
controller/patch.c | 6 +-
controller/physical.c | 2 +-
lib/ovn-util.c | 87 ++++++++++
lib/ovn-util.h | 26 +++
tests/automake.mk | 1 +
tests/ovn-macros.at | 6 +-
tests/ovn.at | 318 ++++++++++++++++++++++++++++++++++++
tests/ovs-macros.at | 2 +
13 files changed, 780 insertions(+), 152 deletions(-)
--
2.34.1
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
