78b5fe2ff4
The OVN changed support for NAT rules including a new column and auto discovery logic (which may not work in some cases) [1][2]. If the OVN backend supports this column in the Northbound DB Schema, set gateway port uuid to any floating IP to prevent North/South traffic issues for floating IPs. This patch updates the method for creating FIP NAT rules in OVN backend and updates previously created FIP rules to include the gateway_port reference. This NAT rule update task runs only once during the maintenance task, and if all entries are already configured no action is performed. [1]15348b7b80[2]2d942be7dbCloses-Bug: 2035281 Change-Id: I802b6bd8c281cb6dacdee2e9c15285f069d4e04c
16 lines
758 B
YAML
16 lines
758 B
YAML
---
|
|
prelude: >
|
|
The OVN changed support for NAT rules including a new column and
|
|
auto-discovery logic to know about logical router gateway ports for NAT on
|
|
a Logical Router.
|
|
features:
|
|
- |
|
|
A new OVN driver Northbound DB column has been added to allow configuring
|
|
gateway port for NAT rule. If the OVN backend supports the `gateway_port`
|
|
column in the Northbound DB NAT table, the gateway port uuid will be
|
|
configured to any floating IP to prevent North/South traffic issues.
|
|
Previously created FIP rules will be updated only once during the
|
|
maintenance task to include the gateway_port reference (if OVN backend
|
|
supports it). In case all FIP entries are already configured no maintenance
|
|
action will be performed.
|