drop unnecessary files

This commit is contained in:
Artem Goncharov 2022-03-08 13:37:36 +01:00
parent f39e70949b
commit e113352f45
474 changed files with 0 additions and 62274 deletions

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,71 +0,0 @@
Deleting a Certificate
======================
Function
^^^^^^^^
This API is used to delete an SSL certificate.
Constraints
^^^^^^^^^^^
If the certificate is used by a listener, the certificate cannot be deleted, and the 409 Conflict error code will be displayed.
URI
^^^
DELETE /v3/{project_id}/elb/certificates/{certificate_id}
.. table:: **Table 1** Path parameters
============== ========= ====== ===========================
Parameter Mandatory Type Description
============== ========= ====== ===========================
project_id Yes String Specifies the project ID.
certificate_id Yes String Specifies a certificate ID.
============== ========= ====== ===========================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/{project_id}/elb/certificates/{certificate_id}
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Certificate <topic_300000004.html>`__

View File

@ -1,72 +0,0 @@
Deleting a Health Check
=======================
Function
^^^^^^^^
This API is used to delete a health check.
Constraints
^^^^^^^^^^^
The health check can be deleted only when the provisioning status of the associated load balancer is **ACTIVE**.
URI
^^^
DELETE /v3/{project_id}/elb/healthmonitors/{healthmonitor_id}
.. table:: **Table 1** Path parameters
================ ========= ====== ==============================
Parameter Mandatory Type Description
================ ========= ====== ==============================
project_id Yes String Specifies the project ID.
healthmonitor_id Yes String Specifies the health check ID.
================ ========= ====== ==============================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/99a3fff0d03c428eac3678da6a7d0f24/elb/healthmonitors/c2b210b2-60c4-449d-91e2-9e9ea1dd7441
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Health Check <topic_300000008.html>`__

View File

@ -1,67 +0,0 @@
Deleting a Forwarding Policy
============================
Function
^^^^^^^^
This API is used to delete a forwarding policy.
URI
^^^
DELETE /v3/{project_id}/elb/l7policies/{l7policy_id}
.. table:: **Table 1** Path parameters
=========== ========= ====== ===================================
Parameter Mandatory Type Description
=========== ========= ====== ===================================
project_id Yes String Specifies the project ID.
l7policy_id Yes String Specifies the forwarding policy ID.
=========== ========= ====== ===================================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/99a3fff0d03c428eac3678da6a7d0f24/elb/l7policies/cf4360fd-8631-41ff-a6f5-b72c35da74be
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Forwarding Policy <topic_300000009.html>`__

View File

@ -1,68 +0,0 @@
Deleting a Forwarding Rule
==========================
Function
^^^^^^^^
This API is used to delete a forwarding rule.
URI
^^^
DELETE /v3/{project_id}/elb/l7policies/{l7policy_id}/rules/{l7rule_id}
.. table:: **Table 1** Path parameters
=========== ========= ====== ===================================
Parameter Mandatory Type Description
=========== ========= ====== ===================================
project_id Yes String Specifies the project ID.
l7policy_id Yes String Specifies the forwarding policy ID.
l7rule_id Yes String Specifies the forwarding rule ID.
=========== ========= ====== ===================================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/99a3fff0d03c428eac3678da6a7d0f24/elb/l7policies/cf4360fd-8631-41ff-a6f5-b72c35da74be/rules/84f4fcae-9c15-4e19-a99f-72c0b08fd3d7
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Forwarding Rule <topic_300000010.html>`__

View File

