From 244c8fa25b1595588ebf477b64315bfd88e9543b Mon Sep 17 00:00:00 2001 From: Anne Gentle Date: Mon, 8 Sep 2014 16:41:39 -0500 Subject: [PATCH] Provides LBaaS v1.0 extension info - removes experimental v2.0 - Updates health_monitor JSON example Closes-bug:1214353 Closes-bug:1361413 Change-Id: Id5bd7417090ec65fb6f797870b909c75ba14d634 --- api-ref/src/docbkx/ch_netconn-ext-v2.xml | 102 +-- .../HealthMonitor-post-associate-req.json | 5 + .../HealthMonitor-post-associate-resp.json | 5 + .../HealthMonitor-put-update-resp.json | 19 + .../HealthMonitor-put-update.req.json | 5 + .../api_samples/Member-put-update-resp.json | 13 + .../api_samples/Member-put-update.req.json | 5 + .../src/api_samples/Pool-put-update-resp.json | 20 + .../src/api_samples/hms-get-resp.json | 25 + .../src/api_samples/member-get-resp.json | 24 + .../src/api_samples/pool-put-update.req.json | 5 + .../src/api_samples/pools-get-resp.json | 24 + api-ref/src/wadls/netconn-api/src/common.ent | 827 +++++++++++++++++- .../netconn-api/src/os-lbaasv1.0-ext.wadl | 492 +++++++++++ ...s-lbaas-ext.wadl => os-lbaasv2.0-ext.wadl} | 0 15 files changed, 1492 insertions(+), 79 deletions(-) create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-req.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-resp.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update-resp.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update.req.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update-resp.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update.req.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/Pool-put-update-resp.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/hms-get-resp.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/member-get-resp.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/pool-put-update.req.json create mode 100644 api-ref/src/wadls/netconn-api/src/api_samples/pools-get-resp.json create mode 100644 api-ref/src/wadls/netconn-api/src/os-lbaasv1.0-ext.wadl rename api-ref/src/wadls/netconn-api/src/{os-lbaas-ext.wadl => os-lbaasv2.0-ext.wadl} (100%) diff --git a/api-ref/src/docbkx/ch_netconn-ext-v2.xml b/api-ref/src/docbkx/ch_netconn-ext-v2.xml index 455eea5d5..d95cba740 100644 --- a/api-ref/src/docbkx/ch_netconn-ext-v2.xml +++ b/api-ref/src/docbkx/ch_netconn-ext-v2.xml @@ -22,7 +22,6 @@ List, show information for, update, and reset quotas. - @@ -61,7 +60,7 @@ provider:physical_network, and provider:segmentation_id. The validation rules for these attributes are the same as for the Networks provider extended attributes. You cannot use both extensions at the same time. The NSX and ML2 plug-ins support this extension. With the ML2 plug-in, you can specify @@ -133,13 +132,17 @@ -
- Load-Balancer-as-a-Service (LBaaS) - The LBaaS extension enables OpenStack tenants to load-balance their VM traffic. The - extension enables you to load-balance client traffic from one network to application - services, such as VMs, on the same or a different network. You can load-balance several - protocols, such as TCP and HTTP and monitor the health of application services. The - LBaaS extension supports session persistence. +
+ Load-Balancer-as-a-Service (LBaaS) 1.0 (STABLE) + The LBaaS version 1.0 extension pairs with the + Networking 2.0 API to enable OpenStack tenants to manage + load balancers for their VMs. With this extension + you can load-balance client traffic from one network to application + services, such as VMs, on the same network. + Use this extension to create and manage virtual IP + addresses (VIPs), pools, members of a pool, health + monitors associated with a pool, and view status of a + resource. @@ -149,95 +152,40 @@ - - - - + + - - + - - + - - - - - - - + - - + - - +
Load balancer statuses
Status DescriptionOperational
DEFERREDAn entity was created but is not yet linked to a load balancer.NoACTIVEResource is ready and active.
PENDING_CREATEAn entity is being created.NoResource is being created.
PENDING_UPDATEAn entity was updated. It remains in an operational state.YesResource is being updated.
PENDING_DELETEAn entity is in the process of being deleted.No
ACTIVEAn entity is in a normal operational state.YesResource is going to be deleted.
INACTIVEApplies to members that fail health checks.NoResource is created but not active.
ERRORSomething has gone wrong.This might be in either an operational or non-operational state.Object within the service is not working. Look + for an extra attribute called error_details + for a textual explanation on the error, its + cause, and possibly a solution.
- Use this extension to create and manage load balancers, listeners, pools, members, and - health monitors. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-req.json b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-req.json new file mode 100644 index 000000000..f8d8d34ec --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-req.json @@ -0,0 +1,5 @@ +{ + "health_monitor":{ + "id":"b624decf-d5d3-4c66-9a3d-f047e7786181" + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-resp.json b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-resp.json new file mode 100644 index 000000000..622fa17f7 --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-post-associate-resp.json @@ -0,0 +1,5 @@ +{ + "health_monitor":{ + + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update-resp.json b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update-resp.json new file mode 100644 index 000000000..56db860c8 --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update-resp.json @@ -0,0 +1,19 @@ +{ + "health_monitor": { + "admin_state_up": true, + "tenant_id": "4fd44f30292945e481c7b8a0c8908869", + "delay": 5, + "max_retries": 5, + "http_method": "GET", + "timeout": 1, + "pools": [ + { + "status": "PENDING_CREATE", + "status_description": null, + "pool_id": "6e55751f-6ad4-4e53-b8d4-02e442cd21df" + } + ], + "type": "PING", + "id": "b05e44b5-81f9-4551-b474-711a722698f7" + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update.req.json b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update.req.json new file mode 100644 index 000000000..cfc0831cc --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/HealthMonitor-put-update.req.json @@ -0,0 +1,5 @@ +{ + "health_monitor":{ + "delay":"3" + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update-resp.json b/api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update-resp.json new file mode 100644 index 000000000..ab7fd3418 --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update-resp.json @@ -0,0 +1,13 @@ +{ + "member":{ + "status":"PENDING_UPDATE", + "protocol_port":8080, + "weight":1, + "admin_state_up":false, + "tenant_id":"4fd44f30292945e481c7b8a0c8908869", + "pool_id":"7803631d-f181-4500-b3a2-1b68ba2a75fd", + "address":"10.0.0.5", + "status_description":null, + "id":"48a471ea-64f1-4eb6-9be7-dae6bbe40a0f" + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update.req.json b/api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update.req.json new file mode 100644 index 000000000..61ae6090b --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/Member-put-update.req.json @@ -0,0 +1,5 @@ +{ + "member":{ + "admin_state_up":false + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/Pool-put-update-resp.json b/api-ref/src/wadls/netconn-api/src/api_samples/Pool-put-update-resp.json new file mode 100644 index 000000000..3075ecda0 --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/Pool-put-update-resp.json @@ -0,0 +1,20 @@ +{ + "pool":{ + "status":"PENDING_UPDATE", + "lb_method":"ROUND_ROBIN", + "protocol":"TCP", + "description":"", + "health_monitors":[ + + ], + "subnet_id":"8032909d-47a1-4715-90af-5153ffe39861", + "tenant_id":"83657cfcdfe44cd5920adaf26c48ceea", + "admin_state_up":true, + "name":"SuperPool", + "members":[ + + ], + "id":"61b1f87a-7a21-4ad3-9dda-7f81d249944f", + "vip_id":null + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/hms-get-resp.json b/api-ref/src/wadls/netconn-api/src/api_samples/hms-get-resp.json new file mode 100644 index 000000000..f0c925eef --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/hms-get-resp.json @@ -0,0 +1,25 @@ +{ + "health_monitors":[ + { + "admin_state_up":true, + "tenant_id":"83657cfcdfe44cd5920adaf26c48ceea", + "delay":10, + "max_retries":1, + "timeout":1, + "type":"PING", + "id":"466c8345-28d8-4f84-a246-e04380b0461d" + }, + { + "admin_state_up":true, + "tenant_id":"83657cfcdfe44cd5920adaf26c48ceea", + "delay":5, + "expected_codes":"200", + "max_retries":2, + "http_method":"GET", + "timeout":2, + "url_path":"/", + "type":"HTTP", + "id":"5d4b5228-33b0-4e60-b225-9b727c1a20e7" + } + ] +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/member-get-resp.json b/api-ref/src/wadls/netconn-api/src/api_samples/member-get-resp.json new file mode 100644 index 000000000..30a118c43 --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/member-get-resp.json @@ -0,0 +1,24 @@ +{ + "members":[ + { + "status":"ACTIVE", + "weight":1, + "admin_state_up":true, + "tenant_id":"83657cfcdfe44cd5920adaf26c48ceea", + "pool_id":"72741b06-df4d-4715-b142-276b6bce75ab", + "address":"10.0.0.4", + "protocol_port":80, + "id":"701b531b-111a-4f21-ad85-4795b7b12af6" + }, + { + "status":"ACTIVE", + "weight":1, + "admin_state_up":true, + "tenant_id":"83657cfcdfe44cd5920adaf26c48ceea", + "pool_id":"72741b06-df4d-4715-b142-276b6bce75ab", + "address":"10.0.0.3", + "protocol_port":80, + "id":"beb53b4d-230b-4abd-8118-575b8fa006ef" + } + ] +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/pool-put-update.req.json b/api-ref/src/wadls/netconn-api/src/api_samples/pool-put-update.req.json new file mode 100644 index 000000000..3ff8458bb --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/pool-put-update.req.json @@ -0,0 +1,5 @@ +{ + "pool":{ + "name":"SuperPool" + } +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/api_samples/pools-get-resp.json b/api-ref/src/wadls/netconn-api/src/api_samples/pools-get-resp.json new file mode 100644 index 000000000..a67cad912 --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/api_samples/pools-get-resp.json @@ -0,0 +1,24 @@ +{ + "pools":[ + { + "status":"ACTIVE", + "lb_method":"ROUND_ROBIN", + "protocol":"HTTP", + "description":"", + "health_monitors":[ + "466c8345-28d8-4f84-a246-e04380b0461d", + "5d4b5228-33b0-4e60-b225-9b727c1a20e7" + ], + "subnet_id":"8032909d-47a1-4715-90af-5153ffe39861", + "tenant_id":"83657cfcdfe44cd5920adaf26c48ceea", + "admin_state_up":true, + "name":"app_pool", + "members":[ + "701b531b-111a-4f21-ad85-4795b7b12af6", + "beb53b4d-230b-4abd-8118-575b8fa006ef" + ], + "id":"72741b06-df4d-4715-b142-276b6bce75ab", + "vip_id":"4ec89087-d057-4e2c-911f-60a3b47ee304" + } + ] +} \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/common.ent b/api-ref/src/wadls/netconn-api/src/common.ent index c644a2d28..ee13e76ad 100644 --- a/api-ref/src/wadls/netconn-api/src/common.ent +++ b/api-ref/src/wadls/netconn-api/src/common.ent @@ -1064,7 +1064,9 @@ - The load-balancer algorithm, which is round-robin, least-connections, and so on. This value, which must be supported, is dependent on the load-balancer provider. Round robin must be supported. + The load-balancer algorithm, which is round-robin, least-connections, and so on. + This value, which must be supported, is dependent on the load-balancer provider. Round-robin must be supported. + @@ -1382,7 +1384,8 @@ - Number of allowed connection failures before changing the status of the member to INACTIVE. A valid value is from 1 to 10. + Number of allowed connection failures before changing + the status of the member to INACTIVE. A valid value is from 1 to 10. The administrative state of the member, which is up (true) or down (false). ' > + + + The unique ID for the VIP. + + + + + Owner of the VIP. Only an admin user can specify a tenant ID other than its own. + + + + + Human-readable name for the VIP. Does not have to be unique. + + + + + Human-readable description for the VIP. + + + + + The ID of the subnet on which to allocate the VIP address. + + + + + The IP address of the VIP. + + + + + The protocol of the VIP address. A valid value is TCP, HTTP, or HTTPS. + + + + + The port on which to listen to client traffic that is associated with the VIP address. + A valid value is from 0 to 65535. + + + + + The ID of the pool with which the VIP is associated. + + + + + Session persistence parameters for the VIP. Omit the + session_persistence parameter to prevent + session persistence. When no session persistence is used, + the session_persistence parameter does not appear in the + API response. + To clear session persistence for the VIP, set the + session_persistence parameter to null in a VIP update request. + + + + + The maximum number of connections allowed for the VIP. + Default is -1, meaning no limit. + + + + + The administrative state of the VIP. A valid value is + true (UP) or false (DOWN). + + + + + The status of the VIP. Indicates whether the VIP is operational. + +' > + + + Owner of the VIP. Only an admin user can specify a tenant ID other than its own. + + + + + Human-readable name for the VIP. Does not have to be unique. + + + + + Human-readable description for the VIP. + + + + + The ID of the subnet on which to allocate the VIP address. + + + + + The IP address of the VIP. + + + + + The protocol of the VIP address. A valid value is TCP, HTTP, or HTTPS. + + + + + The port on which to listen to client traffic that is associated with the VIP address. A valid value is from 0 to 65535. + + + + + The ID of the pool with which the VIP is associated. + + + + + Session persistence parameters for the VIP. Omit the + session_persistence parameter to prevent + session persistence. When no session persistence is used, + the session_persistence parameter does not appear in the + API response. + To clear session persistence for the VIP, set the + session_persistence parameter to null in a VIP update request. + + + + + The maximum number of connections allowed for the VIP. + Value is -1 if the limit is not set. + + + + + The administrative state of the VIP. A valid value is true (UP) or false (DOWN). + +' > + + + Human-readable name for the VIP. Does not have to be unique. + + + + + Human-readable description for the VIP. + + + + + The ID of the pool with which the VIP is associated. + + + + + Session persistence parameters for the VIP. Omit the + session_persistence parameter to prevent + session persistence. When no session persistence is used, + the session_persistence parameter does not appear in the + API response. + To clear session persistence for the VIP, set the + session_persistence parameter to null in a VIP update request. + + + + + The maximum number of connections allowed for the VIP. + Value is -1 if the limit is not set. + + + + + The administrative state of the VIP. A valid value is true (UP) or false (DOWN). + +' > + + + + The unique ID for the pool. + + + + + Owner of the pool. Only an admin user can specify a tenant ID other than its own. + + + + + The ID of the VIP with which the pool is associated. + + + + + Human-readable name for the pool. Does not have to be unique. + + + + + Human-readable description for the pool. + + + + + The ID of the network to which pool members belong. + + + + + The protocol of the pool. A valid value is TCP, HTTP, or HTTPS. + + + + + The algorithm that is used to distribute the load among pool members. + + + + + List of members that belong to the pool. + + + + + The administrative state of the pool. A valid value is true (UP) or false (DOWN). + + + + + The status of the pool. Indicates whether the pool is operational. + +' > + + + Owner of the pool. Only an admin user can specify a tenant ID other than its own. + + + + + Human-readable name for the pool. Does not have to be unique. + + + + + Human-readable description for the pool. + + + + + The ID of the network to which pool members belong. + + + + + The protocol of the pool. A valid value is TCP, HTTP, or HTTPS. + + + + + The algorithm that is used to distribute the load among pool members. + + + + + List of health monitors that are associated with the pool. + + + + + The administrative state of the pool. A valid value is true (UP) or false (DOWN). + +' > + + + Human-readable name for the pool. Does not have to be unique. + + + + + Human-readable description for the pool. + + + + + The algorithm that is used to distribute the load among pool members. + + + + + List of health monitors that are associated with the pool. + + + + + The administrative state of the pool. A valid value is true (UP) or false (DOWN). + +' > + + + + The unique ID for the VIP. + + + + + Owner of the VIP. Only an admin user can specify a tenant ID other than its own. + + + + + The type of probe sent by the load balancer to verify the member state. A valid value is PING, TCP, HTTP, or HTTPS. + + + + + The time, in seconds, between sending probes to members. + + + + + The maximum number of seconds for a monitor to wait for a connection to be established before it times out. This value must be less than the delay value. + + + + + Number of allowed connection failures before changing the status of the member to INACTIVE. A valid value is from 1 to 10. + + + + + The HTTP method that the monitor uses for requests. + + + + + The HTTP path of the request sent by the monitor to test the health of a member. Must be a string beginning with a forward slash (/). + + + + + The list of HTTP status codes expected in response from + the member to declare it healthy. Valid values include: a single value, + such as 200, a list, such as 200, 202, or a range, such as 200-204. + + + + + The administrative state of the health monitor. A valid + value is true (UP) or false (DOWN). + + + + + The status of the health monitor. Indicates whether the health monitor is operational. + +' > + + + Owner of the VIP. Only an admin user can specify a tenant ID other than its own. + + + + + The type of probe sent by the load balancer to verify the member state. A valid value is PING, TCP, HTTP, or HTTPS. + + + + + The time, in seconds, between sending probes to members. + + + + + The maximum number of seconds for a monitor to wait for a connection to be established before it times out. This value must be less than the delay value. + + + + + Number of allowed connection failures before changing the status of the member to INACTIVE. A valid value is from 1 to 10. + + + + + The HTTP method that the monitor uses for requests. + + + + + The HTTP path of the request sent by the monitor to test the health of a member. A valid value is a string that begins with a forward slash (/). + + + + + The list of HTTP status codes expected in response from the member to declare it healthy. A valid value is a single value, such as 200, a list, such as 200, 202, or a range, such as 200-204. + + + + + The administrative state of the health monitor. A valid value is true (UP) or false (DOWN). + +' > + + + The time, in seconds, between sending probes to members. + + + + + The maximum number of seconds for a monitor to wait for a connection to be established before it times out. This value must be less than the delay value. + + + + + Number of allowed connection failures before changing the status of the member to INACTIVE. A valid value is from 1 to 10. + + + + + The HTTP method that the monitor uses for requests. + + + + + The HTTP path of the request sent by the monitor to test the health of a member. Must be a string beginning with a forward slash (/). + + + + + The list of HTTP status codes expected in response from the member to declare it healthy. A valid value is a single value, such as 200, a list, such as 200, 202, or a range, such as 200-204. + + + + + The administrative state of the health monitor. A valid value is true (UP) or false (DOWN). + +' > + + + + The unique ID for the member. + + + + + Owner of the member. Only an admin user can specify a tenant ID other than its own. + + + + + The ID of the pool to which the member belongs. + + + + + The IP address of the member. + + + + + The protocol of the VIP address. A valid value is TCP, HTTP, or HTTPS. + + + + + The port on which the application is hosted. + + + + + The weight of a member determines the portion of requests or connections + it services compared to the other members of the pool. + A value of 0 means the member does not participate in load-balancing but still accepts persistent connections. A valid value is from 0 to 256. + + + + + The administrative state of the member. A valid value is true (UP) or false (DOWN). + + + + + The status of the member. Indicates whether the member is operational. + +' > + + + Owner of the member. Only an admin user can specify a tenant ID other than its own. + + + + + The ID of the pool to which the member belongs. + + + + + The IP address of the member. + + + + + The protocol of the VIP address. A valid value is TCP, HTTP, or HTTPS. + + + + + The port on which the application is hosted. + + + + + The weight of a member determines the portion of requests or connections it services compared to the other members of the pool. A value of 0 means the member does not participate in load-balancing but still accepts persistent connections. A valid value is from 0 to 256. + + + + + The administrative state of the member. A valid value is true (UP) or false (DOWN). + + +' > + + + The ID of the pool to which the member belongs. + + + + + The weight of a member determines the portion of requests or connections it services compared to the other members of the pool. A value of 0 means the member does not participate in load-balancing but still accepts persistent connections. A valid value is from 0 to 256. + + + + + The administrative state of the member. A valid value is true (UP) or false (DOWN). + + +' > GET'> PUT'> diff --git a/api-ref/src/wadls/netconn-api/src/os-lbaasv1.0-ext.wadl b/api-ref/src/wadls/netconn-api/src/os-lbaasv1.0-ext.wadl new file mode 100644 index 000000000..4e14685cf --- /dev/null +++ b/api-ref/src/wadls/netconn-api/src/os-lbaasv1.0-ext.wadl @@ -0,0 +1,492 @@ + + + + + + + + + + +%common;]> + + + + + + + + + + + + The UUID for + the VIP. + + + + + + + + + + + + + + + + + + + + + + The UUID + for the pool. + + + + + + + + + The UUID for the health + monitor. + + + + + + + + + + + + The UUID + for the member. + + + + + + + + + + + + + + + + Lists VIPs. + + &vipResponseParams; + + + + + &fault401; &fault403; + + + Creates a load balancer VIP. + + &vipCreateRequestParams; + + + + + + &vipResponseParams; + + + + + &fault400; &fault401; + + + Shows details for a specified + VIP. + + &vipResponseParams; + + + + + &fault401; &fault403; &fault404; + + + Updates a specified load balancer + VIP. + + &vipUpdateRequestParams; + + + + + + &vipResponseParams; + + + + + &fault400; &fault401; &fault403; &fault404; + + + Deletes a specified load balancer + VIP. + + &fault401; &fault404; + &fault409conflict; + + + + Lists pools. + + &poolResponseParams; + + + + + &fault401; &fault403; + + + Creates a load balancer + pool. + + &poolCreateRequestParams; + + + + + + &vipResponseParams; + + + + + &fault400; &fault401; + + + Shows details for a specified + pool. + + &poolResponseParams; + + + + + &fault401; &fault403; &fault404; + + + Updates a specified load balancer + pool. + + &poolUpdateRequestParams; + + + + + + &poolResponseParams; + + + + + &fault400; &fault401; &fault403; &fault404; + + + Deletes a specified load balancer + pool. + + &fault401; &fault404; + &fault409conflict; + + + + Lists members. + + &memberResponseParams; + + + + + &fault401; &fault403; + + + Creates a load balancer + member. + + &memberCreateRequestParams; + + + + + + &memberResponseParams; + + + + + &fault400; &fault401; + + + Shows details for a specified + member. + + &memberResponseParams; + + + + + &fault401; &fault403; &fault404; + + + Updates a specified load balancer + member. + + &memberUpdateRequestParams; + + + + + + &memberResponseParams; + + + + + &fault400; &fault401; &fault403; &fault404; + + + Deletes a specified load balancer + member. + + &fault401; &fault404; + &fault409conflict; + + + + Lists health monitors. + + &hmResponseParams; + + + + + &fault401; &fault403; + + + Creates a load balancer health + monitor. + + &hmCreateRequestParams; + + + + + + &hmResponseParams; + + + + + &fault400; &fault401; + + + Shows details for a specified + health monitor. + + &hmResponseParams; + + + + + &fault401; &fault403; &fault404; + + + Updates a specified load balancer + health monitor. + + &hmUpdateRequestParams; + + + + + + &hmResponseParams; + + + + + &fault400; &fault401; &fault403; &fault404; + + + Deletes a specified load balancer + health monitor. + + + + &fault401; &fault404; + &fault409conflict; + + + Associates a health monitor with a + specified pool. + + &hmCreateRequestParams; + + + + + + &hmResponseParams; + + + + + &fault400; &fault401; + + + Disassociates a specified health + monitor from a pool. + + &fault401; &fault404; + &fault409conflict; + \ No newline at end of file diff --git a/api-ref/src/wadls/netconn-api/src/os-lbaas-ext.wadl b/api-ref/src/wadls/netconn-api/src/os-lbaasv2.0-ext.wadl similarity index 100% rename from api-ref/src/wadls/netconn-api/src/os-lbaas-ext.wadl rename to api-ref/src/wadls/netconn-api/src/os-lbaasv2.0-ext.wadl