On Tue, Aug 18, 2026 at 2:38 PM Dumitru Ceara <[email protected]> wrote:
> The co-hosted ovn-controller support has been present in OVN since OVN
> 23.03.0. At that point the feature was considered experimental as there
> was no way of preventing co-hosted controllers from "fighting" over
> conntrack zones for stateful features (NAT, LB, stateful ACLs).
>
> Since then commit f2363f49f6a4 ("controller: Add the capability to specify
> a min/max value for ct_zone.") added a way to use different conntrack
> zone ranges for co-hosted controllers (since OVN 24.09.0).
>
> And b543a882f8d2 ("test: Test co-hosted ovn-controllers with different CT
> range.") adds a test that validates this behavior in our CI (since OVN
> 26.03.0).
>
> Signed-off-by: Dumitru Ceara <[email protected]>
> ---
> NEWS | 2 ++
> controller/ovn-controller.8.xml | 8 +++++---
> 2 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/NEWS b/NEWS
> index fcee8b8c2b..3f16ccdfb4 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -97,6 +97,8 @@ Post v26.03.0
> - Added a new "ovn-debug lflow-pipeline-oftable-start-list" command
> that
> prints the starting OpenFlow table number of the logical ingress and
> egress pipelines.
> + - The support for co-hosting multiple controller instances is now
> + considered stable. Its "experimental" tag has been removed.
>
> OVN v26.03.0 - xxx xx xxxx
> --------------------------
> diff --git a/controller/ovn-controller.8.xml
> b/controller/ovn-controller.8.xml
> index e355046901..8121f70454 100644
> --- a/controller/ovn-controller.8.xml
> +++ b/controller/ovn-controller.8.xml
> @@ -468,9 +468,11 @@
> names on the same host using the same <code>vswitchd</code>
> instance.
> This may be useful when running a hybrid setup with more than one
> CMS
> managing ports on the host, or to use different datapath types on
> the
> - same host. Also note that this ability is highly experimental and
> - has known limitations (for example, stateful ACLs are not
> supported).
> - Use at your own risk.
> + same host. In order to support stateful features (ACLs, LBs,
> NAT) in
> + multiple OVN deployments co-hosted on the same chassis, CMS also
> need
> + to separate conntrack zone ranges between the co-hosted
> ovn-controllers
> + through the <code>external_ids:ct-zone-range</code> configuration
> + described in upcoming sections.
> </p>
>
> <p>
> --
> 2.55.0
>
>
Looks good to me, thanks.
Acked-by: Ales Musil <[email protected]>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
