Hi Justin, I know it's a while ago since this patch [0][1] made it in OVN but I was wondering if you remembered some of the reasons behind doing this.
More recently, OVN got a new feature to allow the CMS to explicitly specify a zone ID to be used for conntrack for gateway routers [2]. The reason behind that was that, in some cases, ovn-kubernetes shares the gateway router conntrack zone with the host [3]. The fact that an ovn-controller restart flushes the shared zone becomes an issue sometimes. We're trying to see if there's a way to avoid that, potentially via an ovn-controller cmdline argument or configuration. But before that, I wonder if you know of any CMS that relies on the flush-on-use behavior. Thanks, Dumitru [0] https://github.com/ovn-org/ovn/commit/11b75557aebd7caa433658895ff5c5e0381c34a0 [1] https://mail.openvswitch.org/pipermail/ovs-dev/2016-September/323402.html [2] https://github.com/ovn-org/ovn/commit/f9cab11d5fabe2ae321a3b4bad5972b61df958c0 [3] https://github.com/ovn-org/ovn-kubernetes/commit/f2cc64dcfb9d3205eda5fd0cb0de340a7abcb565 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
