[ovs-dev] [PATCH ovn 0/4] Handle DNAT/no-NAT conntrack tuple collisions if possible.
Mark Gray
mark.d.gray at redhat.com
Fri Jun 4 14:50:41 UTC 2021
On 03/06/2021 16:05, Dumitru Ceara wrote:
> This depends on the following OVS patch to be accepted:
>
> https://patchwork.ozlabs.org/project/openvswitch/patch/162264080113.315078.1220132318734842720.stgit@ebuild/
Just to be clear, will this break OVN without the above patch? Can this
be applied without it? I presume so as the capability would not be detected.
>
> However, the capability name, "ct_zero_snat" has been agreed upon so it
> is very unlikely that it will change if new revisions of the OVS patch
> are required.
>
> Dumitru Ceara (4):
> ovs: Include ovs-vswitchd segfault fixes.
> system-ovn.at: Use ADD_BR macro instead of bare ovs-vsctl.
> ovn-controller: Detect OVS datapath capabilities.
> ovn-controller: Handle DNAT/no-NAT conntrack tuple collisions.
>
>
> controller/lflow.c | 1
> controller/ovn-controller.c | 125 ++++++++++++++++++++++++++++--------
> include/ovn/actions.h | 4 +
> include/ovn/features.h | 16 +++++
> lib/actions.c | 34 +++++++++-
> lib/automake.mk | 1
> lib/features.c | 39 +++++++++++
> ovs | 2 -
> tests/ovn-controller.at | 11 +--
> tests/ovn.at | 2 -
> tests/system-common-macros.at | 4 +
> tests/system-ovn.at | 141 ++++++++++++++++++++++++++++++++++++++++-
> 12 files changed, 341 insertions(+), 39 deletions(-)
> create mode 100644 lib/features.c
>
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
More information about the dev
mailing list