2145901d6f
Using stateless NAT in OVN should always be a better choice for
floating IPs in some deployments because it allows to avoid hitting
conntrack, potentially improving NAT performance.
The only limitation for using stateless NAT in OVN is that it requires
1:1 IP mapping; which is always the case for FIPs.
This functionality was introduced in OVN in [1], provided in v20.03.0.
Neutron implies this version is used and does not check it.
This functionality is configurable via Neutron config file. The new
option introduced is ``[ovn]stateless_nat_enabled``, disabled by
default to keep the previous behaviour.
NOTE: this patch is also reducing the cover rate to 78%. cover job only
considers unit tests, not functional tests.
[1]cc87c4827f
Closes-Bug: #2111899
Signed-off-by: Rodolfo Alonso Hernandez <ralonsoh@redhat.com>
Change-Id: I3551babe7986f1aef59080aba35a2a1586e40af5
10 lines
420 B
YAML
10 lines
420 B
YAML
---
|
|
features:
|
|
- |
|
|
The ML2/OVN driver can now use stateless NAT for floating IP addresses.
|
|
This functionality is configurable using the new boolean config option
|
|
``[ovn]stateless_nat_enabled``. By default, this option is disabled,
|
|
keeping the current behaviour. This functionality improves the performance
|
|
in some deployments (DPDK based, for example) by avoiding hitting
|
|
conntrack OVN actions.
|