diff --git a/doc/source/contributor/drivers/ovn_bgp_mode_design.rst b/doc/source/contributor/drivers/ovn_bgp_mode_design.rst index dcf8a73e..60c2f83e 100644 --- a/doc/source/contributor/drivers/ovn_bgp_mode_design.rst +++ b/doc/source/contributor/drivers/ovn_bgp_mode_design.rst @@ -69,12 +69,15 @@ The OVN routing architecture proposes the following mapping: (``br-osp``). - ``br-osp`` does not have any physical resources attached, just patch - ports connecting them to ``br-int`` and ``br-bgp``. + ports connecting them to ``br-int`` and ``br-bgp``. The name of this bridge can + be arbitrary so long as ovn-bridge-mappings for both OVN clusters (the primary and + the extra node-local one) are set accordingly. - ``br-bgp`` is the integration bridge managed by the extra OVN cluster deployed per node. This is where the virtual OVN resources are be created - (routers and switches). It creates mappings to ``br-osp`` and ``br-ex`` - (patch ports). + (routers and switches). OVN creates patch ports between ``br-osp`` and ``br-ex`` + based on ovn-bridge-mappings set for the extra OVN cluster. The name of this bridge + is configurable and can be changed by setting a relevant instance-specific OVSDB option. - ``br-ex`` keeps being the external bridge, where the physical NICs are attached (as in default environments without BGP). But instead of being @@ -236,6 +239,71 @@ range for the provider networks to expose/handle: external_nics=eth1,eth2 peer_ips=100.64.1.5,100.65.1.5 provider_networks_pool_prefixes=172.16.0.0/16 + # This will be used as a suffix for options relevant to the node-local OVN. + bgp_chassis_id = bgp + + +Multiple OVN Controllers +++++++++++++++++++++++++ + +This mode relies on running two ovn-controllers on the same host. However, a single +OVSDB is shared for both controllers. To achieve that, OVN supports having option +suffixes for options stored in OVSDB that look like this: ``