@ -1,71 +0,0 @@
Deleting a Listener
===================
Function
^^^^^^^^
This API is used to delete a listener.
Constraints
^^^^^^^^^^^
Before you delete a listener, delete the associated backend server group or disassociate the backend server group from the listener, and then delete all forwarding policies.
URI
^^^
DELETE /v3/{project_id}/elb/listeners/{listener_id}
.. table:: **Table 1** Path parameters
=========== ========= ====== ==========================
Parameter Mandatory Type Description
=========== ========= ====== ==========================
project_id Yes String Specifies the project ID.
listener_id Yes String Specifies the listener ID.
=========== ========= ====== ==========================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/{project_id}/elb/listeners/{listener_id}
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Listener <topic_300000005.html>`__

View File

@ -1,72 +0,0 @@
Deleting a Load Balancer
========================
Function
^^^^^^^^
This API is used to delete a load balancer.
Constraints
^^^^^^^^^^^
All listeners added to the load balancer must be deleted before the load balancer is deleted.
URI
^^^
DELETE /v3/{project_id}/elb/loadbalancers/{loadbalancer_id}
.. table:: **Table 1** Path parameters
=============== ========= ====== ===============================
Parameter Mandatory Type Description
=============== ========= ====== ===============================
project_id Yes String Specifies the project ID.
loadbalancer_id Yes String Specifies the load balancer ID.
=============== ========= ====== ===============================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/{project_id}/elb/loadbalancers/{loadbalancer_id}
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Load Balancer <topic_300000003.html>`__

View File

