openstack
/
ovn-octavia-provider
Code Issues Proposed changes

Update documentation about ovn-octavia limitations 

Clarify that some specific amphora functionality is not needed at
ovn-octavia (not a real limitation, it just does not apply when you
don't have a VM doing the loadbalancing).

Also drop the limitation about the load balancers stuck in pending_X
as this should be no longer the case, and if that so it is a bug that
needs fixing, not a limitation.

Change-Id: Ic5b39d7a23f0d8d0bf2bae5e3ab5e67920ff348a
This commit is contained in:
Luis Tomas Bolivar 2022-09-14 08:14:16 +02:00
parent d490778979
commit 0c248ddb5e
2 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/admin/driver.rst
View File

@ -44,7 +44,13 @@ These include:
* Only the SOURCE_IP_PORT load balancing algorithm is supported, others
like ROUND_ROBIN and LEAST_CONNECTIONS are not currently supported.
* Octavia flavors are not supported.
* Due to nature of OVN octavia driver (flows distributed in all the nodes)
there is no need for some of the amphora specific functionality that is
specific to the fact that a VM is created for the load balancing actions. As
an example, there is no need for flavors (no VM is created), failovers (no
need to recover a VM), or HA (no need to create extra VMs as in the
ovn-octavia case the flows are injected in all the nodes, i.e., it is HA by
default).
Creating an OVN based Load Balancer
-----------------------------------

11
doc/source/contributor/loadbalancer.rst
View File

@ -286,10 +286,13 @@ The Following actions are not supported by the OVN Provider Driver:
- Currently only one algorithm is supported for pool management
(Source IP Port)
The following issue exists with OVN's integration with Octavia:
- If creation/deletion of a LoadBalancer, Listener, Pool or Member fails, then
the corresponding object will remain in the DB in a PENDING_* state.
- Due to nature of OVN octavia driver (flows distributed in all the nodes)
there is no need for some of the amphora specific functionality that is
specific to the fact that a VM is created for the load balancing actions. As
an example, there is no need for flavors (no VM is created), failovers (no
need to recover a VM), or HA (no need to create extra VMs as in the
ovn-octavia case the flows are injected in all the nodes, i.e., it is HA by
default).
Support Matrix
--------------