Update docs based on support added recently.

Change-Id: Icdde0389845e5f74a660ed33946cb5cd068803ed
This commit is contained in:
Brian Haley 2021-08-25 12:30:10 -04:00
parent b25bc57734
commit c5a8e25dd7
2 changed files with 3 additions and 13 deletions

View File

@ -28,14 +28,8 @@ Limitations of the OVN Provider Driver
OVN has its own set of limitations when considered as an Load Balancer driver.
These include:
* OVN currently supports TCP and UDP, so Layer-7 based load balancing is not
possible with OVN.
* While Health Checks are now available in OVN, they are not currently
implemented in OVN's Provider Driver for Octavia.
* There are currently no *Health Monitors* in OVN's Provider Driver for Octavia.
Therefore Health Checking is not possible with OVN.
* OVN currently supports TCP, UDP and SCTP, so Layer-7 based load balancing
is not possible with OVN.
* Currently, the OVN Provider Driver supports a 1:1 protocol mapping between
Listeners and associated Pools, i.e. a Listener which can handle TCP

View File

@ -43,8 +43,7 @@ Octavia with OVN
----------------
The OVN native LoadBalancer currently supports L4 protocols, with support for
L7 protocols aimed for future releases. Currently, it also does not have any
monitoring facility. However, it does not need any extra
L7 protocols aimed for future releases. It does not need any extra
hardware/VM/Container for deployment, which is a major positive point when
compared with Amphorae. Also, it does not need any special network to
handle the LoadBalancer's requests as they are taken care by OpenFlow rules
@ -284,9 +283,6 @@ The Following actions are not supported by the OVN Provider Driver:
- Creating a LoadBalancer/Listener/Pool with an L7 Protocol
- While Health Checks are now available in OVN, they are not currently
implemented in OVN's Provider Driver for Octavia.
- Currently only one algorithm is supported for pool management
(Source IP Port)