session_persistence
+ attribute means no session persistence
+ mechanism is used.session_persistence attribute
+ does not appear in the API response, instead
+ of returning null.null in
+ session_persistence attribute
+ in a VIP update request.| R | generated | N/A | -Unique identifier for the vip. | +Unique identifier for the VIP. | ||
| tenant_id | @@ -234,8 +257,9 @@CR | Derived from authentication token. | N/A | -Owner of the vip. Only an admin user can specify - a tenant ID other than its own. | +Owner of the VIP. Only an admin user can + specify a tenant identifier other than its + own. | |
| name | @@ -244,7 +268,7 @@CRU | None | N/A | -Human readable name for the vip. Does not have + | Human readable name for the VIP. Does not have to be unique. | |
| CRU | None | N/A | -Human readable description for the vip. | +Human readable description for the VIP. | ||
| subnet_id | @@ -263,7 +287,7 @@CR | None | UUID pattern. | -The subnet on which to allocate the vip + | The subnet on which to allocate the VIP address. | |
| No | CR | None | -IP address or null. | -The IP address of the vip. | +IP address or null | +The IP address of the VIP. |
| protocol | @@ -282,7 +306,7 @@CR | None | { "TCP" | "HTTP" | "HTTPS" } | -The protocol of the vip address. | +The protocol of the VIP address. | |
| protocol_port | @@ -292,7 +316,7 @@None | [0..65535] | The port on which to listen to client traffic - that is associated with the vip address. | + that is associated with the VIP address.|||
| pool_id | @@ -301,7 +325,8 @@CRU | None | UUID pattern. | -The |
+ The |
|
| session_persistence | @@ -329,7 +354,22 @@ -Session persistence parameters of the vip. | +session_persistence
+ attribute means no session persistence
+ mechanism is used.session_persistence
+ attribute does not appear in the API
+ response, instead of returning
+ null.null in
+ session_persistence
+ attribute in a VIP update
+ request. |
||||
| connection_limit | @@ -337,9 +377,10 @@No | CRU | -1 | -None. | +None | The maximum number of connections allowed for
- the vip or -1 if the limit is not set. |
+ the VIP or
| admin_state_up | @@ -348,7 +389,7 @@CRU | true | {true | false } | -Administrative state of the vip. | +Administrative state of the VIP | |
| status | @@ -357,18 +398,9 @@R | N/A | N/A | -Indicates whether or not a vip is currently + | Indicates whether a VIP is currently operational. | |
| status_description | -String | -N/A | -CRU | -null | -- | - |
| Derived from authentication token. | N/A | Owner of the pool. Only an admin user can - specify a tenant ID other than its - own. | + specify a tenant identifier other than its + own||||
| vip_id | @@ -656,7 +691,8 @@ Content-Length: 0R | None | UUID pattern. | -The |
+ The |
|
| name | @@ -713,7 +749,7 @@ Content-Length: 0None | N/A | List of health monitors to associate with the - pool | + pool.|||
| members | @@ -722,7 +758,7 @@ Content-Length: 0R | None | N/A | -List of members that belong to the pool | +List of members that belong to the pool. | |
| admin_state_up | @@ -731,7 +767,7 @@ Content-Length: 0CRU | true | {true | false } | -Administrative state of the pool | +Administrative state of the pool. | |
| status | @@ -741,16 +777,7 @@ Content-Length: 0N/A | N/A | Indicates whether a pool is currently - operational or not | -|||
| status_description | -String | -N/A | -CRU | -null | -- | + operational or not. |
| Derived from authentication token. | N/A | Owner of the member. Only an admin user can - specify a tenant ID other than its + specify a tenant identifier other than its own. | ||||
| CRU | None | UUID pattern. | -The |
+ The |
||
| address | @@ -1097,15 +1129,6 @@ Content-Length: 0Indicates whether or not a member is currently operational. | |||||
| status_description | -String | -N/A | -CRU | -null | -- | - |
| CR | Derived from authentication token. | N/A | -Owner of the health monitor. Only an admin user - can specify a tenant ID other than its - own. | +Owner of the health monitor. Only an admin + user can specify a tenant identifier other + than its own. | |||
| type | @@ -1399,8 +1425,8 @@ Content-Length: 0CR | None | {"PING" | "TCP" | "HTTP" | "HTTPS"} | -The type of probe sent by load balancer to - verify member state. | +The type of probe send by load balancer to + verify member state | ||
| delay | @@ -1432,7 +1458,7 @@ Content-Length: 0None | [1..10] | Number of allowed connection failures before - changing the status of the member to INACTIVE. | + changing the member's status to INACTIVE.||||
| http_method | @@ -1441,7 +1467,7 @@ Content-Length: 0 xml:id="lbaas_health_monitor_http_method">CRU | GET | @@ -1457,10 +1483,10 @@ Content-Length: 0 />CRU | / | -None. | +None | The HTTP path of the request sent by the
- monitor to test the health of a member. This must
- be a string beginning with a / (forward
+ monitor to test a member's health. This must
+ be a string beginning with a / (forward
slash). |
| CRU | 200 | -Single value, such as 200, list, such as 200, 202, - or range, such as 200-204. | +Single value, such as 200, list, such as 200, + 202, or range, such as 200-204. | The list of HTTP status codes expected in response from the member to declare it healthy. | @@ -1487,6 +1513,16 @@ Content-Length: 0Administrative state of the health monitor. | ||
| status | +String | +N/A | +R | +N/A | +N/A | +Indicates whether or not a health monitor is + currently operational. | +