diff options
| author | Ihar Hrachyshka <ihrachys@redhat.com> | 2022-04-20 18:57:03 +0000 |
|---|---|---|
| committer | Ihar Hrachyshka <ihrachys@redhat.com> | 2022-06-08 18:12:28 +0000 |
| commit | ffd64df9d306bf56091b2f3ae8a8f579f578de53 (patch) | |
| tree | 0db685903355244c6cb302d7d7bf2ffd21f87bc0 /releasenotes | |
| parent | ae66417cee7af1eb2692353282f5c9b1c9c57947 (diff) | |
| download | neutron-ffd64df9d306bf56091b2f3ae8a8f579f578de53.tar.gz | |
ovn: revert to stateful dnat_and_snat
This is an effective revert of:
I312a950131d62d93fb4bc121bc5e60febb8d35ee
"ovn: use stateless NAT rules for FIPs".
The performance benefits promised by the "reverted" patch never
materialized. On the contrary, the discussion in [1] revealed that the
switch to stateless=true made it impossible to fully hw offload nat
rules, while it's possible with stateless=false. Specifically, see this
comment [2].
Since at this point it's unclear if keeping stateless=true as an option
is beneficial for any case, even when w/o hw offload, and to avoid
complexity of introducing a config option for unclear benefit, this
patch reverts the effects of the original patch, switching all
dnat_and_snat objects to implicit stateless=false state.
This patch cannot be a clean revert because of the need for db
migration.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2004995
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2004995#c18
Change-Id: I9e6e05b7a4f36383a44bd80f07d25052b17bdfa0
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/revert-ovn-stateless-nat-88076892fd6f7354.yaml | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/releasenotes/notes/revert-ovn-stateless-nat-88076892fd6f7354.yaml b/releasenotes/notes/revert-ovn-stateless-nat-88076892fd6f7354.yaml new file mode 100644 index 0000000000..4f59d70b19 --- /dev/null +++ b/releasenotes/notes/revert-ovn-stateless-nat-88076892fd6f7354.yaml @@ -0,0 +1,8 @@ +--- +other: + - | + OVN driver reverted to using stateful NAT for floating IP implementation. + The previous switch to stateless didn't materialize the expected + performance benefits and instead introduced problems with potential + hardware offloading. + |