openstack/neutron
Code Issues Proposed changes

[Docs] Add info about incompatible PF configuration in ML2/OVN gaps

Browse Source 
This patch adds info about the fact that FIP PFs aren't working when
in the ML2/OVN backend distributed routing is enabled and provider
networks are added to the router as internal networks.

Conflicts:
    doc/source/ovn/gaps.rst

Related-Bug: #2028846
Change-Id: I3a0ab43c52a3090257a1accaee00f33abff54e74
(cherry picked from commit cce872ead3)
(cherry picked from commit 8748557738)
This commit is contained in:
Slawek Kaplonski
2024-02-01 11:50:43 +01:00
parent bd6595ddb8
commit 475a25259f
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/ovn/gaps.rst
View File

@@ -56,6 +56,17 @@ at [1]_.
The NDP proxy functionality for IPv6 addresses is not supported by OVN.
* Floating IP Port Forwarding in provider networks and with distributed routing
Currently, when provider network types like ``vlan`` or ``flat`` are plugged
to a router as internal networks while the ``enable_distributed_floating_ip``
configuration option is enabled, Floating IP port forwardings
which are using such router will not work properly.
Due to an incompatible setting of the router to make traffic in the vlan/flat
networks to be distributed but port forwardings are always centralized in
ML2/OVN backend.
This is being reported in [9]_.
References
----------
@@ -67,3 +78,4 @@ References
.. [6] https://bugs.launchpad.net/neutron/+bug/1926515
.. [7] https://review.opendev.org/c/openstack/neutron/+/788594
.. [8] https://docs.openstack.org/neutron/latest/admin/config-dns-res.html
.. [9] https://bugs.launchpad.net/neutron/+bug/2028846