On 4/4/24 18:06, Vladislav Odintsov wrote: > Commit [1] introduced a "vxlan mode" concept. It brought a limitation > for available tunnel IDs because of lack of space in VXLAN VNI. > In vxlan mode OVN is limited by 4095 datapaths (LRs or non-transit LSs) > and 2047 logical switch ports per datapath. > > Prior to this patch vxlan mode was enabled automatically if at least one > chassis had encap of vxlan type. In scenarios where one want to use VXLAN > only for HW VTEP (RAMP) switch, such limitation makes no sence. > > This patch adds support for explicit disabling of vxlan mode via > Northbound database. > > 1: https://github.com/ovn-org/ovn/commit/b07f1bc3d068 > > CC: Ihar Hrachyshka <ihrac...@redhat.com> > Fixes: b07f1bc3d068 ("Add VXLAN support for non-VTEP datapath bindings") > Signed-off-by: Vladislav Odintsov <odiv...@gmail.com> > ---
> diff --git a/ovs b/ovs > index fe55ce37a..94191b7a4 160000 > --- a/ovs > +++ b/ovs > @@ -1 +1 @@ > -Subproject commit fe55ce37a7b090d09dee5c01ae0797320ad678f6 > +Subproject commit 94191b7a4926204510931770c52992c9ea24d4e2 Looks like you included a submodule change by accident. This causes the CI to fail: https://github.com/ovsrobot/ovn/actions/runs/8557944614 Regards, Dumitru _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
