openstack
/
octavia
Code Issues Proposed changes

Merge "Run codespell on doc directory"

This commit is contained in:
Zuul 2023-11-01 19:45:32 +00:00 committed by Gerrit Code Review
parent 5f8eb7a4a9 deeb4acca5
commit 51ae11032e
7 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/contributor/contributing.rst
View File

@ -104,7 +104,7 @@ RFE
understands the goal of the change.
specs
If the new feature is a major change or additon to Octavia that will need
If the new feature is a major change or addition to Octavia that will need
a detailed design to be successful, the Octavia team requires a
specification (spec) proposal be submitted as a patch.

2
doc/source/contributor/guides/providers.rst
View File

@ -508,7 +508,7 @@ are:
| | | backend ``member`` that contains 0 if the |
| | | client authentication was successful, or an|
| | | result error number greater than 0 that |
| | | align to the openssl veryify error codes. |
| | | align to the openssl verify error codes. |
+-----------------------+--------+--------------------------------------------+
| X-SSL-Client-Has-Cert | string | When "``true``" a ``X-SSL-Client-Has-Cert``|
| | | header is inserted into the request to the |

2
doc/source/user/feature-classification/feature-matrix-listener.ini
View File

@ -121,7 +121,7 @@ driver.ovn=missing
[operation.insert_headers.X-SSL-Client-Verify]
title=insert_headers - X-SSL-Client-Verify
status=optional
notes=When “true” a X-SSL-Client-Verify header is inserted into the request to the backend member that contains 0 if the client authentication was successful, or an result error number greater than 0 that align to the openssl veryify error codes.
notes=When “true” a X-SSL-Client-Verify header is inserted into the request to the backend member that contains 0 if the client authentication was successful, or an result error number greater than 0 that align to the openssl verify error codes.
cli=openstack loadbalancer listener create [--insert-headers X-SSL-Client-Verify=true] <loadbalancer>
driver.amphora=complete
driver.ovn=missing

2
doc/source/user/feature-classification/feature-matrix-pool.ini
View File

@ -63,7 +63,7 @@ driver.ovn=missing
[operation.lb_algorithm.ROUND_ROBIN]
title=lb_algorithm - ROUND_ROBIN
notes=The pool will direct connections to the next member server, one after the other, rotating through the available memeber servers.
notes=The pool will direct connections to the next member server, one after the other, rotating through the available member servers.
cli=openstack loadbalancer pool create --lb-algorithm ROUND_ROBIN --listener <listener>
driver.amphora=complete
driver.ovn=missing

4
doc/source/user/guides/basic-cookbook.rst
View File

@ -731,7 +731,7 @@ terminated listener, see the above section
Deploy a load balancer with backend re-encryption and client authentication
---------------------------------------------------------------------------
This example will demostrate how to enable TLS encryption from the load
This example will demonstrate how to enable TLS encryption from the load
balancer to the backend member servers with the load balancer being
authenticated using TLS client authentication. Typically this is used with TLS
termination enabled on the listener, but, to simplify the example, we are going
@ -945,7 +945,7 @@ In this case, using ``TLS-HELLO`` type monitoring is an alternative.
If an application is listening on this port, the Operating System should reply
with an INIT ACK packet, but if the port is closed, it replies with an ABORT
packet.
If the health monitor receives an INIT ACK packet, it immediatly closes the
If the health monitor receives an INIT ACK packet, it immediately closes the
connection with an ABORT packet, and considers that the server is ONLINE.
``TLS-HELLO`` health monitors simply ensure the back-end server responds to

2
doc/source/user/guides/l7.rst
View File

@ -93,7 +93,7 @@ L7 rules have the following types:
certificate validation result. A value of '0' means the certificate was
successfully validated. A value greater than '0' means the certificate
failed validation. This value follows the `openssl-verify result codes <https://github.com/openssl/openssl/blob/master/include/openssl/x509_vfy.h#L99>`_.
* ``SSL_DN_FIELD``: The rule looks for a Distinguished Name feild defined in
* ``SSL_DN_FIELD``: The rule looks for a Distinguished Name field defined in
the key parameter and compares it against the value parameter in the rule.
Comparison types

2
doc/source/user/guides/monitoring.rst
View File

@ -77,7 +77,7 @@ Monitoring with Prometheus
==========================
Some provider drivers, such as the Octavia amphora driver, provide a prometheus
endpoint. This allows you to configure your Prometheus infrastruture to collect
endpoint. This allows you to configure your Prometheus infrastructure to collect
metrics from Octavia load balancers.
To add a Prometheus endpoint on an Octavia load balancer, create a listener