@ -1,77 +0,0 @@
Removing a Backend Server
=========================
Function
^^^^^^^^
This API is used to remove a backend server.
Constraints
^^^^^^^^^^^
When you remove backend servers, note the following:
- After you remove a backend server, new connections to this server will not be established. However, persistent connections that have been established will be maintained.
- The last backend server cannot be removed. If it is removed, 403 will be returned.
URI
^^^
DELETE /v3/{project_id}/elb/pools/{pool_id}/members/{member_id}
.. table:: **Table 1** Path parameters
========== ========= ====== =============================================
Parameter Mandatory Type Description
========== ========= ====== =============================================
project_id Yes String Specifies the project ID.
pool_id Yes String Specifies the ID of the backend server group.
member_id Yes String Specifies the backend server ID.
========== ========= ====== =============================================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/9a3fff0d03c428eac3678da6a7d0f24/elb/pools/36ce7086-a496-4666-9064-5ba0e6840c75/members/1923923e-fe8a-484f-bdbc-e11559b1f48f
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Backend Server <topic_300000007.html>`__

View File

@ -1,72 +0,0 @@
Deleting a Backend Server Group
===============================
Function
^^^^^^^^
This API is used to delete a backend server group.
Constraints
^^^^^^^^^^^
A backend server group can be deleted only after all servers are removed from the group, the health check configured for the group is deleted, and the group has no forwarding policies associated.
URI
^^^
DELETE /v3/{project_id}/elb/pools/{pool_id}
.. table:: **Table 1** Path parameters
========== ========= ====== =============================================
Parameter Mandatory Type Description
========== ========= ====== =============================================
project_id Yes String Specifies the project ID.
pool_id Yes String Specifies the ID of the backend server group.
========== ========= ====== =============================================
Request Parameters
^^^^^^^^^^^^^^^^^^
.. table:: **Table 2** Request header parameters
============ ========= ====== ================================================
Parameter Mandatory Type Description
============ ========= ====== ================================================
X-Auth-Token Yes String Specifies the token used for IAM authentication.
============ ========= ====== ================================================
Response Parameters
^^^^^^^^^^^^^^^^^^^
None
Example Requests
^^^^^^^^^^^^^^^^
.. code:: screen
DELETE
https://{elb_endpoint}/v3/99a3fff0d03c428eac3678da6a7d0f24/elb/pools/36ce7086-a496-4666-9064-5ba0e6840c75
Example Responses
^^^^^^^^^^^^^^^^^
None
Status Codes
^^^^^^^^^^^^
=========== ===================
Status Code Description
=========== ===================
204 Successful request.
=========== ===================
Error Codes
^^^^^^^^^^^
See `Error Codes <errorcode.html>`__.
**Parent topic:** `Backend Server Group <topic_300000006.html>`__

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,15 +0,0 @@
Dedicated Load Balancer APIs
============================
- `API Call Precaution <en-us_topic_0000001088310753.html>`__
- `Quota <topic_300000000.html>`__
- `AZ <topic_300000001.html>`__
- `Load Balancer Flavor <topic_300000002.html>`__
- `Load Balancer <topic_300000003.html>`__
- `Certificate <topic_300000004.html>`__
- `Listener <topic_300000005.html>`__
- `Backend Server Group <topic_300000006.html>`__
- `Backend Server <topic_300000007.html>`__
- `Health Check <topic_300000008.html>`__
- `Forwarding Policy <topic_300000009.html>`__
- `Forwarding Rule <topic_300000010.html>`__

View File

@ -1,6 +0,0 @@
Examples
========
- `Creating a Dedicated Load Balancer and Binding a New EIP to It <en-us_topic_0000001127879251.html>`__
- `Adding a Listener to a Dedicated Load Balancer <elb_eg_v3_0002.html>`__
- `Deleting a Dedicated Load Balancer <elb_eg_v3_0003.html>`__

View File

@ -1,85 +0,0 @@
Adding a Listener to a Dedicated Load Balancer
==============================================
Scenarios
^^^^^^^^^
Call the API to add a listener to a dedicated load balancer.
Prerequisites
^^^^^^^^^^^^^
- You have created a dedicated load balancer.
- You have obtained the ID of the dedicated load balancer.
Procedure
^^^^^^^^^
#. Add a listener.
a. Send **POST https://**\ *{elb_endpoint}*\ **/v3/**\ *{project_id}*\ **/elb/listeners**. *project_id* indicates the project ID.
b. Add **X-Auth-Token** to the request header.
c. Ensure that the following parameters are passed in the request body:
.. code:: screen
{
"listener": {
"protocol_port": 80, // Frontend port. The listener will use this port to receive requests.
"protocol": "HTTP", // Frontend protocol. The listener will use this protocol to receive requests.
"loadbalancer_id": "f77281cb-9f58-4347-8f82-2180d8bea789", // Load balancer that the listener is added to
"name": "my_listener" // Listener name
}
}
d. Check the response.
- The request is successful if the following response is displayed:
.. code:: screen
{
"listener": {
"id": "90ad2705-4ffd-43d3-8f75-af8086bde841",
"name": "my_listener",
"protocol_port": 80,
"protocol": "HTTP",
"description": "",
"default_tls_container_ref": null,
"admin_state_up": true,
"loadbalancers": [
{
"id": "f77281cb-9f58-4347-8f82-2180d8bea789"
}
],
"client_ca_tls_container_ref": null,
"project_id": "057ef081eb00d2732fd1c01a9be75e6f",
"sni_container_refs": [],
"connection_limit": -1,
"default_pool_id": null,
"tls_ciphers_policy": null,
"tags": [],
"created_at": "2020-11-21T03:09:13Z",
"updated_at": "2020-11-21T03:09:13Z",
"http2_enable": false,
"insert_headers": {
"X-Forwarded-ELB-IP": false,
"X-Forwarded-Host": true,
"X-Forwarded-For-Port": false,
"X-Forwarded-Port": false
},
"member_timeout": 60,
"client_timeout": 60,
"keepalive_timeout": 60,
"ipgroup": null,
"enable_member_retry": true,
"transparent_client_ip_enable": true
},
"request_id": "fcd61ee6a6a6c673c65fa0df0577fed9"
}
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
**Parent topic:** `Examples <elb_eg_v3_0000.html>`__

View File

@ -1,86 +0,0 @@
Deleting a Dedicated Load Balancer
==================================
Scenarios
^^^^^^^^^
Call APIs to delete a dedicated load balancer.
Before you delete a dedicated load balancer, delete all resources associated with it. `Figure 1 <#elb_eg_v3_0003__fig14527132320389>`__ shows the associated resources.
| **Figure 1** Resources associated with a dedicated load balancer
| |image1|
Procedure
^^^^^^^^^
Perform the following steps to delete the associated resources and the load balancer. Skip the corresponding step if the associated resources do not exist. For example, you can skip `1 <#elb_eg_v3_0003__li693163653915>`__ if no health check is configured.
#. Delete the health check configured for each associated backend server group.
a. Send **DELETE https://**\ *{elb_endpoint}*\ **/v3/**\ *{project_id}*\ **/elb/healthmonitors/**\ *{healthmonitor_id}*. *project_id* indicates the project ID, and *healthmonitor_id* indicates the health check ID.
b. Add **X-Auth-Token** to the request header.
c. Check the response.
- If the request is successful, 204 is returned, and the response body is empty.
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
#. Remove backend servers from each associated backend server group.
a. Send **DELETE https://**\ *{elb_endpoint}*\ **/v3/**\ *{project_id}*\ **/elb/pools/**\ *{pool_id}*\ **/members/**\ *{member_id}*. *project_id* indicates the project ID, *pool_id* indicates the backend server group ID, and **member_id** indicates the backend server ID.
b. Add **X-Auth-Token** to the request header.
c. Check the response.
- If the request is successful, 204 is returned, and the response body is empty.
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
#. Delete each associated backend server group.
a. Send **DELETE https://**\ *{elb_endpoint}*\ **/v3/{project_id}/elb/pools/**\ *{pool_id}*. *project_id* indicates the project ID, and *pool_id* indicates the backend server group ID.
b. Add **X-Auth-Token** to the request header.
c. Check the response.
- If the request is successful, 204 is returned, and the response body is empty.
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
#. Delete the forwarding rules added to each listener.
a. Send **DELETE https://**\ *{elb_endpoint}*\ **/v3/**\ *{project_id}*\ **/elb/l7policies/**\ *{policy_id}*\ **/rules/**\ *{rule_id}*. *project_id* indicates the project ID, *policy_id* indicates the forwarding policy ID, and *rule_id* indicates the forwarding rule ID.
b. Add **X-Auth-Token** to the request header.
c. Check the response.
- If the request is successful, 204 is returned, and the response body is empty.
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
#. Delete the forwarding policies added to each listener.
a. Send **DELETE https://**\ *{elb_endpoint}*\ **/v3/**\ *{project_id}*\ **/elb/l7policies/**\ *{policy_id}*. *project_id* indicates the project ID, and *policy_id* indicates the forwarding policy ID.
b. Add **X-Auth-Token** to the request header.
c. Check the response.
- If the request is successful, 204 is returned, and the response body is empty.
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
#. Delete each listener added to the load balancer.
a. Send **DELETE https://**\ *{elb_endpoint}*\ **/v3/**\ *{project_id}*\ **/elb/listeners/**\ *{listener_id}*. *project_id* indicates the project ID, and *listener_id* indicates the listener ID.
b. Add **X-Auth-Token** to the request header.
c. Check the response.
- If the request is successful, 204 is returned, and the response body is empty.
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
#. Delete the load balancer.
a. Send **DELETE https://**\ *{elb_endpoint}*\ **/v3/**\ *{project_id}*\ **/elbloadbalancers/**\ *{loadbalancer_id}*. *project_id* indicates the project ID, and *loadbalancer_id* indicates the load balancer ID.
b. Add **X-Auth-Token** to the request header.
c. Check the response.
- If the request is successful, 204 is returned, and the response body is empty.
- If the request is abnormal, locate the fault by referring to `HTTP Status Codes for Dedicated Load Balancers <errorcode.html>`__.
**Parent topic:** `Examples <elb_eg_v3_0000.html>`__
.. |image1| image:: en-us_image_0294158472.png
:class: eddx
:name: elb_eg_v3_0003__image9527192311384

Some files were not shown because too many files have changed in this diff Show More