ansible-collections/google.cloud
1
0
Fork 0
mirror of https://github.com/ansible-collections/google.cloud.git synced 2025-04-25 20:31:24 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

fix doc formatting errors (#4118) (#310)

Browse source 
Co-authored-by: Riley Karson <rileykarson@google.com>
Signed-off-by: Modular Magician <magic-modules@google.com>

Co-authored-by: Riley Karson <rileykarson@google.com>
This commit is contained in:
The Magician 2020-10-16 13:41:31 -07:00 • committed by GitHub
parent 3228844456
commit 3af242d21d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
16 changed files with 285 additions and 282 deletions
Download patch file Download diff file Expand all files Collapse all files

38
plugins/modules/gcp_compute_backend_service.py
View file

@ -406,19 +406,19 @@ options:
locality_lb_policy:
description:
- The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each
- The possible values are - * ROUND_ROBIN - This is a simple policy in which each
healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and
picks the host which has fewer active requests.
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing
- "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts
and picks the host which has fewer active requests."
- "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
to backends. The algorithm has the property that the addition/removal of a host
from a set of N hosts only affects 1/N of the requests.
- RANDOM - The load balancer selects a random healthy host.
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection
from a set of N hosts only affects 1/N of the requests."
- "* RANDOM - The load balancer selects a random healthy host."
- "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to the
load balancer.
- MAGLEV - used as a drop in replacement for the ring hash load balancer.
load balancer."
- "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times
and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED.
@ -1067,19 +1067,19 @@ loadBalancingScheme:
localityLbPolicy:
description:
- The load balancing algorithm used within the scope of the locality.
- The possible values are - ROUND_ROBIN - This is a simple policy in which each
- The possible values are - * ROUND_ROBIN - This is a simple policy in which each
healthy backend is selected in round robin order.
- LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks
the host which has fewer active requests.
- RING_HASH - The ring/modulo hash load balancer implements consistent hashing to
backends. The algorithm has the property that the addition/removal of a host from
a set of N hosts only affects 1/N of the requests.
- RANDOM - The load balancer selects a random healthy host.
- ORIGINAL_DESTINATION - Backend host is selected based on the client connection
- "* LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and
picks the host which has fewer active requests."
- "* RING_HASH - The ring/modulo hash load balancer implements consistent hashing
to backends. The algorithm has the property that the addition/removal of a host
from a set of N hosts only affects 1/N of the requests."
- "* RANDOM - The load balancer selects a random healthy host."
- "* ORIGINAL_DESTINATION - Backend host is selected based on the client connection
metadata, i.e., connections are opened to the same address as the destination
address of the incoming connection before the connection was redirected to the
load balancer.
- MAGLEV - used as a drop in replacement for the ring hash load balancer.
load balancer."
- "* MAGLEV - used as a drop in replacement for the ring hash load balancer."
- Maglev is not as stable as ring hash but has faster table lookup build times and
host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824
This field is applicable only when the load_balancing_scheme is set to INTERNAL_SELF_MANAGED.