diff --git a/docs/css/api-ref/ALL_META.TXT.json b/docs/css/api-ref/ALL_META.TXT.json index bc8dfba7..30aa7ca7 100644 --- a/docs/css/api-ref/ALL_META.TXT.json +++ b/docs/css/api-ref/ALL_META.TXT.json @@ -7,91 +7,26 @@ "node_id":"css_03_0001.xml", "product_code":"css", "code":"1", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "des":"Welcome to Cloud Search Service (CSS) API Reference. CSS is a fully managed, distributed search service that enables you to perform quick, real-time search on both struct", "doc_type":"api", - "kw":"Before You Start", + "kw":"Before You Start,API Reference", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], "title":"Before You Start", "githuburl":"" }, - { - "uri":"css_03_0051.html", - "node_id":"css_03_0051.xml", - "product_code":"css", - "code":"2", - "des":"Welcome to Cloud Search Service API Reference. Cloud Search Service (CSS) provides hosted, distributed search engine services. It is fully compatible with open-source Ela", - "doc_type":"api", - "kw":"Overview,Before You Start,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Overview", - "githuburl":"" - }, - { - "uri":"css_03_0053.html", - "node_id":"css_03_0053.xml", - "product_code":"css", - "code":"3", - "des":"An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For the endpoints of all services, see Regions and Endpoints.", - "doc_type":"api", - "kw":"Endpoints,Before You Start,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Endpoints", - "githuburl":"" - }, - { - "uri":"css_03_0056.html", - "node_id":"css_03_0056.xml", - "product_code":"css", - "code":"4", - "des":"In CSS, Elasticsearch 7.6.2, 7.9.3, and 7.10.2 are supported. OpenSearch 1.3.6 and 2.11.0 are supported. Kibana 7.6.2, 7.9.3, and 7.10.2 are supported.", - "doc_type":"api", - "kw":"Supported Cluster Versions,Before You Start,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Supported Cluster Versions", - "githuburl":"" - }, { "uri":"css_03_0057.html", "node_id":"css_03_0057.xml", "product_code":"css", - "code":"5", - "des":"The CSS API is a self-developed API that complies with RESTful API design specifications. You can call CSS APIs to implement the CSS functions described in Table 1.", + "code":"2", + "des":"CSS APIs comply with RESTful API design specifications. You can use the functions described in Table 1 by calling the corresponding APIs.", "doc_type":"api", "kw":"API Overview,API Reference", "search_title":"", @@ -99,19 +34,17 @@ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], "title":"API Overview", "githuburl":"" }, { - "uri":"css_03_0137.html", - "node_id":"css_03_0137.xml", + "uri":"css_03_0077.html", + "node_id":"css_03_0077.xml", "product_code":"css", - "code":"6", + "code":"3", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", "kw":"Calling APIs", @@ -120,20 +53,18 @@ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], "title":"Calling APIs", "githuburl":"" }, { - "uri":"css_03_0138.html", - "node_id":"css_03_0138.xml", + "uri":"css_03_0078.html", + "node_id":"css_03_0078.xml", "product_code":"css", - "code":"7", - "des":"This section describes the structure of a RESTful API request, and uses the API for Obtaining a User Token as an example to describe how to call an API. A token is a user", + "code":"4", + "des":"This section describes the structure of a RESTful API request, and uses the IAM API for obtain a user token as an example to describe how to call an API.A request URI is ", "doc_type":"api", "kw":"Making an API Request,Calling APIs,API Reference", "search_title":"", @@ -141,20 +72,18 @@ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], "title":"Making an API Request", "githuburl":"" }, { - "uri":"css_03_0139.html", - "node_id":"css_03_0139.xml", + "uri":"css_03_0079.html", + "node_id":"css_03_0079.xml", "product_code":"css", - "code":"8", - "des":"CSS supports token authentication.The validity period of a token is 24 hours. When using a token for authentication, cache it to prevent frequently calling the IAM API.A ", + "code":"5", + "des":"You can use either of the following authentication methods when calling APIs:AK/SK-based authentication: Requests are encrypted using AK/SK pairs.Token authentication: Re", "doc_type":"api", "kw":"Authentication,Calling APIs,API Reference", "search_title":"", @@ -162,19 +91,17 @@ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], "title":"Authentication", "githuburl":"" }, { - "uri":"css_03_0140.html", - "node_id":"css_03_0140.xml", + "uri":"css_03_0080.html", + "node_id":"css_03_0080.xml", "product_code":"css", - "code":"9", + "code":"6", "des":"After sending a request, you will receive a response containing the status code, response header, and response body.A status code is a group of digits, ranging from 1xx t", "doc_type":"api", "kw":"Returned Values,Calling APIs,API Reference", @@ -183,576 +110,499 @@ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], "title":"Returned Values", "githuburl":"" }, { - "uri":"css_03_0062.html", - "node_id":"css_03_0062.xml", + "uri":"css_03_0097.html", + "node_id":"css_03_0097.xml", "product_code":"css", - "code":"10", - "des":"This section describes how to create a CSS cluster by using APIs. Figure 1 illustrates the API calling process.The token obtained on IAM is valid for only 24 hours. If yo", - "doc_type":"api", - "kw":"Getting Started,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Getting Started", - "githuburl":"" - }, - { - "uri":"css_03_0008.html", - "node_id":"css_03_0008.xml", - "product_code":"css", - "code":"11", + "code":"7", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", - "kw":"Cluster Management APIs", + "kw":"APIs", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], - "title":"Cluster Management APIs", + "title":"APIs", "githuburl":"" }, { - "uri":"css_03_0019.html", - "node_id":"css_03_0019.xml", - "product_code":"css", - "code":"12", - "des":"This API is used to create a cluster.Table 2 describes the request parameters.Table 11 describes the response parameters.Example requestExample response{\n \"cluster\": {\n ", + "uri":"cluster_management.html", + "node_id":"cluster_management.xml", + "product_code":"", + "code":"8", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", - "kw":"Creating a Cluster,Cluster Management APIs,API Reference", + "kw":"Cluster Management", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], - "title":"Creating a Cluster", + "title":"Cluster Management", "githuburl":"" }, { - "uri":"css_03_0018.html", - "node_id":"css_03_0018.xml", - "product_code":"css", - "code":"13", - "des":"This API is used to query and display the cluster list and cluster status.NoneTable 2 describes the response parameters.Example requestExample request of querying cluster", + "uri":"CreateCluster.html", + "node_id":"createcluster.xml", + "product_code":"", + "code":"9", + "des":"This API is used to create a cluster.POST /v1.0/{project_id}/clustersStatus code: 200Example request for creating a pay-per-use cluster.Status code: 200Request succeeded.", "doc_type":"api", - "kw":"Querying the List of Clusters,Cluster Management APIs,API Reference", + "kw":"Creating a cluster,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"CreateCluster" } ], - "title":"Querying the List of Clusters", + "title":"Creating a cluster", + "githuburl":"" + }, + { + "uri":"ListClustersDetails.html", + "node_id":"listclustersdetails.xml", + "product_code":"", + "code":"10", + "des":"This API is used to query and display the cluster list and cluster status.GET /v1.0/{project_id}/clustersNoneStatus code: 200Query the first two clusters.- Method 1: GET ", + "doc_type":"api", + "kw":"Querying the Cluster List,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"ListClustersDetails" + } + ], + "title":"Querying the Cluster List", "githuburl":"" }, { "uri":"ShowClusterDetail.html", "node_id":"showclusterdetail.xml", - "product_code":"css", - "code":"14", - "des":"This API is used to query and display details about a cluster.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster_i", + "product_code":"", + "code":"11", + "des":"This API is used to query and display the details of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}NoneStatus code: 200NoneStatus code: 200Request succeeded.See E", "doc_type":"api", - "kw":"Querying Cluster Details,Cluster Management APIs,API Reference", + "kw":"Querying Cluster Details,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ShowClusterDetail" } ], "title":"Querying Cluster Details", "githuburl":"" }, { - "uri":"css_03_0084.html", - "node_id":"css_03_0084.xml", - "product_code":"css", - "code":"15", - "des":"This API is used to change the name of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/changenameNoneNone", + "uri":"DeleteCluster.html", + "node_id":"deletecluster.xml", + "product_code":"", + "code":"12", + "des":"This API is used to delete a cluster. All resources of the deleted cluster, including customer data, will be released. If you want to retain the data in a customer cluste", "doc_type":"api", - "kw":"Changing a Cluster Name,Cluster Management APIs,API Reference", + "kw":"Deleting a Cluster,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Changing a Cluster Name", - "githuburl":"" - }, - { - "uri":"css_03_0021.html", - "node_id":"css_03_0021.xml", - "product_code":"css", - "code":"16", - "des":"This API is used to restart a cluster. Restarting the cluster will interrupt ongoing services.NoneNoneNoneTable 2 describes the status code.", - "doc_type":"api", - "kw":"Restarting a Cluster,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Restarting a Cluster", - "githuburl":"" - }, - { - "uri":"css_03_0020.html", - "node_id":"css_03_0020.xml", - "product_code":"css", - "code":"17", - "des":"This API is used to delete a cluster. All resources, including customer data, of the deleted cluster will be released. For data security reasons, create a snapshot for th", - "doc_type":"api", - "kw":"Deleting a Cluster,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "operation_id":"DeleteCluster" } ], "title":"Deleting a Cluster", "githuburl":"" }, + { + "uri":"UpdateClusterName.html", + "node_id":"updateclustername.xml", + "product_code":"", + "code":"13", + "des":"This API is used to change the name of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/changenameNoneChange the display name of the current cluster.NoneSee Error ", + "doc_type":"api", + "kw":"Renaming a Cluster,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateClusterName" + } + ], + "title":"Renaming a Cluster", + "githuburl":"" + }, { "uri":"ResetPassword.html", "node_id":"resetpassword.xml", - "product_code":"css", + "product_code":"", + "code":"14", + "des":"This API is used to change the password of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/password/resetNoneChange the administrator password of the current clus", + "doc_type":"api", + "kw":"Changing the Password of a Cluster,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"ResetPassword" + } + ], + "title":"Changing the Password of a Cluster", + "githuburl":"" + }, + { + "uri":"RestartCluster.html", + "node_id":"restartcluster.xml", + "product_code":"", + "code":"15", + "des":"This API is used to restart a cluster. Services will be interrupted during the restart.POST /v1.0/{project_id}/clusters/{cluster_id}/restartNoneNoneNoneNoneSee Error Code", + "doc_type":"api", + "kw":"Restarting a Cluster,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"RestartCluster" + } + ], + "title":"Restarting a Cluster", + "githuburl":"" + }, + { + "uri":"UpdateExtendCluster.html", + "node_id":"updateextendcluster.xml", + "product_code":"", + "code":"16", + "des":"This API is used to add instances to a cluster (only Elasticsearch instances can be added). This API can only scale out clusters that only have common nodes. Clusters wit", + "doc_type":"api", + "kw":"Scaling Out a Cluster,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateExtendCluster" + } + ], + "title":"Scaling Out a Cluster", + "githuburl":"" + }, + { + "uri":"UpdateExtendInstanceStorage.html", + "node_id":"updateextendinstancestorage.xml", + "product_code":"", + "code":"17", + "des":"This API is used to add instances of different types and expand instance storage capacity in a cluster. This API is available for clusters with master, client, or cold da", + "doc_type":"api", + "kw":"Adding Instances and Expanding Instance Storage Capacity,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateExtendInstanceStorage" + } + ], + "title":"Adding Instances and Expanding Instance Storage Capacity", + "githuburl":"" + }, + { + "uri":"UpdateFlavor.html", + "node_id":"updateflavor.xml", + "product_code":"", "code":"18", - "des":"This API is used to change the password of a cluster.For details, see Calling APIs.POST /v1.0/{project_id}/clusters/{cluster_id}/password/resetNoneChange the administrato", + "des":"This API is used to modify the specifications of a cluster. Only the nodes of the ESS type can be modified.POST /v1.0/{project_id}/clusters/{cluster_id}/flavorNonePOST /v", "doc_type":"api", - "kw":"Changing a Password,Cluster Management APIs,API Reference", + "kw":"Changing Specifications,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateFlavor" } ], - "title":"Changing a Password", - "githuburl":"" - }, - { - "uri":"css_03_0086.html", - "node_id":"css_03_0086.xml", - "product_code":"css", - "code":"19", - "des":"This API is used to modify the specifications of a cluster. Only the specifications of ESS nodes can be modified.You can debug this API in . Automatic authentication is s", - "doc_type":"api", - "kw":"Modifying Cluster Specifications,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Modifying Cluster Specifications", - "githuburl":"" - }, - { - "uri":"css_03_0087.html", - "node_id":"css_03_0087.xml", - "product_code":"css", - "code":"20", - "des":"This API is used to change the specifications of a specified node type. The following node types are supported:ess: data nodeess-cold: cold data nodeess-client: client no", - "doc_type":"api", - "kw":"Changing the Specifications of a Specified Node Type,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Changing the Specifications of a Specified Node Type", - "githuburl":"" - }, - { - "uri":"css_03_0025.html", - "node_id":"css_03_0025.xml", - "product_code":"css", - "code":"21", - "des":"This API is used to scale out a cluster with only common nodes. Clusters with master, client, or cold data nodes cannot use this API.Table 2 describes the request paramet", - "doc_type":"api", - "kw":"Scaling Out a Cluster with only Common Nodes,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Scaling Out a Cluster with only Common Nodes", - "githuburl":"" - }, - { - "uri":"css_03_0038.html", - "node_id":"css_03_0038.xml", - "product_code":"css", - "code":"22", - "des":"This API is used to scale out a cluster with special nodes. That is, if a cluster has master, client, or cold data nodes, this API is used for scale-out.Table 2 describes", - "doc_type":"api", - "kw":"Scaling Out a Cluster with Special Nodes,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Scaling Out a Cluster with Special Nodes", - "githuburl":"" - }, - { - "uri":"css_03_0088.html", - "node_id":"css_03_0088.xml", - "product_code":"css", - "code":"23", - "des":"This API is used to scale in a cluster by removing specified nodes. Yearly/Monthly clusters do not support the removal of specified nodes by calling this API.You can debu", - "doc_type":"api", - "kw":"Scaling in a Cluster By Removing Specified Nodes,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Scaling in a Cluster By Removing Specified Nodes", - "githuburl":"" - }, - { - "uri":"css_03_0089.html", - "node_id":"css_03_0089.xml", - "product_code":"css", - "code":"24", - "des":"This API is used to remove instances of specific types and reduce instance storage capacity in a cluster.You can debug this API in . Automatic authentication is supported", - "doc_type":"api", - "kw":"Removing Nodes of a Specific Type,Cluster Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Removing Nodes of a Specific Type", + "title":"Changing Specifications", "githuburl":"" }, { "uri":"ListFlavors.html", "node_id":"listflavors.xml", - "product_code":"css", - "code":"25", - "des":"This API is used to query and display the IDs of supported instance flavors.NoneTable 2 describes the response parameters.Example requestGET /v1.0/6204a5bd270343b5885144c", + "product_code":"", + "code":"19", + "des":"This API is used to query and display the IDs of supported instance specifications.GET /v1.0/{project_id}/es-flavorsNoneStatus code: 200NoneStatus code: 200Request succee", "doc_type":"api", - "kw":"Obtaining the List of Instance Flavors,Cluster Management APIs,API Reference", + "kw":"Obtaining the Instance Specifications List,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ListFlavors" } ], - "title":"Obtaining the List of Instance Flavors", + "title":"Obtaining the Instance Specifications List", "githuburl":"" }, { - "uri":"css_03_0050.html", - "node_id":"css_03_0050.xml", - "product_code":"css", - "code":"26", - "des":"This API is used to download the HTTPS certificate of the server.NoneExample requestExample responseAfter obtaining the preceding character string, run the following comm", + "uri":"ListClustersTags.html", + "node_id":"listclusterstags.xml", + "product_code":"", + "code":"20", + "des":"This API is used to query all tags in a specified region.GET /v1.0/{project_id}/{resource_type}/tagsNoneStatus code: 200NoneStatus code: 200Request succeeded.See Error Co", "doc_type":"api", - "kw":"Downloading the Certificate,Cluster Management APIs,API Reference", + "kw":"Querying All Tags,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Downloading the Certificate", - "githuburl":"" - }, - { - "uri":"css_03_0077.html", - "node_id":"css_03_0077.xml", - "product_code":"css", - "code":"27", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"api", - "kw":"Tag Management APIs", - "search_title":"", - "metedata":[ - { "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Tag Management APIs", - "githuburl":"" - }, - { - "uri":"css_03_0078.html", - "node_id":"css_03_0078.xml", - "product_code":"css", - "code":"28", - "des":"This API is used to query the tag information about a specified cluster.NoneTable 2 describes the response parameters.Example requestExample responseTable 4 describes the", - "doc_type":"api", - "kw":"Querying Tags of a Specified Cluster,Tag Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Querying Tags of a Specified Cluster", - "githuburl":"" - }, - { - "uri":"css_03_0079.html", - "node_id":"css_03_0079.xml", - "product_code":"css", - "code":"29", - "des":"This API is used to query all tags in a specified region.NoneTable 2 describes the response parameters.Example requestExample responseTable 4 describes the status code.", - "doc_type":"api", - "kw":"Querying All Tags,Tag Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "operation_id":"ListClustersTags" } ], "title":"Querying All Tags", "githuburl":"" }, { - "uri":"css_03_0083.html", - "node_id":"css_03_0083.xml", - "product_code":"css", - "code":"30", - "des":"This API is used to add tags to a cluster. A cluster can have a maximum of 10 tags.NoneExample requestPOST /v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa", + "uri":"ShowClusterTag.html", + "node_id":"showclustertag.xml", + "product_code":"", + "code":"21", + "des":"This API is used to query the tags of a specified cluster.GET /v1.0/{project_id}/{resource_type}/{cluster_id}/tagsNoneStatus code: 200NoneStatus code: 200Request succeede", "doc_type":"api", - "kw":"Adding Tags to a Cluster,Tag Management APIs,API Reference", + "kw":"Querying Tags of a Specified Cluster,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ShowClusterTag" + } + ], + "title":"Querying Tags of a Specified Cluster", + "githuburl":"" + }, + { + "uri":"CreateClustersTags.html", + "node_id":"createclusterstags.xml", + "product_code":"", + "code":"22", + "des":"This API is used to add tags to a cluster.POST /v1.0/{project_id}/{resource_type}/{cluster_id}/tagsNoneCreate a cluster tag.NoneSee Error Codes.", + "doc_type":"api", + "kw":"Adding Tags to a Cluster,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"CreateClustersTags" } ], "title":"Adding Tags to a Cluster", "githuburl":"" }, { - "uri":"css_03_0081.html", - "node_id":"css_03_0081.xml", - "product_code":"css", - "code":"31", - "des":"This API is used to add or delete tags to or from a specified cluster in batches. Tag Management Service (TMS) uses this API to batch manage tags of a cluster. A cluster ", + "uri":"DeleteClustersTags.html", + "node_id":"deleteclusterstags.xml", + "product_code":"", + "code":"23", + "des":"This API is used to delete a cluster tag.DELETE /v1.0/{project_id}/{resource_type}/{cluster_id}/tags/{key}NoneNoneNoneNoneSee Error Codes.", "doc_type":"api", - "kw":"Adding or Deleting Cluster Tags in Batches,Tag Management APIs,API Reference", + "kw":"Deleting a Cluster Tag,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"DeleteClustersTags" + } + ], + "title":"Deleting a Cluster Tag", + "githuburl":"" + }, + { + "uri":"UpdateBatchClustersTags.html", + "node_id":"updatebatchclusterstags.xml", + "product_code":"", + "code":"24", + "des":"This API is used to add tags to or delete tags from a cluster in batches.POST /v1.0/{project_id}/{resource_type}/{cluster_id}/tags/actionNoneCreate or delete cluster tags", + "doc_type":"api", + "kw":"Adding or Deleting Cluster Tags in Batches,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateBatchClustersTags" } ], "title":"Adding or Deleting Cluster Tags in Batches", "githuburl":"" }, { - "uri":"css_03_0082.html", - "node_id":"css_03_0082.xml", - "product_code":"css", - "code":"32", - "des":"This API is used to delete specified cluster tags.NoneNoneExample requestDELETE /v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/ta", + "uri":"UpdateShrinkNodes.html", + "node_id":"updateshrinknodes.xml", + "product_code":"", + "code":"25", + "des":"This API is used to scale in a cluster by removing a specified node.POST /v1.0/{project_id}/clusters/{cluster_id}/node/offlineNoneScale in a cluster by scaling in specifi", "doc_type":"api", - "kw":"Deleting Specified Cluster Tags,Tag Management APIs,API Reference", + "kw":"Scaling In a Cluster by Removing a Specific Node,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateShrinkNodes" } ], - "title":"Deleting Specified Cluster Tags", + "title":"Scaling In a Cluster by Removing a Specific Node", "githuburl":"" }, { - "uri":"css_03_0090.html", - "node_id":"css_03_0090.xml", - "product_code":"css", - "code":"33", - "des":"This API is used to replace a failed node.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/instance/{instanc", + "uri":"UpdateFlavorByType.html", + "node_id":"updateflavorbytype.xml", + "product_code":"", + "code":"26", + "des":"This API is used to modify cluster specifications. The following node types can be changed:ess: data nodeess: data nodeess-cold: cold data nodeess-cold: cold data nodeess", "doc_type":"api", - "kw":"Replacing a Node,Cluster Management APIs,API Reference", + "kw":"Changing the Specifications of a Specified Node Type,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateFlavorByType" + } + ], + "title":"Changing the Specifications of a Specified Node Type", + "githuburl":"" + }, + { + "uri":"UpdateShrinkCluster.html", + "node_id":"updateshrinkcluster.xml", + "product_code":"", + "code":"27", + "des":"This API is used to remove instances of different types and reduce instance storage capacity in a cluster.POST /v1.0/extend/{project_id}/clusters/{cluster_id}/role/shrink", + "doc_type":"api", + "kw":"Scaling In Nodes of a Specific Type,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateShrinkCluster" + } + ], + "title":"Scaling In Nodes of a Specific Type", + "githuburl":"" + }, + { + "uri":"DownloadCert.html", + "node_id":"downloadcert.xml", + "product_code":"", + "code":"28", + "des":"This API is used to download a security certificate.GET /v1.0/{project_id}/cer/downloadNoneStatus code: 200NoneStatus code: 200Request succeeded.See Error Codes.", + "doc_type":"api", + "kw":"Downloading a Security Certificate,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"DownloadCert" + } + ], + "title":"Downloading a Security Certificate", + "githuburl":"" + }, + { + "uri":"UpdateInstance.html", + "node_id":"updateinstance.xml", + "product_code":"", + "code":"29", + "des":"This API is used to replace a failed node.PUT /v1.0/{project_id}/clusters/{cluster_id}/instance/{instance_id}/replaceNoneNoneNoneSee Error Codes.", + "doc_type":"api", + "kw":"Replacing a Node,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateInstance" } ], "title":"Replacing a Node", "githuburl":"" }, { - "uri":"css_03_0091.html", - "node_id":"css_03_0091.xml", - "product_code":"css", - "code":"34", - "des":"This API is used to change the security mode of a cluster.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/", + "uri":"ChangeMode.html", + "node_id":"changemode.xml", + "product_code":"", + "code":"30", + "des":"This API is used to configure the security mode of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/mode/changeNoneChange the security mode of the current cluster.", "doc_type":"api", - "kw":"Changing the Security Mode,Cluster Management APIs,API Reference", + "kw":"Configuring the Security Mode.,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ChangeMode" } ], - "title":"Changing the Security Mode", + "title":"Configuring the Security Mode.", "githuburl":"" }, { - "uri":"css_03_0092.html", - "node_id":"css_03_0092.xml", - "product_code":"css", - "code":"35", - "des":"This API is used to change the security group after a cluster is created.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/cluster", + "uri":"AddIndependentNode.html", + "node_id":"addindependentnode.xml", + "product_code":"", + "code":"31", + "des":"If you have not enabled the master or client node when creating a cluster, you can call this API to add one.POST /v1.0/{project_id}/clusters/{cluster_id}/type/{type}/inde", "doc_type":"api", - "kw":"Changing the Security Group,Cluster Management APIs,API Reference", + "kw":"Adding Independent Masters and Clients,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"AddIndependentNode" } ], - "title":"Changing the Security Group", + "title":"Adding Independent Masters and Clients", "githuburl":"" }, { "uri":"UpgradeCore.html", "node_id":"upgradecore.xml", - "product_code":"css", - "code":"36", - "des":"This API is used to upgrade Elasticsearch from an earlier version to a later version or the same version.For details, see Calling APIs.POST /v1.0/{project_id}/clusters/{c", + "product_code":"", + "code":"32", + "des":"This API is used to upgrade Elasticsearch from an earlier version to a later version or the same version.POST /v1.0/{project_id}/clusters/{cluster_id}/inst-type/{inst_typ", "doc_type":"api", - "kw":"Upgrading a Cluster Kernel,Cluster Management APIs,API Reference", + "kw":"Upgrading a Cluster Kernel,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpgradeCore" } ], "title":"Upgrading a Cluster Kernel", @@ -761,19 +611,17 @@ { "uri":"ListImages.html", "node_id":"listimages.xml", - "product_code":"css", - "code":"37", - "des":"This API is used to obtain the ID of an image that can be upgraded in the current cluster.For details, see Calling APIs.GET /v1.0/{project_id}/clusters/{cluster_id}/targe", + "product_code":"", + "code":"33", + "des":"This API is used to obtain the ID of an image that can be upgraded in the current cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/target/{upgrade_type}/imagesNoneSta", "doc_type":"api", - "kw":"Obtaining a Target Image ID,Cluster Management APIs,API Reference", + "kw":"Obtaining a Target Image ID,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ListImages" } ], "title":"Obtaining a Target Image ID", @@ -782,19 +630,17 @@ { "uri":"UpgradeDetail.html", "node_id":"upgradedetail.xml", - "product_code":"css", - "code":"38", - "des":"The upgrade takes a long time. You can call this API to check the upgrade progress on a node.For details, see Calling APIs.GET /v1.0/{project_id}/clusters/{cluster_id}/up", + "product_code":"", + "code":"34", + "des":"The upgrade takes a long time. You can call this API to check the upgrade progress on a node.GET /v1.0/{project_id}/clusters/{cluster_id}/upgrade/detailNoneStatus code: 2", "doc_type":"api", - "kw":"Obtaining Upgrade Details,Cluster Management APIs,API Reference", + "kw":"Obtaining Upgrade Details,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpgradeDetail" } ], "title":"Obtaining Upgrade Details", @@ -803,49 +649,121 @@ { "uri":"RetryUpgradeTask.html", "node_id":"retryupgradetask.xml", - "product_code":"css", - "code":"39", - "des":"The upgrade takes a long time and the upgrade may fail due to network problems. You can use this API to retry a task or terminate the impact of a task.For details, see Ca", + "product_code":"", + "code":"35", + "des":"The upgrade may fail due to network problems. In this case, you can call this API to retry.PUT /v1.0/{project_id}/clusters/{cluster_id}/upgrade/{action_id}/retryNoneNoneE", "doc_type":"api", - "kw":"Retrying a Failed Upgrade Task,Cluster Management APIs,API Reference", + "kw":"Retrying a Failed Upgrade Task,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"RetryUpgradeTask" } ], "title":"Retrying a Failed Upgrade Task", "githuburl":"" }, { - "uri":"AddIndependentNode.html", - "node_id":"addindependentnode.xml", - "product_code":"css", - "code":"40", - "des":"This API is used to add master and client nodes to a cluster.For details, see Calling APIs.POST /v1.0/{project_id}/clusters/{cluster_id}/type/{type}/independentStatus cod", + "uri":"ChangeSecurityGroup.html", + "node_id":"changesecuritygroup.xml", + "product_code":"", + "code":"36", + "des":"This API is used to change the security group after a cluster is created.POST /v1.0/{project_id}/clusters/{cluster_id}/sg/changeNoneChange the security group that the cur", "doc_type":"api", - "kw":"Adding Master and Client Nodes,Cluster Management APIs,API Reference", + "kw":"Changing the Security Group,Cluster Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ChangeSecurityGroup" } ], - "title":"Adding Master and Client Nodes", + "title":"Changing the Security Group", "githuburl":"" }, { - "uri":"css_03_0119.html", - "node_id":"css_03_0119.xml", - "product_code":"css", + "uri":"UpdateAzByInstanceType.html", + "node_id":"updateazbyinstancetype.xml", + "product_code":"", + "code":"37", + "des":"This API is used to change the AZ by specifying node types.POST /v1.0/{project_id}/clusters/{cluster_id}/inst-type/{inst_type}/azmigrateNoneSwitch the AZ of the current c", + "doc_type":"api", + "kw":"Changing the AZ of a Cluster Instance,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateAzByInstanceType" + } + ], + "title":"Changing the AZ of a Cluster Instance", + "githuburl":"" + }, + { + "uri":"CreateClusterMultiRole.html", + "node_id":"createclustermultirole.xml", + "product_code":"", + "code":"38", + "des":"This API is used to create a cluster with multiple node types (for example, ess, ess-cold, ess-client, ess-master).POST /v2.0/{project_id}/clustersStatus code: 200Example", + "doc_type":"api", + "kw":"Creating a Cluster (V2),Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"CreateClusterMultiRole" + } + ], + "title":"Creating a Cluster (V2)", + "githuburl":"" + }, + { + "uri":"RestartClusterMultiRole.html", + "node_id":"restartclustermultirole.xml", + "product_code":"", + "code":"39", + "des":"This API is used to restart nodes of all node types or the combination of some node types in the current cluster.POST /v2.0/{project_id}/clusters/{cluster_id}/restartNone", + "doc_type":"api", + "kw":"Restarting a Cluster (V2),Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"RestartClusterMultiRole" + } + ], + "title":"Restarting a Cluster (V2)", + "githuburl":"" + }, + { + "uri":"RollingRestart.html", + "node_id":"rollingrestart.xml", + "product_code":"", + "code":"40", + "des":"This API is used to restart nodes one by one, which requires a long time when the nodes have a large number of indexes.POST /v2.0/{project_id}/clusters/{cluster_id}/rolli", + "doc_type":"api", + "kw":"Rolling Restart,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"RollingRestart" + } + ], + "title":"Rolling Restart", + "githuburl":"" + }, + { + "uri":"kibana_public_network_access.html", + "node_id":"kibana_public_network_access.xml", + "product_code":"", "code":"41", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", @@ -853,125 +771,111 @@ "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], "title":"Kibana Public Network Access", "githuburl":"" }, { - "uri":"css_03_0120.html", - "node_id":"css_03_0120.xml", - "product_code":"css", + "uri":"StartKibanaPublic.html", + "node_id":"startkibanapublic.xml", + "product_code":"", "code":"42", - "des":"This API is used to enable Kibana public network access.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/pu", + "des":"This API is used to enable public network access to Kibana.POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/openNoneNoneSee Error Codes.", "doc_type":"api", "kw":"Enabling Kibana Public Access,Kibana Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StartKibanaPublic" } ], "title":"Enabling Kibana Public Access", "githuburl":"" }, { - "uri":"css_03_0121.html", - "node_id":"css_03_0121.xml", - "product_code":"css", + "uri":"UpdateCloseKibana.html", + "node_id":"updateclosekibana.xml", + "product_code":"", "code":"43", - "des":"This API is used to disable Kibana public network access.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/pu", + "des":"This API is used to disable public network access to Kibana.Yearly/Monthly clusters cannot disable public access using APIs.PUT /v1.0/{project_id}/clusters/{cluster_id}/p", "doc_type":"api", "kw":"Disabling Kibana Public Access,Kibana Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateCloseKibana" } ], "title":"Disabling Kibana Public Access", "githuburl":"" }, { - "uri":"css_03_0122.html", - "node_id":"css_03_0122.xml", - "product_code":"css", + "uri":"UpdateAlterKibana.html", + "node_id":"updatealterkibana.xml", + "product_code":"", "code":"44", - "des":"This API is used to modify the Kibana public network bandwidth.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster", + "des":"This API is used to modify the public network bandwidth of Kibana.POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/bandwidthNoneModify the Kibana public network", "doc_type":"api", "kw":"Modifying the Kibana Public Network Bandwidth,Kibana Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateAlterKibana" } ], "title":"Modifying the Kibana Public Network Bandwidth", "githuburl":"" }, { - "uri":"css_03_0123.html", - "node_id":"css_03_0123.xml", - "product_code":"css", + "uri":"UpdatePublicKibanaWhitelist.html", + "node_id":"updatepublickibanawhitelist.xml", + "product_code":"", "code":"45", - "des":"This API is used to modify the Kibana public network access whitelist.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{", + "des":"This API is used to modify the Kibana access permission by modifying the Kibana whitelist.POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/updateNoneT", "doc_type":"api", "kw":"Modifying Kibana Public Access Control,Kibana Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdatePublicKibanaWhitelist" } ], "title":"Modifying Kibana Public Access Control", "githuburl":"" }, { - "uri":"css_03_0124.html", - "node_id":"css_03_0124.xml", - "product_code":"css", + "uri":"StopPublicKibanaWhitelist.html", + "node_id":"stoppublickibanawhitelist.xml", + "product_code":"", "code":"46", - "des":"This API is used to disable the Kibana public network access control.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cl", + "des":"This API is used to disable public network access control for Kibana.PUT /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/closeNoneNoneNoneNoneSee Error Co", "doc_type":"api", "kw":"Disabling Kibana Public Network Access Control,Kibana Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StopPublicKibanaWhitelist" } ], "title":"Disabling Kibana Public Network Access Control", "githuburl":"" }, { - "uri":"css_03_0093.html", - "node_id":"css_03_0093.xml", - "product_code":"css", + "uri":"log_management.html", + "node_id":"log_management.xml", + "product_code":"", "code":"47", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", @@ -979,1001 +883,893 @@ "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], "title":"Log Management", "githuburl":"" }, { - "uri":"css_03_0094.html", - "node_id":"css_03_0094.xml", - "product_code":"css", + "uri":"StartLogs.html", + "node_id":"startlogs.xml", + "product_code":"", "code":"48", - "des":"This API is used to enable the log function.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/openNoneN", + "des":"This API is used to enable the log function.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/openNoneEnable the log function.POST /v1.0/6204a5bd270343b5885144cf9c8c158d", "doc_type":"api", "kw":"Enabling the Log Function,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StartLogs" } ], "title":"Enabling the Log Function", "githuburl":"" }, { - "uri":"css_03_0095.html", - "node_id":"css_03_0095.xml", - "product_code":"css", + "uri":"StopLogs.html", + "node_id":"stoplogs.xml", + "product_code":"", "code":"49", - "des":"This API is used to disable the log function.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/closeNone", + "des":"This API is used to disable the log function.PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/closeNoneNoneNoneNoneSee Error Codes.", "doc_type":"api", "kw":"Disabling the Log Function,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StopLogs" } ], "title":"Disabling the Log Function", "githuburl":"" }, { - "uri":"css_03_0096.html", - "node_id":"css_03_0096.xml", - "product_code":"css", + "uri":"ListLogsJob.html", + "node_id":"listlogsjob.xml", + "product_code":"", "code":"50", - "des":"This API is used to query the job list in the logs of a cluster.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster", + "des":"This API is used to query the job list in the logs of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/logs/recordsNoneStatus code: 200NoneStatus code: 200Request s", "doc_type":"api", - "kw":"Viewing the Job List,Log Management,API Reference", + "kw":"Querying the Job List,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ListLogsJob" } ], - "title":"Viewing the Job List", + "title":"Querying the Job List", "githuburl":"" }, { - "uri":"css_03_0097.html", - "node_id":"css_03_0097.xml", - "product_code":"css", + "uri":"ShowGetLogSetting.html", + "node_id":"showgetlogsetting.xml", + "product_code":"", "code":"51", - "des":"This API is used to query basic log configurations.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster_id}/logs/set", + "des":"This API is used to query basic log configurations.GET /v1.0/{project_id}/clusters/{cluster_id}/logs/settingsNoneStatus code: 200NoneStatus code: 200Request succeeded.Exa", "doc_type":"api", "kw":"Querying Basic Log Configurations,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ShowGetLogSetting" } ], "title":"Querying Basic Log Configurations", "githuburl":"" }, { - "uri":"css_03_0098.html", - "node_id":"css_03_0098.xml", - "product_code":"css", + "uri":"UpdateLogSetting.html", + "node_id":"updatelogsetting.xml", + "product_code":"", "code":"52", - "des":"This API is used to modify basic log configurations.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/s", + "des":"This API is used to modify basic log configurations.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/settingsNoneModify basic log configurations.POST /v1.0/6204a5bd2703", "doc_type":"api", "kw":"Modifying Basic Log Configurations,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateLogSetting" } ], "title":"Modifying Basic Log Configurations", "githuburl":"" }, { - "uri":"css_03_0099.html", - "node_id":"css_03_0099.xml", - "product_code":"css", + "uri":"StartLogAutoBackupPolicy.html", + "node_id":"startlogautobackuppolicy.xml", + "product_code":"", "code":"53", - "des":"This API is used to enable the automatic log backup policy.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}", + "des":"This API is used to enable the automatic log backup policy.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/updateNoneEnable the automatic log backup policy.None", "doc_type":"api", "kw":"Enabling the Automatic Log Backup Policy,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StartLogAutoBackupPolicy" } ], "title":"Enabling the Automatic Log Backup Policy", "githuburl":"" }, { - "uri":"css_03_0100.html", - "node_id":"css_03_0100.xml", - "product_code":"css", + "uri":"StopLogAutoBackupPolicy.html", + "node_id":"stoplogautobackuppolicy.xml", + "product_code":"", "code":"54", - "des":"This API is used to disable the automatic log backup policy.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}", + "des":"This API is used to disable the automatic log backup policy.PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/closeNoneNoneNoneNoneSee Error Codes.", "doc_type":"api", "kw":"Disabling the Automatic Log Backup Policy,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StopLogAutoBackupPolicy" } ], "title":"Disabling the Automatic Log Backup Policy", "githuburl":"" }, { - "uri":"css_03_0101.html", - "node_id":"css_03_0101.xml", - "product_code":"css", + "uri":"CreateLogBackup.html", + "node_id":"createlogbackup.xml", + "product_code":"", "code":"55", - "des":"This API is used to back up logs.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/collectNoneNoneNoneN", + "des":"This API is used to back up logs.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/collectNoneNoneNoneNoneSee Error Codes.", "doc_type":"api", "kw":"Backing Up Logs,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"CreateLogBackup" } ], "title":"Backing Up Logs", "githuburl":"" }, { - "uri":"css_03_0102.html", - "node_id":"css_03_0102.xml", - "product_code":"css", + "uri":"ShowLogBackup.html", + "node_id":"showlogbackup.xml", + "product_code":"", "code":"56", - "des":"This API is used to query log information.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/searchStatu", + "des":"This API is used to query log information.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/searchStatus code: 200Query logs.Status code: 200Request succeeded.See Error ", "doc_type":"api", - "kw":"Querying Logs,Log Management,API Reference", + "kw":"Searching for Logs,Log Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ShowLogBackup" } ], - "title":"Querying Logs", + "title":"Searching for Logs", "githuburl":"" }, { - "uri":"css_03_0103.html", - "node_id":"css_03_0103.xml", - "product_code":"css", + "uri":"StartTargetClusterConnectivityTest.html", + "node_id":"starttargetclusterconnectivitytest.xml", + "product_code":"", "code":"57", + "des":"This API is used to test connectivity.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/connectivityNoneTest connectivity to the target cluster.Status code: 200Request s", + "doc_type":"api", + "kw":"Test connectivity.,Log Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"StartTargetClusterConnectivityTest" + } + ], + "title":"Test connectivity.", + "githuburl":"" + }, + { + "uri":"public_network_access.html", + "node_id":"public_network_access.xml", + "product_code":"", + "code":"58", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", "kw":"Public Network Access", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], "title":"Public Network Access", "githuburl":"" }, { - "uri":"css_03_0104.html", - "node_id":"css_03_0104.xml", - "product_code":"css", - "code":"58", - "des":"This API is used to enable public network access.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/public/op", + "uri":"CreateBindPublic.html", + "node_id":"createbindpublic.xml", + "product_code":"", + "code":"59", + "des":"This API is used to enable public network access.POST /v1.0/{project_id}/clusters/{cluster_id}/public/openStatus code: 200Status code: 200Request succeeded.See Error Code", "doc_type":"api", "kw":"Enabling Public Network Access,Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"CreateBindPublic" } ], "title":"Enabling Public Network Access", "githuburl":"" }, { - "uri":"css_03_0105.html", - "node_id":"css_03_0105.xml", - "product_code":"css", - "code":"59", - "des":"This API is used to disable public network access.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/public/cl", + "uri":"UpdateUnbindPublic.html", + "node_id":"updateunbindpublic.xml", + "product_code":"", + "code":"60", + "des":"This API is used to disable public network access to Kibana.Yearly/Monthly clusters cannot disable Kibana public access using APIs.PUT /v1.0/{project_id}/clusters/{cluste", "doc_type":"api", "kw":"Disabling Public Network Access,Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateUnbindPublic" } ], "title":"Disabling Public Network Access", "githuburl":"" }, { - "uri":"css_03_0106.html", - "node_id":"css_03_0106.xml", - "product_code":"css", - "code":"60", - "des":"This API is used to modify the public network access bandwidth.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster", + "uri":"UpdatePublicBandWidth.html", + "node_id":"updatepublicbandwidth.xml", + "product_code":"", + "code":"61", + "des":"This API is used to modify the public network access bandwidth.POST /v1.0/{project_id}/clusters/{cluster_id}/public/bandwidthNoneModify public network access bandwidth.No", "doc_type":"api", "kw":"Modifying Public Network Access Bandwidth,Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdatePublicBandWidth" } ], "title":"Modifying Public Network Access Bandwidth", "githuburl":"" }, { - "uri":"css_03_0107.html", - "node_id":"css_03_0107.xml", - "product_code":"css", - "code":"61", - "des":"This API is used to enable the public network access whitelist.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster", - "doc_type":"api", - "kw":"Enabling the Public Network Access Whitelist,Public Network Access,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Enabling the Public Network Access Whitelist", - "githuburl":"" - }, - { - "uri":"css_03_0108.html", - "node_id":"css_03_0108.xml", - "product_code":"css", + "uri":"StartPublicWhitelist.html", + "node_id":"startpublicwhitelist.xml", + "product_code":"", "code":"62", - "des":"This API is used to disable the public network access whitelist.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster", + "des":"This API is used to enable the public network access control whitelist.POST /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/updateNoneEnable the public network ", "doc_type":"api", - "kw":"Disabling the Public Network Access Whitelist,Public Network Access,API Reference", + "kw":"Enabling the Public Network Access Control Whitelist,Public Network Access,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StartPublicWhitelist" } ], - "title":"Disabling the Public Network Access Whitelist", + "title":"Enabling the Public Network Access Control Whitelist", "githuburl":"" }, { - "uri":"css_03_0010.html", - "node_id":"css_03_0010.xml", - "product_code":"css", + "uri":"StopPublicWhitelist.html", + "node_id":"stoppublicwhitelist.xml", + "product_code":"", "code":"63", + "des":"This API is used to disable the public network access control whitelist.PUT /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/closeNoneNoneNoneNoneSee Error Codes", + "doc_type":"api", + "kw":"Disabling the Public Network Access Control Whitelist,Public Network Access,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"StopPublicWhitelist" + } + ], + "title":"Disabling the Public Network Access Control Whitelist", + "githuburl":"" + }, + { + "uri":"snapshot_management.html", + "node_id":"snapshot_management.xml", + "product_code":"", + "code":"64", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", - "kw":"Snapshot Management APIs", + "kw":"Snapshot Management", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], - "title":"Snapshot Management APIs", + "title":"Snapshot Management", "githuburl":"" }, { - "uri":"css_03_0037.html", - "node_id":"css_03_0037.xml", - "product_code":"css", - "code":"64", - "des":"The API for automatically configuring a cluster snapshot can automatically create OBS buckets and agencies for storing snapshots. If you have multiple clusters, an OBS bu", - "doc_type":"api", - "kw":"(Not Recommended) Automatically Configuring Basic Settings of a Cluster Snapshot,Snapshot Management", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"(Not Recommended) Automatically Configuring Basic Settings of a Cluster Snapshot", - "githuburl":"" - }, - { - "uri":"css_03_0030.html", - "node_id":"css_03_0030.xml", - "product_code":"css", + "uri":"StartAutoSetting.html", + "node_id":"startautosetting.xml", + "product_code":"", "code":"65", - "des":"Using this API will automatically enable the snapshot function.This API is used to modify the basic configurations of a cluster snapshot. The basic configurations include", + "des":"This API is used to automatically set basic configurations for a cluster snapshot, including configuring OBS buckets and IAM agency.OBS Bucket: Enter the location of the ", "doc_type":"api", - "kw":"Modifying Basic Configurations of a Cluster Snapshot,Snapshot Management APIs,API Reference", + "kw":"(Not Recommended) Automatically Setting Basic Configurations of a Cluster Snapshot,Snapshot Manageme", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StartAutoSetting" + } + ], + "title":"(Not Recommended) Automatically Setting Basic Configurations of a Cluster Snapshot", + "githuburl":"" + }, + { + "uri":"UpdateSnapshotSetting.html", + "node_id":"updatesnapshotsetting.xml", + "product_code":"", + "code":"66", + "des":"This API is used to modify the basic configurations for a cluster snapshot, including OBS buckets and IAM agency.You can also use this API to enable the snapshot function", + "doc_type":"api", + "kw":"Modifying Basic Configurations of a Cluster Snapshot,Snapshot Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateSnapshotSetting" } ], "title":"Modifying Basic Configurations of a Cluster Snapshot", "githuburl":"" }, { - "uri":"css_03_0031.html", - "node_id":"css_03_0031.xml", - "product_code":"css", - "code":"66", - "des":"This API is used to set parameters related to automatic snapshot creation. By default, a snapshot is created per day.Table 2 describes the request parameters.NoneExample ", - "doc_type":"api", - "kw":"Setting the Automatic Snapshot Creation Policy,Snapshot Management APIs,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Setting the Automatic Snapshot Creation Policy", - "githuburl":"" - }, - { - "uri":"css_03_0032.html", - "node_id":"css_03_0032.xml", - "product_code":"css", + "uri":"CreateSnapshot.html", + "node_id":"createsnapshot.xml", + "product_code":"", "code":"67", - "des":"This API is used to query the automatic snapshot creation policy for a cluster.NoneTable 2 describes the response parameters.Example requestExample responseTable 3 descri", + "des":"This API is used to manually create a snapshot.POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshotStatus code: 201Create a snapshot.Status code: 201Resource crea", "doc_type":"api", - "kw":"Querying the Automatic Snapshot Creation Policy for a Cluster,Snapshot Management APIs,API Reference", + "kw":"Manually Creating a Snapshot,Snapshot Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Querying the Automatic Snapshot Creation Policy for a Cluster", - "githuburl":"" - }, - { - "uri":"css_03_0033.html", - "node_id":"css_03_0033.xml", - "product_code":"css", - "code":"68", - "des":"This API is used to manually create a snapshot.Table 2 describes the request parameters.Table 3 describes the response parameters.Example requestExample responseTable 5 d", - "doc_type":"api", - "kw":"Manually Creating a Snapshot,Snapshot Management APIs,API Reference", - "search_title":"", - "metedata":[ - { "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "operation_id":"CreateSnapshot" } ], "title":"Manually Creating a Snapshot", "githuburl":"" }, { - "uri":"css_03_0034.html", - "node_id":"css_03_0034.xml", - "product_code":"css", - "code":"69", - "des":"This API is used to query all snapshots of a cluster.NoneExample requestExample responseTable 5 describes the status code.", + "uri":"RestoreSnapshot.html", + "node_id":"restoresnapshot.xml", + "product_code":"", + "code":"68", + "des":"This API is used to manually restore a snapshot.POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}/restoreNoneRestore a snapshot.NoneSee Error Cod", "doc_type":"api", - "kw":"Querying the List of Snapshots,Snapshot Management APIs,API Reference", + "kw":"Restoring a Snapshot,Snapshot Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Querying the List of Snapshots", - "githuburl":"" - }, - { - "uri":"css_03_0035.html", - "node_id":"css_03_0035.xml", - "product_code":"css", - "code":"70", - "des":"This API is used to manually restore a snapshot.Table 2 describes the request parameters.NoneExample requestExample responseThe return value is empty.Table 3 describes th", - "doc_type":"api", - "kw":"Restoring a Snapshot,Snapshot Management APIs,API Reference", - "search_title":"", - "metedata":[ - { "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "operation_id":"RestoreSnapshot" } ], "title":"Restoring a Snapshot", "githuburl":"" }, { - "uri":"css_03_0036.html", - "node_id":"css_03_0036.xml", - "product_code":"css", - "code":"71", - "des":"This API is used to delete a snapshot.NoneNoneExample requestTable 2 describes the status code.", + "uri":"DeleteSnapshot.html", + "node_id":"deletesnapshot.xml", + "product_code":"", + "code":"69", + "des":"This API is used to delete a snapshot.DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}NoneNoneNoneNoneSee Error Codes.", "doc_type":"api", - "kw":"Deleting a Snapshot,Snapshot Management APIs,API Reference", + "kw":"Deleting a Snapshot,Snapshot Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"DeleteSnapshot" } ], "title":"Deleting a Snapshot", "githuburl":"" }, { - "uri":"css_03_0039.html", - "node_id":"css_03_0039.xml", - "product_code":"css", - "code":"72", - "des":"This API is used to disable the snapshot function.NoneNoneExample requestTable 2 describes the status code.", + "uri":"CreateAutoCreatePolicy.html", + "node_id":"createautocreatepolicy.xml", + "product_code":"", + "code":"70", + "des":"This API is used to configure automatic snapshot creation. By default, a snapshot is created every day.POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy", "doc_type":"api", - "kw":"Disabling the Snapshot Function,Snapshot Management APIs,API Reference", + "kw":"Configuring the Automatic Snapshot Creation Policy,Snapshot Management,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"CreateAutoCreatePolicy" + } + ], + "title":"Configuring the Automatic Snapshot Creation Policy", + "githuburl":"" + }, + { + "uri":"ShowAutoCreatePolicy.html", + "node_id":"showautocreatepolicy.xml", + "product_code":"", + "code":"71", + "des":"This API is used to query the automatic snapshot creation policy.GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policyNoneStatus code: 200NoneStatus code: 20", + "doc_type":"api", + "kw":"Querying the Automatic Snapshot Creation Policy,Snapshot Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"ShowAutoCreatePolicy" + } + ], + "title":"Querying the Automatic Snapshot Creation Policy", + "githuburl":"" + }, + { + "uri":"ListSnapshots.html", + "node_id":"listsnapshots.xml", + "product_code":"", + "code":"72", + "des":"This API is used to query all the snapshots of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshotsNoneStatus code: 200NoneStatus code: 200Request succe", + "doc_type":"api", + "kw":"Querying a Snapshot List,Snapshot Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"ListSnapshots" + } + ], + "title":"Querying a Snapshot List", + "githuburl":"" + }, + { + "uri":"StopSnapshot.html", + "node_id":"stopsnapshot.xml", + "product_code":"", + "code":"73", + "des":"This API is used to disable the snapshot function.DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshotsNoneNoneNoneNoneSee Error Codes.", + "doc_type":"api", + "kw":"Disabling the Snapshot Function,Snapshot Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"StopSnapshot" } ], "title":"Disabling the Snapshot Function", "githuburl":"" }, { - "uri":"css_03_0109.html", - "node_id":"css_03_0109.xml", - "product_code":"css", - "code":"73", + "uri":"StartAutoCreateSnapshots.html", + "node_id":"startautocreatesnapshots.xml", + "product_code":"", + "code":"74", + "des":"This API is used to enable the automatic snapshot creation function.POST /v2.0/{project_id}/clusters/{cluster_id}/snapshots/policy/openNoneEnable the automatic backup fun", + "doc_type":"api", + "kw":"Enabling Automatic Snapshot Creation,Snapshot Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"StartAutoCreateSnapshots" + } + ], + "title":"Enabling Automatic Snapshot Creation", + "githuburl":"" + }, + { + "uri":"StopAutoCreateSnapshots.html", + "node_id":"stopautocreatesnapshots.xml", + "product_code":"", + "code":"75", + "des":"This API is used to disable the automatic snapshot creation function.PUT /v2.0/{project_id}/clusters/{cluster_id}/snapshots/policy/closeNoneNoneDisable the automatic back", + "doc_type":"api", + "kw":"Disabling Automatic Snapshot Creation,Snapshot Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"StopAutoCreateSnapshots" + } + ], + "title":"Disabling Automatic Snapshot Creation", + "githuburl":"" + }, + { + "uri":"vpecp_management.html", + "node_id":"vpecp_management.xml", + "product_code":"", + "code":"76", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", "kw":"VPC Endpoint", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], "title":"VPC Endpoint", "githuburl":"" }, { - "uri":"css_03_0110.html", - "node_id":"css_03_0110.xml", - "product_code":"css", - "code":"74", - "des":"This API is used to enable the VPC endpoint service.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/vpceps", + "uri":"StartVpecp.html", + "node_id":"startvpecp.xml", + "product_code":"", + "code":"77", + "des":"This API is used to enable the VPC endpoint service.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/openStatus code: 200Enable the VPC endpoint service.Status ", "doc_type":"api", "kw":"Enabling the VPC Endpoint Service,VPC Endpoint,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StartVpecp" } ], "title":"Enabling the VPC Endpoint Service", "githuburl":"" }, { - "uri":"css_03_0111.html", - "node_id":"css_03_0111.xml", - "product_code":"css", - "code":"75", - "des":"This API is used to disable the VPC endpoint service.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/vpceps", + "uri":"StopVpecp.html", + "node_id":"stopvpecp.xml", + "product_code":"", + "code":"78", + "des":"This API is used to disable the VPC endpoint service.PUT /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/closeNoneStatus code: 200NoneStatus code: 200Request succee", "doc_type":"api", "kw":"Disabling the VPC Endpoint Service,VPC Endpoint,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"StopVpecp" } ], "title":"Disabling the VPC Endpoint Service", "githuburl":"" }, { - "uri":"css_03_0112.html", - "node_id":"css_03_0112.xml", - "product_code":"css", - "code":"76", - "des":"This API is used to obtain a VPC endpoint connection.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster_id}/vpceps", + "uri":"ShowVpcepConnection.html", + "node_id":"showvpcepconnection.xml", + "product_code":"", + "code":"79", + "des":"This API is used to obtain a VPC endpoint connection.GET /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connectionsNoneStatus code: 200NoneStatus code: 200Request ", "doc_type":"api", - "kw":"Obtaining a VPC Endpoint Connection,VPC Endpoint,API Reference", + "kw":"Obtaining an Endpoint Connection,VPC Endpoint,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ShowVpcepConnection" } ], - "title":"Obtaining a VPC Endpoint Connection", + "title":"Obtaining an Endpoint Connection", "githuburl":"" }, { - "uri":"css_03_0113.html", - "node_id":"css_03_0113.xml", - "product_code":"css", - "code":"77", - "des":"This API is used to update a VPC endpoint connection.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcep", + "uri":"UpdateVpcepConnection.html", + "node_id":"updatevpcepconnection.xml", + "product_code":"", + "code":"80", + "des":"This API is used to update an endpoint connection.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connectionsNoneUpdate an endpoint connection.NoneSee Error Co", "doc_type":"api", - "kw":"Updating a VPC Endpoint Connection,VPC Endpoint,API Reference", + "kw":"Updating an Endpoint Connection,VPC Endpoint,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateVpcepConnection" } ], - "title":"Updating a VPC Endpoint Connection", + "title":"Updating an Endpoint Connection", "githuburl":"" }, { - "uri":"css_03_0114.html", - "node_id":"css_03_0114.xml", - "product_code":"css", - "code":"78", - "des":"This API is used to modify the endpoint service whitelist.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/", + "uri":"UpdateVpcepWhitelist.html", + "node_id":"updatevpcepwhitelist.xml", + "product_code":"", + "code":"81", + "des":"This API is used to modify the endpoint service whitelist.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/permissionsNoneModify the endpoint service whitelist.", "doc_type":"api", "kw":"Modifying the Endpoint Service Whitelist,VPC Endpoint,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateVpcepWhitelist" } ], "title":"Modifying the Endpoint Service Whitelist", "githuburl":"" }, { - "uri":"css_03_0115.html", - "node_id":"css_03_0115.xml", - "product_code":"css", - "code":"79", + "uri":"ymls_management.html", + "node_id":"ymls_management.xml", + "product_code":"", + "code":"82", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", "kw":"Parameter Configuration", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], "title":"Parameter Configuration", "githuburl":"" }, { - "uri":"css_03_0116.html", - "node_id":"css_03_0116.xml", - "product_code":"css", - "code":"80", - "des":"This API is used to modify parameter configurations.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/ymls/u", + "uri":"UpdateYmls.html", + "node_id":"updateymls.xml", + "product_code":"", + "code":"83", + "des":"This API is used to modify the parameter settings of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/ymls/updateStatus code: 200Modify parameter settings.Status c", "doc_type":"api", - "kw":"Modifying Parameter Configurations,Parameter Configuration,API Reference", + "kw":"Modifying Cluster Parameters,Parameter Configuration,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"UpdateYmls" } ], - "title":"Modifying Parameter Configurations", + "title":"Modifying Cluster Parameters", "githuburl":"" }, { - "uri":"css_03_0117.html", - "node_id":"css_03_0117.xml", - "product_code":"css", - "code":"81", - "des":"This API is used to obtain the task list of parameter configurations.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cl", + "uri":"ListYmlsJob.html", + "node_id":"listymlsjob.xml", + "product_code":"", + "code":"84", + "des":"This API is used to obtain the parameter configuration task list of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/joblistsNoneStatus code: 200NoneStatus cod", "doc_type":"api", "kw":"Obtaining the Task List of Parameter Configurations,Parameter Configuration,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ListYmlsJob" } ], "title":"Obtaining the Task List of Parameter Configurations", "githuburl":"" }, { - "uri":"css_03_0118.html", - "node_id":"css_03_0118.xml", - "product_code":"css", - "code":"82", - "des":"This API is used to obtain the parameter configuration list of the current cluster.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id", + "uri":"ListYmls.html", + "node_id":"listymls.xml", + "product_code":"", + "code":"85", + "des":"This API is used to obtain the parameter configuration list of the current cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/templateNoneStatus code: 200NoneStatu", "doc_type":"api", "kw":"Obtaining the Parameter Configuration List,Parameter Configuration,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ListYmls" } ], "title":"Obtaining the Parameter Configuration List", "githuburl":"" }, { - "uri":"css_03_0125.html", - "node_id":"css_03_0125.xml", - "product_code":"css", - "code":"83", + "uri":"topic_300000010.html", + "node_id":"topic_300000010.xml", + "product_code":"", + "code":"86", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", "kw":"Load Balancing", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api" } ], "title":"Load Balancing", "githuburl":"" }, { - "uri":"css_03_0126.html", - "node_id":"css_03_0126.xml", - "product_code":"css", - "code":"84", - "des":"This API is used to query the ELB V3 load balancers supported by a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/loadbalancersNoneStatus code: 200NoneStatus code: ", - "doc_type":"api", - "kw":"Querying ELB V3 Load Balancer Supported by a Cluster,Load Balancing,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Querying ELB V3 Load Balancer Supported by a Cluster", - "githuburl":"" - }, - { - "uri":"css_03_0127.html", - "node_id":"css_03_0127.xml", - "product_code":"css", - "code":"85", - "des":"This API is used to enable or disable the ES load balancer.POST /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers/es-switchStatus code: 200Enable the load balancer.N", - "doc_type":"api", - "kw":"Enabling or Disabling the ES Load Balancer,Load Balancing,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Enabling or Disabling the ES Load Balancer", - "githuburl":"" - }, - { - "uri":"css_03_0128.html", - "node_id":"css_03_0128.xml", - "product_code":"css", - "code":"86", - "des":"This API is used to configure the ES listener.POST /v1.0/{project_id}/clusters/{cluster_id}/es-listenersStatus code: 200Status code: 200The request is processed.See Error", - "doc_type":"api", - "kw":"Configuring the ES Listener,Load Balancing,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Configuring the ES Listener", - "githuburl":"" - }, - { - "uri":"css_03_0129.html", - "node_id":"css_03_0129.xml", - "product_code":"css", + "uri":"ListElbs.html", + "node_id":"listelbs.xml", + "product_code":"", "code":"87", - "des":"This API is used to obtain the ES ELB information and health check status.GET /v1.0/{project_id}/clusters/{cluster_id}/es-listenersNoneStatus code: 200NoneStatus code: 20", + "des":"This API is used to query the ELBv3 load balancers supported by a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/loadbalancersNoneStatus code: 200NoneStatus code: 2", "doc_type":"api", - "kw":"Obtaining the ELB Information and Health Check Status,Load Balancing,API Reference", + "kw":"Querying ELBv3 Load Balancers Supported by a Cluster,Load Balancing,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ListElbs" } ], - "title":"Obtaining the ELB Information and Health Check Status", + "title":"Querying ELBv3 Load Balancers Supported by a Cluster", "githuburl":"" }, { - "uri":"css_03_0130.html", - "node_id":"css_03_0130.xml", - "product_code":"css", + "uri":"EnableOrDisableElb.html", + "node_id":"enableordisableelb.xml", + "product_code":"", "code":"88", - "des":"This API is used to update an ES listener.PUT /v1.0/{project_id}/clusters/{cluster_id}/es-listeners/{listener_id}Status code: 200NoneSee Error Codes.", + "des":"This API is used to enable or disable the Elasticsearch load balancer.POST /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers/es-switchStatus code: 200Enable the load", "doc_type":"api", - "kw":"Updating an ES Listener,Load Balancing,API Reference", + "kw":"Enabling or Disabling the Elasticsearch Load Balancer,Load Balancing,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"EnableOrDisableElb" } ], - "title":"Updating an ES Listener", + "title":"Enabling or Disabling the Elasticsearch Load Balancer", "githuburl":"" }, { - "uri":"css_03_0131.html", - "node_id":"css_03_0131.xml", - "product_code":"css", + "uri":"CreateElbListener.html", + "node_id":"createelblistener.xml", + "product_code":"", "code":"89", - "des":"This API is used to query the certificate list.GET /v1.0/{project_id}/clusters/{cluster_id}/elb/certificatesNoneStatus code: 200NoneStatus code: 200The request is process", + "des":"This API is used to configure the Elasticsearch listener.POST /v1.0/{project_id}/clusters/{cluster_id}/es-listenersStatus code: 200Status code: 200Request succeeded.See E", + "doc_type":"api", + "kw":"Configuring the Elasticsearch Listener,Load Balancing,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"CreateElbListener" + } + ], + "title":"Configuring the Elasticsearch Listener", + "githuburl":"" + }, + { + "uri":"ShowElbDetail.html", + "node_id":"showelbdetail.xml", + "product_code":"", + "code":"90", + "des":"This API is used to obtain the ELB information and health check status of an Elasticsearch cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/es-listenersNoneStatus cod", + "doc_type":"api", + "kw":"Obtaining the ES ELB Information and Displaying the Health Check Status,Load Balancing,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"ShowElbDetail" + } + ], + "title":"Obtaining the ES ELB Information and Displaying the Health Check Status", + "githuburl":"" + }, + { + "uri":"UpdateESListener.html", + "node_id":"updateeslistener.xml", + "product_code":"", + "code":"91", + "des":"This API is used to update an Elasticsearch listener.PUT /v1.0/{project_id}/clusters/{cluster_id}/es-listeners/{listener_id}Status code: 200Status code: 200Request succee", + "doc_type":"api", + "kw":"Updating an Elasticsearch Listener,Load Balancing,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api", + "operation_id":"UpdateESListener" + } + ], + "title":"Updating an Elasticsearch Listener", + "githuburl":"" + }, + { + "uri":"ListElbCerts.html", + "node_id":"listelbcerts.xml", + "product_code":"", + "code":"92", + "des":"This API is used to query the certificate list.GET /v1.0/{project_id}/clusters/{cluster_id}/elb/certificatesNoneStatus code: 200NoneStatus code: 200Request succeeded.See ", "doc_type":"api", "kw":"Querying the Certificate List,Load Balancing,API Reference", "search_title":"", "metedata":[ { - "documenttype":"api", - "prodname":"css", "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "documenttype":"api", + "operation_id":"ListElbCerts" } ], "title":"Querying the Certificate List", "githuburl":"" }, { - "uri":"css_03_0132.html", - "node_id":"css_03_0132.xml", - "product_code":"css", - "code":"90", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"api", - "kw":"Intelligent O&M", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Intelligent O&M", - "githuburl":"" - }, - { - "uri":"css_03_0133.html", - "node_id":"css_03_0133.xml", - "product_code":"css", - "code":"91", - "des":"This API is used to create a cluster detection task.POST /v1.0/{project_id}/clusters/{cluster_id}/ai-opsNoneCreate a cluster detection task.NoneFor details, see Error Cod", - "doc_type":"api", - "kw":"Creating a Cluster Detection Task,Intelligent O&M,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Creating a Cluster Detection Task", - "githuburl":"" - }, - { - "uri":"css_03_0134.html", - "node_id":"css_03_0134.xml", - "product_code":"css", - "code":"92", - "des":"This API is used to obtain the intelligent O&M task list and details.GET /v1.0/{project_id}/clusters/{cluster_id}/ai-opsNoneStatus code: 200Obtain the intelligent O&M tas", - "doc_type":"api", - "kw":"Obtaining the Intelligent O&M Task List and Details,Intelligent O&M,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Obtaining the Intelligent O&M Task List and Details", - "githuburl":"" - }, - { - "uri":"css_03_0135.html", - "node_id":"css_03_0135.xml", + "uri":"en-us_topic_0000002083557490.html", + "node_id":"en-us_topic_0000002083557490.xml", "product_code":"css", "code":"93", - "des":"This API is used to delete a detection task record.DELETE /v1.0/{project_id}/clusters/{cluster_id}/ai-ops/{aiops_id}NoneNoneDelete a detection task record.NoneFor details", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", - "kw":"Deleting a Detection Task Record,Intelligent O&M,API Reference", + "kw":"Examples", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], - "title":"Deleting a Detection Task Record", + "title":"Examples", "githuburl":"" }, { - "uri":"css_03_0136.html", - "node_id":"css_03_0136.xml", + "uri":"css_03_0062.html", + "node_id":"css_03_0062.xml", "product_code":"css", "code":"94", - "des":"This API is used to obtain SMN topics available for intelligent O&M alarms.GET /v1.0/{project_id}/domains/{domain_id}/ai-ops/smn-topicsNoneStatus code: 200Obtain the inte", + "des":"This section describes how to create a CSS cluster by using APIs. Figure 1 illustrates the API calling process.The token obtained on IAM is valid for only 24 hours. If yo", "doc_type":"api", - "kw":"Obtaining SMN Topics Available for Intelligent O&M Alarms,Intelligent O&M,API Reference", + "kw":"Creating a Pay-per-Use Elasticsearch Cluster,Examples,API Reference", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], - "title":"Obtaining SMN Topics Available for Intelligent O&M Alarms", + "title":"Creating a Pay-per-Use Elasticsearch Cluster", "githuburl":"" }, { @@ -1981,20 +1777,18 @@ "node_id":"css_03_0065.xml", "product_code":"css", "code":"95", - "des":"This section describes fine-grained permissions management for your CSS. If your cloud account does not need individual IAM users, then you may skip over this chapter.By ", + "des":"This section describes fine-grained permissions management for your CSS. If your account does not need individual IAM users, then you may skip over this chapter.By defaul", "doc_type":"api", - "kw":"Permissions Policies and Supported Actions,API Reference", + "kw":"Permissions and Supported Actions,API Reference", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], - "title":"Permissions Policies and Supported Actions", + "title":"Permissions and Supported Actions", "githuburl":"" }, { @@ -2004,81 +1798,73 @@ "code":"96", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", - "kw":"Common Parameters", + "kw":"Appendixes", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], - "title":"Common Parameters", - "githuburl":"" - }, - { - "uri":"css_03_0071.html", - "node_id":"css_03_0071.xml", - "product_code":"css", - "code":"97", - "des":"A project ID or project name is required in some API requests. You need to obtain the project ID and name before calling an API.Log in to the console.In the upper right c", - "doc_type":"api", - "kw":"Obtaining a Project ID and Name,Common Parameters,API Reference", - "search_title":"", - "metedata":[ - { - "documenttype":"api", - "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" - } - ], - "title":"Obtaining a Project ID and Name", + "title":"Appendixes", "githuburl":"" }, { "uri":"css_03_0075.html", "node_id":"css_03_0075.xml", "product_code":"css", - "code":"98", - "des":"Table 1 describes the status code.", + "code":"97", + "des":"Table 1 describes the status codes.", "doc_type":"api", - "kw":"Status Code,Common Parameters,API Reference", + "kw":"Status Codes,Appendixes,API Reference", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], - "title":"Status Code", + "title":"Status Codes", "githuburl":"" }, { "uri":"css_03_0076.html", "node_id":"css_03_0076.xml", "product_code":"css", - "code":"99", - "des":"No data is returned if an API fails to be invoked. You can locate the cause of an error according to the error code of each API. When the API calling fails, HTTPS status ", + "code":"98", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api", - "kw":"Error Code,Common Parameters,API Reference", + "kw":"Error Codes,Appendixes,API Reference", "search_title":"", "metedata":[ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], - "title":"Error Code", + "title":"Error Codes", + "githuburl":"" + }, + { + "uri":"css_03_0071.html", + "node_id":"css_03_0071.xml", + "product_code":"css", + "code":"99", + "des":"A project ID or project name is required in some API requests. You need to obtain the project ID and name before calling an API.Log in to the console.In the upper right c", + "doc_type":"api", + "kw":"Obtaining a Project ID and Name,Appendixes,API Reference", + "search_title":"", + "metedata":[ + { + "documenttype":"api", + "prodname":"css", + "opensource":"true" + } + ], + "title":"Obtaining a Project ID and Name", "githuburl":"" }, { @@ -2094,9 +1880,7 @@ { "documenttype":"api", "prodname":"css", - "opensource":"true", - "operation_id":"AddIndependentNode", - "version":"v1" + "opensource":"true" } ], "title":"Change History", diff --git a/docs/css/api-ref/AddIndependentNode.html b/docs/css/api-ref/AddIndependentNode.html index 488a4cdf..fbab8e47 100644 --- a/docs/css/api-ref/AddIndependentNode.html +++ b/docs/css/api-ref/AddIndependentNode.html @@ -1,143 +1,145 @@ -

Adding Master and Client Nodes

-

Function

This API is used to add master and client nodes to a cluster.

+

Adding Independent Masters and Clients

+

Function

If you have not enabled the master or client node when creating a cluster, you can call this API to add one.

-

Calling Method

For details, see Calling APIs.

-
-

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/type/{type}/independent

+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/type/{type}/independent

-
Table 1 Path parameters

Parameter

+
- - - - - - - - - - - - - - -
Table 1 Path Parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

project_id

+

project_id

Yes

+

Yes

String

+

String

Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

cluster_id

+

cluster_id

Yes

+

Yes

String

+

String

ID of the cluster that needs an independent master or client.

+

ID of the cluster that needs an independent master or client.

type

+

type

Yes

+

Yes

String

+

String

Node type. The value can be:

-
  • ess-master: Master node
  • ess-client: Client node
+

Node type. Its value can be:

+
  • ess-master: master node

    +
  • ess-client: client node

    +
-

Request Parameters

-
Table 2 Request body parameters

Parameter

+

Request Parameters

+
- - - - - - -
Table 2 Request body parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

type

+

type

Yes

+

Yes

IndependentBodyReq object

+

IndependentTypeReq object

Master/Client request body parameter

+

Master/Client request body parameter

-
Table 3 IndependentBodyReq

Parameter

+
- - - - - - - - - - - - - - -
Table 3 IndependentTypeReq

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

flavor_ref

+

flavor_ref

Yes

+

Yes

String

+

String

Flavor ID. You can obtain the value of this parameter by calling the API Obtaining the Instance Specifications List. Select the flavor ID suitable for your cluster version.

+

Flavor ID. You can obtain the value of this parameter by calling the API for [Obtaining the Instance Specifications List] (ListFlavors.xml). Select the flavor ID suitable for your cluster version.

node_size

+

node_size

Yes

+

Yes

Integer

+

Integer

Number of nodes.

-
  • If the node type is ess-master, the number of nodes must be an odd number in the range 3 to 10.
  • If the node type is ess-client, the number of nodes must be in the range 1 to 32.
+

Number of nodes.

+
  • If the node type is ess-master, the number of nodes must be an odd number in the range 3 to 10.

    +
  • If the node type is ess-client, the number of nodes must be in the range 1 to 32.

    +

volume_type

+

volume_type

Yes

+

Yes

String

+

String

Node storage type. Its value can be ULTRAHIGH, COMMON, or HIGH.

+

Node storage type. Its value can be ULTRAHIGH, COMMON, or HIGH.

-

Response Parameters

Status code: 200

+

Response Parameters

Status code: 200

-
Table 4 Response body parameters

Parameter

+
- - - - -
Table 4 Response body parameters

Parameter

Type

+

Type

Description

+

Description

id

+

id

String

+

String

Cluster ID.

+

Cluster ID.

-

Request Example

Add the master and client nodes.

-
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/type/ess-client/independent
+

Example Requests

Add independent master and client nodes.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/type/ess-client/independent
 
 {
   "type" : {
@@ -147,44 +149,44 @@
   }
 }
-

Response Example

Status code: 200

-

The request is processed.

-
{
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
   "id" : "320afa24-ff2a-4f44-8460-6ba95e512ad4"
 }
-

Status Codes

-

Status Code

+

Status Codes

+
- - - - - - -

Status Code

Description

+

Description

200

+

200

The request is processed.

+

Request succeeded.

403

+

403

The request is rejected. The server has received and understood the request, but refused to respond to it. Modify the request directly and do not attempt to retry it.

+

Request rejected.The server has received the request and understood it, but refused to respond to it. The client should not repeat the request without modifications.

500

+

500

The server can be accessed by the request, but it cannot understand the user's request.

+

The server has received the request but could not understand it.

-

Error Codes

For details, see Error Code.

+

Error Codes

See Error Codes.

diff --git a/docs/css/api-ref/CLASS.TXT.json b/docs/css/api-ref/CLASS.TXT.json index 0f9d7874..705d7e39 100644 --- a/docs/css/api-ref/CLASS.TXT.json +++ b/docs/css/api-ref/CLASS.TXT.json @@ -1,6 +1,6 @@ [ { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"Welcome to Cloud Search Service (CSS) API Reference. CSS is a fully managed, distributed search service that enables you to perform quick, real-time search on both struct", "product_code":"css", "title":"Before You Start", "uri":"css_03_0001.html", @@ -9,406 +9,406 @@ "code":"1" }, { - "desc":"Welcome to Cloud Search Service API Reference. Cloud Search Service (CSS) provides hosted, distributed search engine services. It is fully compatible with open-source Ela", - "product_code":"css", - "title":"Overview", - "uri":"css_03_0051.html", - "doc_type":"api", - "p_code":"1", - "code":"2" - }, - { - "desc":"An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For the endpoints of all services, see Regions and Endpoints.", - "product_code":"css", - "title":"Endpoints", - "uri":"css_03_0053.html", - "doc_type":"api", - "p_code":"1", - "code":"3" - }, - { - "desc":"In CSS, Elasticsearch 7.6.2, 7.9.3, and 7.10.2 are supported. OpenSearch 1.3.6 and 2.11.0 are supported. Kibana 7.6.2, 7.9.3, and 7.10.2 are supported.", - "product_code":"css", - "title":"Supported Cluster Versions", - "uri":"css_03_0056.html", - "doc_type":"api", - "p_code":"1", - "code":"4" - }, - { - "desc":"The CSS API is a self-developed API that complies with RESTful API design specifications. You can call CSS APIs to implement the CSS functions described in Table 1.", + "desc":"CSS APIs comply with RESTful API design specifications. You can use the functions described in Table 1 by calling the corresponding APIs.", "product_code":"css", "title":"API Overview", "uri":"css_03_0057.html", "doc_type":"api", "p_code":"", - "code":"5" + "code":"2" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", "title":"Calling APIs", - "uri":"css_03_0137.html", + "uri":"css_03_0077.html", "doc_type":"api", "p_code":"", - "code":"6" + "code":"3" }, { - "desc":"This section describes the structure of a RESTful API request, and uses the API for Obtaining a User Token as an example to describe how to call an API. A token is a user", + "desc":"This section describes the structure of a RESTful API request, and uses the IAM API for obtain a user token as an example to describe how to call an API.A request URI is ", "product_code":"css", "title":"Making an API Request", - "uri":"css_03_0138.html", + "uri":"css_03_0078.html", "doc_type":"api", - "p_code":"6", - "code":"7" + "p_code":"3", + "code":"4" }, { - "desc":"CSS supports token authentication.The validity period of a token is 24 hours. When using a token for authentication, cache it to prevent frequently calling the IAM API.A ", + "desc":"You can use either of the following authentication methods when calling APIs:AK/SK-based authentication: Requests are encrypted using AK/SK pairs.Token authentication: Re", "product_code":"css", "title":"Authentication", - "uri":"css_03_0139.html", + "uri":"css_03_0079.html", "doc_type":"api", - "p_code":"6", - "code":"8" + "p_code":"3", + "code":"5" }, { "desc":"After sending a request, you will receive a response containing the status code, response header, and response body.A status code is a group of digits, ranging from 1xx t", "product_code":"css", "title":"Returned Values", - "uri":"css_03_0140.html", + "uri":"css_03_0080.html", "doc_type":"api", - "p_code":"6", - "code":"9" - }, - { - "desc":"This section describes how to create a CSS cluster by using APIs. Figure 1 illustrates the API calling process.The token obtained on IAM is valid for only 24 hours. If yo", - "product_code":"css", - "title":"Getting Started", - "uri":"css_03_0062.html", - "doc_type":"api", - "p_code":"", - "code":"10" + "p_code":"3", + "code":"6" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", - "title":"Cluster Management APIs", - "uri":"css_03_0008.html", + "title":"APIs", + "uri":"css_03_0097.html", "doc_type":"api", "p_code":"", - "code":"11" + "code":"7" }, { - "desc":"This API is used to create a cluster.Table 2 describes the request parameters.Table 11 describes the response parameters.Example requestExample response{\n \"cluster\": {\n ", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", - "title":"Creating a Cluster", - "uri":"css_03_0019.html", + "title":"Cluster Management", + "uri":"cluster_management.html", "doc_type":"api", - "p_code":"11", - "code":"12" + "p_code":"7", + "code":"8" }, { - "desc":"This API is used to query and display the cluster list and cluster status.NoneTable 2 describes the response parameters.Example requestExample request of querying cluster", + "desc":"This API is used to create a cluster.POST /v1.0/{project_id}/clustersStatus code: 200Example request for creating a pay-per-use cluster.Status code: 200Request succeeded.", "product_code":"css", - "title":"Querying the List of Clusters", - "uri":"css_03_0018.html", + "title":"Creating a cluster", + "uri":"CreateCluster.html", "doc_type":"api", - "p_code":"11", - "code":"13" + "p_code":"8", + "code":"9" }, { - "desc":"This API is used to query and display details about a cluster.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster_i", + "desc":"This API is used to query and display the cluster list and cluster status.GET /v1.0/{project_id}/clustersNoneStatus code: 200Query the first two clusters.- Method 1: GET ", + "product_code":"css", + "title":"Querying the Cluster List", + "uri":"ListClustersDetails.html", + "doc_type":"api", + "p_code":"8", + "code":"10" + }, + { + "desc":"This API is used to query and display the details of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}NoneStatus code: 200NoneStatus code: 200Request succeeded.See E", "product_code":"css", "title":"Querying Cluster Details", "uri":"ShowClusterDetail.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", + "code":"11" + }, + { + "desc":"This API is used to delete a cluster. All resources of the deleted cluster, including customer data, will be released. If you want to retain the data in a customer cluste", + "product_code":"css", + "title":"Deleting a Cluster", + "uri":"DeleteCluster.html", + "doc_type":"api", + "p_code":"8", + "code":"12" + }, + { + "desc":"This API is used to change the name of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/changenameNoneChange the display name of the current cluster.NoneSee Error ", + "product_code":"css", + "title":"Renaming a Cluster", + "uri":"UpdateClusterName.html", + "doc_type":"api", + "p_code":"8", + "code":"13" + }, + { + "desc":"This API is used to change the password of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/password/resetNoneChange the administrator password of the current clus", + "product_code":"css", + "title":"Changing the Password of a Cluster", + "uri":"ResetPassword.html", + "doc_type":"api", + "p_code":"8", "code":"14" }, { - "desc":"This API is used to change the name of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/changenameNoneNone", + "desc":"This API is used to restart a cluster. Services will be interrupted during the restart.POST /v1.0/{project_id}/clusters/{cluster_id}/restartNoneNoneNoneNoneSee Error Code", "product_code":"css", - "title":"Changing a Cluster Name", - "uri":"css_03_0084.html", + "title":"Restarting a Cluster", + "uri":"RestartCluster.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"15" }, { - "desc":"This API is used to restart a cluster. Restarting the cluster will interrupt ongoing services.NoneNoneNoneTable 2 describes the status code.", + "desc":"This API is used to add instances to a cluster (only Elasticsearch instances can be added). This API can only scale out clusters that only have common nodes. Clusters wit", "product_code":"css", - "title":"Restarting a Cluster", - "uri":"css_03_0021.html", + "title":"Scaling Out a Cluster", + "uri":"UpdateExtendCluster.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"16" }, { - "desc":"This API is used to delete a cluster. All resources, including customer data, of the deleted cluster will be released. For data security reasons, create a snapshot for th", + "desc":"This API is used to add instances of different types and expand instance storage capacity in a cluster. This API is available for clusters with master, client, or cold da", "product_code":"css", - "title":"Deleting a Cluster", - "uri":"css_03_0020.html", + "title":"Adding Instances and Expanding Instance Storage Capacity", + "uri":"UpdateExtendInstanceStorage.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"17" }, { - "desc":"This API is used to change the password of a cluster.For details, see Calling APIs.POST /v1.0/{project_id}/clusters/{cluster_id}/password/resetNoneChange the administrato", + "desc":"This API is used to modify the specifications of a cluster. Only the nodes of the ESS type can be modified.POST /v1.0/{project_id}/clusters/{cluster_id}/flavorNonePOST /v", "product_code":"css", - "title":"Changing a Password", - "uri":"ResetPassword.html", + "title":"Changing Specifications", + "uri":"UpdateFlavor.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"18" }, { - "desc":"This API is used to modify the specifications of a cluster. Only the specifications of ESS nodes can be modified.You can debug this API in . Automatic authentication is s", + "desc":"This API is used to query and display the IDs of supported instance specifications.GET /v1.0/{project_id}/es-flavorsNoneStatus code: 200NoneStatus code: 200Request succee", "product_code":"css", - "title":"Modifying Cluster Specifications", - "uri":"css_03_0086.html", + "title":"Obtaining the Instance Specifications List", + "uri":"ListFlavors.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"19" }, { - "desc":"This API is used to change the specifications of a specified node type. The following node types are supported:ess: data nodeess-cold: cold data nodeess-client: client no", + "desc":"This API is used to query all tags in a specified region.GET /v1.0/{project_id}/{resource_type}/tagsNoneStatus code: 200NoneStatus code: 200Request succeeded.See Error Co", "product_code":"css", - "title":"Changing the Specifications of a Specified Node Type", - "uri":"css_03_0087.html", + "title":"Querying All Tags", + "uri":"ListClustersTags.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"20" }, { - "desc":"This API is used to scale out a cluster with only common nodes. Clusters with master, client, or cold data nodes cannot use this API.Table 2 describes the request paramet", + "desc":"This API is used to query the tags of a specified cluster.GET /v1.0/{project_id}/{resource_type}/{cluster_id}/tagsNoneStatus code: 200NoneStatus code: 200Request succeede", "product_code":"css", - "title":"Scaling Out a Cluster with only Common Nodes", - "uri":"css_03_0025.html", + "title":"Querying Tags of a Specified Cluster", + "uri":"ShowClusterTag.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"21" }, { - "desc":"This API is used to scale out a cluster with special nodes. That is, if a cluster has master, client, or cold data nodes, this API is used for scale-out.Table 2 describes", + "desc":"This API is used to add tags to a cluster.POST /v1.0/{project_id}/{resource_type}/{cluster_id}/tagsNoneCreate a cluster tag.NoneSee Error Codes.", "product_code":"css", - "title":"Scaling Out a Cluster with Special Nodes", - "uri":"css_03_0038.html", + "title":"Adding Tags to a Cluster", + "uri":"CreateClustersTags.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"22" }, { - "desc":"This API is used to scale in a cluster by removing specified nodes. Yearly/Monthly clusters do not support the removal of specified nodes by calling this API.You can debu", + "desc":"This API is used to delete a cluster tag.DELETE /v1.0/{project_id}/{resource_type}/{cluster_id}/tags/{key}NoneNoneNoneNoneSee Error Codes.", "product_code":"css", - "title":"Scaling in a Cluster By Removing Specified Nodes", - "uri":"css_03_0088.html", + "title":"Deleting a Cluster Tag", + "uri":"DeleteClustersTags.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"23" }, { - "desc":"This API is used to remove instances of specific types and reduce instance storage capacity in a cluster.You can debug this API in . Automatic authentication is supported", + "desc":"This API is used to add tags to or delete tags from a cluster in batches.POST /v1.0/{project_id}/{resource_type}/{cluster_id}/tags/actionNoneCreate or delete cluster tags", "product_code":"css", - "title":"Removing Nodes of a Specific Type", - "uri":"css_03_0089.html", + "title":"Adding or Deleting Cluster Tags in Batches", + "uri":"UpdateBatchClustersTags.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"24" }, { - "desc":"This API is used to query and display the IDs of supported instance flavors.NoneTable 2 describes the response parameters.Example requestGET /v1.0/6204a5bd270343b5885144c", + "desc":"This API is used to scale in a cluster by removing a specified node.POST /v1.0/{project_id}/clusters/{cluster_id}/node/offlineNoneScale in a cluster by scaling in specifi", "product_code":"css", - "title":"Obtaining the List of Instance Flavors", - "uri":"ListFlavors.html", + "title":"Scaling In a Cluster by Removing a Specific Node", + "uri":"UpdateShrinkNodes.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"25" }, { - "desc":"This API is used to download the HTTPS certificate of the server.NoneExample requestExample responseAfter obtaining the preceding character string, run the following comm", + "desc":"This API is used to modify cluster specifications. The following node types can be changed:ess: data nodeess: data nodeess-cold: cold data nodeess-cold: cold data nodeess", "product_code":"css", - "title":"Downloading the Certificate", - "uri":"css_03_0050.html", + "title":"Changing the Specifications of a Specified Node Type", + "uri":"UpdateFlavorByType.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"26" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"This API is used to remove instances of different types and reduce instance storage capacity in a cluster.POST /v1.0/extend/{project_id}/clusters/{cluster_id}/role/shrink", "product_code":"css", - "title":"Tag Management APIs", - "uri":"css_03_0077.html", + "title":"Scaling In Nodes of a Specific Type", + "uri":"UpdateShrinkCluster.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"27" }, { - "desc":"This API is used to query the tag information about a specified cluster.NoneTable 2 describes the response parameters.Example requestExample responseTable 4 describes the", + "desc":"This API is used to download a security certificate.GET /v1.0/{project_id}/cer/downloadNoneStatus code: 200NoneStatus code: 200Request succeeded.See Error Codes.", "product_code":"css", - "title":"Querying Tags of a Specified Cluster", - "uri":"css_03_0078.html", + "title":"Downloading a Security Certificate", + "uri":"DownloadCert.html", "doc_type":"api", - "p_code":"27", + "p_code":"8", "code":"28" }, { - "desc":"This API is used to query all tags in a specified region.NoneTable 2 describes the response parameters.Example requestExample responseTable 4 describes the status code.", + "desc":"This API is used to replace a failed node.PUT /v1.0/{project_id}/clusters/{cluster_id}/instance/{instance_id}/replaceNoneNoneNoneSee Error Codes.", "product_code":"css", - "title":"Querying All Tags", - "uri":"css_03_0079.html", + "title":"Replacing a Node", + "uri":"UpdateInstance.html", "doc_type":"api", - "p_code":"27", + "p_code":"8", "code":"29" }, { - "desc":"This API is used to add tags to a cluster. A cluster can have a maximum of 10 tags.NoneExample requestPOST /v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa", + "desc":"This API is used to configure the security mode of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/mode/changeNoneChange the security mode of the current cluster.", "product_code":"css", - "title":"Adding Tags to a Cluster", - "uri":"css_03_0083.html", + "title":"Configuring the Security Mode.", + "uri":"ChangeMode.html", "doc_type":"api", - "p_code":"27", + "p_code":"8", "code":"30" }, { - "desc":"This API is used to add or delete tags to or from a specified cluster in batches. Tag Management Service (TMS) uses this API to batch manage tags of a cluster. A cluster ", + "desc":"If you have not enabled the master or client node when creating a cluster, you can call this API to add one.POST /v1.0/{project_id}/clusters/{cluster_id}/type/{type}/inde", "product_code":"css", - "title":"Adding or Deleting Cluster Tags in Batches", - "uri":"css_03_0081.html", + "title":"Adding Independent Masters and Clients", + "uri":"AddIndependentNode.html", "doc_type":"api", - "p_code":"27", + "p_code":"8", "code":"31" }, { - "desc":"This API is used to delete specified cluster tags.NoneNoneExample requestDELETE /v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/ta", - "product_code":"css", - "title":"Deleting Specified Cluster Tags", - "uri":"css_03_0082.html", - "doc_type":"api", - "p_code":"27", - "code":"32" - }, - { - "desc":"This API is used to replace a failed node.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/instance/{instanc", - "product_code":"css", - "title":"Replacing a Node", - "uri":"css_03_0090.html", - "doc_type":"api", - "p_code":"11", - "code":"33" - }, - { - "desc":"This API is used to change the security mode of a cluster.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/", - "product_code":"css", - "title":"Changing the Security Mode", - "uri":"css_03_0091.html", - "doc_type":"api", - "p_code":"11", - "code":"34" - }, - { - "desc":"This API is used to change the security group after a cluster is created.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/cluster", - "product_code":"css", - "title":"Changing the Security Group", - "uri":"css_03_0092.html", - "doc_type":"api", - "p_code":"11", - "code":"35" - }, - { - "desc":"This API is used to upgrade Elasticsearch from an earlier version to a later version or the same version.For details, see Calling APIs.POST /v1.0/{project_id}/clusters/{c", + "desc":"This API is used to upgrade Elasticsearch from an earlier version to a later version or the same version.POST /v1.0/{project_id}/clusters/{cluster_id}/inst-type/{inst_typ", "product_code":"css", "title":"Upgrading a Cluster Kernel", "uri":"UpgradeCore.html", "doc_type":"api", - "p_code":"11", - "code":"36" + "p_code":"8", + "code":"32" }, { - "desc":"This API is used to obtain the ID of an image that can be upgraded in the current cluster.For details, see Calling APIs.GET /v1.0/{project_id}/clusters/{cluster_id}/targe", + "desc":"This API is used to obtain the ID of an image that can be upgraded in the current cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/target/{upgrade_type}/imagesNoneSta", "product_code":"css", "title":"Obtaining a Target Image ID", "uri":"ListImages.html", "doc_type":"api", - "p_code":"11", - "code":"37" + "p_code":"8", + "code":"33" }, { - "desc":"The upgrade takes a long time. You can call this API to check the upgrade progress on a node.For details, see Calling APIs.GET /v1.0/{project_id}/clusters/{cluster_id}/up", + "desc":"The upgrade takes a long time. You can call this API to check the upgrade progress on a node.GET /v1.0/{project_id}/clusters/{cluster_id}/upgrade/detailNoneStatus code: 2", "product_code":"css", "title":"Obtaining Upgrade Details", "uri":"UpgradeDetail.html", "doc_type":"api", - "p_code":"11", - "code":"38" + "p_code":"8", + "code":"34" }, { - "desc":"The upgrade takes a long time and the upgrade may fail due to network problems. You can use this API to retry a task or terminate the impact of a task.For details, see Ca", + "desc":"The upgrade may fail due to network problems. In this case, you can call this API to retry.PUT /v1.0/{project_id}/clusters/{cluster_id}/upgrade/{action_id}/retryNoneNoneE", "product_code":"css", "title":"Retrying a Failed Upgrade Task", "uri":"RetryUpgradeTask.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", + "code":"35" + }, + { + "desc":"This API is used to change the security group after a cluster is created.POST /v1.0/{project_id}/clusters/{cluster_id}/sg/changeNoneChange the security group that the cur", + "product_code":"css", + "title":"Changing the Security Group", + "uri":"ChangeSecurityGroup.html", + "doc_type":"api", + "p_code":"8", + "code":"36" + }, + { + "desc":"This API is used to change the AZ by specifying node types.POST /v1.0/{project_id}/clusters/{cluster_id}/inst-type/{inst_type}/azmigrateNoneSwitch the AZ of the current c", + "product_code":"css", + "title":"Changing the AZ of a Cluster Instance", + "uri":"UpdateAzByInstanceType.html", + "doc_type":"api", + "p_code":"8", + "code":"37" + }, + { + "desc":"This API is used to create a cluster with multiple node types (for example, ess, ess-cold, ess-client, ess-master).POST /v2.0/{project_id}/clustersStatus code: 200Example", + "product_code":"css", + "title":"Creating a Cluster (V2)", + "uri":"CreateClusterMultiRole.html", + "doc_type":"api", + "p_code":"8", + "code":"38" + }, + { + "desc":"This API is used to restart nodes of all node types or the combination of some node types in the current cluster.POST /v2.0/{project_id}/clusters/{cluster_id}/restartNone", + "product_code":"css", + "title":"Restarting a Cluster (V2)", + "uri":"RestartClusterMultiRole.html", + "doc_type":"api", + "p_code":"8", "code":"39" }, { - "desc":"This API is used to add master and client nodes to a cluster.For details, see Calling APIs.POST /v1.0/{project_id}/clusters/{cluster_id}/type/{type}/independentStatus cod", + "desc":"This API is used to restart nodes one by one, which requires a long time when the nodes have a large number of indexes.POST /v2.0/{project_id}/clusters/{cluster_id}/rolli", "product_code":"css", - "title":"Adding Master and Client Nodes", - "uri":"AddIndependentNode.html", + "title":"Rolling Restart", + "uri":"RollingRestart.html", "doc_type":"api", - "p_code":"11", + "p_code":"8", "code":"40" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", "title":"Kibana Public Network Access", - "uri":"css_03_0119.html", + "uri":"kibana_public_network_access.html", "doc_type":"api", - "p_code":"", + "p_code":"7", "code":"41" }, { - "desc":"This API is used to enable Kibana public network access.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/pu", + "desc":"This API is used to enable public network access to Kibana.POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/openNoneNoneSee Error Codes.", "product_code":"css", "title":"Enabling Kibana Public Access", - "uri":"css_03_0120.html", + "uri":"StartKibanaPublic.html", "doc_type":"api", "p_code":"41", "code":"42" }, { - "desc":"This API is used to disable Kibana public network access.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/pu", + "desc":"This API is used to disable public network access to Kibana.Yearly/Monthly clusters cannot disable public access using APIs.PUT /v1.0/{project_id}/clusters/{cluster_id}/p", "product_code":"css", "title":"Disabling Kibana Public Access", - "uri":"css_03_0121.html", + "uri":"UpdateCloseKibana.html", "doc_type":"api", "p_code":"41", "code":"43" }, { - "desc":"This API is used to modify the Kibana public network bandwidth.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster", + "desc":"This API is used to modify the public network bandwidth of Kibana.POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/bandwidthNoneModify the Kibana public network", "product_code":"css", "title":"Modifying the Kibana Public Network Bandwidth", - "uri":"css_03_0122.html", + "uri":"UpdateAlterKibana.html", "doc_type":"api", "p_code":"41", "code":"44" }, { - "desc":"This API is used to modify the Kibana public network access whitelist.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{", + "desc":"This API is used to modify the Kibana access permission by modifying the Kibana whitelist.POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/updateNoneT", "product_code":"css", "title":"Modifying Kibana Public Access Control", - "uri":"css_03_0123.html", + "uri":"UpdatePublicKibanaWhitelist.html", "doc_type":"api", "p_code":"41", "code":"45" }, { - "desc":"This API is used to disable the Kibana public network access control.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cl", + "desc":"This API is used to disable public network access control for Kibana.PUT /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/closeNoneNoneNoneNoneSee Error Co", "product_code":"css", "title":"Disabling Kibana Public Network Access Control", - "uri":"css_03_0124.html", + "uri":"StopPublicKibanaWhitelist.html", "doc_type":"api", "p_code":"41", "code":"46" @@ -417,438 +417,438 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", "title":"Log Management", - "uri":"css_03_0093.html", + "uri":"log_management.html", "doc_type":"api", - "p_code":"", + "p_code":"7", "code":"47" }, { - "desc":"This API is used to enable the log function.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/openNoneN", + "desc":"This API is used to enable the log function.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/openNoneEnable the log function.POST /v1.0/6204a5bd270343b5885144cf9c8c158d", "product_code":"css", "title":"Enabling the Log Function", - "uri":"css_03_0094.html", + "uri":"StartLogs.html", "doc_type":"api", "p_code":"47", "code":"48" }, { - "desc":"This API is used to disable the log function.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/closeNone", + "desc":"This API is used to disable the log function.PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/closeNoneNoneNoneNoneSee Error Codes.", "product_code":"css", "title":"Disabling the Log Function", - "uri":"css_03_0095.html", + "uri":"StopLogs.html", "doc_type":"api", "p_code":"47", "code":"49" }, { - "desc":"This API is used to query the job list in the logs of a cluster.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster", + "desc":"This API is used to query the job list in the logs of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/logs/recordsNoneStatus code: 200NoneStatus code: 200Request s", "product_code":"css", - "title":"Viewing the Job List", - "uri":"css_03_0096.html", + "title":"Querying the Job List", + "uri":"ListLogsJob.html", "doc_type":"api", "p_code":"47", "code":"50" }, { - "desc":"This API is used to query basic log configurations.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster_id}/logs/set", + "desc":"This API is used to query basic log configurations.GET /v1.0/{project_id}/clusters/{cluster_id}/logs/settingsNoneStatus code: 200NoneStatus code: 200Request succeeded.Exa", "product_code":"css", "title":"Querying Basic Log Configurations", - "uri":"css_03_0097.html", + "uri":"ShowGetLogSetting.html", "doc_type":"api", "p_code":"47", "code":"51" }, { - "desc":"This API is used to modify basic log configurations.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/s", + "desc":"This API is used to modify basic log configurations.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/settingsNoneModify basic log configurations.POST /v1.0/6204a5bd2703", "product_code":"css", "title":"Modifying Basic Log Configurations", - "uri":"css_03_0098.html", + "uri":"UpdateLogSetting.html", "doc_type":"api", "p_code":"47", "code":"52" }, { - "desc":"This API is used to enable the automatic log backup policy.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}", + "desc":"This API is used to enable the automatic log backup policy.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/updateNoneEnable the automatic log backup policy.None", "product_code":"css", "title":"Enabling the Automatic Log Backup Policy", - "uri":"css_03_0099.html", + "uri":"StartLogAutoBackupPolicy.html", "doc_type":"api", "p_code":"47", "code":"53" }, { - "desc":"This API is used to disable the automatic log backup policy.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}", + "desc":"This API is used to disable the automatic log backup policy.PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/closeNoneNoneNoneNoneSee Error Codes.", "product_code":"css", "title":"Disabling the Automatic Log Backup Policy", - "uri":"css_03_0100.html", + "uri":"StopLogAutoBackupPolicy.html", "doc_type":"api", "p_code":"47", "code":"54" }, { - "desc":"This API is used to back up logs.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/collectNoneNoneNoneN", + "desc":"This API is used to back up logs.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/collectNoneNoneNoneNoneSee Error Codes.", "product_code":"css", "title":"Backing Up Logs", - "uri":"css_03_0101.html", + "uri":"CreateLogBackup.html", "doc_type":"api", "p_code":"47", "code":"55" }, { - "desc":"This API is used to query log information.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/searchStatu", + "desc":"This API is used to query log information.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/searchStatus code: 200Query logs.Status code: 200Request succeeded.See Error ", "product_code":"css", - "title":"Querying Logs", - "uri":"css_03_0102.html", + "title":"Searching for Logs", + "uri":"ShowLogBackup.html", "doc_type":"api", "p_code":"47", "code":"56" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"This API is used to test connectivity.POST /v1.0/{project_id}/clusters/{cluster_id}/logs/connectivityNoneTest connectivity to the target cluster.Status code: 200Request s", "product_code":"css", - "title":"Public Network Access", - "uri":"css_03_0103.html", + "title":"Test connectivity.", + "uri":"StartTargetClusterConnectivityTest.html", "doc_type":"api", - "p_code":"", + "p_code":"47", "code":"57" }, { - "desc":"This API is used to enable public network access.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/public/op", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", - "title":"Enabling Public Network Access", - "uri":"css_03_0104.html", + "title":"Public Network Access", + "uri":"public_network_access.html", "doc_type":"api", - "p_code":"57", + "p_code":"7", "code":"58" }, { - "desc":"This API is used to disable public network access.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/public/cl", + "desc":"This API is used to enable public network access.POST /v1.0/{project_id}/clusters/{cluster_id}/public/openStatus code: 200Status code: 200Request succeeded.See Error Code", "product_code":"css", - "title":"Disabling Public Network Access", - "uri":"css_03_0105.html", + "title":"Enabling Public Network Access", + "uri":"CreateBindPublic.html", "doc_type":"api", - "p_code":"57", + "p_code":"58", "code":"59" }, { - "desc":"This API is used to modify the public network access bandwidth.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster", + "desc":"This API is used to disable public network access to Kibana.Yearly/Monthly clusters cannot disable Kibana public access using APIs.PUT /v1.0/{project_id}/clusters/{cluste", "product_code":"css", - "title":"Modifying Public Network Access Bandwidth", - "uri":"css_03_0106.html", + "title":"Disabling Public Network Access", + "uri":"UpdateUnbindPublic.html", "doc_type":"api", - "p_code":"57", + "p_code":"58", "code":"60" }, { - "desc":"This API is used to enable the public network access whitelist.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster", + "desc":"This API is used to modify the public network access bandwidth.POST /v1.0/{project_id}/clusters/{cluster_id}/public/bandwidthNoneModify public network access bandwidth.No", "product_code":"css", - "title":"Enabling the Public Network Access Whitelist", - "uri":"css_03_0107.html", + "title":"Modifying Public Network Access Bandwidth", + "uri":"UpdatePublicBandWidth.html", "doc_type":"api", - "p_code":"57", + "p_code":"58", "code":"61" }, { - "desc":"This API is used to disable the public network access whitelist.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster", + "desc":"This API is used to enable the public network access control whitelist.POST /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/updateNoneEnable the public network ", "product_code":"css", - "title":"Disabling the Public Network Access Whitelist", - "uri":"css_03_0108.html", + "title":"Enabling the Public Network Access Control Whitelist", + "uri":"StartPublicWhitelist.html", "doc_type":"api", - "p_code":"57", + "p_code":"58", "code":"62" }, + { + "desc":"This API is used to disable the public network access control whitelist.PUT /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/closeNoneNoneNoneNoneSee Error Codes", + "product_code":"css", + "title":"Disabling the Public Network Access Control Whitelist", + "uri":"StopPublicWhitelist.html", + "doc_type":"api", + "p_code":"58", + "code":"63" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", - "title":"Snapshot Management APIs", - "uri":"css_03_0010.html", + "title":"Snapshot Management", + "uri":"snapshot_management.html", "doc_type":"api", - "p_code":"", - "code":"63" - }, - { - "desc":"The API for automatically configuring a cluster snapshot can automatically create OBS buckets and agencies for storing snapshots. If you have multiple clusters, an OBS bu", - "product_code":"css", - "title":"(Not Recommended) Automatically Configuring Basic Settings of a Cluster Snapshot", - "uri":"css_03_0037.html", - "doc_type":"api", - "p_code":"63", + "p_code":"7", "code":"64" }, { - "desc":"Using this API will automatically enable the snapshot function.This API is used to modify the basic configurations of a cluster snapshot. The basic configurations include", + "desc":"This API is used to automatically set basic configurations for a cluster snapshot, including configuring OBS buckets and IAM agency.OBS Bucket: Enter the location of the ", "product_code":"css", - "title":"Modifying Basic Configurations of a Cluster Snapshot", - "uri":"css_03_0030.html", + "title":"(Not Recommended) Automatically Setting Basic Configurations of a Cluster Snapshot", + "uri":"StartAutoSetting.html", "doc_type":"api", - "p_code":"63", + "p_code":"64", "code":"65" }, { - "desc":"This API is used to set parameters related to automatic snapshot creation. By default, a snapshot is created per day.Table 2 describes the request parameters.NoneExample ", + "desc":"This API is used to modify the basic configurations for a cluster snapshot, including OBS buckets and IAM agency.You can also use this API to enable the snapshot function", "product_code":"css", - "title":"Setting the Automatic Snapshot Creation Policy", - "uri":"css_03_0031.html", + "title":"Modifying Basic Configurations of a Cluster Snapshot", + "uri":"UpdateSnapshotSetting.html", "doc_type":"api", - "p_code":"63", + "p_code":"64", "code":"66" }, { - "desc":"This API is used to query the automatic snapshot creation policy for a cluster.NoneTable 2 describes the response parameters.Example requestExample responseTable 3 descri", + "desc":"This API is used to manually create a snapshot.POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshotStatus code: 201Create a snapshot.Status code: 201Resource crea", "product_code":"css", - "title":"Querying the Automatic Snapshot Creation Policy for a Cluster", - "uri":"css_03_0032.html", + "title":"Manually Creating a Snapshot", + "uri":"CreateSnapshot.html", "doc_type":"api", - "p_code":"63", + "p_code":"64", "code":"67" }, { - "desc":"This API is used to manually create a snapshot.Table 2 describes the request parameters.Table 3 describes the response parameters.Example requestExample responseTable 5 d", + "desc":"This API is used to manually restore a snapshot.POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}/restoreNoneRestore a snapshot.NoneSee Error Cod", "product_code":"css", - "title":"Manually Creating a Snapshot", - "uri":"css_03_0033.html", + "title":"Restoring a Snapshot", + "uri":"RestoreSnapshot.html", "doc_type":"api", - "p_code":"63", + "p_code":"64", "code":"68" }, { - "desc":"This API is used to query all snapshots of a cluster.NoneExample requestExample responseTable 5 describes the status code.", + "desc":"This API is used to delete a snapshot.DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}NoneNoneNoneNoneSee Error Codes.", "product_code":"css", - "title":"Querying the List of Snapshots", - "uri":"css_03_0034.html", + "title":"Deleting a Snapshot", + "uri":"DeleteSnapshot.html", "doc_type":"api", - "p_code":"63", + "p_code":"64", "code":"69" }, { - "desc":"This API is used to manually restore a snapshot.Table 2 describes the request parameters.NoneExample requestExample responseThe return value is empty.Table 3 describes th", + "desc":"This API is used to configure automatic snapshot creation. By default, a snapshot is created every day.POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy", "product_code":"css", - "title":"Restoring a Snapshot", - "uri":"css_03_0035.html", + "title":"Configuring the Automatic Snapshot Creation Policy", + "uri":"CreateAutoCreatePolicy.html", "doc_type":"api", - "p_code":"63", + "p_code":"64", "code":"70" }, { - "desc":"This API is used to delete a snapshot.NoneNoneExample requestTable 2 describes the status code.", + "desc":"This API is used to query the automatic snapshot creation policy.GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policyNoneStatus code: 200NoneStatus code: 20", "product_code":"css", - "title":"Deleting a Snapshot", - "uri":"css_03_0036.html", + "title":"Querying the Automatic Snapshot Creation Policy", + "uri":"ShowAutoCreatePolicy.html", "doc_type":"api", - "p_code":"63", + "p_code":"64", "code":"71" }, { - "desc":"This API is used to disable the snapshot function.NoneNoneExample requestTable 2 describes the status code.", + "desc":"This API is used to query all the snapshots of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshotsNoneStatus code: 200NoneStatus code: 200Request succe", + "product_code":"css", + "title":"Querying a Snapshot List", + "uri":"ListSnapshots.html", + "doc_type":"api", + "p_code":"64", + "code":"72" + }, + { + "desc":"This API is used to disable the snapshot function.DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshotsNoneNoneNoneNoneSee Error Codes.", "product_code":"css", "title":"Disabling the Snapshot Function", - "uri":"css_03_0039.html", + "uri":"StopSnapshot.html", "doc_type":"api", - "p_code":"63", - "code":"72" + "p_code":"64", + "code":"73" + }, + { + "desc":"This API is used to enable the automatic snapshot creation function.POST /v2.0/{project_id}/clusters/{cluster_id}/snapshots/policy/openNoneEnable the automatic backup fun", + "product_code":"css", + "title":"Enabling Automatic Snapshot Creation", + "uri":"StartAutoCreateSnapshots.html", + "doc_type":"api", + "p_code":"64", + "code":"74" + }, + { + "desc":"This API is used to disable the automatic snapshot creation function.PUT /v2.0/{project_id}/clusters/{cluster_id}/snapshots/policy/closeNoneNoneDisable the automatic back", + "product_code":"css", + "title":"Disabling Automatic Snapshot Creation", + "uri":"StopAutoCreateSnapshots.html", + "doc_type":"api", + "p_code":"64", + "code":"75" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", "title":"VPC Endpoint", - "uri":"css_03_0109.html", + "uri":"vpecp_management.html", "doc_type":"api", - "p_code":"", - "code":"73" - }, - { - "desc":"This API is used to enable the VPC endpoint service.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/vpceps", - "product_code":"css", - "title":"Enabling the VPC Endpoint Service", - "uri":"css_03_0110.html", - "doc_type":"api", - "p_code":"73", - "code":"74" - }, - { - "desc":"This API is used to disable the VPC endpoint service.You can debug this API in . Automatic authentication is supported.PUT /v1.0/{project_id}/clusters/{cluster_id}/vpceps", - "product_code":"css", - "title":"Disabling the VPC Endpoint Service", - "uri":"css_03_0111.html", - "doc_type":"api", - "p_code":"73", - "code":"75" - }, - { - "desc":"This API is used to obtain a VPC endpoint connection.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cluster_id}/vpceps", - "product_code":"css", - "title":"Obtaining a VPC Endpoint Connection", - "uri":"css_03_0112.html", - "doc_type":"api", - "p_code":"73", + "p_code":"7", "code":"76" }, { - "desc":"This API is used to update a VPC endpoint connection.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcep", + "desc":"This API is used to enable the VPC endpoint service.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/openStatus code: 200Enable the VPC endpoint service.Status ", "product_code":"css", - "title":"Updating a VPC Endpoint Connection", - "uri":"css_03_0113.html", + "title":"Enabling the VPC Endpoint Service", + "uri":"StartVpecp.html", "doc_type":"api", - "p_code":"73", + "p_code":"76", "code":"77" }, { - "desc":"This API is used to modify the endpoint service whitelist.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/", + "desc":"This API is used to disable the VPC endpoint service.PUT /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/closeNoneStatus code: 200NoneStatus code: 200Request succee", + "product_code":"css", + "title":"Disabling the VPC Endpoint Service", + "uri":"StopVpecp.html", + "doc_type":"api", + "p_code":"76", + "code":"78" + }, + { + "desc":"This API is used to obtain a VPC endpoint connection.GET /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connectionsNoneStatus code: 200NoneStatus code: 200Request ", + "product_code":"css", + "title":"Obtaining an Endpoint Connection", + "uri":"ShowVpcepConnection.html", + "doc_type":"api", + "p_code":"76", + "code":"79" + }, + { + "desc":"This API is used to update an endpoint connection.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connectionsNoneUpdate an endpoint connection.NoneSee Error Co", + "product_code":"css", + "title":"Updating an Endpoint Connection", + "uri":"UpdateVpcepConnection.html", + "doc_type":"api", + "p_code":"76", + "code":"80" + }, + { + "desc":"This API is used to modify the endpoint service whitelist.POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/permissionsNoneModify the endpoint service whitelist.", "product_code":"css", "title":"Modifying the Endpoint Service Whitelist", - "uri":"css_03_0114.html", + "uri":"UpdateVpcepWhitelist.html", "doc_type":"api", - "p_code":"73", - "code":"78" + "p_code":"76", + "code":"81" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", "title":"Parameter Configuration", - "uri":"css_03_0115.html", + "uri":"ymls_management.html", "doc_type":"api", - "p_code":"", - "code":"79" + "p_code":"7", + "code":"82" }, { - "desc":"This API is used to modify parameter configurations.You can debug this API in . Automatic authentication is supported.POST /v1.0/{project_id}/clusters/{cluster_id}/ymls/u", + "desc":"This API is used to modify the parameter settings of a cluster.POST /v1.0/{project_id}/clusters/{cluster_id}/ymls/updateStatus code: 200Modify parameter settings.Status c", "product_code":"css", - "title":"Modifying Parameter Configurations", - "uri":"css_03_0116.html", + "title":"Modifying Cluster Parameters", + "uri":"UpdateYmls.html", "doc_type":"api", - "p_code":"79", - "code":"80" + "p_code":"82", + "code":"83" }, { - "desc":"This API is used to obtain the task list of parameter configurations.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id}/clusters/{cl", + "desc":"This API is used to obtain the parameter configuration task list of a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/joblistsNoneStatus code: 200NoneStatus cod", "product_code":"css", "title":"Obtaining the Task List of Parameter Configurations", - "uri":"css_03_0117.html", + "uri":"ListYmlsJob.html", "doc_type":"api", - "p_code":"79", - "code":"81" + "p_code":"82", + "code":"84" }, { - "desc":"This API is used to obtain the parameter configuration list of the current cluster.You can debug this API in . Automatic authentication is supported.GET /v1.0/{project_id", + "desc":"This API is used to obtain the parameter configuration list of the current cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/templateNoneStatus code: 200NoneStatu", "product_code":"css", "title":"Obtaining the Parameter Configuration List", - "uri":"css_03_0118.html", + "uri":"ListYmls.html", "doc_type":"api", - "p_code":"79", - "code":"82" + "p_code":"82", + "code":"85" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", "title":"Load Balancing", - "uri":"css_03_0125.html", + "uri":"topic_300000010.html", "doc_type":"api", - "p_code":"", - "code":"83" - }, - { - "desc":"This API is used to query the ELB V3 load balancers supported by a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/loadbalancersNoneStatus code: 200NoneStatus code: ", - "product_code":"css", - "title":"Querying ELB V3 Load Balancer Supported by a Cluster", - "uri":"css_03_0126.html", - "doc_type":"api", - "p_code":"83", - "code":"84" - }, - { - "desc":"This API is used to enable or disable the ES load balancer.POST /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers/es-switchStatus code: 200Enable the load balancer.N", - "product_code":"css", - "title":"Enabling or Disabling the ES Load Balancer", - "uri":"css_03_0127.html", - "doc_type":"api", - "p_code":"83", - "code":"85" - }, - { - "desc":"This API is used to configure the ES listener.POST /v1.0/{project_id}/clusters/{cluster_id}/es-listenersStatus code: 200Status code: 200The request is processed.See Error", - "product_code":"css", - "title":"Configuring the ES Listener", - "uri":"css_03_0128.html", - "doc_type":"api", - "p_code":"83", + "p_code":"7", "code":"86" }, { - "desc":"This API is used to obtain the ES ELB information and health check status.GET /v1.0/{project_id}/clusters/{cluster_id}/es-listenersNoneStatus code: 200NoneStatus code: 20", + "desc":"This API is used to query the ELBv3 load balancers supported by a cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/loadbalancersNoneStatus code: 200NoneStatus code: 2", "product_code":"css", - "title":"Obtaining the ELB Information and Health Check Status", - "uri":"css_03_0129.html", + "title":"Querying ELBv3 Load Balancers Supported by a Cluster", + "uri":"ListElbs.html", "doc_type":"api", - "p_code":"83", + "p_code":"86", "code":"87" }, { - "desc":"This API is used to update an ES listener.PUT /v1.0/{project_id}/clusters/{cluster_id}/es-listeners/{listener_id}Status code: 200NoneSee Error Codes.", + "desc":"This API is used to enable or disable the Elasticsearch load balancer.POST /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers/es-switchStatus code: 200Enable the load", "product_code":"css", - "title":"Updating an ES Listener", - "uri":"css_03_0130.html", + "title":"Enabling or Disabling the Elasticsearch Load Balancer", + "uri":"EnableOrDisableElb.html", "doc_type":"api", - "p_code":"83", + "p_code":"86", "code":"88" }, { - "desc":"This API is used to query the certificate list.GET /v1.0/{project_id}/clusters/{cluster_id}/elb/certificatesNoneStatus code: 200NoneStatus code: 200The request is process", + "desc":"This API is used to configure the Elasticsearch listener.POST /v1.0/{project_id}/clusters/{cluster_id}/es-listenersStatus code: 200Status code: 200Request succeeded.See E", + "product_code":"css", + "title":"Configuring the Elasticsearch Listener", + "uri":"CreateElbListener.html", + "doc_type":"api", + "p_code":"86", + "code":"89" + }, + { + "desc":"This API is used to obtain the ELB information and health check status of an Elasticsearch cluster.GET /v1.0/{project_id}/clusters/{cluster_id}/es-listenersNoneStatus cod", + "product_code":"css", + "title":"Obtaining the ES ELB Information and Displaying the Health Check Status", + "uri":"ShowElbDetail.html", + "doc_type":"api", + "p_code":"86", + "code":"90" + }, + { + "desc":"This API is used to update an Elasticsearch listener.PUT /v1.0/{project_id}/clusters/{cluster_id}/es-listeners/{listener_id}Status code: 200Status code: 200Request succee", + "product_code":"css", + "title":"Updating an Elasticsearch Listener", + "uri":"UpdateESListener.html", + "doc_type":"api", + "p_code":"86", + "code":"91" + }, + { + "desc":"This API is used to query the certificate list.GET /v1.0/{project_id}/clusters/{cluster_id}/elb/certificatesNoneStatus code: 200NoneStatus code: 200Request succeeded.See ", "product_code":"css", "title":"Querying the Certificate List", - "uri":"css_03_0131.html", + "uri":"ListElbCerts.html", "doc_type":"api", - "p_code":"83", - "code":"89" + "p_code":"86", + "code":"92" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", - "title":"Intelligent O&M", - "uri":"css_03_0132.html", + "title":"Examples", + "uri":"en-us_topic_0000002083557490.html", "doc_type":"api", "p_code":"", - "code":"90" - }, - { - "desc":"This API is used to create a cluster detection task.POST /v1.0/{project_id}/clusters/{cluster_id}/ai-opsNoneCreate a cluster detection task.NoneFor details, see Error Cod", - "product_code":"css", - "title":"Creating a Cluster Detection Task", - "uri":"css_03_0133.html", - "doc_type":"api", - "p_code":"90", - "code":"91" - }, - { - "desc":"This API is used to obtain the intelligent O&M task list and details.GET /v1.0/{project_id}/clusters/{cluster_id}/ai-opsNoneStatus code: 200Obtain the intelligent O&M tas", - "product_code":"css", - "title":"Obtaining the Intelligent O&M Task List and Details", - "uri":"css_03_0134.html", - "doc_type":"api", - "p_code":"90", - "code":"92" - }, - { - "desc":"This API is used to delete a detection task record.DELETE /v1.0/{project_id}/clusters/{cluster_id}/ai-ops/{aiops_id}NoneNoneDelete a detection task record.NoneFor details", - "product_code":"css", - "title":"Deleting a Detection Task Record", - "uri":"css_03_0135.html", - "doc_type":"api", - "p_code":"90", "code":"93" }, { - "desc":"This API is used to obtain SMN topics available for intelligent O&M alarms.GET /v1.0/{project_id}/domains/{domain_id}/ai-ops/smn-topicsNoneStatus code: 200Obtain the inte", + "desc":"This section describes how to create a CSS cluster by using APIs. Figure 1 illustrates the API calling process.The token obtained on IAM is valid for only 24 hours. If yo", "product_code":"css", - "title":"Obtaining SMN Topics Available for Intelligent O&M Alarms", - "uri":"css_03_0136.html", + "title":"Creating a Pay-per-Use Elasticsearch Cluster", + "uri":"css_03_0062.html", "doc_type":"api", - "p_code":"90", + "p_code":"93", "code":"94" }, { - "desc":"This section describes fine-grained permissions management for your CSS. If your cloud account does not need individual IAM users, then you may skip over this chapter.By ", + "desc":"This section describes fine-grained permissions management for your CSS. If your account does not need individual IAM users, then you may skip over this chapter.By defaul", "product_code":"css", - "title":"Permissions Policies and Supported Actions", + "title":"Permissions and Supported Actions", "uri":"css_03_0065.html", "doc_type":"api", "p_code":"", @@ -857,35 +857,35 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", - "title":"Common Parameters", + "title":"Appendixes", "uri":"css_03_0040.html", "doc_type":"api", "p_code":"", "code":"96" }, { - "desc":"A project ID or project name is required in some API requests. You need to obtain the project ID and name before calling an API.Log in to the console.In the upper right c", + "desc":"Table 1 describes the status codes.", "product_code":"css", - "title":"Obtaining a Project ID and Name", - "uri":"css_03_0071.html", + "title":"Status Codes", + "uri":"css_03_0075.html", "doc_type":"api", "p_code":"96", "code":"97" }, { - "desc":"Table 1 describes the status code.", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"css", - "title":"Status Code", - "uri":"css_03_0075.html", + "title":"Error Codes", + "uri":"css_03_0076.html", "doc_type":"api", "p_code":"96", "code":"98" }, { - "desc":"No data is returned if an API fails to be invoked. You can locate the cause of an error according to the error code of each API. When the API calling fails, HTTPS status ", + "desc":"A project ID or project name is required in some API requests. You need to obtain the project ID and name before calling an API.Log in to the console.In the upper right c", "product_code":"css", - "title":"Error Code", - "uri":"css_03_0076.html", + "title":"Obtaining a Project ID and Name", + "uri":"css_03_0071.html", "doc_type":"api", "p_code":"96", "code":"99" diff --git a/docs/css/api-ref/ChangeMode.html b/docs/css/api-ref/ChangeMode.html new file mode 100644 index 00000000..2d0aa69e --- /dev/null +++ b/docs/css/api-ref/ChangeMode.html @@ -0,0 +1,139 @@ + + +

Configuring the Security Mode.

+

Function

This API is used to configure the security mode of a cluster.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/mode/change

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

Cluster ID.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

authorityEnable

+

Yes

+

Boolean

+

Security mode. Its value can be:

+
  • true: enabled

    +
  • false: disabled

    +

    Default value: true

    +
+

adminPwd

+

No

+

String

+

Cluster password in security mode.

+

httpsEnable

+

Yes

+

Boolean

+

Enable HTTPS. Its value can be:

+
  • true: enabled

    +
  • false: disabled

    +

    Default value: true

    +
+
+
+
+

Response Parameters

None

+
+

Example Requests

Change the security mode of the current cluster.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/mode/change
+
+{
+  "authorityEnable" : true,
+  "adminPwd" : "admin@1234",
+  "httpsEnable" : true
+}
+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

404

+

The requested resource could not be found.

+

Modify the request before retry.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ChangeSecurityGroup.html b/docs/css/api-ref/ChangeSecurityGroup.html new file mode 100644 index 00000000..c2f80004 --- /dev/null +++ b/docs/css/api-ref/ChangeSecurityGroup.html @@ -0,0 +1,110 @@ + + +

Changing the Security Group

+

Function

This API is used to change the security group after a cluster is created.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/sg/change

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

Cluster ID.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

security_group_ids

+

Yes

+

String

+

Security group ID.

+
+
+
+

Response Parameters

None

+
+

Example Requests

Change the security group that the current cluster belongs to.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/sg/change
+
+{
+  "security_group_ids" : "b1038649-1f77-4ae9-b64d-9af56e422652"
+}
+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

The client should not repeat the request without modifications.

+

403

+

Request rejected.The server has received the request and understood it, but refused to respond to it. The client should not repeat the request without modifications.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateAutoCreatePolicy.html b/docs/css/api-ref/CreateAutoCreatePolicy.html new file mode 100644 index 00000000..cc7fd6fe --- /dev/null +++ b/docs/css/api-ref/CreateAutoCreatePolicy.html @@ -0,0 +1,175 @@ + + +

Configuring the Automatic Snapshot Creation Policy

+

Function

This API is used to configure automatic snapshot creation. By default, a snapshot is created every day.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster for which you want to create snapshots automatically.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

indices

+

No

+

String

+

Name of the index to be backed up. * indicates all indexes.

+

prefix

+

No

+

String

+

Prefix of a snapshot that is automatically created, which is manually entered.

+

Enter up to 32 characters and start with a lowercase letter. Lowercase letters, digits, hyphens (-), and underscores (_) are allowed.

+
NOTE:

This parameter is mandatory when enable is set to true.

+
+

period

+

No

+

String

+

Time when a snapshot is generated every day. Snapshots can only be generated on the hour. The format is HH:mm z: HH:mm refers to the hour time and z refers to the time zone. For example, 00:00 GMT+08:00 and 01:00 GMT+08:00.

+
NOTE:

The default value is 00:00 GMT+08:00. When frequency is set to HOUR, you do not need to specify period. By default, snapshot creation starts from the next hour after the settings are successful. This parameter is mandatory when enable is set to true.

+
+

keepday

+

No

+

Integer

+

Set the number of retained snapshots. The value ranges from 1 to 90. Expired snapshots will be automatically deleted on the half hour. The deletion policy applies only to automated snapshots that are executed at the same frequency as the current automatic snapshot creation policy.

+
NOTE:

This parameter is mandatory when enable is set to true.

+
+

enable

+

Yes

+

String

+

Whether to enable the automatic snapshot creation policy.

+
  • true: The automatic snapshot creation policy is enabled.

    +
  • false:The automatic snapshot creation policy is disabled, and other parameters do not need to be delivered.

    +
+

deleteAuto

+

No

+

String

+

Whether to clear all the automatically created snapshots when the automatic snapshot creation policy is disabled. The default value is false, indicating that automatically created snapshots will not be deleted. If this parameter is set to true, all created snapshots will be deleted when the automatic snapshot creation policy is disabled.

+

frequency

+

No

+

String

+

Frequency of automatically creating snapshots.

+
NOTE:

The default value is DAY. If this parameter is set to HOUR, the scheduled task is executed every hour. If this parameter is set to DAY, the scheduled task is executed every day. If this parameter is set to SUN, MON, TUE, WED, THU, FRI or SAT, the scheduled task is executed at the specified day of every week. For example, SUN indicates that the task is executed once every Sunday. The number of retained snapshots depends on the execution frequency and indexes set in the automatic snapshot creation policy. If the execution interval is short or the index data volume is large, the number of retained automatic snapshots may not reach the preset value. Set this value based on actual conditions.

+
+
+
+
+

Response Parameters

None

+
+

Example Requests

Configure the automatic snapshot creation policy.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/index_snapshot/policy
+
+{
+  "prefix" : "snapshot",
+  "period" : "16:00 GMT+08:00",
+  "keepday" : 7,
+  "frequency" : "DAY",
+  "enable" : "true",
+  "deleteAuto" : "false"
+}
+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

406

+

The server could not fulfill the request according to the content characteristics of the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateBindPublic.html b/docs/css/api-ref/CreateBindPublic.html new file mode 100644 index 00000000..ee02f855 --- /dev/null +++ b/docs/css/api-ref/CreateBindPublic.html @@ -0,0 +1,186 @@ + + +

Enabling Public Network Access

+

Function

This API is used to enable public network access.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/public/open

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster whose public network access you want to enable.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

eip

+

Yes

+

BindPublicReqEip object

+

EIP information.

+
+
+ +
+ + + + + + + + + + + +
Table 3 BindPublicReqEip

Parameter

+

Mandatory

+

Type

+

Description

+

bandWidth

+

Yes

+

BindPublicReqEipBandWidth object

+

Public network bandwidth.

+
+
+ +
+ + + + + + + + + + + +
Table 4 BindPublicReqEipBandWidth

Parameter

+

Mandatory

+

Type

+

Description

+

size

+

Yes

+

Integer

+

Bandwidth range. Unit: Mbit/s

+
+
+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 5 Response body parameters

Parameter

+

Type

+

Description

+

action

+

String

+

Operations. The fixed value is bindZone, indicating that the binding is successful.

+
+
+
+

Example Requests

{
+  "eip" : {
+    "bandWidth" : {
+      "size" : 5
+    }
+  }
+}
+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "action" : "bindZone"
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateCluster.html b/docs/css/api-ref/CreateCluster.html new file mode 100644 index 00000000..5e330fde --- /dev/null +++ b/docs/css/api-ref/CreateCluster.html @@ -0,0 +1,616 @@ + + +

Creating a cluster

+

Function

This API is used to create a cluster.

+
+

URI

POST /v1.0/{project_id}/clusters

+ +
+ + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

cluster

+

Yes

+

CreateClusterBody object

+

Cluster object.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 CreateClusterBody

Parameter

+

Mandatory

+

Type

+

Description

+

instance

+

Yes

+

CreateClusterInstanceBody object

+

Instance.

+

datastore

+

Yes

+

CreateClusterDatastoreBody object

+

Search engine.

+

name

+

Yes

+

String

+

Cluster name It can contain 4 to 32 characters. Only digits, letters, hyphens (-), and underscores (_) are allowed. The value must start with a letter.

+

instanceNum

+

Yes

+

Integer

+

Number of clusters. The value range is 1 to 32.

+

backupStrategy

+

No

+

CreateClusterBackupStrategyBody object

+

Automatic snapshot creation policy, which is disabled by default.

+

The automatic snapshot creation policy is enabled only if backupStrategy is not left blank.

+

httpsEnable

+

No

+

Boolean

+

Whether communication is encrypted on the cluster. The value can be true or false. By default, communication encryption is disabled. If httpsEnable is set to true, authorityEnable must be set to true.

+
  • true: Communication is encrypted on the cluster.

    +
  • false: Communication is not encrypted on the cluster.

    +
+

This parameter is supported in clusters 6.5.4 or later.

+

authorityEnable

+

No

+

Boolean

+

Whether to enable authentication. The value can be true or false. Authentication is disabled by default.

+
  • true indicates that authentication is enabled for the cluster.

    +
  • true indicates that authentication is enabled for the cluster.

    +
+

This parameter is supported in clusters 6.5.4 or later.

+

adminPwd

+

No

+

String

+

Password of the cluster user admin in security mode. This parameter is mandatory only if authorityEnable is set to true.

+
  • The administrator password must meet the following requirements:

    +
    • The password can contain 8 to 32 characters.

      +
    • Passwords must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^&*()-_=+\|[{}];:,<.>/?).

      +
    +
  • Weak password verification is required for a security cluster. You are advised to set a strong password.

    +
+

enterprise_project_id

+

No

+

String

+

Enterprise project ID. When creating a cluster, associate the enterprise project ID with the cluster. The value can contain a maximum of 36 characters. It is string 0 or in UUID format with hyphens (-). Value 0 indicates the default enterprise project.

+

tags

+

No

+

Array of CreateClusterTagsBody objects

+

Cluster tag.

+

ipv6_enable

+

No

+

Boolean

+

Whether to enable automatic IPv6 address assignment for the cluster. The default value is false.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 CreateClusterInstanceBody

Parameter

+

Mandatory

+

Type

+

Description

+

flavorRef

+

Yes

+

String

+

Instance flavor. For details about the current instance flavor, see the name attribute in Obtaining the Instance Specifications List.

+

volume

+

Yes

+

CreateClusterInstanceVolumeBody object

+

Volume information. You do not need to set this parameter when flavorRef is set to a local disk flavor. Currently, the following local disk flavors are supported:

+
  • ess.spec-i3small

    +
  • ess.spec-i3medium

    +
  • ess.spec-i3.8xlarge.8

    +
  • ess.spec-ds.xlarge.8

    +
  • ess.spec-ds.2xlarge.8

    +
  • ess.spec-ds.4xlarge.8

    +
+

nics

+

Yes

+

CreateClusterInstanceNicsBody object

+

Subnet ID.

+

availability_zone

+

Yes

+

String

+

Availability zone (AZ). You need to specify the AZ name.

+

By default, a single AZ is specified. If multiple AZs are specified, use commas (,) to separate AZ names. Take CN North-Beijing4 as an example. If three AZs are selected, the value of availability_zone is cn-north-4a,cn-north-4b,cn-north-4c. If a single AZ is used, the value of availability_zone is empty by default.

+
NOTE:

NOTE

+

- If multiple AZs are selected, the name of each AZ must be unique, and the number of nodes must be greater than or equal to the number of AZs.

+

- If the number of nodes is a multiple of the number of AZs, the nodes are evenly distributed to each AZ.

+

- If the number of nodes is not a multiple of the number of AZs, the absolute difference between node quantity in any two AZs is 1 at most.

+
+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 5 CreateClusterInstanceVolumeBody

Parameter

+

Mandatory

+

Type

+

Description

+

volume_type

+

Yes

+

String

+

Volume type

+
  • COMMON: common I/O

    +
  • HIGH: high I/O

    +
  • ULTRAHIGH: ultra-high I/O

    +
  • ESSD: ultra-fast SSD

    +
+

size

+

Yes

+

Integer

+

Volume size. The value must be greater than 0 and a multiple of 4 and 10. For details about the local disk size, see the diskrange attribute in Obtaining the Instance Specifications List. Unit: GB

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 6 CreateClusterInstanceNicsBody

Parameter

+

Mandatory

+

Type

+

Description

+

vpcId

+

Yes

+

String

+

VPC ID, which is used for configuring cluster network.

+

netId

+

Yes

+

String

+

Subnet ID (network ID).

+

securityGroupId

+

Yes

+

String

+

Security group ID.

+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 7 CreateClusterDatastoreBody

Parameter

+

Mandatory

+

Type

+

Description

+

version

+

Yes

+

String

+

Elasticsearch/Logstash engine version. For details, see the supported versions in Before You Start.

+

type

+

Yes

+

String

+

Engine type. The value can be elasticsearch, logstash, or opensearch.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 8 CreateClusterBackupStrategyBody

Parameter

+

Mandatory

+

Type

+

Description

+

period

+

Yes

+

String

+

Time when a snapshot is generated every day. Snapshots can only be generated on the hour. The format is HH:mm z: HH:mm refers to the hour time and z refers to the time zone. For example, 00:00 GMT+08:00 and 01:00 GMT+08:00.

+
NOTE:

The default value is 00:00 GMT+08:00. When frequency is set to HOUR, you do not need to specify period. By default, snapshot creation starts from the next hour after the settings are successful.

+
+

prefix

+

Yes

+

String

+

Prefix of a snapshot that is automatically created, which is manually entered. Enter up to 32 characters and start with a lowercase letter. Lowercase letters, digits, hyphens (-), and underscores (_) are allowed.

+

keepday

+

Yes

+

Integer

+

Set the number of retained snapshots. The value ranges from 1 to 90. Expired snapshots will be automatically deleted on the half hour. The deletion policy applies only to automated snapshots that are executed at the same frequency as the current automatic snapshot creation policy.

+

bucket

+

No

+

String

+

Name of the OBS bucket used for backup.

+

basePath

+

No

+

String

+

Storage path of the snapshot in the OBS bucket.

+

agency

+

No

+

String

+

IAM agency used to access OBS.

+

If none of the bucket, basePath, and agency parameters are specified, the system will automatically create an OBS bucket and an IAM agency. If the creation fails, you need to manually configure correct parameters.

+

frequency

+

No

+

String

+

Frequency of automatically creating snapshots.

+
NOTE:

The default value is DAY. If this parameter is set to HOUR, the scheduled task is executed every hour. If this parameter is set to DAY, the scheduled task is executed every day. If this parameter is set to SUN, MON, TUE, WED, THU, FRI or SAT, the scheduled task is executed at the specified day of every week. For example, SUN indicates that the task is executed once every Sunday. The number of retained snapshots depends on the execution frequency and indexes set in the automatic snapshot creation policy. If the execution interval is short or the index data volume is large, the number of retained automatic snapshots may not reach the preset value. Set this value based on actual conditions.

+
+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 9 CreateClusterTagsBody

Parameter

+

Mandatory

+

Type

+

Description

+

key

+

Yes

+

String

+

Separate multiple AZs with commas (,). For example, to specify three AZs in CN North-Beijing4, you can set availability_zone to cn-north-4a,cn-north-4b,cn-north-4c. By default, a single AZ is created when this parameter is not specified.

+

value

+

Yes

+

String

+

Tag value. The value can contain 0 to 43 characters. It can only contain digits, letters, hyphens (-), and underscores (_).

+
+
+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 10 Response body parameters

Parameter

+

Type

+

Description

+

cluster

+

CreateClusterClusterResponse object

+

Cluster object.

+
+
+ +
+ + + + + + + + + + + + + +
Table 11 CreateClusterClusterResponse

Parameter

+

Type

+

Description

+

id

+

String

+

Cluster ID.

+

name

+

String

+

Cluster name

+
+
+
+

Example Requests

Example request for creating a pay-per-use cluster.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters
+
+{
+  "cluster" : {
+    "instance" : {
+      "flavorRef" : "ess.spec-4u16g",
+      "volume" : {
+        "volume_type" : "COMMON",
+        "size" : 120
+      },
+      "nics" : {
+        "vpcId" : "{VPC ID}",
+        "netId" : "{NET ID}",
+        "securityGroupId" : "{Security group ID}"
+      },
+      "availability_zone" : "{AZ CODE}"
+    },
+    "datastore" : {
+      "version" : "{cluster-version}",
+      "type" : "elasticsearch"
+    },
+    "name" : "cluster-name",
+    "instanceNum" : 3,
+    "backupStrategy" : {
+      "period" : "16:00 GMT+08:00",
+      "prefix" : "snapshot",
+      "keepday" : 7,
+      "frequency" : "DAY",
+      "bucket" : "css-obs-backup",
+      "basePath" : "css_repository/obs-path",
+      "agency" : "css_obs_agency"
+    },
+    "httpsEnable" : true,
+    "authorityEnable" : true,
+    "adminPwd" : "{password}",
+    "enterprise_project_id" : "0",
+    "tags" : [ {
+      "key" : "k1",
+      "value" : "v1"
+    }, {
+      "key" : "k2",
+      "value" : "v2"
+    } ]
+  }
+}
+
+

Example Responses

Status code: 200

+

Request succeeded.

+
  • Example response for creating a pay-per-use cluster.

    +
    {
    +  "cluster" : {
    +    "id" : "ef683016-871e-48bc-bf93-74a29d60d214",
    +    "name" : "ES-Test"
    +  }
    +}
    +
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateClusterMultiRole.html b/docs/css/api-ref/CreateClusterMultiRole.html new file mode 100644 index 00000000..dfad7833 --- /dev/null +++ b/docs/css/api-ref/CreateClusterMultiRole.html @@ -0,0 +1,950 @@ + + +

Creating a Cluster (V2)

+

Function

This API is used to create a cluster with multiple node types (for example, ess, ess-cold, ess-client, ess-master).

+
+

URI

POST /v2.0/{project_id}/clusters

+ +
+ + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

cluster

+

Yes

+

CreateClusterBody object

+

Cluster object.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 CreateClusterBody

Parameter

+

Mandatory

+

Type

+

Description

+

name

+

Yes

+

String

+

Cluster name It can contain 4 to 32 characters. Only digits, letters, hyphens (-), and underscores (_) are allowed. The value must start with a letter.

+

backupStrategy

+

No

+

CreateClusterBackupStrategyBody object

+

Automatic snapshot creation.

+

The automatic snapshot creation policy is enabled only if backupStrategy is not left blank.

+

roles

+

Yes

+

Array of CreateClusterRolesBody objects

+

Cluster information

+

nics

+

Yes

+

CreateClusterInstanceNicsBody object

+

Subnet ID.

+

enterprise_project_id

+

No

+

String

+

Enterprise project ID. When creating a cluster, associate the enterprise project ID with the cluster. The value can contain a maximum of 36 characters. It is string 0 or in UUID format with hyphens (-). Value 0 indicates the default enterprise project.

+

tags

+

No

+

Array of CreateClusterTagsBody objects

+

Cluster tag.

+

availability_zone

+

Yes

+

String

+

Availability zone (AZ). You need to specify the AZ name.

+

By default, a single AZ is specified. If multiple AZs are specified, use commas (,) to separate AZ names. Take CN North-Beijing4 as an example. If three AZs are selected, the value of availability_zone is cn-north-4a,cn-north-4b,cn-north-4c. If a single AZ is used, the value of availability_zone is empty by default.

+
NOTE:

NOTE

+

- If multiple AZs are selected, the name of each AZ must be unique, and the number of nodes must be greater than or equal to the number of AZs.

+

- If the number of nodes is a multiple of the number of AZs, the nodes are evenly distributed to each AZ.

+
+
  • If the number of nodes is not a multiple of the number of AZs, the absolute difference between node quantity in any two AZs is 1 at most.

    +
+

datastore

+

Yes

+

CreateClusterDatastoreBody object

+

Engine type. Its value can be elasticsearch, opensearch, or logstash.

+

authorityEnable

+

No

+

Boolean

+

Whether to enable authentication. The value can be true or false. Authentication is disabled by default.

+
  • true: Authentication is enabled for the cluster.

    +
  • false: Authentication is disabled for the cluster.

    +
+

This parameter is supported in clusters 6.5.4 or later.

+

httpsEnable

+

No

+

Boolean

+

Whether communication is encrypted on the cluster. The value can be true or false. By default, communication encryption is disabled. When httpsEnable is set to true, authorityEnable must be set to true.- true: Communication is encrypted on the cluster.- false: Communication is not encrypted for the cluster.This parameter is supported in clusters 6.5.4 or later.

+

adminPwd

+

No

+

String

+

Password of the cluster user admin in security mode. This parameter is mandatory only when authorityEnable is set to true. Input requirements:

+
  • Must contain 8 to 32 characters.

    +
  • Must contain at least three of the following character types: letters, digits, and special characters ~!@#$%^&*()-_=+\|[{}];:,<.>/?

    +
+

publicIPReq

+

No

+

CreateClusterPublicIpReq object

+

Public network access information. This parameter is valid only when httpsEnable is set to true.

+

loadBalance

+

No

+

CreateClusterLoadBalance object

+

VPC endpoint service information

+

publicKibanaReq

+

No

+

CreateClusterPublicKibanaReq object

+

Kibana public network access information. This parameter is valid only when authorityEnable is set to true.

+

ipv6_enable

+

No

+

Boolean

+

Whether to enable automatic IPv6 address assignment for the cluster. The default value is false.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 CreateClusterBackupStrategyBody

Parameter

+

Mandatory

+

Type

+

Description

+

period

+

Yes

+

String

+

Time when a snapshot is generated every day. Snapshots can only be generated on the hour. The format is HH:mm z: HH:mm refers to the hour time and z refers to the time zone. For example, 00:00 GMT+08:00 and 01:00 GMT+08:00.

+
NOTE:

The default value is 00:00 GMT+08:00. When frequency is set to HOUR, you do not need to specify period. By default, snapshot creation starts from the next hour after the settings are successful.

+
+

frequency

+

No

+

String

+

Frequency of automatically creating snapshots.

+
NOTE:

The default value is DAY. If this parameter is set to HOUR, the scheduled task is executed every hour. If this parameter is set to DAY, the scheduled task is executed every day. If this parameter is set to SUN, MON, TUE, WED, THU, FRI or SAT, the scheduled task is executed at the specified day of every week. For example, SUN indicates that the task is executed once every Sunday. The number of retained snapshots depends on the execution frequency and indexes set in the automatic snapshot creation policy. If the execution interval is short or the index data volume is large, the number of retained automatic snapshots may not reach the preset value. Set this value based on actual conditions.

+
+

prefix

+

Yes

+

String

+

Prefix of a snapshot that is automatically created, which is manually entered. Enter up to 32 characters and start with a lowercase letter. Lowercase letters, digits, hyphens (-), and underscores (_) are allowed.

+

keepday

+

Yes

+

Integer

+

Set the number of retained snapshots. The value ranges from 1 to 90. Expired snapshots will be automatically deleted on the half hour. The deletion policy applies only to automated snapshots that are executed at the same frequency as the current automatic snapshot creation policy.

+

bucket

+

No

+

String

+

Name of the OBS bucket used for backup.

+

basePath

+

No

+

String

+

Storage path of the snapshot in the OBS bucket.

+

agency

+

No

+

String

+

IAM agency used to access OBS.

+

If none of the bucket, base_path, and agency parameters are specified, the system will automatically create an OBS bucket and an IAM agency. If the creation fails, you need to manually configure correct parameters.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 5 CreateClusterRolesBody

Parameter

+

Mandatory

+

Type

+

Description

+

flavorRef

+

Yes

+

String

+

Instance flavor. For details about the current instance flavor, see the name attribute in Obtaining the Instance Specifications List.

+

volume

+

Yes

+

CreateClusterInstanceVolumeBody object

+

Volume information. If flavorRef is set to a local disk flavor, leave this parameter blank. Obtain the the local disk flavor by referring to the diskrange attribute in Obtaining the Instance Specifications List. Currently, the following local disk flavors are supported:

+
  • ess.spec-i3small

    +
  • ess.spec-i3medium

    +
  • ess.spec-i3.8xlarge.8

    +
  • ess.spec-ds.xlarge.8

    +
  • ess.spec-ds.2xlarge.8

    +
  • ess.spec-ds.4xlarge.8

    +
+

type

+

Yes

+

String

+
  • ess-master indicates a master node.

    +
  • ess-client indicates a client node.

    +
  • ess-cold indicates a cold data node.

    +
  • ess indicates a data node.

    +
  • lgs indicates a Logstash node.

    +

    [- chinese indicates a Chinese language model.

    +
  • english indicates an English language model.

    +
  • arabic indicates an Arabic model.

    +
  • thai indicates a Thai model.

    +
  • turkish indicates a Turkish language model.

    +
  • tools indicates a tools model.] (tag:white)

    +
+

instanceNum

+

Yes

+

Integer

+

Number of instances.

+
  • If ess is selected, you can set the value to 1 to 32.

    +
    • If both ess and ess-master are selected, you can set the value to 1 to 200.

      +
    • If both ess and ess-client are selected, you can set the value to 1 to 32.

      +
    • If both ess and ess-cold are selected, you can set the value to 32.

      +
    +
  • If ess-master is selected, you can set the value to 3 to 10.

    +
  • If ess-client is selected, you can set the value to 1 to 32.

    +
  • If ess-cold is selected, you can set the value to 1 to 32.

    +
+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 6 CreateClusterInstanceVolumeBody

Parameter

+

Mandatory

+

Type

+

Description

+

volume_type

+

Yes

+

String

+

Volume type

+
  • COMMON: common I/O

    +
  • HIGH: high I/O

    +
  • ULTRAHIGH: ultra-high I/O

    +
  • ESSD: ultra-fast SSD

    +
+

size

+

Yes

+

Integer

+

Volume size. The value must be greater than 0 and a multiple of 4 and 10. Unit: GB

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 7 CreateClusterInstanceNicsBody

Parameter

+

Mandatory

+

Type

+

Description

+

vpcId

+

Yes

+

String

+

VPC ID, which is used for configuring cluster network.

+

netId

+

Yes

+

String

+

Subnet ID (network ID).

+

securityGroupId

+

Yes

+

String

+

Security group ID.

+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 8 CreateClusterTagsBody

Parameter

+

Mandatory

+

Type

+

Description

+

key

+

Yes

+

String

+

Tag key. The value can contain 1 to 36 characters. It can only contain digits, letters, hyphens (-), and underscores (_).

+

value

+

Yes

+

String

+

Tag value. The value can contain 0 to 43 characters. It can only contain digits, letters, hyphens (-), and underscores (_).

+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 9 CreateClusterDatastoreBody

Parameter

+

Mandatory

+

Type

+

Description

+

version

+

Yes

+

String

+

Version of the CSS cluster engine. For details, see the supported versions in Before You Start.

+

[For a serverless cluster, logs, search, and vector are supported.] (tag:white)

+

type

+

Yes

+

String

+

Engine type. Its value can be elasticsearch, opensearch, or logstash.

+

[For a serverless cluster, serverless-opensearch is used.] (tag:white)

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 10 CreateClusterPublicIpReq

Parameter

+

Mandatory

+

Type

+

Description

+

eip

+

Yes

+

CreateClusterPublicEip object

+

Public network bandwidth.

+

elbWhiteListReq

+

Yes

+

CreateClusterElbWhiteList object

+

EIP whitelist.

+

publicBindType

+

Yes

+

String

+

Whether to automatically bind an EIP. Specifies whether to automatically bind an EIP. Currently, only auto_assign is supported.

+

eipId

+

No

+

String

+

EIP ID.

+
+
+ +
+ + + + + + + + + + + +
Table 11 CreateClusterPublicEip

Parameter

+

Mandatory

+

Type

+

Description

+

bandWidth

+

Yes

+

CreateClusterPublicEipSize object

+

Public network bandwidth.

+
+
+ +
+ + + + + + + + + + + +
Table 12 CreateClusterPublicEipSize

Parameter

+

Mandatory

+

Type

+

Description

+

size

+

Yes

+

Integer

+

Bandwidth range.

+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 13 CreateClusterElbWhiteList

Parameter

+

Mandatory

+

Type

+

Description

+

enableWhiteList

+

Yes

+

Boolean

+

Whether to enable the public network access control.

+

whiteList

+

No

+

String

+

Public network access control whitelist. Separate the whitelisted network segments or IP addresses with commas (,), and each of them must be unique.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 14 CreateClusterLoadBalance

Parameter

+

Mandatory

+

Type

+

Description

+

endpointWithDnsName

+

Yes

+

Boolean

+

Whether to enable the private domain name.

+
  • true: The private zone is enabled.

    +
  • false: The private zone is disabled.

    +
+

vpcPermissions

+

No

+

Array of strings

+

Access control.

+

professionVpcep

+

No

+

Boolean

+

Create a professional VPC endpoint.

+
  • true: enabled.

    +
  • false: disabled.

    +
+

dualstackEnable

+

No

+

Boolean

+

Whether to enable the IPv4/IPv6 dual-stack network. The IPv4/IPv6 dual-stack network can be enabled only when a professional VPC endpoint is created and the VPC of the cluster supports IPv6.

+
  • true: enabled.

    +
  • false: disabled.

    +
+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 15 CreateClusterPublicKibanaReq

Parameter

+

Mandatory

+

Type

+

Description

+

eipSize

+

Yes

+

Integer

+

Bandwidth range.

+

elbWhiteList

+

Yes

+

CreateClusterPublicKibanaElbWhiteList object

+

Kibana whitelist information.

+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 16 CreateClusterPublicKibanaElbWhiteList

Parameter

+

Mandatory

+

Type

+

Description

+

whiteList

+

Yes

+

String

+

Whitelist. Separate the whitelisted network segments or IP addresses with commas (,), and each of them must be unique.

+

enableWhiteList

+

Yes

+

Boolean

+

Whether to enable the Kibana access control.

+
+
+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 17 Response body parameters

Parameter

+

Type

+

Description

+

cluster

+

CreateClusterResp object

+

Cluster object.

+
+
+ +
+ + + + + + + + + + + + + +
Table 18 CreateClusterResp

Parameter

+

Type

+

Description

+

id

+

String

+

Cluster ID.

+

name

+

String

+

Cluster name

+
+
+
+

Example Requests

Example request for creating a pay-per-use cluster.

+
{
+  "cluster" : {
+    "name" : "css-cluster",
+    "backupStrategy" : {
+      "period" : "16:00 GMT+08:00",
+      "prefix" : "snapshot",
+      "keepday" : 7,
+      "frequency" : "DAY",
+      "bucket" : "OBS-obsName",
+      "basePath" : "css_repository/obs-path",
+      "agency" : "css_obs_agency"
+    },
+    "roles" : [ {
+      "flavorRef" : "ess.spec-4u8g",
+      "volume" : {
+        "volume_type" : "COMMON",
+        "size" : 100
+      },
+      "type" : "ess",
+      "instanceNum" : 1
+    } ],
+    "nics" : {
+      "vpcId" : "{VPC ID}",
+      "netId" : "{NET ID}",
+      "securityGroupId" : "{Security group ID}"
+    },
+    "enterprise_project_id" : 0,
+    "tags" : [ {
+      "key" : "k1",
+      "value" : "v1"
+    }, {
+      "key" : "k2",
+      "value" : "v2"
+    } ],
+    "availability_zone" : "{Az code}",
+    "datastore" : {
+      "version" : "{cluster-version}",
+      "type" : "elasticsearch"
+    },
+    "authorityEnable" : true,
+    "httpsEnable" : true,
+    "adminPwd" : "{password}",
+    "publicIPReq" : {
+      "eip" : {
+        "bandWidth" : {
+          "size" : 5
+        }
+      },
+      "elbWhiteListReq" : {
+        "enableWhiteList" : true,
+        "whiteList" : "127.0.0.1"
+      },
+      "publicBindType" : "auto_assign",
+      "eipId" : null
+    },
+    "loadBalance" : {
+      "endpointWithDnsName" : false,
+      "vpcPermissions" : [ "{Account ID}" ]
+    },
+    "publicKibanaReq" : {
+      "eipSize" : 5,
+      "elbWhiteList" : {
+        "whiteList" : "127.0.0.1",
+        "enableWhiteList" : true
+      }
+    }
+  }
+}
+
+

Example Responses

Status code: 200

+

Request succeeded.

+
  • Example response for creating a pay-per-use cluster.

    +
    {
    +  "cluster" : {
    +    "id" : "ef683016-871e-48bc-bf93-74a29d60d214",
    +    "name" : "ES-Test"
    +  }
    +}
    +
  • Example response for creating a yearly/monthly cluster.

    +
    {
    +  "orderId" : "CS2208241141LY94J",
    +  "cluster" : {
    +    "id" : "ef683016-871e-48bc-bf93-74a29d60d214",
    +    "name" : "ES-Test"
    +  }
    +}
    +
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateClustersTags.html b/docs/css/api-ref/CreateClustersTags.html new file mode 100644 index 00000000..e35d2176 --- /dev/null +++ b/docs/css/api-ref/CreateClustersTags.html @@ -0,0 +1,160 @@ + + +

Adding Tags to a Cluster

+

Function

This API is used to add tags to a cluster.

+
+

URI

POST /v1.0/{project_id}/{resource_type}/{cluster_id}/tags

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster that you want to add tags to.

+

resource_type

+

Yes

+

String

+

Resource type. Currently, its value can only be css-cluster.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

tag

+

Yes

+

Tag object

+

Tag object you want to add.

+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 3 Tag

Parameter

+

Mandatory

+

Type

+

Description

+

key

+

Yes

+

String

+

Tag name.

+

value

+

Yes

+

String

+

Tag value.

+
+
+
+

Response Parameters

None

+
+

Example Requests

Create a cluster tag.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/tags
+
+{
+  "tag" : {
+    "key" : "K1",
+    "value" : "V1"
+  }
+}
+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

204

+

Request succeeded.

+

400

+

Invalid request.

+

The client should modify the request instead of re-initiating it.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateElbListener.html b/docs/css/api-ref/CreateElbListener.html new file mode 100644 index 00000000..8f41b3d9 --- /dev/null +++ b/docs/css/api-ref/CreateElbListener.html @@ -0,0 +1,168 @@ + + +

Configuring the Elasticsearch Listener

+

Function

This API is used to configure the Elasticsearch listener.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/es-listeners

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster that you want to rename.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

protocol

+

Yes

+

String

+

Protocol type. HTTP and HTTPS are supported.

+

protocol_port

+

Yes

+

Integer

+

Port

+

server_cert_id

+

No

+

String

+

Server certificate ID. This parameter is mandatory when protocol is set to HTTPS.

+

ca_cert_id

+

No

+

String

+

CA certificate ID. This parameter is mandatory when protocol is set to HTTPS and bidirectional authentication is used.

+
+
+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 3 Response body parameters

Parameter

+

Type

+

Description

+

elb_id

+

String

+

Load balancer ID

+
+
+
+

Example Requests

POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/es-listeners
+
+{
+  "protocol" : "HTTPS",
+  "protocol_port" : "9200",
+  "server_cert_id" : "1b74ae4afad741e6bc9497429d3d0838",
+  "ca_cert_id" : "2a7b050f598e4ea8a61cffbe2bdb312f"
+}
+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "elb_id" : "56a83547-a55a-407a-8245-7f9b3a0606c0"
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request instead of retrying.

+

409

+

The request cannot be processed due to a conflict.

+

This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

+

412

+

The server does not meet one of the requirements that the requester puts on the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateLogBackup.html b/docs/css/api-ref/CreateLogBackup.html new file mode 100644 index 00000000..08ba75f0 --- /dev/null +++ b/docs/css/api-ref/CreateLogBackup.html @@ -0,0 +1,89 @@ + + +

Backing Up Logs

+

Function

This API is used to back up logs.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/logs/collect

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster whose logs you want to back up.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

None

+
+

Example Requests

None

+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/CreateSnapshot.html b/docs/css/api-ref/CreateSnapshot.html new file mode 100644 index 00000000..9b93f17c --- /dev/null +++ b/docs/css/api-ref/CreateSnapshot.html @@ -0,0 +1,196 @@ + + +

Manually Creating a Snapshot

+

Function

This API is used to manually create a snapshot.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster for which you want to create a snapshot.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

name

+

Yes

+

String

+

Snapshot name. Enter 4 to 64 characters. Lowercase letters, digits, hyphens (-), and underscores (_) are allowed. The value must start with a letter.

+

description

+

No

+

String

+

Snapshot description. The value can contain up to 256 characters and cannot contain the following characters: !<>=&"'

+

indices

+

No

+

String

+

Name of an index to be backed up. Multiple indexes are separated by commas (,). By default, all indexes are backed up. You can use the combination of a backslash and an asterisk (*) to back up data of certain indexes. For example, if you specify 2018-06*, then the data of the indexes with the prefix 2018-06 will be backed up.The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and the following special characters are not allowed: "\<|>/?

+
+
+
+

Response Parameters

Status code: 201

+ +
+ + + + + + + + + +
Table 3 Response body parameters

Parameter

+

Type

+

Description

+

backup

+

backupRsp object

+

Snapshot information.

+
+
+ +
+ + + + + + + + + + + + + +
Table 4 backupRsp

Parameter

+

Type

+

Description

+

id

+

String

+

Snapshot ID

+

name

+

String

+

Snapshot name

+
+
+
+

Example Requests

Create a snapshot.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/index_snapshot
+
+{
+  "name" : "snapshot_001",
+  "indices" : "myindex1myindex2"
+}
+
+

Example Responses

Status code: 201

+

Resource created.

+
{
+  "backup" : {
+    "id" : "9dc4f5c9-33c0-45c7-9378-ae35ae350682",
+    "name" : "snapshot_101"
+  }
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + + + + + + + +

Status Code

+

Description

+

201

+

Resource created.

+

400

+

Invalid request.

+

Modify the request before retry.

+

403

+

Request rejected.The server has received the request and understood it, but refused to respond to it. The client should not repeat the request without modifications.

+

406

+

The server could not fulfill the request according to the content characteristics of the request.

+

500

+

The server has received the request but could not understand it.

+

501

+

The server does not support the function required to fulfill the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/DeleteCluster.html b/docs/css/api-ref/DeleteCluster.html new file mode 100644 index 00000000..f3a900bd --- /dev/null +++ b/docs/css/api-ref/DeleteCluster.html @@ -0,0 +1,85 @@ + + +

Deleting a Cluster

+

Function

This API is used to delete a cluster. All resources of the deleted cluster, including customer data, will be released. If you want to retain the data in a customer cluster, create a snapshot before deleting the cluster.

+

This API can also be used to unsubscribe from clusters in yearly/monthly mode. Clusters frozen for public security cannot be deleted.

+
+

URI

DELETE /v1.0/{project_id}/clusters/{cluster_id}

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to delete.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

None

+
+

Example Requests

None

+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

404

+

The requested resource could not be found.

+

Modify the request before retry.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/DeleteClustersTags.html b/docs/css/api-ref/DeleteClustersTags.html new file mode 100644 index 00000000..b6526230 --- /dev/null +++ b/docs/css/api-ref/DeleteClustersTags.html @@ -0,0 +1,102 @@ + + +

Deleting a Cluster Tag

+

Function

This API is used to delete a cluster tag.

+
+

URI

DELETE /v1.0/{project_id}/{resource_type}/{cluster_id}/tags/{key}

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster that you want to delete tags from.

+

resource_type

+

Yes

+

String

+

Resource type. Currently, its value can only be css-cluster.

+

key

+

Yes

+

String

+

Name of the tag you want to delete. If the tag name is in Chinese, encode the tag name using URL before calling the API.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

None

+
+

Example Requests

None

+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

204

+

Request succeeded.

+

400

+

Invalid request.

+

The client should modify the request instead of re-initiating it.

+

404

+

The requested resource could not be found.

+

The client should not repeat the request without modifications.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/DeleteSnapshot.html b/docs/css/api-ref/DeleteSnapshot.html new file mode 100644 index 00000000..c476ba27 --- /dev/null +++ b/docs/css/api-ref/DeleteSnapshot.html @@ -0,0 +1,92 @@ + + +

Deleting a Snapshot

+

Function

This API is used to delete a snapshot.

+
+

URI

DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster whose snapshot you want to delete.

+

snapshot_id

+

Yes

+

String

+

ID of the snapshot you want to delete.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

None

+
+

Example Requests

None

+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

403

+

Request rejected.The server has received the request and understood it, but refused to respond to it. The client should not repeat the request without modifications.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/DownloadCert.html b/docs/css/api-ref/DownloadCert.html new file mode 100644 index 00000000..f743f9ea --- /dev/null +++ b/docs/css/api-ref/DownloadCert.html @@ -0,0 +1,96 @@ + + +

Downloading a Security Certificate

+

Function

This API is used to download a security certificate.

+
+

URI

GET /v1.0/{project_id}/cer/download

+ +
+ + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 2 Response body parameters

Parameter

+

Type

+

Description

+

-

+

File

+

File stream

+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
"Certificate:xxxx"
+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

404

+

The requested resource could not be found.

+

Modify the request before retry.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/EnableOrDisableElb.html b/docs/css/api-ref/EnableOrDisableElb.html new file mode 100644 index 00000000..8d793e62 --- /dev/null +++ b/docs/css/api-ref/EnableOrDisableElb.html @@ -0,0 +1,162 @@ + + +

Enabling or Disabling the Elasticsearch Load Balancer

+

Function

This API is used to enable or disable the Elasticsearch load balancer.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers/es-switch

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster to be modified

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

enable

+

Yes

+

Boolean

+

Enable or disable the ES load balancer.

+
  • true: enable the ES load balancer.

    +
  • false: disable the ES load balancer.

    +
+

agency

+

No

+

String

+

Agency name

+

elb_id

+

No

+

String

+

Load balancer ID

+
+
+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 3 Response body parameters

Parameter

+

Type

+

Description

+

elb_id

+

String

+

Load balancer ID

+
+
+
+

Example Requests

Enable the load balancer.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/58ee0f27-70b3-47e0-ac72-9e3df6cd15cd/loadbalancers/es-switch
+
+{
+  "enable" : true,
+  "elb_id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6268",
+  "agency" : "css_elb_agency"
+}
+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "elb_id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6268"
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request instead of retrying.

+

409

+

The request cannot be processed due to a conflict.

+

This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

+

412

+

The server does not meet one of the requirements that the requester puts on the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListClustersDetails.html b/docs/css/api-ref/ListClustersDetails.html new file mode 100644 index 00000000..89a69786 --- /dev/null +++ b/docs/css/api-ref/ListClustersDetails.html @@ -0,0 +1,762 @@ + + +

Querying the Cluster List

+

Function

This API is used to query and display the cluster list and cluster status.

+
+

URI

GET /v1.0/{project_id}/clusters

+ +
+ + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Parameter description:

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

Constraints:

+

N/A

+

Options:

+

Letters and digits

+

Default value:

+

N/A

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 2 Query Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

start

+

No

+

Integer

+

Parameter description:

+

The start value of the query. The default value is 1, indicating that the query starts from the first cluster.

+

Constraints:

+

N/A

+

Options:

+

1-1000

+

Default value:

+

1

+

limit

+

No

+

Integer

+

Parameter description:

+

Number of clusters to be queried. The default value is 10, indicating that the information about 10 clusters is queried at a time.

+

Constraints:

+

N/A

+

Options:

+

1-1000

+

Default value:

+

10

+

datastoreType

+

No

+

String

+

Parameter description:

+

Cluster engine type.

+

Constraints:

+

N/A

+

Options:

+

elasticsearch, logstash, or opensearch.

+

Default value:

+

elasticsearch.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + + + + + +
Table 3 Response body parameters

Parameter

+

Type

+

Description

+

totalSize

+

Integer

+

Number of clusters

+

clusters

+

Array of ClusterList objects

+

List of cluster objects.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 ClusterList

Parameter

+

Type

+

Description

+

datastore

+

ClusterListDatastore object

+

Search engine.

+

instances

+

Array of ClusterListInstances objects

+

List of node objects.

+

publicKibanaResp

+

publicKibanaRespBody object

+

Kibana public network access information.

+

elbWhiteList

+

elbWhiteListResp object

+

EIP whitelist.

+

updated

+

String

+

Last modification time of a cluster. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

+

name

+

String

+

Cluster name

+

publicIp

+

String

+

Public IP address information.

+

created

+

String

+

Cluster creation time. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

+

The returned cluster list is sorted by creation time in descending order. The latest cluster is displayed at the top.

+

id

+

String

+

Cluster ID.

+

status

+

String

+

Cluster status.

+
  • 100: Creating

    +
  • 200: Available

    +
  • 303: Unavailable, for example, due to a creation failure.

    +
+

endpoint

+

String

+

IPv4 address and port number accessed from the cluster's private network. [If the cluster type is KooSearch, this field indicates the internal address and port number for accessing the knowledge management service.] (tag:white)

+

vpcId

+

String

+

ID of a VPC.

+

subnetId

+

String

+

Subnet ID.

+

securityGroupId

+

String

+

Security group ID.

+

bandwidthSize

+

Integer

+

Public network bandwidth. Unit: Mbit/s

+

httpsEnable

+

Boolean

+

Communication encryption status.

+
  • false: Communication encryption is not enabled.

    +
  • true: Communication encryption is enabled.

    +
+

authorityEnable

+

Boolean

+

Whether to enable authentication.

+
  • true: Authentication is enabled for the cluster.

    +
  • false: Authentication is not enabled for the cluster.

    +
+

diskEncrypted

+

Boolean

+

Whether disks are encrypted.

+
  • true: Disks are encrypted.

    +
  • false: Disk are not encrypted.

    +
+

backupAvailable

+

Boolean

+

Whether the snapshot function is enabled.

+
  • true: The snapshot function is enabled.

    +
  • false: The snapshot function is disabled.

    +
+

actionProgress

+

Object

+

Cluster behavior progress, which shows the progress of cluster creation and scaling in percentage. CREATING indicates the progress of creation.

+

actions

+

Array of strings

+

Current behavior of a cluster. REBOOTING indicates that the cluster is being restarted. GROWING indicates that the cluster is being scaled. RESTORING indicates that the cluster is being restored. SNAPSHOTTING indicates that a snapshot is being created.

+

enterpriseProjectId

+

String

+

ID of the enterprise project that a cluster belongs to.

+

If the user of the cluster does not enable the enterprise project, the setting of this parameter is not returned.

+

tags

+

Array of ClusterListTags objects

+

Cluster tag.

+

failedReason

+

ClusterListFailedReasons object

+

Failure cause. If the cluster is in the available status, this parameter is not returned.

+

bandwidthResourceId

+

String

+

ID of the resource accessed from the ES public network

+

ipv6Endpoint

+

String

+

IPv6 address and port number accessible from the cluster's private network.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 5 ClusterListDatastore

Parameter

+

Type

+

Description

+

type

+

String

+

Engine type. Its value can be elasticsearch or logstash.

+

version

+

String

+

Version of the CSS cluster engine. For details, see the supported versions in Before You Start.

+

supportSecuritymode

+

Boolean

+

Whether the security mode is supported.

+

subVersion

+

String

+

Cluster image version.

+

isEosCluster

+

Boolean

+

Whether the cluster image version has reached EOS. The value can be true or false.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 6 ClusterListInstances

Parameter

+

Type

+

Description

+

status

+

String

+

Node status.

+
  • 100: Creating

    +
  • 200: Available

    +
  • 303: Unavailable, for example, due to a creation failure.

    +
+

type

+

String

+

Type of the current node.

+

id

+

String

+

Instance ID.

+

name

+

String

+

Instance name.

+

specCode

+

String

+

Node specifications.

+

azCode

+

String

+

AZ of a node.

+

ip

+

String

+

Instance IP address.

+

volume

+

ClusterVolumeRsp object

+

definitions.ClusterVolumeRsp.description

+

resourceId

+

String

+

ID of the instance resource

+
+
+ +
+ + + + + + + + + + + + + + + + + +
Table 7 ClusterVolumeRsp

Parameter

+

Type

+

Description

+

type

+

String

+

Type of the disk used by the instance.

+

size

+

Integer

+

Instance disk information

+

resourceIds

+

Array of strings

+

Instance disk resource ID

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 8 publicKibanaRespBody

Parameter

+

Type

+

Description

+

eipSize

+

Integer

+

Bandwidth range. Unit: Mbit/s

+

elbWhiteListResp

+

kibanaElbWhiteListResp object

+

Kibana public network access information.

+

publicKibanaIp

+

String

+

Specifies the IP address for accessing Kibana.

+

bandwidthResourceId

+

String

+

Resource ID corresponding to the Kibana public network

+
+
+ +
+ + + + + + + + + + + + + +
Table 9 kibanaElbWhiteListResp

Parameter

+

Type

+

Description

+

enableWhiteList

+

Boolean

+

Whether the Kibana access control is enabled.

+
  • true: Access control is enabled.

    +
  • false: Access control is disabled.

    +
+

whiteList

+

String

+

Whitelist of public network for accessing Kibana.

+
+
+ +
+ + + + + + + + + + + + + +
Table 10 elbWhiteListResp

Parameter

+

Type

+

Description

+

enableWhiteList

+

Boolean

+

Whether the public network access control is enabled.

+
  • true: Public network access control is enabled.

    +
  • false: Public network access control is disabled.

    +
+

whiteList

+

String

+

Whitelist for public network access.

+
+
+ +
+ + + + + + + + + + + + + +
Table 11 ClusterListTags

Parameter

+

Type

+

Description

+

key

+

String

+

Tag key.

+

value

+

String

+

Tag value.

+
+
+ +
+ + + + + + + + + + + + + +
Table 12 ClusterListFailedReasons

Parameter

+

Type

+

Description

+

errorCode

+

String

+

Error code.

+
  • CSS.6000: A cluster fails to be created.

    +
  • CSS.6001: A cluster fails to be scaled out.

    +
  • CSS.6002: A cluster fails to be restarted.

    +
  • CSS.6004: A node fails to be created in a cluster.

    +
  • CSS.6005: A service fails to be initialized.

    +
+

errorMsg

+

String

+

Error details.

+
+
+
+

Example Requests

  • Query the first two clusters.

    +
    - Method 1: GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?start=1&limit=2
    +- Method 2: GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?limit=2
    +
  • Query the first ten clusters.

    +
    - Method 1: GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?start=1&limit=10
    +- Method 2: GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?limit=10
    +
+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "totalSize" : 1,
+  "clusters" : [ {
+    "datastore" : {
+      "type" : "elasticsearch",
+      "version" : "7.10.2",
+      "subVersion" : "7.10.2_24.3.0_0827",
+      "isEosCluster" : false,
+      "supportSecuritymode" : false
+    },
+    "instances" : [ {
+      "status" : "200",
+      "type" : "ess",
+      "id" : "{INSTANCE_ID}",
+      "name" : "css-8bc5-ess-esn-1-1",
+      "specCode" : "ess.spec-4u8g",
+      "azCode" : "{AZ_CODE}",
+      "volume" : {
+        "type" : "ULTRAHIGH",
+        "size" : 40,
+        "resourceIds" : [ "{RESOURCE_ID}" ]
+      },
+      "ip" : "192.168.0.122",
+      "resourceId" : "{RESOURCE_ID}"
+    } ],
+    "publicKibanaResp" : {
+      "eipSize" : 10,
+      "publicKibanaIp" : "100.95.152.28:9200",
+      "elbWhiteListResp" : null,
+      "bandwidthResourceId" : "18bec13f-5cc1-4631-867f-33505d15be12"
+    },
+    "elbWhiteList" : {
+      "whiteList" : "",
+      "enableWhiteList" : false
+    },
+    "updated" : "2023-10-09T02:07:13",
+    "name" : "css-8bc5",
+    "publicIp" : "100.85.222.202",
+    "created" : "2023-10-09T02:07:13",
+    "id" : "{CLUSTER_ID}",
+    "status" : "200",
+    "endpoint" : "192.168.0.122:9200",
+    "vpcId" : "{VPC_ID}",
+    "subnetId" : "{SUBNET_ID}",
+    "securityGroupId" : "{SECURITY_GROUP_ID}",
+    "bandwidthResourceId" : "{BANDWIDTH_RESOURCE_ID}",
+    "bandwidthSize" : 3,
+    "httpsEnable" : true,
+    "authorityEnable" : true,
+    "diskEncrypted" : false,
+    "backupAvailable" : false,
+    "actionProgress" : { },
+    "actions" : [ ],
+    "enterpriseProjectId" : "0",
+    "tags" : [ ],
+    "period" : true
+  } ]
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

404

+

The requested resource could not be found.

+

Modify the request before retry.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListClustersTags.html b/docs/css/api-ref/ListClustersTags.html new file mode 100644 index 00000000..fff6b1d4 --- /dev/null +++ b/docs/css/api-ref/ListClustersTags.html @@ -0,0 +1,139 @@ + + +

Querying All Tags

+

Function

This API is used to query all tags in a specified region.

+
+

URI

GET /v1.0/{project_id}/{resource_type}/tags

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

resource_type

+

Yes

+

String

+

Resource type. Currently, its value can only be css-cluster.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 2 Response body parameters

Parameter

+

Type

+

Description

+

tags

+

Array of ShowAllTagsTagsResp objects

+

List of cluster tags

+
+
+ +
+ + + + + + + + + + + + + +
Table 3 ShowAllTagsTagsResp

Parameter

+

Type

+

Description

+

key

+

String

+

Tag key

+

values

+

Array of strings

+

Tag value

+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "tags" : [ {
+    "key" : "key1",
+    "values" : [ "value1", "value2" ]
+  }, {
+    "key" : "key2",
+    "values" : [ "value1", "value2" ]
+  } ]
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

The client should modify the request instead of re-initiating it.

+

404

+

The requested resource could not be found.

+

The client should not repeat the request without modifications.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListElbCerts.html b/docs/css/api-ref/ListElbCerts.html new file mode 100644 index 00000000..124a83c9 --- /dev/null +++ b/docs/css/api-ref/ListElbCerts.html @@ -0,0 +1,157 @@ + + +

Querying the Certificate List

+

Function

This API is used to query the certificate list.

+
+

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/elb/certificates

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to query

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 2 Response body parameters

Parameter

+

Type

+

Description

+

certificates

+

CertificatesResource object

+

Certificate list information

+
+
+ +
+ + + + + + + + + + + + + + + + + +
Table 3 CertificatesResource

Parameter

+

Type

+

Description

+

id

+

String

+

Certificate ID

+

name

+

String

+

Certificate name

+

type

+

String

+

Type of the SL certificate. The value can be server or client. server indicates server certificates, and client indicates CA certificates.

+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "certificates" : [ {
+    "id" : "8c415d2e2f4c4fdbbfc9c21c98d7832b",
+    "name" : "server1",
+    "type" : "server"
+  }, {
+    "id" : "8c415d2e2f4c4fdbbfc9c21c98d7832b",
+    "name" : "ca1",
+    "type" : "client"
+  }, {
+    "id" : "8c415d2e2f4c4fdbbfc9c21c98d7832b",
+    "name" : "server-css",
+    "type" : "server"
+  } ]
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request instead of retrying.

+

409

+

The request cannot be processed due to a conflict.

+

This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

+

412

+

The server does not meet one of the requirements that the requester puts on the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListElbs.html b/docs/css/api-ref/ListElbs.html new file mode 100644 index 00000000..8547aec9 --- /dev/null +++ b/docs/css/api-ref/ListElbs.html @@ -0,0 +1,162 @@ + + +

Querying ELBv3 Load Balancers Supported by a Cluster

+

Function

This API is used to query the ELBv3 load balancers supported by a cluster.

+
+

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to query.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 2 Response body parameters

Parameter

+

Type

+

Description

+

loadbalancers

+

Array of LoadbalancersResource objects

+

Load balancer list

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 3 LoadbalancersResource

Parameter

+

Type

+

Description

+

id

+

String

+

Load balancer ID

+

name

+

String

+

Load balancer name

+

l7_flavor_id

+

String

+

Layer 7 protocol ID

+

ip_target_enable

+

Boolean

+

Indicates whether to enable the cross-VPC backend.

+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "loadbalancers" : [ {
+    "id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6268",
+    "name" : "elb-css",
+    "l7_flavor_id" : "9c8c2425-e061-4bf8-ac65-cd1db92b18e1",
+    "ip_target_enable" : true
+  }, {
+    "id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6269",
+    "name" : "elb-b832",
+    "l7_flavor_id" : "9c8c2425-e061-4bf8-ac65-cd1db92b18e1",
+    "ip_target_enable" : true
+  } ]
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request instead of retrying.

+

409

+

The request cannot be processed due to a conflict.

+

This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

+

412

+

The server does not meet one of the requirements that the requester puts on the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListFlavors.html b/docs/css/api-ref/ListFlavors.html index f33b2438..1c75a437 100644 --- a/docs/css/api-ref/ListFlavors.html +++ b/docs/css/api-ref/ListFlavors.html @@ -1,241 +1,220 @@ -

Obtaining the List of Instance Flavors

-

Function

This API is used to query and display the IDs of supported instance flavors.

+

Obtaining the Instance Specifications List

+

Function

This API is used to query and display the IDs of supported instance specifications.

-

URI

GET /v1.0/{project_id}/flavors
+

URI

GET /v1.0/{project_id}/es-flavors

-
Table 1 Parameter description

Parameter

+
- - - - - - -
Table 1 Path Parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

project_id

+

project_id

Yes

+

Yes

String

+

String

Project ID. For details, see Obtaining a Project ID and Name.

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

-

Request

None

+

Request Parameters

None

-

Response

Table 2 describes the response parameters.

+

Response Parameters

Status code: 200

-
Table 2 Parameter description

Parameter

+
- - - - -
Table 2 Response body parameters

Parameter

Type

+

Type

Description

+

Description

versions

+

versions

Array of versions objects

+

Array of EsflavorsVersionsResp objects

List of engine versions.

+

Engine version list.

-
Table 3 versions field description

Parameter

+
- - - - - - - - - - -
Table 3 EsflavorsVersionsResp

Parameter

Type

+

Type

Description

+

Description

version

+

version

String

+

String

Engine version.

+

Elasticsearch engine version. For details, see the supported versions in Before You Start.

type

+

flavors

String

+

Array of EsflavorsVersionsFlavorsResp objects

Instance type. The options are ess, ess-cold, ess-master, and ess-client.

+

instance flavor list.

flavors

+

type

Array of flavors objects

+

String

Flavor list

+

Instance type. The options are ess, ess-cold, ess-master, and ess-client.

-
Table 4 flavors field description

Parameter

+
- - - - - - - - - - - - - - - - - - - - + + + +
Table 4 EsflavorsVersionsFlavorsResp

Parameter

Type

+

Type

Description

+

Description

ram

+

cpu

Integer

+

Integer

Memory size of an instance. Unit: GB

+

Number of CPU cores of an instance.

cpu

+

ram

Integer

+

Integer

Number of vCPUs of an instance.

+

Memory size of an instance. Unit: GB

name

+

name

String

+

String

Flavor name.

+

Flavor name

region

+

region

String

+

String

AZ

+

Available region

diskrange

+

diskrange

String

+

String

Disk capacity range of an instance.

+

Disk capacity range of an instance

flavor_id

+

availableAZ

String

+

String

ID of a flavor.

+

AZ

+

flavor_id

+

String

+

Flavor ID

-

Examples

Example request
GET /v1.0/6204a5bd270343b5885144cf9c8c158d/flavors
+

Example Requests

None

-

Example response

-
{
-  "versions": [
-    {
-      "version": "6.2.3",
-      "flavors": [
-        {
-          "cpu": 1,
-          "ram": 8,
-          "name": "css.medium.8",
-          "region": "eu-de",
-          "diskrange": "40,640",
-          "flavor_id": "6b6c0bcf-750d-4f8a-b6f5-c45a143f5198"
-
-        },
-        {
-          "cpu": 2,
-          "ram": 16,
-          "name": "css.large.8",
-          "region": "eu-de",
-          "diskrange": "40,1280",
-          "flavor_id": "d373e339-3cf4-4c00-9739-2259e9f3ec16"
-
-        },
-        {
-          "cpu": 4,
-          "ram": 32,
-          "name": "css.xlarge.8",
-          "region": "eu-de",
-          "diskrange": "40,2560",
-          "flavor_id": "2d8daf1b-873f-4c2e-a7b9-2f9cbcf2f213"
-
-        },
-        {
-          "cpu": 8,
-          "ram": 64,
-          "name": "css.2xlarge.8",
-          "region": "eu-de",
-          "diskrange": "80,5120",
-          "flavor_id": "b3d33ec6-d58a-40f0-aa51-4f671ce64b2a"
-
-        },
-        {
-          "cpu": 16,
-          "ram": 128,
-          "name": "css.4xlarge.8",
-          "region": "eu-de",
-          "diskrange": "160,10240",
-          "flavor_id": "f74419ca-bc91-4558-b4e2-90eeefb37c6e"
-        }
-      ]
-    }
-  ]
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "versions" : [ {
+    "flavors" : [ {
+      "cpu" : 4,
+      "ram" : 32,
+      "name" : "ess.spec-4u32g",
+      "region" : "xx-xxx-xx",
+      "diskrange" : "40,2560",
+      "availableAZ" : "xx-xxx-xx,xx-xxx-xx",
+      "flavor_id" : "2d8daf1b-873f-4c2e-a7b9-2f9cbcf2f213"
+    }, {
+      "cpu" : 8,
+      "ram" : 64,
+      "name" : "ess.spec-8u64g",
+      "region" : "xx-xxx-xx",
+      "diskrange" : "80,5120",
+      "availableAZ" : "xx-xxx-xx,xx-xxx-xx",
+      "flavor_id" : "b3d33ec6-d58a-40f0-aa51-4f671ce64b2a"
+    }, {
+      "cpu" : 16,
+      "ram" : 128,
+      "name" : "ess.spec-16u128g",
+      "region" : "xx-xxx-xx",
+      "diskrange" : "160,10240",
+      "availableAZ" : "xx-xxx-xx,xx-xxx-xx",
+      "flavor_id" : "f74419ca-bc91-4558-b4e2-90eeefb37c6e"
+    } ],
+    "type" : "ess",
+    "version" : "x.x.x"
+  } ]
 }
-

Status Code

Table 5 describes the status code.

- -
Table 5 Status codes

Status Code

+

Status Codes

+
- - - - - - - - - - -

Status Code

Message

-

Description

+

Description

400

+

200

BadRequest

-

Invalid request.

-

Modify the request instead of retrying.

+

Request succeeded.

404

+

400

NotFound

-

The requested resource cannot be found.

-

Modify the request instead of retrying.

+

Invalid request.

+

Modify the request before retry.

200

+

404

OK

-

The request is processed.

+

The requested resource could not be found.

+

Modify the request before retry.

+

Error Codes

See Error Codes.

+
diff --git a/docs/css/api-ref/ListImages.html b/docs/css/api-ref/ListImages.html index c83a0e24..3c60da08 100644 --- a/docs/css/api-ref/ListImages.html +++ b/docs/css/api-ref/ListImages.html @@ -1,184 +1,187 @@

Obtaining a Target Image ID

-

Function

This API is used to obtain the ID of an image that can be upgraded in the current cluster.

+

Function

This API is used to obtain the ID of an image that can be upgraded in the current cluster.

-

Calling Method

For details, see Calling APIs.

-
-

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/target/{upgrade_type}/images

+

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/target/{upgrade_type}/images

-
Table 1 Path parameters

Parameter

+
- - - - - - - - - - - - - - -
Table 1 Path Parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

project_id

+

project_id

Yes

+

Yes

String

+

String

Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

cluster_id

+

cluster_id

Yes

+

Yes

String

+

String

ID of the cluster to be upgraded.

+

ID of the cluster to be upgraded.

upgrade_type

+

upgrade_type

Yes

+

Yes

String

+

String

Version type. The value can be:

-
  • same: upgrade to the same version.
  • cross: upgrade to a different version.
  • crossEngine: cross-engine upgrade.
+

Version type:

+
  • same: upgrade to the same version.

    +
  • cross: upgrade to a different version.

    +
  • cross-engine: cross-engine upgrade.

    +
-

Request Parameters

None

+

Request Parameters

None

-

Response Parameters

Status code: 200

+

Response Parameters

Status code: 200

-
Table 2 Response body parameters

Parameter

+
- - - - - - - -
Table 2 Response body parameters

Parameter

Type

+

Type

Description

+

Description

needUploadUpgradePlugin

+

needUploadUpgradePlugin

Boolean

+

Boolean

Indicates whether to upload the plug-in of the target version.

+

Whether to upload the plug-in of the target version.

imageInfoList

+

imageInfoList

Array of GetTargetImageIdDetail objects

+

Array of GetTargetImageIdDetail objects

Image details.

+

Image details.

-
Table 3 GetTargetImageIdDetail

Parameter

+
- - - - - - - - - - - - - - - - - - - -
Table 3 GetTargetImageIdDetail

Parameter

Type

+

Type

Description

+

Description

id

+

id

String

+

String

ID of an image that can be upgraded.

+

ID of an image that can be upgraded.

displayName

+

displayName

String

+

String

Name of an image that can be upgraded.

+

Name of an image that can be upgraded.

imageDesc

+

imageDesc

String

+

String

Image description.

+

Image description.

datastoreType

+

datastoreType

String

+

String

Image engine type.

+

Image engine type.

datastoreVersion

+

datastoreVersion

String

+

String

Image engine version.

+

Image engine version.

priority

+

priority

Integer

+

Integer

Priority

+

Priority.

-

Request Example

GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/target/cross/images
+

Example Requests

GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/target/cross/images
 
 {
   "needUploadUpgradePlugin" : false,
   "imageInfoList" : [ ]
 }
-

Response Example

Status code: 200

-

The request is processed.

-
{
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
   "needUploadUpgradePlugin" : false,
   "imageInfoList" : [ ]
 }
-

Status Codes

-

Status Code

+

Status Codes

+
- - - - - - -

Status Code

Description

+

Description

200

+

200

The request is processed.

+

Request succeeded.

400

+

400

Invalid request. Modify the request directly and do not attempt to retry it.

+

Invalid request.

+

The client should not repeat the request without modifications.

403

+

403

The request is rejected. The server has received and understood the request, but refused to respond to it. Modify the request directly and do not attempt to retry it.

+

Request rejected.

+

The server has received the request and understood it, but the server refuses to respond to it. The client should not repeat the request without modifications.

-

Error Codes

For details, see Error Code.

+

Error Codes

See Error Codes.

diff --git a/docs/css/api-ref/ListLogsJob.html b/docs/css/api-ref/ListLogsJob.html new file mode 100644 index 00000000..33c70957 --- /dev/null +++ b/docs/css/api-ref/ListLogsJob.html @@ -0,0 +1,247 @@ + + +

Querying the Job List

+

Function

This API is used to query the job list in the logs of a cluster.

+
+

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/logs/records

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to query.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 2 Query Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

start

+

No

+

Integer

+

The start value of the query. The default value is 1, indicating that the query starts from the first task.

+

limit

+

No

+

Integer

+

Number of task to be queried. The default value is 10, indicating that the information about 10 tasks is queried at a time.

+

status

+

No

+

String

+

Specifies the status of the log task to be queried. If this parameter is not set, all log tasks of the cluster are queried.

+

FAIL: failed tasks

+

NOT_FAIL: ongoing or successful tasks

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 3 Response body parameters

Parameter

+

Type

+

Description

+

clusterLogRecord

+

Array of clusterLogRecord objects

+

Cluster log entity object.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 clusterLogRecord

Parameter

+

Type

+

Description

+

id

+

String

+

Log task ID, which is generated based on the system UUID.

+

clusterId

+

String

+

Cluster ID.

+

createAt

+

String

+

Creation time. Format: Unix timestamp.

+

logPath

+

String

+

Storage path of backed up logs in the OBS bucket.

+

status

+

String

+

Task status

+
  • RUNNING: The line is being backed up.

    +
  • SUCCESS: The backup succeeded.

    +
  • FAIL: The backup failed.

    +
+

finishedAt

+

Long

+

End time. If the creation has not been completed, the end time is null. Format: Unix timestamp.

+

jobTypes

+

String

+

Task type.

+
  • Manual: Manual backup.

    +
  • Auto: Automatic backup.

    +
+

failedMsg

+

String

+

Error information. If the task did not fail, the value of this parameter is null.

+

jobId

+

String

+

Task ID.

+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "clusterLogRecord" : [ {
+    "id" : "d455a541-597e-4846-a6be-baad0ea361b1",
+    "clusterId" : "4213d908-f5dc-4633-8401-cfd7175fca0c",
+    "createAt" : 1656042837000,
+    "logPath" : "css-backup-1610678043608/css/log",
+    "status" : "RUNNING",
+    "finishedAt" : null,
+    "jobTypes" : "Manual",
+    "failedMsg" : null,
+    "jobId" : "2c9080df7c171342017c5e0884f8011c"
+  } ]
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListSnapshots.html b/docs/css/api-ref/ListSnapshots.html new file mode 100644 index 00000000..b11dca24 --- /dev/null +++ b/docs/css/api-ref/ListSnapshots.html @@ -0,0 +1,347 @@ + + +

Querying a Snapshot List

+

Function

This API is used to query all the snapshots of a cluster.

+
+

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster whose snapshots you want to query.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 2 Response body parameters

Parameter

+

Type

+

Description

+

backups

+

Array of ListSnapshotBackupsResp objects

+

Snapshot list

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 ListSnapshotBackupsResp

Parameter

+

Type

+

Description

+

created

+

String

+

Snapshot creation time

+

datastore

+

ListSnapshotBackupsDatastoreResp object

+

Search engine

+

description

+

String

+

Snapshot description

+

id

+

String

+

Snapshot ID

+

clusterId

+

String

+

Cluster ID

+

clusterName

+

String

+

Cluster name

+

name

+

String

+

Snapshot name

+

status

+

String

+

Snapshot status

+

updated

+

String

+

Time when the snapshot was updated. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

+

backupType

+

String

+

Snapshot creation type. The options are as follows:

+
  • 0: Automatic creation.

    +
  • 1: Manual creation.

    +
+

backupMethod

+

String

+

Snapshot creation mode

+

backupExpectedStartTime

+

String

+

Snapshot start time

+

backupKeepDay

+

Integer

+

Snapshot retention period

+

backupPeriod

+

String

+

Time when a snapshot is created every day

+

indices

+

String

+

Index you want to back up

+

totalShards

+

Integer

+

Total number of shards of the index you want to back up

+

failedShards

+

Integer

+

Number of shards that fail to be backed up

+

version

+

String

+

Snapshot version

+

restoreStatus

+

String

+

Snapshot restoration status

+

startTime

+

Long

+

Snapshot start timestamp

+

endTime

+

Long

+

Snapshot end timestamp

+

bucketName

+

String

+

Name of the bucket that stores snapshot data

+
+
+ +
+ + + + + + + + + + + + + +
Table 4 ListSnapshotBackupsDatastoreResp

Parameter

+

Type

+

Description

+

type

+

String

+

Engine type. Currently, only Elasticsearch is supported.

+

version

+

String

+

Elasticsearch engine version. For details, see the supported versions in Before You Start.

+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "backups" : [ {
+    "created" : "2018-03-07T07:34:47",
+    "datastore" : {
+      "type" : "elasticsearch",
+      "version" : "x.x.x"
+    },
+    "description" : "",
+    "id" : "e29d99c1-3d19-4ea4-ae8d-f252df76cbe9",
+    "clusterId" : "37cb1075-c38e-4cd8-81df-442d52df3786",
+    "clusterName" : "Es-xfx",
+    "name" : "snapshot-002",
+    "status" : "COMPLETED",
+    "updated" : "2018-03-07T07:40:12",
+    "backupType" : "1",
+    "backupMethod" : "manual",
+    "backupExpectedStartTime" : null,
+    "backupKeepDay" : null,
+    "backupPeriod" : null,
+    "indices" : ".kibanawebsite2",
+    "totalShards" : 6,
+    "failedShards" : 0,
+    "version" : "x.x.x",
+    "restoreStatus" : "success",
+    "startTime" : 1520408087099,
+    "endTime" : 1520408412219,
+    "bucketName" : "obs-b8ed"
+  }, {
+    "created" : "2018-03-06T15:42:37",
+    "datastore" : {
+      "type" : "elasticsearch",
+      "version" : "x.x.x"
+    },
+    "description" : "",
+    "id" : "29a2254e-947f-4463-b65a-5f0b17515fae",
+    "clusterId" : "37cb1075-c38e-4cd8-81df-442d52df3786",
+    "clusterName" : "Es-xfx",
+    "name" : "snapshot-001",
+    "status" : "COMPLETED",
+    "updated" : "2018-03-06T15:48:04",
+    "backupType" : "1",
+    "backupMethod" : "manual",
+    "backupExpectedStartTime" : null,
+    "backupKeepDay" : null,
+    "backupPeriod" : null,
+    "indices" : ".kibana",
+    "totalShards" : 1,
+    "failedShards" : 0,
+    "version" : "x.x.x",
+    "restoreStatus" : "none",
+    "startTime" : 1520350957275,
+    "endTime" : 1520351284357,
+    "bucketName" : "obs-b8ed"
+  } ]
+}
+
+

Status Codes

+
+ + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

406

+

The server could not fulfill the request according to the content characteristics of the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListYmls.html b/docs/css/api-ref/ListYmls.html new file mode 100644 index 00000000..68babde7 --- /dev/null +++ b/docs/css/api-ref/ListYmls.html @@ -0,0 +1,144 @@ + + +

Obtaining the Parameter Configuration List

+

Function

This API is used to obtain the parameter configuration list of the current cluster.

+
+

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/template

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to query.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 2 Response body parameters

Parameter

+

Type

+

Description

+

configurations

+

Object

+

Cluster parameter configuration list. The key value in the object is subject to the actual situation. The value has the following attributes:

+
  • id: parameter ID.

    +
  • key: parameter name.

    +
  • value: parameter value.

    +
  • defaultValue: parameter default value.

    +
  • regex: parameter constraint.

    +
  • desc: parameter description.

    +
  • type: parameter type description.

    +
  • moduleDesc: parameter function description.

    +
  • modifyEnable: whether a parameter can be modified. true: The value can be changed. false: The value cannot be changed.

    +
  • enableValue: parameter value that can be changed.

    +
  • fileName: name of the file where parameters exist. The default value is elasticsearch.yml.

    +
  • version: version information.

    +
  • descENG: parameter description.

    +
  • moduleDescENG: parameter function description.

    +
+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "configurations" : {
+    "http.cors.allow-credentials" : {
+      "id" : "b462d13c-294b-4e0f-91d3-58be2ad02b99",
+      "key" : "http.cors.allow-credentials",
+      "value" : "false",
+      "defaultValue" : "false",
+      "regex" : "^(true|false)$",
+      "desc" : "Indicates whether to return **Access-Control-Allow-Credentials** in the header during cross-domain access. The value is of the Boolean type and can be **true** or **false**.",
+      "type" : "Boolean",
+      "moduleDesc" : "Cross-domain access",
+      "modifyEnable" : "true",
+      "enableValue" : "true,false",
+      "fileName" : "elasticsearch.yml",
+      "version" : null,
+      "descENG" : "Whether to return the Access-Control-Allow-Credentials of the header during cross-domain access. The value is a Boolean value and the options are true and false.",
+      "moduleDescENG" : "Cross-domain Access"
+    }
+  }
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ListYmlsJob.html b/docs/css/api-ref/ListYmlsJob.html new file mode 100644 index 00000000..e6ee2834 --- /dev/null +++ b/docs/css/api-ref/ListYmlsJob.html @@ -0,0 +1,216 @@ + + +

Obtaining the Task List of Parameter Configurations

+

Function

This API is used to obtain the parameter configuration task list of a cluster.

+
+

URI

GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/joblists

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to query.

+
+
+ +
+ + + + + + + + + + + + + + + + +
Table 2 Query Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

start

+

No

+

Integer

+

The start value of the query. The default value is 1, indicating that the query starts from the first task.

+

limit

+

No

+

Integer

+

Number of task to be queried. The default value is 10, indicating that the information about 10 tasks is queried at a time.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

Status code: 200

+ +
+ + + + + + + + + +
Table 3 Response body parameters

Parameter

+

Type

+

Description

+

configList

+

Array of configListRsp objects

+

List of historical configuration changes

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 configListRsp

Parameter

+

Type

+

Description

+

id

+

String

+

Operation ID.

+

clusterId

+

String

+

Cluster ID.

+

createAt

+

String

+

Creation time. Format: Unix timestamp.

+

status

+

String

+

Task execution status.

+
  • true: The operation is successful.

    +
  • false: The execution failed.

    +
+

finishedAt

+

String

+

End time. If the creation has not been completed, the end time is null. Format: Unix timestamp.

+

modifyDeleteReset

+

String

+

History of parameter setting modifications.

+

failedMsg

+

String

+

Returned error message. If the status is success, the value of this parameter is null.

+
+
+
+

Example Requests

None

+
+

Example Responses

Status code: 200

+

Request succeeded.

+
{
+  "configList" : [ {
+    "id" : "7ed7258a-60a8-46fe-8814-52819d491b80",
+    "clusterId" : "4213d908-f5dc-4633-8401-cfd7175fca0c",
+    "createAt" : 1633658735000,
+    "status" : "success",
+    "finishedAt" : null,
+    "modifyDeleteReset" : "{\"modify\":{\"elasticsearch.yml\":{\"thread_pool.force_merge.size\":\"1\"}}}",
+    "failedMsg" : ""
+  } ]
+}
+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/ResetPassword.html b/docs/css/api-ref/ResetPassword.html index 9673e1f9..c51a77d1 100644 --- a/docs/css/api-ref/ResetPassword.html +++ b/docs/css/api-ref/ResetPassword.html @@ -1,119 +1,119 @@ -

Changing a Password

-

Function

This API is used to change the password of a cluster.

+

Changing the Password of a Cluster

+

Function

This API is used to change the password of a cluster.

-

Calling Method

For details, see Calling APIs.

-
-

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/password/reset

+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/password/reset

-
Table 1 Path parameters

Parameter

+
- - - - - - - - - - -
Table 1 Path Parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

project_id

+

project_id

Yes

+

Yes

String

+

String

Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

cluster_id

+

cluster_id

Yes

+

Yes

String

+

String

ID of the cluster whose password you want to change.

+

ID of the cluster whose password you want to change.

-

Request Parameters

-
Table 2 Request body parameters

Parameter

+

Request Parameters

+
- - - - - - -
Table 2 Request body parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

newpassword

+

newpassword

Yes

+

Yes

String

+

String

Password of the cluster user admin in security mode. This API is available only when authorityEnable is set to true.

-
  • The value can contain 8 to 32 characters.
  • The value must contain at least 3 of the following character types: uppercase letters, lowercase letters, numbers, and special characters ~!@#$%&*()-_=|[{}];:,<.>/?
+

Password of the cluster user admin in security mode. This API is available only if authorityEnable is set to true.

+
  • Must contain 8 to 32 characters.

    +
  • Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^&*()-_=+\|[{}];:,<.>/?).

    +
-

Response Parameters

None

+

Response Parameters

None

-

Request Example

Change the administrator password of the current cluster.

-
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/password/reset
+

Example Requests

Change the administrator password of the current cluster.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/password/reset
 
 {
   "newpassword" : "xxxxxx"
 }
-

Response Example

None

+

Example Responses

None

-

Status Codes

-

Status Code

+

Status Codes

+
- - - - - - - - -

Status Code

Description

+

Description

200

+

200

The request is processed.

+

Request succeeded.

400

+

400

Invalid request.

-

Modify the request instead of retrying.

+

Invalid request.

+

Modify the request before retry.

409

+

409

The request cannot be processed due to a conflict.

-

This status code indicates that the resource the client is attempting to create already exists, or that the update operation requested cannot be completed due to a conflict.

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

412

+

412

The server did not satisfy one of the preconditions set by the requester in the request.

+

The server did not meet one of the preconditions contained in the request.

-

Error Codes

For details, see Error Code.

+

Error Codes

See Error Codes.

diff --git a/docs/css/api-ref/RestartCluster.html b/docs/css/api-ref/RestartCluster.html new file mode 100644 index 00000000..06de325e --- /dev/null +++ b/docs/css/api-ref/RestartCluster.html @@ -0,0 +1,84 @@ + + +

Restarting a Cluster

+

Function

This API is used to restart a cluster. Services will be interrupted during the restart.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/restart

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to restart.

+
+
+
+

Request Parameters

None

+
+

Response Parameters

None

+
+

Example Requests

None

+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

404

+

The requested resource could not be found.

+

Modify the request before retry.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/RestartClusterMultiRole.html b/docs/css/api-ref/RestartClusterMultiRole.html new file mode 100644 index 00000000..52a4a7c7 --- /dev/null +++ b/docs/css/api-ref/RestartClusterMultiRole.html @@ -0,0 +1,132 @@ + + +

Restarting a Cluster (V2)

+

Function

This API is used to restart nodes of all node types or the combination of some node types in the current cluster.

+
+

URI

POST /v2.0/{project_id}/clusters/{cluster_id}/restart

+ +
+ + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster you want to restart.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

type

+

Yes

+

String

+

Operation role. Value range:

+
  • node

    +
  • role

    +
+

value

+

Yes

+

String

+

Operation parameter. Parameter description:

+
  • If the operation role is node, the value is the node ID. You can obtain the ID attribute in instances by referring to Querying Cluster Details.

    +
  • If the operation role is role, the value is one or multiple node types (such as ess, ess-master, ess-client, and ess-cold).

    +
+
+
+
+

Response Parameters

None

+
+

Example Requests

Restart nodes of all or some types in the current cluster.

+
POST /v2.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/restart
+
+{
+  "type" : "role",
+  "value" : "ess"
+}
+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + + + + +

Status Code

+

Description

+

200

+

Request succeeded.

+

400

+

Invalid request.

+

Modify the request before retry.

+

409

+

The request could not be completed due to a conflict with the current state of the resource.

+

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

+

412

+

The server did not meet one of the preconditions contained in the request.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/RestoreSnapshot.html b/docs/css/api-ref/RestoreSnapshot.html new file mode 100644 index 00000000..95dad2e4 --- /dev/null +++ b/docs/css/api-ref/RestoreSnapshot.html @@ -0,0 +1,160 @@ + + +

Restoring a Snapshot

+

Function

This API is used to manually restore a snapshot.

+
+

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}/restore

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 Path Parameters

Parameter

+

Mandatory

+

Type

+

Description

+

project_id

+

Yes

+

String

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

+

cluster_id

+

Yes

+

String

+

ID of the cluster whose snapshot you want to restore.

+

snapshot_id

+

Yes

+

String

+

Snapshot ID.

+
+
+
+

Request Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Request body parameters

Parameter

+

Mandatory

+

Type

+

Description

+

targetCluster

+

Yes

+

String

+

ID of the cluster that a snapshot is to be restored to.

+

indices

+

No

+

String

+

Name of an index to be restored. Multiple indexes are separated by commas (,). By default, all indexes are restored. You can use the combination of a backslash and an asterisk (*) to back up data of certain indexes. For example, if you specify 2018-06*, then the data of the indexes with the prefix 2018-06 will be restored.The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and the following special characters are not allowed: "\<|>/?

+

renamePattern

+

No

+

String

+

Rule for defining the indexes to be restored. The value contains a maximum of 1,024 characters. Indexes that match this rule will be restored. The filtering condition must be a regular expression.

+

The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and the following special characters are not allowed: "\<|>/?

+

This parameter takes effect only when both renameReplacement and renamePattern are set.

+

renameReplacement

+

No

+

String

+

Rule for renaming an index. The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and the following special characters are not allowed: "\<|>/? For example, restored_index_$1 indicates adding the restored_ prefix to the names of all the restored indexes.The renamePattern and renameReplacement parameters must be set at the same time in order for them to take effect.

+

replace_exist_indices

+

No

+

Boolean

+

Replacing an existing index.

+
+
+
+

Response Parameters

None

+
+

Example Requests

Restore a snapshot.

+
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/index_snapshot/653c086f-ebe7-4383-b902-c031b354f1dd/restore
+
+{
+  "targetCluster" : "ea244205-d641-45d9-9dcb-ab2236bcd07e",
+  "indices" : "myindex1,myindex2",
+  "renamePattern" : "index",
+  "renameReplacement" : "restored_index_$1"
+}
+
+

Example Responses

None

+
+

Status Codes

+
+ + + + + + + + + + + + + +

Status Code

+

Description

+

201

+

Resource created.

+

400

+

Invalid request.

+

Modify the request before retry.

+

403

+

Request rejected.The server has received the request and understood it, but refused to respond to it. The client should not repeat the request without modifications.

+
+
+
+

Error Codes

See Error Codes.

+
+
+
+ +
+ diff --git a/docs/css/api-ref/RetryUpgradeTask.html b/docs/css/api-ref/RetryUpgradeTask.html index f3d78a01..a9f3e2c4 100644 --- a/docs/css/api-ref/RetryUpgradeTask.html +++ b/docs/css/api-ref/RetryUpgradeTask.html @@ -1,118 +1,120 @@

Retrying a Failed Upgrade Task

-

Function

The upgrade takes a long time and the upgrade may fail due to network problems. You can use this API to retry a task or terminate the impact of a task.

+

Function

The upgrade may fail due to network problems. In this case, you can call this API to retry.

-

Calling Method

For details, see Calling APIs.

-
-

URI

PUT /v1.0/{project_id}/clusters/{cluster_id}/upgrade/{action_id}/retry

+

URI

PUT /v1.0/{project_id}/clusters/{cluster_id}/upgrade/{action_id}/retry

-
Table 1 Path parameters

Parameter

+
- - - - - - - - - - - - - - -
Table 1 Path Parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

project_id

+

project_id

Yes

+

Yes

String

+

String

Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

+

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

cluster_id

+

cluster_id

Yes

+

Yes

String

+

String

ID of the cluster to be retried.

+

ID of the cluster to retry upgrade.

action_id

+

action_id

Yes

+

Yes

String

+

String

ID of the task to be retried.

+

ID of the task to be retried.

-
Table 2 Query parameters

Parameter

+
- - - - - - -
Table 2 Query Parameters

Parameter

Mandatory

+

Mandatory

Type

+

Type

Description

+

Description

retry_mode

+

retry_mode

No

+

No

String

+

String

If this parameter is not left blank, the impact of the task is terminated. Currently, only abort is supported.

+

Impact of terminating the task. Currently, its value can only be abort.

-

Request Parameters

None

+

Request Parameters

None

-

Response Parameters

None

+

Response Parameters

None

-

Request Example

  • Example request for retrying an upgrade task.
    PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/bcdb711c-a7f0-4007-b8ee-9f13c05f8326/retry
    -
  • Example request for terminating an upgrade task.
    PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/bcdb711c-a7f0-4007-b8ee-9f13c05f8326/retry?retry_mode=abort
    +

    Example Requests

    • Example of an upgrade task retry request.

      +
      PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/bcdb711c-a7f0-4007-b8ee-9f13c05f8326/retry
      +
    • Example of an upgrade task termination request.

      +
      PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/bcdb711c-a7f0-4007-b8ee-9f13c05f8326/retry?retry_mode=abort
    -

    Response Example

    None

    +

    Example Responses

    None

    -

    Status Codes

    -

    Status Code

    +

    Status Codes

    +
    - - - - - - -

    Status Code

    Description

    +

    Description

    200

    +

    200

    The request is processed.

    +

    Request succeeded.

    400

    +

    400

    Invalid request. Modify the request directly and do not attempt to retry it.

    +

    Invalid request.

    +

    The client should not repeat the request without modifications.

    403

    +

    403

    The request is rejected. The server has received and understood the request, but refused to respond to it. Modify the request directly and do not attempt to retry it.

    +

    Request rejected.

    +

    The server has received the request and understood it, but the server refuses to respond to it. The client should not repeat the request without modifications.

    -

    Error Codes

    For details, see Error Code.

    +

    Error Codes

    See Error Codes.

    diff --git a/docs/css/api-ref/RollingRestart.html b/docs/css/api-ref/RollingRestart.html new file mode 100644 index 00000000..24e9ecd3 --- /dev/null +++ b/docs/css/api-ref/RollingRestart.html @@ -0,0 +1,132 @@ + + +

    Rolling Restart

    +

    Function

    This API is used to restart nodes one by one, which requires a long time when the nodes have a large number of indexes.

    +
    +

    URI

    POST /v2.0/{project_id}/clusters/{cluster_id}/rolling_restart

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to restart.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    type

    +

    Yes

    +

    String

    +

    Operation role. Its type can only be role.

    +

    value

    +

    Yes

    +

    String

    +

    Instance type. (At least one data node is required when you configure instance types.) Use commas (,) to separate multiple types. For example:

    +
    • ess-master indicates a master node.

      +
    • ess-client indicates a client node.

      +
    • ess-cold indicates a cold data node.

      +
    • ess indicates a data node.

      +
    • all indicates all nodes.

      +
    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Restart a node.

    +
    POST /v2.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/rolling_restart
    +
    +{
    +  "type" : "role",
    +  "value" : "ess"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/ShowAutoCreatePolicy.html b/docs/css/api-ref/ShowAutoCreatePolicy.html new file mode 100644 index 00000000..759c4421 --- /dev/null +++ b/docs/css/api-ref/ShowAutoCreatePolicy.html @@ -0,0 +1,159 @@ + + +

    Querying the Automatic Snapshot Creation Policy

    +

    Function

    This API is used to query the automatic snapshot creation policy.

    +
    +

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster where snapshots are to be automatically created.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    keepday

    +

    Integer

    +

    Customize the number of snapshots to be retained.

    +

    period

    +

    String

    +

    Time when a snapshot is created every day.

    +

    prefix

    +

    String

    +

    Snapshot name prefix, which needs to be manually entered.

    +

    bucket

    +

    String

    +

    Name of the OBS bucket where snapshots are stored.

    +

    basePath

    +

    String

    +

    Storage path of the snapshot in the OBS bucket.

    +

    agency

    +

    String

    +

    Agency used to access OBS buckets.

    +

    enable

    +

    String

    +

    Whether to enable the automatic snapshot creation policy.

    +
    • true: The automatic snapshot creation policy is enabled.

      +
    • false: The automatic snapshot creation policy is disabled.

      +
    +

    frequency

    +

    String

    +

    Frequency of automatically creating snapshots.

    +
    +
    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "keepday" : 2,
    +  "frequency" : "DAY",
    +  "period" : "16:00 GMT+08:00",
    +  "prefix" : "snapshot",
    +  "bucket" : "es-backup",
    +  "basePath" : "css_repository/tests",
    +  "agency" : "usearch",
    +  "enable" : "true"
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    406

    +

    The server could not fulfill the request according to the content characteristics of the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/ShowClusterDetail.html b/docs/css/api-ref/ShowClusterDetail.html index 9063e2e0..2c19b38b 100644 --- a/docs/css/api-ref/ShowClusterDetail.html +++ b/docs/css/api-ref/ShowClusterDetail.html @@ -1,593 +1,688 @@

    Querying Cluster Details

    -

    Function

    This API is used to query and display details about a cluster.

    +

    Function

    This API is used to query and display the details of a cluster.

    -

    Debugging

    You can debug this API in . Automatic authentication is supported.

    -
    -

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}

    +

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}

    -
    Table 1 Path parameters

    Parameter

    +
    - - - - - - - - - - -
    Table 1 Path Parameters

    Parameter

    Mandatory

    +

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    project_id

    +

    project_id

    Yes

    +

    Yes

    String

    +

    String

    Project ID. For details, see Obtaining a Project ID and Name.

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    cluster_id

    +

    cluster_id

    Yes

    +

    Yes

    String

    +

    String

    ID of the cluster to be queried

    +

    ID of the cluster you want to query.

    -

    Request Parameters

    None

    +

    Request Parameters

    None

    -

    Response Parameters

    Status code: 200

    +

    Response Parameters

    Status code: 200

    -
    Table 2 Response body parameter

    Parameter

    +
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + +
    Table 2 Response body parameters

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    datastore

    +

    datastore

    ClusterDetailDatastore object

    +

    ClusterDetailDatastore object

    Search engine type

    +

    Search engine.

    instances

    +

    instances

    Array of ClusterDetailInstances objects

    +

    Array of ClusterDetailInstances objects

    Node object list

    +

    List of node objects.

    publicKibanaResp

    +

    publicKibanaResp

    publicKibanaRespBody object

    +

    publicKibanaRespBody object

    Kibana public network access information

    +

    Kibana public network access information.

    elbWhiteList

    +

    elbWhiteList

    elbWhiteListResp object

    +

    elbWhiteListResp object

    Public network access information

    +

    Public network access information.

    updated

    +

    updated

    String

    +

    String

    Last modification time of a cluster. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

    +

    Last modification time of a cluster. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

    name

    +

    name

    String

    +

    String

    Cluster name

    +

    Cluster name

    publicIp

    +

    publicIp

    String

    +

    String

    Public IP address

    +

    Public IP address and port number.

    created

    +

    created

    String

    +

    String

    Time when a cluster is created. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

    +

    Cluster creation time. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

    id

    +

    id

    String

    +

    String

    Cluster ID.

    +

    Cluster ID.

    status

    +

    status

    String

    +

    String

    Cluster status.

    -
    • 100: The operation, such as instance creation, is in progress.
    • 200: The cluster is available.
    • 303: The cluster is unavailable.
    +

    Cluster status.

    +
    • 100: An operation, such as creation, is in progress.

      +
    • 200: Available.

      +
    • 303: Unavailable, for example, due to a creation failure.

      +

    endpoint

    +

    endpoint

    String

    +

    String

    IP address and port number for accessing VPC

    +

    IPv4 address and port number accessed from the cluster's private network. [If the cluster type is KooSearch, this field indicates the internal address and port number for accessing the knowledge management service.] (tag:white)

    vpcId

    +

    vpcId

    String

    +

    String

    VPC ID.

    +

    VPC ID

    subnetId

    +

    subnetId

    String

    +

    String

    Subnet ID.

    +

    Subnet ID

    securityGroupId

    +

    securityGroupId

    String

    +

    String

    Security group ID

    +

    Security group ID.

    vpcepIp

    +

    vpcepIp

    String

    +

    String

    VPC endpoint IP address

    +

    Endpoint IP address.

    bandwidthSize

    +

    vpcepIpv6Address

    Integer

    +

    String

    Public network bandwidth Unit: Mbit/s

    +

    IPv6 address of the VPC endpoint.

    httpsEnable

    +

    bandwidthSize

    Boolean

    +

    Integer

    Communication encryption status.

    -
    • Value false indicates that communication encryption is not enabled.
    • true: communication encryption has been enabled.
    +

    Public network bandwidth. Unit: Mbit/s

    diskEncrypted

    +

    httpsEnable

    Boolean

    +

    Boolean

    Indicates whether disks are encrypted.

    -
    • Value true indicates that disks are encrypted.
    • false: disks are not encrypted.
    +

    Communication encryption status.

    +
    • false: Communication encryption is not enabled.

      +
    • true: Communication encryption is enabled.

      +

    authorityEnable

    +

    diskEncrypted

    Boolean

    +

    Boolean

    Indicates whether to enable authentication. The value can be true or false. Authentication is disabled by default.

    -
    • true: authentication is enabled for the cluster.
    • false: authentication is disabled for the cluster.
    +

    Whether disks are encrypted.

    +
    • true: Disks are encrypted.

      +
    • false: Disk are not encrypted.

      +

    backupAvailable

    +

    authorityEnable

    Boolean

    +

    Boolean

    Indicates whether the snapshot function is enabled.

    -
    • true: The snapshot function is enabled.
    • false: The snapshot function is disabled.
    +

    Whether to enable authentication. The value can be true or false. Authentication is disabled by default.

    +
    • true: Authentication is enabled for the cluster.

      +
    • false: Authentication is not enabled for the cluster.

      +

    actionProgress

    +

    backupAvailable

    Object

    +

    Boolean

    Cluster operation progress, which displays the progress of cluster creation or scale-out in percentage.

    +

    Whether the snapshot function is enabled.

    +
    • true: The snapshot function is enabled.

      +
    • false: The snapshot function is disabled.

      +

    actions

    +

    actionProgress

    Array of strings

    +

    Object

    Current behavior of a cluster. The value can be REBOOTING, GROWING, RESTORING, and SNAPSHOTTING.

    +

    Cluster behavior progress, which shows the progress of cluster creation and scaling in percentage.

    enterpriseProjectId

    +

    actions

    String

    +

    Array of strings

    ID of the enterprise project to which a cluster belongs.

    -

    If the user of the cluster does not enable the enterprise project, the setting of this parameter is not returned.

    +

    Current behavior of a cluster. REBOOTING indicates that the cluster is being restarted. GROWING indicates that the cluster is being scaled. RESTORING indicates that the cluster is being restored. SNAPSHOTTING indicates that a snapshot is being created.

    tags

    +

    enterpriseProjectId

    Array of ClusterDetailTags objects

    +

    String

    Cluster tag

    +

    ID of the enterprise project that a cluster belongs to.

    +

    If the user of the cluster does not enable the enterprise project, the setting of this parameter is not returned.

    failedReason

    +

    tags

    ClusterDetailFailedReasons object

    +

    Array of ClusterDetailTags objects

    Failure cause. If the cluster is in the Available state, this parameter is not returned.

    +

    Cluster tag.

    +

    failedReason

    +

    ClusterDetailFailedReasons object

    +

    Failure cause. If the cluster is in the available status, this parameter is not returned.

    +

    bandwidthResourceId

    +

    String

    +

    ID of the resource accessible from the public network.

    +

    ipv6Endpoint

    +

    String

    +

    IPv6 address and port number accessible from the cluster's private network.

    +

    supportVpcep

    +

    Boolean

    +

    Whether the VPCEP service can be enabled for the current cluster.

    -
    Table 3 ClusterDetailDatastore

    Parameter

    +
    - - - - - - - - + + + + + + + + + + + +
    Table 3 ClusterDetailDatastore

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    type

    +

    type

    String

    +

    String

    Engine type. Currently, only Elasticsearch is supported.

    +

    Engine type. Its value can be elasticsearch or logstash.

    version

    +

    version

    String

    +

    String

    CSS cluster engine version. For details, see Supported Cluster Versions.

    +

    Version of the CSS cluster engine. For details, see the supported versions in Before You Start.

    +

    supportSecuritymode

    +

    Boolean

    +

    The security mode is supported.

    +

    subVersion

    +

    String

    +

    Cluster image version.

    +

    isEosCluster

    +

    Boolean

    +

    Whether the cluster image version has reached EOS. The value can be true or false.

    -
    Table 4 ClusterDetailInstances

    Parameter

    +
    - - - - - - - - - - - - - - - - - - - - - - - - - - + + + +
    Table 4 ClusterDetailInstances

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    status

    +

    status

    String

    +

    String

    Node status value.

    -
    • 100: The operation, such as instance creation, is in progress.
    • 200: The cluster is available.
    • 303: The cluster is unavailable.
    +

    Node status value.

    +
    • 100: An operation, such as creation, is in progress.

      +
    • 200: Available.

      +
    • 303: Unavailable, for example, due to a creation failure.

      +

    type

    +

    resourceId

    String

    +

    String

    Node type

    +

    Instance resource ID

    id

    +

    type

    Integer

    +

    String

    Instance ID

    +

    Type of the current node.

    name

    +

    id

    String

    +

    String

    Instance name

    +

    Instance ID.

    specCode

    +

    name

    String

    +

    String

    Node specifications.

    +

    Instance name.

    azCode

    +

    specCode

    String

    +

    String

    AZ to which a node belongs.

    +

    Node specifications.

    ip

    +

    azCode

    String

    +

    String

    Instance IP address

    +

    AZ of a node.

    volume

    +

    privateIp

    ShowClusterVolumeRsp object

    +

    String

    Instance disk information

    +

    Instance IP address.

    +

    volume

    +

    ShowClusterVolumeRsp object

    +

    Instance disk information

    -
    Table 5 ShowClusterVolumeRsp

    Parameter

    +
    - - - - - - - - + + + +
    Table 5 ShowClusterVolumeRsp

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    type

    +

    type

    String

    +

    String

    Instance disk type

    +

    Instance disk type

    size

    +

    size

    Integer

    +

    Integer

    Instance disk size

    +

    Instance disk size

    +

    resourceIds

    +

    Array of strings

    +

    Instance disk resource ID

    -
    Table 6 publicKibanaRespBody

    Parameter

    +
    - - - - - - - - - - - + + + +
    Table 6 publicKibanaRespBody

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    eipSize

    +

    eipSize

    Integer

    +

    Integer

    Bandwidth. Unit: Mbit/s

    +

    Bandwidth range. Unit: Mbit/s

    elbWhiteListResp

    +

    elbWhiteListResp

    kibanaElbWhiteListResp object

    +

    kibanaElbWhiteListResp object

    Kibana public network access information

    +

    Kibana public network access information.

    publicKibanaIp

    +

    publicKibanaIp

    String

    +

    String

    Kibana access IP address

    +

    Specifies the IP address for accessing Kibana.

    +

    bandwidthResourceId

    +

    String

    +

    Resource ID corresponding to the Kibana public network

    -
    Table 7 kibanaElbWhiteListResp

    Parameter

    +
    - - - - - - - -
    Table 7 kibanaElbWhiteListResp

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    enableWhiteList

    +

    enableWhiteList

    Boolean

    +

    Boolean

    Indicates whether access control is enabled.

    -
    • true: Access control is enabled.
    • false: Access control is disabled.
    +

    Whether the Kibana access control is enabled.

    +
    • true: Access control is enabled.

      +
    • false: Access control is disabled.

      +

    whiteList

    +

    whiteList

    String

    +

    String

    Whitelist for Kibana public network access

    +

    Whitelist of public network for accessing Kibana.

    -
    Table 8 elbWhiteListResp

    Parameter

    +
    - - - - - - - -
    Table 8 elbWhiteListResp

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    enableWhiteList

    +

    enableWhiteList

    Boolean

    +

    Boolean

    Indicates whether public access control is enabled.

    -
    • true: Public network access control is enabled.
    • false: Public network access control is disabled.
    +

    Whether the public network access control is enabled.

    +
    • true: Public network access control is enabled.

      +
    • false: Public network access control is disabled.

      +

    whiteList

    +

    whiteList

    String

    +

    String

    Whitelist for public network access

    +

    Whitelist for public network access.

    -
    Table 9 ClusterDetailTags

    Parameter

    +
    - - - - - - - -
    Table 9 ClusterDetailTags

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    key

    +

    key

    String

    +

    String

    Tag key.

    +

    Tag key.

    value

    +

    value

    String

    +

    String

    Tag value

    +

    Tag value.

    -
    Table 10 ClusterDetailFailedReasons

    Parameter

    +
    - - - - - - - -
    Table 10 ClusterDetailFailedReasons

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    errorCode

    +

    errorCode

    String

    +

    String

    Error code.

    -
    • CSS.6000: failed to create a cluster.
    • CSS.6001: failed to scale out a cluster.
    • CSS.6002: failed to restart a cluster.
    • CSS.6004: failed to create a node.
    • CSS.6005: failed to initialize the service.
    +

    Error code.

    +
    • CSS.6000: A cluster fails to be created.

      +
    • CSS.6001: A cluster fails to be scaled out.

      +
    • CSS.6002: A cluster fails to be restarted.

      +
    • CSS.6004: A node fails to be created in a cluster.

      +
    • CSS.6005: A service fails to be initialized.

      +

    errorMsg

    +

    errorMsg

    String

    +

    String

    Detailed error information

    +

    Error details.

    -

    Request Example

    None

    +

    Example Requests

    None

    -

    Response Example

    Status code: 200

    -

    The request is processed successfully.

    -
    {
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
       "datastore" : {
         "type" : "elasticsearch",
    -    "version" : "x.x.x"
    +    "version" : "7.10.2",
    +    "subVersion" : "7.10.2_24.3.0_0827",
    +    "isEosCluster" : false,
    +    "supportSecuritymode" : false
       },
       "instances" : [ {
         "status" : "200",
         "type" : "ess",
    -    "id" : "3c7fe582-a9f6-46fd-9d01-956bed4a8bbc",
    -    "name" : "ES-xx",
    -    "specCode" : "css.xlarge.2",
    -    "azCode" : "xx-xxx-xx",
    -    "ip" : "192.168.0.x",
    +    "id" : "{INSTANCE_ID}",
    +    "name" : "css-8bc5-ess-esn-1-1",
    +    "specCode" : "ess.spec-4u8g",
    +    "azCode" : "{AZ_CODE}",
         "volume" : {
    -      "type" : "COMMON",
    -      "size" : 40
    -    }
    +      "type" : "ULTRAHIGH",
    +      "size" : 40,
    +      "resourceIds" : [ "{RESOURCE_ID}" ]
    +    },
    +    "privateIp" : "192.168.0.122",
    +    "resourceId" : "{RESOURCE_ID}"
       } ],
       "publicKibanaResp" : {
    -    "eipSize" : 5,
    -    "publicKibanaIp" : "100.95.158.x",
    -    "elbWhiteListResp" : {
    -      "whiteList" : "11.11.11.11",
    -      "enableWhiteList" : true
    -    }
    +    "eipSize" : 10,
    +    "publicKibanaIp" : "100.95.152.28",
    +    "elbWhiteListResp" : null,
    +    "bandwidthResourceId" : "18bec13f-5cc1-4631-867f-33505d15be12"
       },
    -  "updated" : "2018-01-16T08:37:18",
    -  "name" : "ES-xx",
    -  "publicIp" : "100.95.149.xx:9200",
       "elbWhiteList" : {
    -    "whiteList" : "10.10.10.10",
    -    "enableWhiteList" : true
    +    "whiteList" : "",
    +    "enableWhiteList" : false
       },
    -  "created" : "2018-01-16T08:37:18",
    -  "id" : "5c77b71c-5b35-4f50-8984-76387e42451a",
    +  "updated" : "2023-10-09T02:07:13",
    +  "name" : "css-8bc5",
    +  "publicIp" : "100.85.222.202",
    +  "created" : "2023-10-09T02:07:13",
    +  "id" : "{CLUSTER_ID}",
       "status" : "200",
    -  "endpoint" : "192.168.0.x:9200",
    -  "vpcId" : "07e7ab39-xxx-xxx-xxx-d3f28ea7f051",
    -  "subnetId" : "025d45f9-xxx-xxx-xxx-e852c6455a5e",
    -  "securityGroupId" : "0347aabc-xxx-xxx-xxx-6b10a79701e2",
    -  "vpcepIp" : "192.168.0.203",
    -  "bandwidthSize" : 0,
    -  "diskEncrypted" : false,
    +  "endpoint" : "192.168.0.122:9200",
    +  "vpcId" : "{VPC_ID}",
    +  "subnetId" : "{SUBNET_ID}",
    +  "securityGroupId" : "{SECURITY_GROUP_ID}",
    +  "bandwidthResourceId" : "{BANDWIDTH_RESOURCE_ID}",
    +  "bandwidthSize" : 3,
       "httpsEnable" : true,
       "authorityEnable" : true,
    -  "backupAvailable" : true,
    +  "diskEncrypted" : false,
    +  "backupAvailable" : false,
       "actionProgress" : { },
       "actions" : [ ],
    -  "enterpriseProjectId" : "3e1c74a0-xxx-xxx-xxx-c6b9e46cf81b",
    -  "tags" : [ {
    -    "key" : "k1",
    -    "value" : "v1"
    -  } ]
    +  "enterpriseProjectId" : "0",
    +  "tags" : [ ],
    +  "period" : true,
    +  "supportVpcep" : true
     }
    -

    Status Codes

    -

    Status Code

    +

    Status Codes

    +
    - - - - - - -

    Status Code

    Description

    +

    Description

    200

    +

    200

    The request is processed.

    +

    Request succeeded.

    400

    +

    400

    Invalid request.

    -

    Modify the request instead of retrying.

    +

    Invalid request.

    +

    Modify the request before retry.

    404

    +

    404

    The requested resource cannot be found.

    -

    Modify the request instead of retrying.

    +

    The requested resource could not be found.

    +

    Modify the request before retry.

    +

    Error Codes

    See Error Codes.

    +
    diff --git a/docs/css/api-ref/ShowClusterTag.html b/docs/css/api-ref/ShowClusterTag.html new file mode 100644 index 00000000..3b2a1486 --- /dev/null +++ b/docs/css/api-ref/ShowClusterTag.html @@ -0,0 +1,148 @@ + + +

    Querying Tags of a Specified Cluster

    +

    Function

    This API is used to query the tags of a specified cluster.

    +
    +

    URI

    GET /v1.0/{project_id}/{resource_type}/{cluster_id}/tags

    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to query.

    +

    resource_type

    +

    Yes

    +

    String

    +

    Resource type. Currently, its value can only be css-cluster.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + +
    Table 2 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    tags

    +

    Array of ShowTagsTagsResp objects

    +

    List of cluster tags

    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 ShowTagsTagsResp

    Parameter

    +

    Type

    +

    Description

    +

    key

    +

    String

    +

    Tag key

    +

    value

    +

    String

    +

    Tag value

    +
    +
    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "tags" : [ {
    +    "key" : "key1",
    +    "value" : "value1"
    +  }, {
    +    "key" : "key2",
    +    "value" : "value3"
    +  } ]
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    The client should modify the request instead of re-initiating it.

    +

    404

    +

    The requested resource could not be found.

    +

    The client should not repeat the request without modifications.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/ShowElbDetail.html b/docs/css/api-ref/ShowElbDetail.html new file mode 100644 index 00000000..b494f89a --- /dev/null +++ b/docs/css/api-ref/ShowElbDetail.html @@ -0,0 +1,482 @@ + + +

    Obtaining the ES ELB Information and Displaying the Health Check Status

    +

    Function

    This API is used to obtain the ELB information and health check status of an Elasticsearch cluster.

    +
    +

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}/es-listeners

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to query.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    serverCertName

    +

    String

    +

    Server certificate name

    +

    serverCertId

    +

    String

    +

    Server certificate ID

    +

    cacertName

    +

    String

    +

    CA certificate name

    +

    cacertId

    +

    String

    +

    CA certificate ID

    +

    elb_enable

    +

    Boolean

    +

    Indicates whether ELB is enabled.

    +

    authentication_type

    +

    String

    +

    Authentication mode

    +

    loadBalancer

    +

    LoadBalancer object

    +

    Load balancer object information

    +

    listener

    +

    Elbv3Listener object

    +

    Listener object information.

    +

    healthmonitors

    +

    Array of Member objects

    +

    Health check result set

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 3 LoadBalancer

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    Load balancer ID.

    +

    name

    +

    String

    +

    Load balancer name

    +

    guaranteed

    +

    String

    +

    Whether the LB is for dedicated use. The value can be false (shared) or true (dedicated).

    +

    billing_info

    +

    String

    +

    Resource billing information. If the value is left blank, the resource will be billed in pay-per-use mode. If the value is not left blank, the resource is billed on a yearly/monthly basis.

    +

    description

    +

    String

    +

    Description.

    +

    vpc_id

    +

    String

    +

    ID of the VPC to which the load balancer belongs

    +

    provisioning_status

    +

    String

    +

    Provisioning status of the load balancer

    +

    listeners

    +

    Array of IdListWrapper objects

    +

    Associated listener list

    +

    vip_address

    +

    String

    +

    IPv4 virtual IP address bound to the load balancer

    +

    vip_port_id

    +

    String

    +

    Port ID bound to the private IPv4 IP address of the load balancer.

    +

    ipv6_vip_address

    +

    String

    +

    IPv6 address of the load balancer.

    +

    publicips

    +

    Array of PublicIpInfo objects

    +

    EIP bound to the load balancer

    +
    +
    + +
    + + + + + + + + + +
    Table 4 IdListWrapper

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    Listener id.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + +
    Table 5 PublicIpInfo

    Parameter

    +

    Type

    +

    Description

    +

    publicip_id

    +

    String

    +

    EIP configuration ID

    +

    publicip_address

    +

    String

    +

    Specifies the EIP.

    +

    ip_version

    +

    Integer

    +

    IP address version. Value range: 4 and 6. 4 indicates IPv4, and 6 indicates IPv6.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 6 Elbv3Listener

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    Listener ID.

    +

    name

    +

    String

    +

    Listener name.

    +

    protocol

    +

    String

    +

    Protocol used by the listener

    +

    protocol_port

    +

    Integer

    +

    Port used by the listener.

    +

    ipgroup

    +

    ListenerIpGroup object

    +

    ipgroup information in the listener object.

    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 7 ListenerIpGroup

    Parameter

    +

    Type

    +

    Description

    +

    ipgroup_id

    +

    String

    +

    ID of the IP address group associated with the listener This parameter is mandatory during creation and is optional during update.

    +

    enable_ipgroup

    +

    Boolean

    +

    Status of an access control group. True: Enable access control. False: Disable access control.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 8 Member

    Parameter

    +

    Type

    +

    Description

    +

    name

    +

    String

    +

    Specifies the backend server name.

    +

    address

    +

    String

    +

    Private IP address bound to the backend server.

    +

    protocol_port

    +

    Integer

    +

    Specifies the port used by the backend server.

    +

    operating_status

    +

    String

    +

    Specifies the operating status of the backend server. - ONLINE: The backend server is running normally. - NO_MONITOR: No health check is configured for the backend server group to which the backend server belongs. - OFFLINE: The cloud server used as the backend server is stopped or does not exist.

    +

    instance_id

    +

    String

    +

    ID of the instance used as the backend server. If this parameter is left blank, the backend server is not an ECS.

    +
    +
    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "loadBalancer" : {
    +    "id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6268",
    +    "name" : "elb-css",
    +    "guaranteed" : "true",
    +    "description" : "",
    +    "listeners" : [ {
    +      "id" : "011d14fa-908b-4cd9-b0d6-0768ddc6cb71"
    +    }, {
    +      "id" : "04b86029-c281-4490-a3bd-5ea1266658ba"
    +    } ],
    +    "publicips" : [ {
    +      "publicip_id" : "f678e23c-96a5-49e8-8ea2-bd8b47d41e78",
    +      "publicip_address" : "100.1.1.1",
    +      "ip_version" : 4
    +    } ],
    +    "billing_info" : null,
    +    "vpc_id" : "4f3deec3-efa8-4598-bf91-560aad1377a3",
    +    "provisioning_status" : "ACTIVE",
    +    "vip_address" : "10.0.0.1",
    +    "ipv6_vip_address" : "2409:27ff:2003:3e:1fd::f3"
    +  },
    +  "listener" : {
    +    "id" : "41ff041d-c7b9-4142-9167-fa93d54f97da",
    +    "name" : "css-searchServer",
    +    "protocol" : "HTTPS",
    +    "ipgroup" : null,
    +    "protocol_port" : 9265
    +  },
    +  "healthmonitors" : [ {
    +    "instance_id" : "bac86342-2222-43e6-817f-57f040a174a6",
    +    "name" : "",
    +    "address" : "10.0.0.87",
    +    "protocol_port" : 9200,
    +    "operating_status" : "ONLINE"
    +  }, {
    +    "instance_id" : "d935b82c-f94b-4ae0-9997-ddc90885d8c6",
    +    "name" : "",
    +    "address" : "10.0.0.61",
    +    "protocol_port" : 9200,
    +    "operating_status" : "ONLINE"
    +  } ],
    +  "serverCertName" : "server1",
    +  "serverCertId" : "82375af01c0d40f6a44c15962c570625",
    +  "cacertName" : null,
    +  "cacertId" : null,
    +  "elb_enable" : true,
    +  "authentication_type" : "single"
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request instead of retrying.

    +

    409

    +

    The request cannot be processed due to a conflict.

    +

    This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

    +

    412

    +

    The server does not meet one of the requirements that the requester puts on the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/ShowGetLogSetting.html b/docs/css/api-ref/ShowGetLogSetting.html new file mode 100644 index 00000000..8341e677 --- /dev/null +++ b/docs/css/api-ref/ShowGetLogSetting.html @@ -0,0 +1,318 @@ + + +

    Querying Basic Log Configurations

    +

    Function

    This API is used to query basic log configurations.

    +
    +

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}/logs/settings

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to query.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 2 Query Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    action

    +

    No

    +

    String

    +

    The action can be base_log_collect or real_time_log_collect. base indicates the historical capability, and real_time indicates the real-time collection capability. If this parameter is not passed, base is used by default, which is compatible with the previous logic.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + + + + + +
    Table 3 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    logConfiguration

    +

    logConfiguration object

    +

    Log configuration entity object.

    +

    realTimeLogCollectRecord

    +

    realTimeLogCollect object

    +

    Configure real-time log collection.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 4 logConfiguration

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    Log backup ID, which is generated using the system UUID.

    +

    clusterId

    +

    String

    +

    Cluster ID.

    +

    obsBucket

    +

    String

    +

    Name of the OBS bucket for storing logs.

    +

    agency

    +

    String

    +

    Agency name. You can create an agency to allow CSS to call other cloud services.

    +

    updateAt

    +

    Long

    +

    Update time. Format: Unix timestamp.

    +

    basePath

    +

    String

    +

    Storage path of backed up logs in the OBS bucket.

    +

    autoEnable

    +

    Boolean

    +

    Whether to enable automatic backup.

    +
    • true: Automatic backup is enabled.

      +
    • false: Automatic backup is disabled.

      +
    +

    period

    +

    String

    +

    Start time of automatic log backup. If autoEnable is set to false, the value of this parameter is null. Format: GMT

    +

    logSwitch

    +

    Boolean

    +

    Whether to enable the log function.

    +
    • true: The log function is enabled.

      +
    • false: The log function is disabled.

      +
    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 5 realTimeLogCollect

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    Log collection ID, which is generated using the system UUID.

    +

    clusterId

    +

    String

    +

    Cluster ID

    +

    indexPrefix

    +

    String

    +

    Prefix of the index for saving logs.

    +

    keepDays

    +

    Integer

    +

    Log retention duration.

    +

    targetClusterId

    +

    String

    +

    ID of the target cluster where logs are saved.

    +

    status

    +

    String

    +

    Status of a real-time log collection task.

    +

    createAt

    +

    Long

    +

    Start time of a real-time log collection task.

    +

    updateAt

    +

    Long

    +

    Update time of a real-time log collection task.

    +
    +
    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    • Example response to a real-time log collection request.

      +
      {
      +  "logConfiguration" : null,
      +  "realTimeLogCollectRecord" : {
      +    "id" : "17939b7b-5a93-4ca5-8d3c-b9f2d0e715b4",
      +    "clusterId" : "e3201ceb-1a3e-49f3-bb2f-23a816440b20",
      +    "keepDays" : 30,
      +    "updateAt" : 1717666418870,
      +    "createAt" : 1717666405897,
      +    "targetClusterId" : "8c19644b-f2ef-44fc-abef-230a4c578ce7",
      +    "indexPrefix" : "aaa",
      +    "status" : "200"
      +  }
      +}
      +
    • Example response to a log backup request.

      +
      {
      +  "logConfiguration" : {
      +    "id" : "00032118-aff5-40e8-b19a-dd4bb576e572",
      +    "clusterId" : "e3201ceb-1a3e-49f3-bb2f-23a816440b20",
      +    "obsBucket" : "css-autobk-notdel-cn-north-7",
      +    "agency" : "css_obs_agency",
      +    "updateAt" : 1639624882000,
      +    "basePath" : "css/log",
      +    "autoEnable" : false,
      +    "period" : null,
      +    "logSwitch" : false
      +  },
      +  "realTimeLogCollectRecord" : null
      +}
      +
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/ShowLogBackup.html b/docs/css/api-ref/ShowLogBackup.html new file mode 100644 index 00000000..f7eec555 --- /dev/null +++ b/docs/css/api-ref/ShowLogBackup.html @@ -0,0 +1,196 @@ + + +

    Searching for Logs

    +

    Function

    This API is used to query log information.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/logs/search

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to query.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    instanceName

    +

    Yes

    +

    String

    +

    Node name. Obtain the name attribute in instances by referring to Querying Cluster Details.

    +

    level

    +

    Yes

    +

    String

    +

    Log level. The levels of logs that can be queried are INFO, ERROR, DEBUG, and WARN.

    +

    logType

    +

    Yes

    +

    String

    +

    Log type. The types of logs that can be queried are deprecation, indexingSlow, searchSlow, and instance.

    +
    +
    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + +
    Table 3 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    logList

    +

    Array of logList objects

    +

    Log list.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + +
    Table 4 logList

    Parameter

    +

    Type

    +

    Description

    +

    content

    +

    String

    +

    Log content.

    +

    date

    +

    String

    +

    Date.

    +

    level

    +

    String

    +

    Log level.

    +
    +
    +
    +

    Example Requests

    Query logs.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/logs/search
    +
    +{
    +  "instanceName" : "css-4312-ess-esn-1-1",
    +  "level" : "INFO",
    +  "logType" : "instance"
    +}
    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "logList" : [ {
    +    "content" : "xxxxxx",
    +    "date" : "2021-10-08T03:55:54,718",
    +    "level" : "INFO"
    +  } ]
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/ShowVpcepConnection.html b/docs/css/api-ref/ShowVpcepConnection.html new file mode 100644 index 00000000..34c7ff19 --- /dev/null +++ b/docs/css/api-ref/ShowVpcepConnection.html @@ -0,0 +1,331 @@ + + +

    Obtaining an Endpoint Connection

    +

    Function

    This API is used to obtain a VPC endpoint connection.

    +
    +

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connections

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to query.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Query Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    start

    +

    No

    +

    Integer

    +

    The start value of the query. The default value is 1, indicating that the query starts from the first task.

    +

    limit

    +

    No

    +

    Integer

    +

    Number of task to be queried. The default value is 10, indicating that the information about 10 tasks is queried at a time.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 3 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    connections

    +

    Array of connections objects

    +

    Connection information

    +

    vpcServiceName

    +

    String

    +

    VPC endpoint service name

    +

    permissions

    +

    Array of permissions objects

    +

    Permission list

    +

    vpcepUpdateSwitch

    +

    Boolean

    +

    Whether to update endpoints.

    +
    • true: The VPC endpoint is enabled.

      +
    • false: The VPC endpoint is disabled.

      +
    +

    total_count

    +

    Integer

    +

    Number of endpoints.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 4 connections

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    Endpoint ID.

    +

    status

    +

    String

    +

    Endpoint status.

    +
    • accepted: The VPC endpoint connection is enabled.

      +
    • rejected: The VPC endpoint connection is disabled.

      +
    +

    maxSession

    +

    String

    +

    Maximum number of connections.

    +

    specificationName

    +

    String

    +

    Endpoint name.

    +

    created_at

    +

    String

    +

    Creation time. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

    +

    update_at

    +

    String

    +

    Update time. The default value is null.

    +

    domain_id

    +

    String

    +

    Owner.

    +

    vpcepIp

    +

    String

    +

    IPv4 address of the VPC endpoint.

    +

    vpcepIpv6Address

    +

    String

    +

    IPv6 address of the VPC endpoint.

    +

    vpcepDnsName

    +

    String

    +

    Private domain name for accessing the VPC endpoint.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 5 permissions

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    id

    +

    permission

    +

    String

    +

    Permissions

    +

    permission_type

    +

    String

    +

    Permission type

    +

    created_at

    +

    String

    +

    Creation time

    +
    +
    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "connections" : [ {
    +    "id" : "54b7f739-31a1-40d0-862b-ac85b83ab2da",
    +    "status" : "accepted",
    +    "maxSession" : "3000",
    +    "specificationName" : "default",
    +    "vpcepIp" : "192.168.0.122",
    +    "vpcepIpv6Address" : null,
    +    "vpcepDnsName" : null,
    +    "created_at" : "2024-06-11T09:36:24Z",
    +    "update_at" : null,
    +    "domain_id" : "db9b76a0d9ae431f8e85e89da2ca867c"
    +  }, {
    +    "id" : "e88ad0bc-c2c7-419c-bd9b-a961111f0a42",
    +    "status" : "accepted",
    +    "maxSession" : "3000",
    +    "specificationName" : "default",
    +    "vpcepIp" : "192.168.0.133",
    +    "vpcepIpv6Address" : null,
    +    "vpcepDnsName" : null,
    +    "created_at" : "2023-10-12T07:33:16Z",
    +    "update_at" : null,
    +    "domain_id" : "db9b76a0d9ae431f8e85e89da2ca867c"
    +  } ],
    +  "vpcepUpdateSwitch" : false,
    +  "total_count" : 2,
    +  "vpcServiceName" : "cn-north-4.css-op-no-delete.cf072729-b076-49db-83d3-020dc9f589bd",
    +  "permissions" : [ {
    +    "id" : "432a6429-f377-4168-8b24-feb5885af08c",
    +    "permission" : "iam:domain::db9b76a0d9ae431f8e85e89da2ca867c",
    +    "permission_type" : "domainId",
    +    "created_at" : "2023-10-12T07:33:11Z"
    +  } ]
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartAutoCreateSnapshots.html b/docs/css/api-ref/StartAutoCreateSnapshots.html new file mode 100644 index 00000000..a8ab144c --- /dev/null +++ b/docs/css/api-ref/StartAutoCreateSnapshots.html @@ -0,0 +1,154 @@ + + +

    Enabling Automatic Snapshot Creation

    +

    Function

    This API is used to enable the automatic snapshot creation function.

    +
    +

    URI

    POST /v2.0/{project_id}/clusters/{cluster_id}/snapshots/policy/open

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster that the snapshot belongs to.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    indices

    +

    No

    +

    String

    +

    Name of an index to be restored. Multiple indexes are separated by commas (,). By default, all indexes are restored. You can use the combination of a backslash and an asterisk (*) to back up data of certain indexes. For example, if you specify 2018-06*, then the data of the indexes with the prefix 2018-06 will be restored.The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and the following special characters are not allowed: "\<|>/?The default value is *, indicating that all indexes are restored.

    +

    keepday

    +

    Yes

    +

    Integer

    +

    Set the number of retained snapshots. The value ranges from 1 to 90. Expired snapshots will be automatically deleted on the half hour. The deletion policy applies only to automated snapshots that are executed at the same frequency as the current automatic snapshot creation policy.

    +

    frequency

    +

    No

    +

    String

    +

    Frequency of automatically creating snapshots.

    +
    NOTE:

    The default value is DAY. If this parameter is set to HOUR, the scheduled task is executed every hour. If this parameter is set to DAY, the scheduled task is executed every day. If this parameter is set to SUN, MON, TUE, WED, THU, FRI or SAT, the scheduled task is executed at the specified day of every week. For example, SUN indicates that the task is executed once every Sunday. The number of retained snapshots depends on the execution frequency and indexes set in the automatic snapshot creation policy. If the execution interval is short or the index data volume is large, the number of retained automatic snapshots may not reach the preset value. Set this value based on actual conditions.

    +
    +

    period

    +

    Yes

    +

    String

    +

    Time when a snapshot is generated every day. Snapshots can only be generated on the hour. The format is HH:mm z: HH:mm refers to the hour time and z refers to the time zone. For example, 00:00 GMT+08:00 and 01:00 GMT+08:00.

    +
    NOTE:

    The default value is 00:00 GMT+08:00. When frequency is set to HOUR, you do not need to specify period. By default, snapshot creation starts from the next hour after the settings are successful.

    +
    +

    prefix

    +

    Yes

    +

    String

    +

    Prefix of a snapshot that is automatically created, which is manually entered. Enter up to 32 characters and start with a lowercase letter. Lowercase letters, digits, hyphens (-), and underscores (_) are allowed.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Enable the automatic backup function.

    +
    POST /v2.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/snapshots/policy/open
    +
    +{
    +  "indices" : "*",
    +  "keepday" : 7,
    +  "frequency" : "DAY",
    +  "period" : "16:00 GMT+08:00",
    +  "prefix" : "snapshot"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    403

    +

    Request rejected.The server has received the request and understood it, but refused to respond to it. The client should not repeat the request without modifications.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartAutoSetting.html b/docs/css/api-ref/StartAutoSetting.html new file mode 100644 index 00000000..821606e0 --- /dev/null +++ b/docs/css/api-ref/StartAutoSetting.html @@ -0,0 +1,82 @@ + + +

    (Not Recommended) Automatically Setting Basic Configurations of a Cluster Snapshot

    +

    Function

    This API is used to automatically set basic configurations for a cluster snapshot, including configuring OBS buckets and IAM agency.

    +
    • OBS Bucket: Enter the location of the OBS bucket used for storing snapshots.

      +
    • Backup Path: Enter the storage path of the snapshot in the OBS bucket.

      +
    • IAM Agency: Authorize you to use OBS in IAM so that snapshots must be stored in OBS.

      +
    +

    This API automatically creates an OBS bucket and an agency for the snapshot. If there are multiple clusters, an OBS bucket will be created for each cluster via this API. As a result, the OBS quota may be insufficient, and many OBS buckets are difficult to maintain. You are advised to perform the operations in Modifying Basic Configurations of a Cluster Snapshot.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/auto_setting

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster where snapshots you want to back up.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    406

    +

    The server could not fulfill the request according to the content characteristics of the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartKibanaPublic.html b/docs/css/api-ref/StartKibanaPublic.html new file mode 100644 index 00000000..5635af18 --- /dev/null +++ b/docs/css/api-ref/StartKibanaPublic.html @@ -0,0 +1,164 @@ + + +

    Enabling Kibana Public Access

    +

    Function

    This API is used to enable public network access to Kibana.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/open

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose Kibana public access you want to enable.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    eipSize

    +

    Yes

    +

    Integer

    +

    Bandwidth. Unit: Mbit/s

    +

    elbWhiteList

    +

    Yes

    +

    StartKibanaPublicReqElbWhitelist object

    +

    ELB whitelist.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 3 StartKibanaPublicReqElbWhitelist

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    enableWhiteList

    +

    Yes

    +

    Boolean

    +

    Whether to enable the whitelist function.

    +
    • true: The whitelist is enabled.

      +
    • false: The whitelist is disabled.

      +
    +

    whiteList

    +

    Yes

    +

    String

    +

    Whitelist.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/publickibana/open
    +
    +{
    +  "eipSize" : 5,
    +  "elbWhiteList" : {
    +    "enableWhiteList" : true,
    +    "whiteList" : "192.168.0.xx"
    +  },
    +  "isAutoPay" : 1
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartLogAutoBackupPolicy.html b/docs/css/api-ref/StartLogAutoBackupPolicy.html new file mode 100644 index 00000000..6f30458d --- /dev/null +++ b/docs/css/api-ref/StartLogAutoBackupPolicy.html @@ -0,0 +1,116 @@ + + +

    Enabling the Automatic Log Backup Policy

    +

    Function

    This API is used to enable the automatic log backup policy.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/update

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose log backup policy you want to enable.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    period

    +

    Yes

    +

    String

    +

    Backup start time. Format: GMT

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Enable the automatic log backup policy.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/logs/policy/update
    +
    +{
    +  "period" : "00:00 GMT+08:00"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartLogs.html b/docs/css/api-ref/StartLogs.html new file mode 100644 index 00000000..728446c8 --- /dev/null +++ b/docs/css/api-ref/StartLogs.html @@ -0,0 +1,195 @@ + + +

    Enabling the Log Function

    +

    Function

    This API is used to enable the log function.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/logs/open

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose log function you want to enable.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 2 Query Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    action

    +

    No

    +

    String

    +

    The action can be base_log_collect or real_time_log_collect. base indicates the historical capability, and real_time indicates the real-time collection capability. If this parameter is not passed, base is used by default, which is compatible with the previous logic.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 3 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    agency

    +

    No

    +

    String

    +

    Agency name. You can create an agency to allow CSS to call other cloud services. This parameter is mandatory when action is not set to real_time_log_collect.

    +

    logBasePath

    +

    No

    +

    String

    +

    Storage path of backed up logs in the OBS bucket. This parameter is mandatory when action is not set to real_time_log_collect.

    +

    logBucket

    +

    No

    +

    String

    +

    Name of the OBS bucket for storing logs. This parameter is mandatory when action is not set to real_time_log_collect.

    +

    index_prefix

    +

    No

    +

    String

    +

    Index prefix for saving logs. This parameter is mandatory when action is set to real_time_log_collect.

    +

    keep_days

    +

    No

    +

    Integer

    +

    Log retention duration. This parameter is mandatory when action is set to real_time_log_collect.

    +

    target_cluster_id

    +

    No

    +

    String

    +

    Specifies the target cluster for saving logs. This parameter is mandatory when action is set to real_time_log_collect.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    • Enable the log function.

      +
      POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/logs/open
      +
      +{
      +  "agency" : "css_obs_agency",
      +  "logBasePath" : "css/log",
      +  "logBucket" : "000-words"
      +}
      +
    • Enable real-time log collection function.

      +
      POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/logs/open?action=real_time_log_collect
      +
      +{
      +  "index_prefix" : "css_log",
      +  "keep_days" : 30,
      +  "target_cluster_id" : "4f3deec3-efa8-4598-bf91-560aad1377a3"
      +}
      +
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartPublicWhitelist.html b/docs/css/api-ref/StartPublicWhitelist.html new file mode 100644 index 00000000..e295745d --- /dev/null +++ b/docs/css/api-ref/StartPublicWhitelist.html @@ -0,0 +1,116 @@ + + +

    Enabling the Public Network Access Control Whitelist

    +

    Function

    This API is used to enable the public network access control whitelist.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/update

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose public network access control whitelist you want to enable.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    whiteList

    +

    Yes

    +

    String

    +

    IP address of the user for whom the whitelist is enabled.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Enable the public network access control whitelist.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/public/whitelist/update
    +
    +{
    +  "whiteList" : "192.168.0.xx"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartTargetClusterConnectivityTest.html b/docs/css/api-ref/StartTargetClusterConnectivityTest.html new file mode 100644 index 00000000..1d959245 --- /dev/null +++ b/docs/css/api-ref/StartTargetClusterConnectivityTest.html @@ -0,0 +1,118 @@ + + +

    Test connectivity.

    +

    Function

    This API is used to test connectivity.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/logs/connectivity

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    Cluster ID.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    target_cluster_id

    +

    Yes

    +

    String

    +

    Target cluster ID.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Test connectivity to the target cluster.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/logs/connectivity
    +
    +{
    +  "target_cluster_id" : "4f3deec3-efa8-4598-bf91-560aad1377a4"
    +}
    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    { }
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    The request could not be understood by the server due to malformed syntax.

    +

    Modify the request instead of retrying.

    +

    409

    +

    The request cannot be processed due to a conflict.

    +

    This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

    +

    412

    +

    The server does not meet one of the requirements that the requester puts on the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StartVpecp.html b/docs/css/api-ref/StartVpecp.html new file mode 100644 index 00000000..2d24f488 --- /dev/null +++ b/docs/css/api-ref/StartVpecp.html @@ -0,0 +1,163 @@ + + +

    Enabling the VPC Endpoint Service

    +

    Function

    This API is used to enable the VPC endpoint service.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/open

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose VPC endpoint you want to enable.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    endpointWithDnsName

    +

    No

    +

    Boolean

    +

    Enable the VPC endpoint.

    +

    professionVpcep

    +

    No

    +

    Boolean

    +

    Create a professional VPC endpoint.

    +
    • true: enabled.

      +
    • false: disabled.

      +
    +

    dualstackEnable

    +

    No

    +

    Boolean

    +

    Whether to enable the IPv4/IPv6 dual-stack network. The IPv4/IPv6 dual-stack network can be enabled only when a professional VPC endpoint is created and the VPC of the cluster supports IPv6.

    +
    • true: enabled.

      +
    • false: disabled.

      +
    +
    +
    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + +
    Table 3 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    action

    +

    String

    +

    Operations. The fixed value is createVpcepservice, indicating that the VPC endpoint is enabled.

    +
    +
    +
    +

    Example Requests

    Enable the VPC endpoint service.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/vpcepservice/open
    +
    +{
    +  "endpointWithDnsName" : true
    +}
    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "action" : "createVpcepservice"
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StopAutoCreateSnapshots.html b/docs/css/api-ref/StopAutoCreateSnapshots.html new file mode 100644 index 00000000..7b00398b --- /dev/null +++ b/docs/css/api-ref/StopAutoCreateSnapshots.html @@ -0,0 +1,84 @@ + + +

    Disabling Automatic Snapshot Creation

    +

    Function

    This API is used to disable the automatic snapshot creation function.

    +
    +

    URI

    PUT /v2.0/{project_id}/clusters/{cluster_id}/snapshots/policy/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster that the snapshot belongs to.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Disable the automatic backup function.

    +
    PUT /v2.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/snapshots/policy/close
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    403

    +

    Request rejected.The server has received the request and understood it, but refused to respond to it. The client should not repeat the request without modifications.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StopLogAutoBackupPolicy.html b/docs/css/api-ref/StopLogAutoBackupPolicy.html new file mode 100644 index 00000000..12d4748e --- /dev/null +++ b/docs/css/api-ref/StopLogAutoBackupPolicy.html @@ -0,0 +1,89 @@ + + +

    Disabling the Automatic Log Backup Policy

    +

    Function

    This API is used to disable the automatic log backup policy.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose automatic log backup policy you want to disable.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StopLogs.html b/docs/css/api-ref/StopLogs.html new file mode 100644 index 00000000..f2a5fc39 --- /dev/null +++ b/docs/css/api-ref/StopLogs.html @@ -0,0 +1,112 @@ + + +

    Disabling the Log Function

    +

    Function

    This API is used to disable the log function.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose log function you want to disable.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 2 Query Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    action

    +

    No

    +

    String

    +

    The action can be base_log_collect or real_time_log_collect. base indicates the historical capability, and real_time indicates the real-time collection capability. If this parameter is not passed, base is used by default, which is compatible with the previous logic.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StopPublicKibanaWhitelist.html b/docs/css/api-ref/StopPublicKibanaWhitelist.html new file mode 100644 index 00000000..62c19700 --- /dev/null +++ b/docs/css/api-ref/StopPublicKibanaWhitelist.html @@ -0,0 +1,89 @@ + + +

    Disabling Kibana Public Network Access Control

    +

    Function

    This API is used to disable public network access control for Kibana.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose Kibana public network access control you want to disable.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StopPublicWhitelist.html b/docs/css/api-ref/StopPublicWhitelist.html new file mode 100644 index 00000000..632a2822 --- /dev/null +++ b/docs/css/api-ref/StopPublicWhitelist.html @@ -0,0 +1,89 @@ + + +

    Disabling the Public Network Access Control Whitelist

    +

    Function

    This API is used to disable the public network access control whitelist.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose public network access control whitelist you want to disable.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StopSnapshot.html b/docs/css/api-ref/StopSnapshot.html new file mode 100644 index 00000000..b4bdd262 --- /dev/null +++ b/docs/css/api-ref/StopSnapshot.html @@ -0,0 +1,77 @@ + + +

    Disabling the Snapshot Function

    +

    Function

    This API is used to disable the snapshot function.

    +
    +

    URI

    DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose snapshot function you want to disable.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    406

    +

    The server could not fulfill the request according to the content characteristics of the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/StopVpecp.html b/docs/css/api-ref/StopVpecp.html new file mode 100644 index 00000000..385a7ebc --- /dev/null +++ b/docs/css/api-ref/StopVpecp.html @@ -0,0 +1,112 @@ + + +

    Disabling the VPC Endpoint Service

    +

    Function

    This API is used to disable the VPC endpoint service.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose VPC endpoint you want to disable.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + +
    Table 2 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    action

    +

    String

    +

    Operations. The fixed value is deleteVpcepservice, indicating that the VPC endpoint has been disabled.

    +
    +
    +
    +

    Example Requests

    None

    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "action" : "deleteVpcepservice"
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateAlterKibana.html b/docs/css/api-ref/UpdateAlterKibana.html new file mode 100644 index 00000000..769ac67e --- /dev/null +++ b/docs/css/api-ref/UpdateAlterKibana.html @@ -0,0 +1,142 @@ + + +

    Modifying the Kibana Public Network Bandwidth

    +

    Function

    This API is used to modify the public network bandwidth of Kibana.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/bandwidth

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose Kibana public network bandwidth you want to modify.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    bandWidth

    +

    Yes

    +

    UpdatePublicKibanaBandwidthReqBandWidth object

    +

    Bandwidth.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 3 UpdatePublicKibanaBandwidthReqBandWidth

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    size

    +

    Yes

    +

    Integer

    +

    New bandwidth size.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Modify the Kibana public network bandwidth.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/publickibana/bandwidth
    +
    +{
    +  "bandWidth" : {
    +    "size" : 5
    +  },
    +  "isAutoPay" : 1
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateAzByInstanceType.html b/docs/css/api-ref/UpdateAzByInstanceType.html new file mode 100644 index 00000000..17af2388 --- /dev/null +++ b/docs/css/api-ref/UpdateAzByInstanceType.html @@ -0,0 +1,169 @@ + + +

    Changing the AZ of a Cluster Instance

    +

    Function

    This API is used to change the AZ by specifying node types.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/inst-type/{inst_type}/azmigrate

    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    Cluster ID.

    +

    inst_type

    +

    Yes

    +

    String

    +

    Type of nodes whose AZ is to be changed. Value:

    +
    • all: all node types

      +
    • ess: data node

      +
    • ess-cold: cold data node

      +
    • ess-client: client node

      +
    • ess-master: master node

      +
    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    source_az

    +

    Yes

    +

    String

    +

    AZ where the node is located.

    +

    target_az

    +

    Yes

    +

    String

    +

    Destination AZ of nodes.

    +

    migrate_type

    +

    Yes

    +

    String

    +

    AZ migration mode:

    +
    • multi_az_change: HA reconstruction

      +
    • az_migrate: AZ migration

      +
    +

    agency

    +

    Yes

    +

    String

    +

    Agency name. You can create an agency to allow CSS to call other cloud services.

    +

    indices_backup_check

    +

    No

    +

    Boolean

    +

    Indicates whether to perform full index snapshot backup check.

    +

    true: Check full index snapshot backup.

    +

    false: Do not perform full index snapshot backup check.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Switch the AZ of the current cluster.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/inst-type/all/azmigrate
    +
    +{
    +  "source_az" : "cn-north-4c",
    +  "target_az" : "cn-north-4a",
    +  "migrate_type" : "az_migrate",
    +  "agency" : "css-test-agency"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    The client should not repeat the request without modifications.

    +

    403

    +

    The request is rejected. The server has received the request and understood it, but the server is refusing to respond to it. The client should not repeat the request without modifications.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateBatchClustersTags.html b/docs/css/api-ref/UpdateBatchClustersTags.html new file mode 100644 index 00000000..14716dfd --- /dev/null +++ b/docs/css/api-ref/UpdateBatchClustersTags.html @@ -0,0 +1,220 @@ + + +

    Adding or Deleting Cluster Tags in Batches

    +

    Function

    This API is used to add tags to or delete tags from a cluster in batches.

    +
    +

    URI

    POST /v1.0/{project_id}/{resource_type}/{cluster_id}/tags/action

    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster that you want to add tags to or delete tags from in batches.

    +

    resource_type

    +

    Yes

    +

    String

    +

    Resource type. Currently, its value can only be css-cluster.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    action

    +

    Yes

    +

    String

    +

    Action type. This attribute is used to identify the required operation type.

    +
    • create: Tags are added in batches.

      +
    • delete: Tags are deleted in batches.

      +
    +

    tags

    +

    Yes

    +

    Array of Tag objects

    +

    Tag list.

    +

    sysTags

    +

    No

    +

    Array of SysTags objects

    +

    System tag list.

    +
    • The value of key is fixed to _sys_enterprise_project_id.

      +
    • The value is UUID or 0. 0 indicates the default enterprise project.

      +
    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 3 Tag

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    key

    +

    Yes

    +

    String

    +

    Tag name.

    +

    value

    +

    Yes

    +

    String

    +

    Tag value.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 4 SysTags

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    key

    +

    Yes

    +

    String

    +

    Tag name.

    +

    value

    +

    Yes

    +

    String

    +

    Tag value.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Create or delete cluster tags in batches.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/tags/action
    +
    +{
    +  "action" : "create",
    +  "tags" : [ {
    +    "key" : "K1",
    +    "value" : "V1"
    +  }, {
    +    "key" : "K2",
    +    "value" : "V2"
    +  } ]
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    204

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Do not retry the request before modification.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateCloseKibana.html b/docs/css/api-ref/UpdateCloseKibana.html new file mode 100644 index 00000000..27509d87 --- /dev/null +++ b/docs/css/api-ref/UpdateCloseKibana.html @@ -0,0 +1,164 @@ + + +

    Disabling Kibana Public Access

    +

    Function

    This API is used to disable public network access to Kibana.Yearly/Monthly clusters cannot disable public access using APIs.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/publickibana/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose Kibana public access you want to disable.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    eipSize

    +

    No

    +

    Integer

    +

    Bandwidth. Unit: Mbit/s

    +

    elbWhiteList

    +

    No

    +

    StartKibanaPublicReqElbWhitelist object

    +

    ELB whitelist.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 3 StartKibanaPublicReqElbWhitelist

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    enableWhiteList

    +

    Yes

    +

    Boolean

    +

    Whether to enable the whitelist function.

    +
    • true: The whitelist is enabled.

      +
    • false: The whitelist is disabled.

      +
    +

    whiteList

    +

    Yes

    +

    String

    +

    Whitelist.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Disable Kibana public access.

    +
    PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/publickibana/close
    +
    +{
    +  "eipSize" : 5,
    +  "elbWhiteList" : {
    +    "enableWhiteList" : true,
    +    "whiteList" : "192.168.0.xx"
    +  }
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateClusterName.html b/docs/css/api-ref/UpdateClusterName.html new file mode 100644 index 00000000..b5d02daf --- /dev/null +++ b/docs/css/api-ref/UpdateClusterName.html @@ -0,0 +1,116 @@ + + +

    Renaming a Cluster

    +

    Function

    This API is used to change the name of a cluster.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/changename

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster that you want to rename.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    displayName

    +

    Yes

    +

    String

    +

    New name of a cluster

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Change the display name of the current cluster.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/changename
    +
    +{
    +  "displayName" : "ES-Test-new"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateESListener.html b/docs/css/api-ref/UpdateESListener.html new file mode 100644 index 00000000..2a946355 --- /dev/null +++ b/docs/css/api-ref/UpdateESListener.html @@ -0,0 +1,271 @@ + + +

    Updating an Elasticsearch Listener

    +

    Function

    This API is used to update an Elasticsearch listener.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/es-listeners/{listener_id}

    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the target cluster

    +

    listener_id

    +

    Yes

    +

    String

    +

    ID of the target listener.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    listener

    +

    Yes

    +

    EsListenerRequest object

    +

    Listener object

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 3 EsListenerRequest

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    default_tls_container_ref

    +

    Yes

    +

    String

    +

    ID of the server certificate used by the listener

    +

    client_ca_tls_container_ref

    +

    No

    +

    String

    +

    ID of the CA certificate used by the listener. This parameter is mandatory when bidirectional authentication is to be updated.

    +
    +
    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + +
    Table 4 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    listener

    +

    EsListenerResponse object

    +

    Listener object

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 5 EsListenerResponse

    Parameter

    +

    Type

    +

    Description

    +

    protocol

    +

    String

    +

    Protocol used by the listener

    +

    id

    +

    String

    +

    Listener ID

    +

    name

    +

    String

    +

    Listener name

    +

    protocol_port

    +

    String

    +

    Port used by the listener

    +

    ipgroup

    +

    EsIpgroupResource object

    +

    Access control information of the listener object

    +
    +
    + +
    + + + + + + + + + + + + + + + + + +
    Table 6 EsIpgroupResource

    Parameter

    +

    Type

    +

    Description

    +

    ipgroup_id

    +

    String

    +

    ID of the IP address group associated with the listener

    +

    enable_ipgroup

    +

    Boolean

    +

    Status of an access control group

    +

    type

    +

    String

    +

    Type of an access control group

    +
    +
    +
    +

    Example Requests

    PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/58ee0f27-70b3-47e0-ac72-9e3df6cd15cd/es-listeners/4425eb63-78ce-4c63-b60e-492befdac0e7
    +
    +{
    +  "listener" : {
    +    "default_tls_container_ref" : "9c82320a8dd049eba49b28e70a2c0c3e"
    +  }
    +}
    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "listener" : {
    +    "id" : "9c82320a8dd049eba49b28e70a2c0c3e",
    +    "name" : "name",
    +    "protocol" : "tcp",
    +    "protocol_port" : 8080,
    +    "ipgroup" : {
    +      "ipgroup_id" : "4f3deec3-efa8-4598-bf91-560aad1377a3",
    +      "enable_ipgroup" : true,
    +      "type" : "white"
    +    }
    +  }
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request instead of retrying.

    +

    409

    +

    The request cannot be processed due to a conflict.

    +

    This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

    +

    412

    +

    The server does not meet one of the requirements that the requester puts on the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateExtendCluster.html b/docs/css/api-ref/UpdateExtendCluster.html new file mode 100644 index 00000000..18860225 --- /dev/null +++ b/docs/css/api-ref/UpdateExtendCluster.html @@ -0,0 +1,138 @@ + + +

    Scaling Out a Cluster

    +

    Function

    This API is used to add instances to a cluster (only Elasticsearch instances can be added). This API can only scale out clusters that only have common nodes. Clusters with master, client, or cold data nodes cannot use this API.For details about how to configure the number and storage capacity of instances in a cluster, see the API for Adding Instances and Expanding Instance Storage Capacity.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/extend

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to scale out.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    grow

    +

    Yes

    +

    ExtendClusterGrowReq object

    +

    Detailed description about the cluster scale-out request.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 3 ExtendClusterGrowReq

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    modifySize

    +

    Yes

    +

    Integer

    +

    Number of instances you want to add.

    +

    The total number of existing instances and newly added instances in a cluster cannot exceed 32.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Change the number of instances in the current cluster.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/extend
    +
    +{
    +  "grow" : {
    +    "modifySize" : 4
    +  },
    +  "isAutoPay" : 1
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    404

    +

    The requested resource could not be found.

    +

    Modify the request before retry.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateExtendInstanceStorage.html b/docs/css/api-ref/UpdateExtendInstanceStorage.html new file mode 100644 index 00000000..919f5536 --- /dev/null +++ b/docs/css/api-ref/UpdateExtendInstanceStorage.html @@ -0,0 +1,193 @@ + + +

    Adding Instances and Expanding Instance Storage Capacity

    +

    Function

    This API is used to add instances of different types and expand instance storage capacity in a cluster. This API is available for clusters with master, client, or cold data nodes.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/role_extend

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to scale out.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    grow

    +

    Yes

    +

    Array of RoleExtendGrowReq objects

    +

    Detailed description about the cluster scale-out request.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 3 RoleExtendGrowReq

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    type

    +

    Yes

    +

    String

    +

    Type of the instance to be scaled out. Select at least one from ess, ess-master, and ess-client. A type can be selected once only.

    +

    You can only add instances, rather than increase storage capacity, on nodes of the ess-master and ess-client types.

    +

    nodesize

    +

    Yes

    +

    Integer

    +

    Number of instances you want to add. The total number of existing instances and newly added instances in a cluster cannot exceed 32.

    +

    disksize

    +

    Yes

    +

    Integer

    +

    Storage capacity of the instance you want to add. The sum of the original instance storage capacity plus the expanded instance storage capacity cannot exceed the default upper limit of storage capacity set during cluster creation. If scale-out is not required, set this parameter to 0. With a yearly/monthly cluster, you cannot change the number of nodes and disk capacity at the same time.

    +

    Unit: GB.

    +
    • The scale-out step of ESS and ESS-cold nodes is 20.

      +
    • Storage capacity of ess-master and ess-client nodes cannot be expanded.

      +
    +
    +
    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + +
    Table 4 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    id

    +

    String

    +

    Cluster ID.

    +
    +
    +
    +

    Example Requests

    Change the number of instances and storage capacity of the current cluster.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/role_extend
    +
    +{
    +  "grow" : [ {
    +    "type" : "ess-master",
    +    "nodesize" : 2,
    +    "disksize" : 0
    +  }, {
    +    "type" : "ess",
    +    "nodesize" : 0,
    +    "disksize" : 40
    +  }, {
    +    "type" : "ess-client",
    +    "nodesize" : 1,
    +    "disksize" : 0
    +  } ],
    +  "isAutoPay" : 1
    +}
    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "id" : "4f3deec3-efa8-4598-bf91-560aad1377a3"
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    404

    +

    The requested resource could not be found.

    +

    Modify the request before retry.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateFlavor.html b/docs/css/api-ref/UpdateFlavor.html new file mode 100644 index 00000000..325094c0 --- /dev/null +++ b/docs/css/api-ref/UpdateFlavor.html @@ -0,0 +1,184 @@ + + +

    Changing Specifications

    +

    Function

    This API is used to modify the specifications of a cluster. Only the nodes of the ESS type can be modified.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/flavor

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose specifications you want to change.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    newFlavorId

    +

    Yes

    +

    String

    +

    When operationType is set to vm, newFlavorId indicates the node flavor ID after the change.

    +

    This parameter is obtained by calling the Obtaining the Instance Specifications List API. The API selects a flavor_id based on the values of the name attribute.

    +

    The old and new node specifications must be under the same Elasticsearch engine version.

    +

    When operationType is set to volume, newFlavorId indicates the new disk type after the change. The following disk types are supported:

    +
    • COMMON: common I/O

      +
    • HIGH: high I/O

      +
    • ULTRAHIGH: ultra-high I/O

      +
    • ESSD: ultra-fast SSD

      +
    +

    operationType

    +

    No

    +

    String

    +

    Operation type. The value can be vm or volume. The default value is vm.

    +
    • vm: Change the node flavor.

      +
    • volume: Change the disk type.

      +
    +

    needCheckReplica

    +

    No

    +

    Boolean

    +

    Indicates whether to verify replicas. Its value can be true or false. This function is enabled by default.

    +
    • *true: Enable the replicas verification.

      +
    • false: Disable the replicas verification.

      +
    +

    needCheckClusterStatus

    +

    No

    +

    Boolean

    +

    Description: Whether to check the cluster status. The value can be true or false. This function is enabled by default.

    +
    • true: Cluster status verification is enabled.

      +
    • false: Cluster status verification is ignored.

      +
    +

    clusterLoadCheck

    +

    No

    +

    Boolean

    +

    Whether to check the cluster load. The value can be true or false. The default value is true.

    +
    • true: enable cluster load check.

      +
    • true: skip cluster load check.

      +
    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    • POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/flavor
      +
      +{
      +  "needCheckReplica" : false,
      +  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2",
      +  "isAutoPay" : 1,
      +  "needCheckClusterStatus" : true
      +}
      +
    • POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/flavor
      +
      +{
      +  "needCheckReplica" : false,
      +  "newFlavorId" : "ULTRAHIGH",
      +  "operationType" : "volume",
      +  "isAutoPay" : 1,
      +  "clusterLoadCheck" : true
      +}
      +
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateFlavorByType.html b/docs/css/api-ref/UpdateFlavorByType.html new file mode 100644 index 00000000..5e5bee0b --- /dev/null +++ b/docs/css/api-ref/UpdateFlavorByType.html @@ -0,0 +1,206 @@ + + +

    Changing the Specifications of a Specified Node Type

    +

    Function

    This API is used to modify cluster specifications. The following node types can be changed:

    +
    • ess: data node

      +
    • ess-cold: cold data node

      +
    • ess-client: client node

      +
    • ess-master: master node

      +
    • lgs: Lgs node.

      +
    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/{types}/flavor

    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose specifications you want to change.

    +

    types

    +

    Yes

    +

    String

    +

    Type of the cluster node you want to modify.

    +
    • ess: data node

      +
    • ess-cold: cold data node

      +
    • ess-client: client node

      +
    • ess-master: master node

      +
    • lgs: Lgs node.

      +
    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    newFlavorId

    +

    Yes

    +

    String

    +

    When operationType is set to vm, newFlavorId indicates the node flavor ID after the change.

    +

    This parameter is obtained by calling the Obtaining the Instance Specifications List API. The API selects a flavor_id based on the values of the name attribute.

    +

    The old and new node specifications must be under the same Elasticsearch engine version.

    +

    When operationType is set to volume, newFlavorId indicates the new disk type after the change. The following disk types are supported:

    +
    • COMMON: common I/O

      +
    • HIGH: high I/O

      +
    • ULTRAHIGH: ultra-high I/O

      +
    • ESSD: ultra-fast SSD

      +
    +

    operationType

    +

    No

    +

    String

    +

    Operation type. The value can be vm or volume. The default value is vm.

    +
    • vm: Change the node flavor.

      +
    • volume: Change the disk type.

      +
    +

    needCheckReplica

    +

    No

    +

    Boolean

    +

    Indicates whether to verify replicas. Its value can be true or false. This function is enabled by default.

    +
    • *true: Enable the replicas verification.

      +
    • false: Disable the replicas verification.

      +
    +

    Master and client nodes are not data nodes, so they do not need to check replicas no matter this parameter is set to true or false.

    +

    needCheckClusterStatus

    +

    No

    +

    Boolean

    +

    Indicates whether to check the cluster status. The value can be true or false. This function is enabled by default.

    +
    • true: Cluster status verification is enabled.

      +
    • false: Cluster status verification is ignored.

      +
    +

    clusterLoadCheck

    +

    No

    +

    Boolean

    +

    Whether to check the cluster load. The value can be true or false. The default value is true.

    +
    • true: enable cluster load check.

      +
    • true: skip cluster load check.

      +
    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    • POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/ess/flavor
      +
      +{
      +  "needCheckReplica" : false,
      +  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2",
      +  "isAutoPay" : 1,
      +  "needCheckClusterStatus" : true
      +}
      +
    • POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/ess/flavor
      +
      +{
      +  "needCheckReplica" : false,
      +  "newFlavorId" : "ULTRAHIGH",
      +  "operationType" : "volume",
      +  "isAutoPay" : 1,
      +  "clusterLoadCheck" : true
      +}
      +
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateInstance.html b/docs/css/api-ref/UpdateInstance.html new file mode 100644 index 00000000..ac843ceb --- /dev/null +++ b/docs/css/api-ref/UpdateInstance.html @@ -0,0 +1,128 @@ + + +

    Replacing a Node

    +

    Function

    This API is used to replace a failed node.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/instance/{instance_id}/replace

    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster where nodes are to be replaced

    +

    instance_id

    +

    Yes

    +

    String

    +

    ID of the node to be replaced

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Query Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    migrateData

    +

    No

    +

    String

    +

    Indicates whether to migrate data. The default value is true.

    +
    • "true": Migrate data.

      +
    • "false": Do not migrate data.

      +
    +

    agency

    +

    No

    +

    String

    +

    Agency name, which is delegated to CSS.

    +
    +
    +
    +

    Request Parameters

    None

    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/instance/43e63449-339c-4280-a6e9-da36b0685995/replace?migrateData=true
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    The client should modify the request instead of re-initiating it.

    +

    404

    +

    The requested resource could not be found.

    +

    The client should modify the request instead of re-initiating it.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateLogSetting.html b/docs/css/api-ref/UpdateLogSetting.html new file mode 100644 index 00000000..98b0e718 --- /dev/null +++ b/docs/css/api-ref/UpdateLogSetting.html @@ -0,0 +1,195 @@ + + +

    Modifying Basic Log Configurations

    +

    Function

    This API is used to modify basic log configurations.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/logs/settings

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose basic log configurations you want to modify.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 2 Query Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    action

    +

    No

    +

    String

    +

    The action can be base_log_collect or real_time_log_collect. base indicates the historical capability, and real_time indicates the real-time collection capability. If this parameter is not passed, base is used by default, which is compatible with the previous logic.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 3 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    agency

    +

    Yes

    +

    String

    +

    Agency name. You can create an agency to allow CSS to call other cloud services. This parameter is mandatory when action is not set to real_time_log_collect.

    +

    logBasePath

    +

    Yes

    +

    String

    +

    Storage path of backed up logs in the OBS bucket. This parameter is mandatory when action is not set to real_time_log_collect.

    +

    logBucket

    +

    Yes

    +

    String

    +

    Name of the OBS bucket for storing logs. This parameter is mandatory when action is not set to real_time_log_collect.

    +

    index_prefix

    +

    No

    +

    String

    +

    Index prefix for storing logs. This parameter is mandatory when action is set to real_time_log_collect.

    +

    keep_days

    +

    No

    +

    Integer

    +

    Log retention duration. This parameter is mandatory when action is set to real_time_log_collect.

    +

    target_cluster_id

    +

    No

    +

    String

    +

    Specifies the target cluster for saving logs. This parameter is mandatory when action is set to real_time_log_collect.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    • Modify basic log configurations.

      +
      POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/logs/settings
      +
      +{
      +  "agency" : "css_obs_agency",
      +  "logBasePath" : "css/log",
      +  "logBucket" : "000-words"
      +}
      +
    • Updating the Real-Time Log Collection Configuration

      +
      POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/logs/settings?action=real_time_log_collect 
      +
      +{
      +  "index_prefix" : "css_log",
      +  "keep_days" : 30,
      +  "target_cluster_id" : "4f3deec3-efa8-4598-bf91-560aad1377a3",
      +}
      +
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdatePublicBandWidth.html b/docs/css/api-ref/UpdatePublicBandWidth.html new file mode 100644 index 00000000..7e2b50e9 --- /dev/null +++ b/docs/css/api-ref/UpdatePublicBandWidth.html @@ -0,0 +1,142 @@ + + +

    Modifying Public Network Access Bandwidth

    +

    Function

    This API is used to modify the public network access bandwidth.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/public/bandwidth

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose public network access bandwidth you want to modify.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    bandWidth

    +

    Yes

    +

    BindPublicReqEipBandWidth object

    +

    Public network bandwidth.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 3 BindPublicReqEipBandWidth

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    size

    +

    Yes

    +

    Integer

    +

    Bandwidth range. Unit: Mbit/s

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Modify public network access bandwidth.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/public/bandwidth
    +
    +{
    +  "bandWidth" : {
    +    "size" : 5
    +  },
    +  "isAutoPay" : 1
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdatePublicKibanaWhitelist.html b/docs/css/api-ref/UpdatePublicKibanaWhitelist.html new file mode 100644 index 00000000..dcd54424 --- /dev/null +++ b/docs/css/api-ref/UpdatePublicKibanaWhitelist.html @@ -0,0 +1,116 @@ + + +

    Modifying Kibana Public Access Control

    +

    Function

    This API is used to modify the Kibana access permission by modifying the Kibana whitelist.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/update

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose Kibana access permission you want to modify.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    whiteList

    +

    Yes

    +

    String

    +

    Whitelisted IP addresses or network segments that can access Kibana. Separate them with commas (,), and each IP address or network segment must be unique.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    The latest whitelist

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/5c77b71c-5b35-4f50-8984-76387e42451a/publickibana/whitelist/update
    +
    +{
    +  "whiteList" : "192.168.0.21"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateShrinkCluster.html b/docs/css/api-ref/UpdateShrinkCluster.html new file mode 100644 index 00000000..6c472404 --- /dev/null +++ b/docs/css/api-ref/UpdateShrinkCluster.html @@ -0,0 +1,161 @@ + + +

    Scaling In Nodes of a Specific Type

    +

    Function

    This API is used to remove instances of different types and reduce instance storage capacity in a cluster.

    +
    +

    URI

    POST /v1.0/extend/{project_id}/clusters/{cluster_id}/role/shrink

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to scale in.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    shrink

    +

    Yes

    +

    Array of ShrinkNodeReq objects

    +

    Type and quantity of nodes you want to remove from a cluster.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 3 ShrinkNodeReq

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    reducedNodeNum

    +

    Yes

    +

    Integer

    +

    Number of nodes you want to remove from a cluster.

    +
    • After the scale-in, there has to be at least one node in each AZ under each node type.

      +
    • In a cross-AZ cluster, the difference between the numbers of the same type nodes in different AZs cannot exceed 1.

      +
    • For a cluster without master nodes, the number of removed data nodes (including cold data nodes and other types of nodes) in a scale-in must be fewer than half of the original data node number, and the number of remaining data nodes after a scale-in must be greater than the maximum number of index replicas.

      +
    +

    For a cluster with master nodes, the number of removed master nodes in a scale-in must be fewer than half of the original master node number. After scale-in, there has to be an odd number of master nodes, and there has to be at least three of them.

    +

    type

    +

    Yes

    +

    String

    +

    Node type.

    +
    • ess: data node

      +
    • ess-cold: cold data node

      +
    • ess-client: client node

      +
    • ess-master: master node

      +
    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Scale in a cluster by scaling in specified type of nodes.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/role/shrink
    +
    +{
    +  "shrink" : [ {
    +    "type" : "ess",
    +    "reducedNodeNum" : 1
    +  } ]
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateShrinkNodes.html b/docs/css/api-ref/UpdateShrinkNodes.html new file mode 100644 index 00000000..906268b2 --- /dev/null +++ b/docs/css/api-ref/UpdateShrinkNodes.html @@ -0,0 +1,130 @@ + + +

    Scaling In a Cluster by Removing a Specific Node

    +

    Function

    This API is used to scale in a cluster by removing a specified node.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/node/offline

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster you want to scale in.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    migrate_data

    +

    No

    +

    String

    +

    Indicates whether to migrate data. The default value is true.

    +
    • "true": Migrate data.

      +
    • "false": Do not migrate data.

      +
    +

    shrinkNodes

    +

    Yes

    +

    Array of strings

    +

    ID of the node you want to remove from a cluster.

    +

    Obtain the ID attribute in instances by referring to Querying Cluster Details.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Scale in a cluster by scaling in specified nodes.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/node/offline
    +
    +{
    +  "shrinkNodes" : [ "2077bdf3-b90d-412e-b460-635b9b159c11" ],
    +  "migrate_data" : "true"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateSnapshotSetting.html b/docs/css/api-ref/UpdateSnapshotSetting.html new file mode 100644 index 00000000..857644e6 --- /dev/null +++ b/docs/css/api-ref/UpdateSnapshotSetting.html @@ -0,0 +1,135 @@ + + +

    Modifying Basic Configurations of a Cluster Snapshot

    +

    Function

    This API is used to modify the basic configurations for a cluster snapshot, including OBS buckets and IAM agency.

    +

    You can also use this API to enable the snapshot function.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/setting

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose snapshot basic configuration you want to modify.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    bucket

    +

    Yes

    +

    String

    +

    Name of the OBS bucket used for backup.

    +

    agency

    +

    Yes

    +

    String

    +

    IAM agency used to access OBS.

    +

    basePath

    +

    No

    +

    String

    +

    Storage path of the snapshot in the OBS bucket.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Enable the snapshot function.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/index_snapshot/setting
    +
    +{
    +  "bucket" : "test-bucket",
    +  "agency" : "usearch",
    +  "basePath" : "css_repository/Es-name"
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    406

    +

    The server could not fulfill the request according to the content characteristics of the request.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +

    504

    +

    A gateway timeout error occurred.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateUnbindPublic.html b/docs/css/api-ref/UpdateUnbindPublic.html new file mode 100644 index 00000000..963d8432 --- /dev/null +++ b/docs/css/api-ref/UpdateUnbindPublic.html @@ -0,0 +1,189 @@ + + +

    Disabling Public Network Access

    +

    Function

    This API is used to disable public network access to Kibana.Yearly/Monthly clusters cannot disable Kibana public access using APIs.

    +
    +

    URI

    PUT /v1.0/{project_id}/clusters/{cluster_id}/public/close

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose public network access you want to disable.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    eip

    +

    No

    +

    UnBindPublicReqEipReq object

    +

    EIP information.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 3 UnBindPublicReqEipReq

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    bandWidth

    +

    No

    +

    BindPublicReqEipBandWidth object

    +

    Public network bandwidth.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 4 BindPublicReqEipBandWidth

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    size

    +

    Yes

    +

    Integer

    +

    Bandwidth range. Unit: Mbit/s

    +
    +
    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + +
    Table 5 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    action

    +

    String

    +

    Operations. The fixed value is unbindZone, indicating that the unbinding is successful.

    +
    +
    +
    +

    Example Requests

    Disable public network access.

    +
    PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/public/close
    +
    +{
    +  "eip" : {
    +    "bandWidth" : {
    +      "size" : 5
    +    }
    +  }
    +}
    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "action" : "unbindZone"
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateVpcepConnection.html b/docs/css/api-ref/UpdateVpcepConnection.html new file mode 100644 index 00000000..069d3a91 --- /dev/null +++ b/docs/css/api-ref/UpdateVpcepConnection.html @@ -0,0 +1,129 @@ + + +

    Updating an Endpoint Connection

    +

    Function

    This API is used to update an endpoint connection.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connections

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose VPC endpoint you want to update.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    action

    +

    Yes

    +

    String

    +

    Expected behavior.

    +
    • receive: Accept the VPC endpoint.

      +
    • reject: Reject the VPC endpoint.

      +
    +

    endpointIdList

    +

    Yes

    +

    Array of strings

    +

    Lists VPC endpoint IDs.

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Update an endpoint connection.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/vpcepservice/connections
    +
    +{
    +  "action" : "receive",
    +  "endpointIdList" : [ "f132bb14-e1d5-4f25-9f7c-a29e4c8effd4" ]
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateVpcepWhitelist.html b/docs/css/api-ref/UpdateVpcepWhitelist.html new file mode 100644 index 00000000..6f54f002 --- /dev/null +++ b/docs/css/api-ref/UpdateVpcepWhitelist.html @@ -0,0 +1,116 @@ + + +

    Modifying the Endpoint Service Whitelist

    +

    Function

    This API is used to modify the endpoint service whitelist.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/permissions

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    Cluster ID.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    vpcPermissions

    +

    Yes

    +

    Array of strings

    +

    Whitelist (user account ID).

    +
    +
    +
    +

    Response Parameters

    None

    +
    +

    Example Requests

    Modify the endpoint service whitelist.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/vpcepservice/permissions
    +
    +{
    +  "vpcPermissions" : [ "dffef70c1db243cbb373e45791165281" ]
    +}
    +
    +

    Example Responses

    None

    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpdateYmls.html b/docs/css/api-ref/UpdateYmls.html new file mode 100644 index 00000000..6bc0899e --- /dev/null +++ b/docs/css/api-ref/UpdateYmls.html @@ -0,0 +1,214 @@ + + +

    Modifying Cluster Parameters

    +

    Function

    This API is used to modify the parameter settings of a cluster.

    +
    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/ymls/update

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Path Parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    project_id

    +

    Yes

    +

    String

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    +

    cluster_id

    +

    Yes

    +

    String

    +

    ID of the cluster whose parameter settings you want to be modify.

    +
    +
    +
    +

    Request Parameters

    +
    + + + + + + + + + + + +
    Table 2 Request body parameters

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    edit

    +

    Yes

    +

    UpdateYmlsReqEdit object

    +

    Configuration file information.

    +
    +
    + +
    + + + + + + + + + + + +
    Table 3 UpdateYmlsReqEdit

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    modify

    +

    Yes

    +

    UpdateYmlsReqEditModify object

    +

    Operations on the configuration file.

    +
    • modify: Modify parameter settings.

      +
    • delete: Delete parameter settings.

      +
    • reset: Reset parameter settings.

      +
    +
    +
    + +
    + + + + + + + + + + + +
    Table 4 UpdateYmlsReqEditModify

    Parameter

    +

    Mandatory

    +

    Type

    +

    Description

    +

    elasticsearch.yml

    +

    Yes

    +

    Object

    +

    Parameter configuration list. The value is the JSON data you want to modify.

    +
    +
    +
    +

    Response Parameters

    Status code: 200

    + +
    + + + + + + + + + + + + + + + + + +
    Table 5 Response body parameters

    Parameter

    +

    Type

    +

    Description

    +

    acknowledged

    +

    Boolean

    +

    Whether the modification is successful.

    +
    • true: The modification succeeded.

      +
    • false: The modification failed.

      +
    +

    externalMessage

    +

    String

    +

    Error message. If acknowledged was set to true, null is returned for this field.

    +

    httpErrorResponse

    +

    String

    +

    HTTP error information. The default value is null.

    +
    +
    +
    +

    Example Requests

    Modify parameter settings.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/ymls/update
    +
    +{
    +  "edit" : {
    +    "modify" : {
    +      "elasticsearch.yml" : {
    +        "thread_pool.force_merge.size" : 1
    +      }
    +    }
    +  }
    +}
    +
    +

    Example Responses

    Status code: 200

    +

    Request succeeded.

    +
    {
    +  "acknowledged" : true,
    +  "externalMessage" : null,
    +  "httpErrorResponse" : null
    +}
    +
    +

    Status Codes

    +
    + + + + + + + + + + + + + + + + +

    Status Code

    +

    Description

    +

    200

    +

    Request succeeded.

    +

    400

    +

    Invalid request.

    +

    Modify the request before retry.

    +

    409

    +

    The request could not be completed due to a conflict with the current state of the resource.

    +

    The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

    +

    412

    +

    The server did not meet one of the preconditions contained in the request.

    +
    +
    +
    +

    Error Codes

    See Error Codes.

    +
    +
    +
    + +
    + diff --git a/docs/css/api-ref/UpgradeCore.html b/docs/css/api-ref/UpgradeCore.html index f7f1cb29..9da6a17c 100644 --- a/docs/css/api-ref/UpgradeCore.html +++ b/docs/css/api-ref/UpgradeCore.html @@ -1,124 +1,125 @@

    Upgrading a Cluster Kernel

    -

    Function

    This API is used to upgrade Elasticsearch from an earlier version to a later version or the same version.

    +

    Function

    This API is used to upgrade Elasticsearch from an earlier version to a later version or the same version.

    -

    Calling Method

    For details, see Calling APIs.

    -
    -

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/inst-type/{inst_type}/image/upgrade

    +

    URI

    POST /v1.0/{project_id}/clusters/{cluster_id}/inst-type/{inst_type}/image/upgrade

    -
    Table 1 Path parameters

    Parameter

    +
    - - - - - - - - - - - - - - -
    Table 1 Path Parameters

    Parameter

    Mandatory

    +

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    project_id

    +

    project_id

    Yes

    +

    Yes

    String

    +

    String

    Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    cluster_id

    +

    cluster_id

    Yes

    +

    Yes

    String

    +

    String

    ID of the cluster to be upgraded.

    +

    ID of the cluster to be upgraded.

    inst_type

    +

    inst_type

    Yes

    +

    Yes

    String

    +

    String

    Type of the node to be upgraded. Currently, its value can only be all.

    +

    Type of the node to be upgraded. Currently, its value can only be all.

    -

    Request Parameters

    -
    Table 2 Request body parameters

    Parameter

    +

    Request Parameters

    +
    - - - - - - - - - - - - - - - - - - - - - - -
    Table 2 Request body parameters

    Parameter

    Mandatory

    +

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    target_image_id

    +

    target_image_id

    Yes

    +

    Yes

    String

    +

    String

    ID of the target image version.

    +

    ID of the target image version.

    upgrade_type

    +

    upgrade_type

    Yes

    +

    Yes

    String

    +

    String

    Upgrade type.

    -
    • same: upgrade to the same version.
    • cross: upgrade to a different version.
    • crossEngine: cross-engine upgrade.
    -

    The value can be:

    -
    • same
    • cross
    • crossEngine
    +

    Upgrade type.

    +
    • same: upgrade to the same version

      +
    • cross: upgrade to a different version

      +
    • crossEngine: cross-engine upgrade.

      +

    indices_backup_check

    +

    indices_backup_check

    Yes

    +

    Yes

    Boolean

    +

    Boolean

    Indicates whether to perform backup verification.

    -
    • true: Verify the backup.
    • false: Do not verify the backup.
    -

    The value can be:

    -
    • true
    • false
    +

    Whether to perform backup verification.

    +
    • true

      +
    • false

      +

    agency

    +

    agency

    Yes

    +

    Yes

    String

    +

    String

    Agency name. You can create an agency to allow CSS to call other cloud services.

    +

    Agency name. You can create an agency to allow CSS to call other cloud services.

    cluster_load_check

    +

    cluster_load_check

    No

    +

    No

    Boolean

    +

    Boolean

    Indicates whether to verify the load. The default value is true.

    -
    • true: Verify the load.
    • false: Do not verify the load.
    +

    Indicates whether to verify the load. The default value is true.

    +
    • true: Verify the load.

      +
    • false: Do not verify the load.

      +
    -

    Response Parameters

    None

    +

    Response Parameters

    None

    -

    Request Example

    Update a cluster version.

    -
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/inst-type/all/image/upgrade
    +

    Example Requests

    Update a cluster version.

    +
    POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/inst-type/all/image/upgrade
     
     {
       "target_image_id" : "{target_image_id}",
    @@ -128,47 +129,47 @@
       "cluster_load_check" : true
     }
    -

    Response Example

    None

    +

    Example Responses

    None

    -

    Status Codes

    -

    Status Code

    +

    Status Codes

    +
    - - - - - - - - -

    Status Code

    Description

    +

    Description

    200

    +

    200

    The request is processed.

    +

    Request succeeded.

    400

    +

    400

    Invalid request.

    -

    Modify the request directly and do not attempt to retry it.

    +

    Invalid request.

    +

    The client should not repeat the request without modifications.

    409

    +

    409

    The request cannot be processed due to a conflict.

    -

    This status code indicates that the resource the client is attempting to create already exists, or that the update operation requested cannot be completed due to a conflict.

    +

    The request cannot be processed due to a conflict.

    +

    This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

    412

    +

    412

    The server did not satisfy one of the preconditions set by the requester in the request.

    +

    The server did not meet one of the preconditions contained in the request.

    -

    Error Codes

    For details, see Error Code.

    +

    Error Codes

    See Error Codes.

    diff --git a/docs/css/api-ref/UpgradeDetail.html b/docs/css/api-ref/UpgradeDetail.html index 5efbac5c..92438582 100644 --- a/docs/css/api-ref/UpgradeDetail.html +++ b/docs/css/api-ref/UpgradeDetail.html @@ -1,335 +1,339 @@

    Obtaining Upgrade Details

    -

    Function

    The upgrade takes a long time. You can call this API to check the upgrade progress on a node.

    +

    Function

    The upgrade takes a long time. You can call this API to check the upgrade progress on a node.

    -

    Calling Method

    For details, see Calling APIs.

    -
    -

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}/upgrade/detail

    +

    URI

    GET /v1.0/{project_id}/clusters/{cluster_id}/upgrade/detail

    -
    Table 1 Path parameters

    Parameter

    +
    - - - - - - - - - - -
    Table 1 Path Parameters

    Parameter

    Mandatory

    +

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    project_id

    +

    project_id

    Yes

    +

    Yes

    String

    +

    String

    Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

    +

    Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

    cluster_id

    +

    cluster_id

    Yes

    +

    Yes

    String

    +

    String

    ID of the cluster to be upgraded.

    +

    ID of the cluster to be upgraded.

    -
    Table 2 Query parameters

    Parameter

    +
    - - - - - - - - - - - - - - -
    Table 2 Query Parameters

    Parameter

    Mandatory

    +

    Mandatory

    Type

    +

    Type

    Description

    +

    Description

    start

    +

    start

    No

    +

    No

    Integer

    +

    Integer

    Offset. All VPC endpoint services after this offset will be queried. The offset must be an integer greater than 0 but less than the number of VPC endpoint services.

    +

    Offset. All VPC endpoint services after this offset will be queried. The offset must be an integer greater than 0 but less than the number of VPC endpoint services.

    limit

    +

    limit

    No

    +

    No

    Integer

    +

    Integer

    Maximum number of connections displayed on each page.

    +

    Specifies the maximum number of connections displayed on each page.

    action_mode

    +

    action_mode

    No

    +

    No

    String

    +

    String

    Upgrade querying behavior.

    -
    • If you need to query the cluster version upgrade details, leave this parameter blank.
    • If you need to query the details about AZ switchover, set this parameter to AZ_MIGRATION.
    +

    Upgrade behavior to be queried. Currently, its value can only be AZ_MIGRATION.

    -

    Request Parameters

    None

    +

    Request Parameters

    None

    -

    Response Parameters

    Status code: 200

    +

    Response Parameters

    Status code: 200

    -
    Table 3 Response body parameters

    Parameter

    +
    - - - - - - - -
    Table 3 Response body parameters

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    totalSize

    +

    totalSize

    Integer

    +

    Integer

    Number of times a request is delivered to the execution API.

    +

    Number of times a request is delivered to the execution API.

    detailList

    +

    detailList

    Array of GetUpgradeDetailInfo objects

    +

    Array of GetUpgradeDetailInfo objects

    Upgrade task details.

    +

    Upgrade task details.

    -
    Table 4 GetUpgradeDetailInfo

    Parameter

    +
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 4 GetUpgradeDetailInfo

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    id

    +

    id

    String

    +

    String

    Task ID

    +

    Task ID.

    startTime

    +

    startTime

    String

    +

    String

    Start time of the upgrade.

    +

    Start time of the upgrade.

    endTime

    +

    endTime

    String

    +

    String

    End time of the upgrade.

    +

    End time of the upgrade.

    status

    +

    status

    String

    +

    String

    Task status. The value can be:

    -
    • RUNNING: The upgrade is in progress.
    • SUCCESS: The upgrade is successful.
    • FAILED: The upgrade failed.
    • PARTIAL_FAILED: The upgrade partially failed.
    +

    Task status.

    +
    • RUNNING: The upgrade is in progress.

      +
    • SUCCESS: The upgrade succeeded.

      +
    • FAILED: The upgrade failed.

      +
    • PARTIAL_FAILED: The upgrade partially failed.

      +

    agencyName

    +

    agencyName

    String

    +

    String

    Agency name. You can create an agency to allow CSS to call other cloud services.

    +

    Agency name. You can create an agency to allow CSS to call other cloud services.

    imageInfo

    +

    imageInfo

    GetTargetImageIdDetail object

    +

    GetTargetImageIdDetail object

    Image details.

    +

    Image details.

    totalNodes

    +

    totalNodes

    String

    +

    String

    Names of the nodes to be upgraded.

    +

    Names of the nodes to be upgraded.

    completedNodes

    +

    completedNodes

    String

    +

    String

    Names of the nodes that have been upgraded.

    +

    Names of the nodes that have been upgraded.

    currentNodeName

    +

    currentNodeName

    String

    +

    String

    Names of the nodes that are being upgraded.

    +

    Names of the nodes that are being upgraded.

    executeTimes

    +

    executeTimes

    String

    +

    String

    Retried times

    +

    Number of retries.

    migrateParam

    +

    migrateParam

    String

    +

    String

    Current upgrade behavior of the cluster. The value is displayed if the query parameter exists.

    +

    Current upgrade behavior of the cluster. The value is displayed if the query parameter exists.

    finalAzInfoMap

    +

    finalAzInfoMap

    String

    +

    String

    Expected result of the cluster upgrade. The value is displayed if the query parameter exists.

    +

    Expected result of the cluster upgrade. The value is displayed if the query parameter exists.

    currentNodeDetail

    +

    currentNodeDetail

    Array of CurrentNodeDetail objects

    +

    Array of CurrentNodeDetail objects

    Task details of the node that is being upgraded.

    +

    Task details of the node that is being upgraded.

    -
    Table 5 GetTargetImageIdDetail

    Parameter

    +
    - - - - - - - - - - - - - - - - - - - -
    Table 5 GetTargetImageIdDetail

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    id

    +

    id

    String

    +

    String

    ID of an image that can be upgraded.

    +

    ID of an image that can be upgraded.

    displayName

    +

    displayName

    String

    +

    String

    Name of an image that can be upgraded.

    +

    Name of an image that can be upgraded.

    imageDesc

    +

    imageDesc

    String

    +

    String

    Image description.

    +

    Image description.

    datastoreType

    +

    datastoreType

    String

    +

    String

    Image engine type.

    +

    Image engine type.

    datastoreVersion

    +

    datastoreVersion

    String

    +

    String

    Image engine version.

    +

    Image engine version.

    priority

    +

    priority

    Integer

    +

    Integer

    Priority

    +

    Priority.

    -
    Table 6 CurrentNodeDetail

    Parameter

    +
    - - - - - - - - - - - - - - - - - - - -
    Table 6 CurrentNodeDetail

    Parameter

    Type

    +

    Type

    Description

    +

    Description

    order

    +

    order

    Integer

    +

    Integer

    Sequence number of an upgrade task.

    +

    Sequence number of an upgrade task.

    name

    +

    name

    String

    +

    String

    Upgrade task name.

    +

    Upgrade task name.

    status

    +

    status

    String

    +

    String

    Status of the current task.

    +

    Current task status.

    desc

    +

    desc

    String

    +

    String

    Description of the current task.

    +

    Description of the current task.

    beginTime

    +

    beginTime

    String

    +

    String

    Start time of the current task.

    +

    Start time of the current task.

    endTime

    +

    endTime

    String

    +

    String

    End time of the current task.

    +

    End time of the current task.

    -

    Request Example

    • Example request for upgrading a cluster.
      GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/detail
      -
    • Example request for upgrading a cluster.
      GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/detail?action_mode=AZ_MIGRATION
      +

      Example Requests

      • Example of a cluster upgrade request.

        +
        GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/detail
        +
      • Example of an AZ switchover.

        +
        GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/upgrade/detail?action_mode=AZ_MIGRATION
      -

      Response Example

      Status code: 200

      -

      The request is processed.

      -
      • Example response for upgrading a cluster image.
        {
        +

        Example Responses

        Status code: 200

        +

        Request succeeded.

        +
        • Example of a cluster image upgrade response.

          +
          {
             "totalSize" : 1,
             "detailList" : [ {
               "id" : "b7ac4c5b-3bda-4feb-a303-eb80f4bce986",
          @@ -366,7 +370,8 @@
               } ]
             } ]
           }
          -
        • Example response for switching the AZ.
          {
          +
        • Example of an AZ switchover response.

          +
          {
             "totalSize" : 1,
             "detailList" : [ {
               "id" : "8ebe958b-b8c6-4939-b5a7-85aee9468888",
          @@ -399,38 +404,40 @@
           }
        -

        Status Codes

        -

        Status Code

        +

        Status Codes

        +
        - - - - - - -

        Status Code

        Description

        +

        Description

        200

        +

        200

        The request is processed.

        +

        Request succeeded.

        400

        +

        400

        Invalid request. Modify the request directly and do not attempt to retry it.

        +

        Invalid request.

        +

        The client should not repeat the request without modifications.

        403

        +

        403

        The request is rejected. The server has received and understood the request, but refused to respond to it. Modify the request directly and do not attempt to retry it.

        +

        Request rejected.

        +

        The server has received the request and understood it, but the server refuses to respond to it. The client should not repeat the request without modifications.

        -

        Error Codes

        For details, see Error Code.

        +

        Error Codes

        See Error Codes.

        diff --git a/docs/css/api-ref/cluster_management.html b/docs/css/api-ref/cluster_management.html new file mode 100644 index 00000000..c47ddede --- /dev/null +++ b/docs/css/api-ref/cluster_management.html @@ -0,0 +1,78 @@ + + +

        Cluster Management

        +

        +
        +
        + + + +
        + diff --git a/docs/css/api-ref/css_03_0001.html b/docs/css/api-ref/css_03_0001.html index 3297a7cd..3e91440e 100644 --- a/docs/css/api-ref/css_03_0001.html +++ b/docs/css/api-ref/css_03_0001.html @@ -1,15 +1,64 @@

        Before You Start

        -
        -
        - +

        Overview

        Welcome to Cloud Search Service (CSS) API Reference. CSS is a fully managed, distributed search service that enables you to perform quick, real-time search on both structured and unstructured data. It is fully compatible with open-source Elasticsearch and provides you search, statistical analysis, and reporting capabilities.

        +

        This document provides CSS API description, syntax, parameters, and examples. CSS provides APIs for cluster management and snapshot management. You can call these APIs to easily create, query, delete, restart, and scale clusters.

        +
        You can search for information you need according to Table 1. +
        + + + + + + + + + + + + + + + + + + + +
        Table 1 Overview

        Chapter

        +

        Description

        +

        API Overview

        +

        An overview of the API and a list

        +

        Environment Preparation

        +

        Prerequisites for using the APIs.

        +

        API Calling

        +

        Representational State Transfer (REST) message bodies, calling methods, and examples

        +

        APIs for each module

        +

        APIs provided by CSS

        +

        Common Parameters

        +

        Common parameters, status codes, and error codes of CSS APIs

        +
        +
        +
        +
        +

        Supported versions

        +

        In CSS, Elasticsearch 7.6.2, 7.9.3, and 7.10.2 and Kibana 7.6.2, 7.9.3, and 7.10.2 are supported.

        +
        +

        Restrictions and Limitations

        • For more constraints, see the API descriptions.

          +
        +
        +

        Endpoints

        +

        An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For more information, see Regions and Endpoints.

        +
        +

        Concepts

        • Account

          An account is created upon successful registration with the cloud system. The account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The account is a payment entity, which should not be used directly to perform routine management. For security purposes, create Identity and Access Management (IAM) users and grant them permissions for routine management.

          +
        • User

          An IAM user is created under an account to use cloud services. Each user has its own identity credentials (password and access keys).

          +

          API authentication requires information such as the account name, username, and password.

          +
        • Region

          A region is a geographic area in which cloud resources are deployed. Availability zones (AZs) in the same region can communicate with each other over an intranet, while AZs in different regions are isolated from each other. By creating cloud resources in different regions, you can design applications to better meet customer requirements and comply with local laws and regulations.

          +
        • AZ

          An AZ comprises of one or multiple physical data centers equipped with independent ventilation, fire, water, and electricity facilities. Computing, network, storage, and other resources in an AZ are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to allow you to build cross-AZ high-availability systems.

          +
        • Project

          A project corresponds to a region. Default projects are defined to group and physically isolate resources (including compute, storage, and network resources) between different regions. Users can be granted permissions in a default project to access all resources under their accounts in the region associated with the project. If you need more refined access control, create sub-projects under a default project and purchase resources in sub-projects. Then you can assign users the permissions required to access only the resources in the specific sub-projects.

          +

          +
          Figure 1 Isolation by project
          +

          +
        • Checkpoint: When an application consumes data, the latest SN of the consumed data is recorded as a checkpoint. When the data is consumed again, the consumption can be continued based on this checkpoint.
        • APP: Multiple applications can access data in the same stream. Checkpoints generated for each application are used to record the consumed data in the stream by each application.
        +
        diff --git a/docs/css/api-ref/css_03_0008.html b/docs/css/api-ref/css_03_0008.html deleted file mode 100644 index a4f37fd9..00000000 --- a/docs/css/api-ref/css_03_0008.html +++ /dev/null @@ -1,57 +0,0 @@ - - -

        Cluster Management APIs

        -
        - - diff --git a/docs/css/api-ref/css_03_0010.html b/docs/css/api-ref/css_03_0010.html deleted file mode 100644 index c49f0b3b..00000000 --- a/docs/css/api-ref/css_03_0010.html +++ /dev/null @@ -1,27 +0,0 @@ - - -

        Snapshot Management APIs

        -
        - - diff --git a/docs/css/api-ref/css_03_0018.html b/docs/css/api-ref/css_03_0018.html deleted file mode 100644 index 138ef983..00000000 --- a/docs/css/api-ref/css_03_0018.html +++ /dev/null @@ -1,517 +0,0 @@ - - -

        Querying the List of Clusters

        -

        Function

        This API is used to query and display the cluster list and cluster status.

        -
        -

        URI

        GET /v1.0/{project_id}/clusters
        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        start

        -

        No

        -

        Integer

        -

        Start value of the query. The default value is 1, indicating that the query starts from the first cluster.

        -

        limit

        -

        No

        -

        Integer

        -

        Number of clusters to be queried. The default value is 10, indicating that 10 clusters are queried at a time.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        Table 2 describes the response parameters.

        - -
        - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Type

        -

        Description

        -

        clusters

        -

        Array of clusters objects

        -

        List of cluster objects

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 3 clusters field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        datastore

        -

        Object

        -

        Type of the data search engine. For details, see Table 4.

        -

        instances

        -

        Array of instance objects

        -

        List of node objects

        -

        updated

        -

        String

        -

        Last modification time of a cluster. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

        -

        name

        -

        String

        -

        Cluster name

        -

        created

        -

        String

        -

        Time when a cluster is created. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

        -
        NOTE:

        The returned cluster list is sorted by creation time in descending order. Specifically, the cluster with the latest creation time is at the top.

        -
        -

        id

        -

        String

        -

        Cluster ID.

        -

        status

        -

        String

        -

        Return value.

        -
        • 100: Creating.
        • 200: Available.
        • 303: Unavailable, such as creation failed.
        -

        endpoint

        -

        String

        -

        IP address and port number of the user used to access the VPC.

        -

        actionProgress

        -

        Object

        -

        Cluster operation progress, which indicates the progress of cluster creation and expansion in percentage. CREATING specifies the progress of creation.

        -

        actions

        -

        Array of strings

        -

        Current behavior on a cluster. Value REBOOTING indicates that the cluster is being restarted, GROWING indicates that capacity expansion is being performed on the cluster, RESTORING indicates that the cluster is being restored, and SNAPSHOTTING indicates that the snapshot is being created.

        -

        failed_reasons

        -

        Object

        -

        Failure cause. If the cluster is in the available status, this parameter is not returned. For details, see Table 6.

        -

        httpsEnable

        -

        Boolean

        -

        Communication encryption status.

        -

        Value false indicates that communication encryption is not enabled.

        -

        Value true indicates that communication encryption is enabled.

        -

        authorityEnable

        -

        String

        -

        Indicates whether to enable authentication. Available values include true and false. Authentication is disabled by default. When authentication is enabled, httpsEnable must be set to true.

        -
        • Value true indicates that authentication is enabled for the cluster.
        • Value false indicates that authentication is disabled for the cluster.
        -

        diskEncrypted

        -

        Boolean

        -

        Indicates whether disks are encrypted.

        -
        • Value true indicates that disks are encrypted.
        • Value false indicates that disks are not encrypted.
        -

        cmkId

        -

        String

        -

        Key ID used for disk encryption.

        -

        vpcId

        -

        String

        -

        VPC ID.

        -

        subnetId

        -

        String

        -

        Subnet ID.

        -

        securityGroupId

        -

        String

        -

        Security group ID.

        -

        tags

        -

        Array of tag objects

        -

        Tags of a cluster.

        -
        -
        - -
        - - - - - - - - - - - - - -
        Table 4 datastore field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        type

        -

        String

        -

        Supported type: elasticsearch

        -

        version

        -

        String

        -

        Engine version number.

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 5 instances field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        type

        -

        String

        -

        Supported type: ess (indicating the Elasticsearch node)

        -

        id

        -

        String

        -

        Instance ID.

        -

        name

        -

        String

        -

        Instance name.

        -

        status

        -

        String

        -

        Instance status.

        -
        • 100: Creating.
        • 200: Available.
        • 303: Unavailable, such as creation failed.
        -

        specCode

        -

        String

        -

        Node specifications.

        -

        azCode

        -

        String

        -

        AZ to which a node belongs.

        -
        -
        - -
        - - - - - - - - - - - - - -
        Table 6 failed_reasons field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        error_code

        -

        String

        -

        Error code.

        -
        • CSS.6000: indicates that a cluster fails to be created.
        • CSS.6001: indicates that a cluster fails to be scaled out.
        • CSS.6002: indicates that a cluster fails to be restarted.
        • CSS.6004: indicates that a node fails to be created in a cluster.
        • CSS.6005: indicates that the service fails to be initialized.
        -

        error_msg

        -

        String

        -

        Detailed error information.

        -
        -
        - -
        - - - - - - - - - - - - - -
        Table 7 tags field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        key

        -

        String

        -

        Tag key.

        -

        value

        -

        String

        -

        Tag value.

        -
        -
        -
        -

        Examples

        • Example request
          • Example request of querying clusters. A maximum of 10 clusters can be queried by default.
            GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters
            -
          -
          • Example request of querying clusters by page

            Example 1: Query the first two clusters.

            -

            Method 1

            -
            GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?start=1&limit=2
            -
            Method 2
            GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?limit=2
            -
            -

            Example 2: Query the first 10 clusters.

            -
            Method 1
            GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?start=1&limit=10
            -
            -
            Method 2
            GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters?start=1
            -
            -
          -
        • Example response
          {
          -    "clusters": [
          -        {
          -            "datastore": {
          -                "type": "elasticsearch",
          -                "version": "7.6.2"
          -            },
          -            "instances": [
          -                {
          -                    "status": "200",
          -                    "type": "ess",
          -                    "id": "c8c90973-924d-4201-b9ff-f32279c87d0e",
          -                    "name": "css-5492-ess-esn-1-1",
          -                    "specCode": "css.xlarge.2",
          -                    "azCode": "eu-de-01"
          -                }
          -            ],
          -            "updated": "2020-12-01T07:47:34",
          -            "name": "css-5492",
          -            "created": "2020-12-01T07:47:34",
          -            "id": "66ea1e42-4ee2-44ad-bd80-c86e6d8c6b9e",
          -            "status": "200",
          -            "endpoint": "10.16.0.151:9200",
          -            "vpcId": "e7daa617-3ee6-4ff1-b042-8cda4a006a46",
          -            "subnetId": "6253dc44-24cd-4c0a-90b3-f965e7f4dcd4",
          -            "securityGroupId": "d478041e-bcbe-4d69-a492-b6122d774b7f",
          -            "httpsEnable": false,
          -            "authorityEnable": false,
          -            "diskEncrypted": true,
          -            "cmkId": "00f05033-f8ac-4ceb-a1ce-4072fadb6b28",
          -            "actionProgress": {},
          -            "actions": [],
          -            "tags": []
          -        },
          -        {
          -            "datastore": {
          -                "type": "elasticsearch",
          -                "version": "7.6.2"
          -            },
          -            "instances": [
          -                {
          -                    "status": "200",
          -                    "type": "ess",
          -                    "id": "a24adddb-1553-4873-9978-9d064418f903",
          -                    "name": "css-1d01-ess-esn-1-1",
          -                    "specCode": "css.xlarge.2",
          -                    "azCode": "eu-de-01"
          -                }
          -            ],
          -            "updated": "2020-11-26T10:08:44",
          -            "name": "css-1d01",
          -            "created": "2020-11-26T10:08:44",
          -            "id": "af5fbac7-b386-4305-b201-820a0f51f4f1",
          -            "status": "200",
          -            "endpoint": "10.16.0.124:9200",
          -            "vpcId": "e7daa617-3ee6-4ff1-b042-8cda4a006a46",
          -            "subnetId": "6253dc44-24cd-4c0a-90b3-f965e7f4dcd4",
          -            "securityGroupId": "d478041e-bcbe-4d69-a492-b6122d774b7f",
          -            "httpsEnable": true,
          -            "authorityEnable": false,
          -            "diskEncrypted": false,
          -            "cmkId": "",
          -            "actionProgress": {},
          -            "actions": [],
          -            "tags": []
          -        },
          -        {
          -            "datastore": {
          -                "type": "elasticsearch",
          -                "version": "7.6.2"
          -            },
          -            "instances": [
          -                {
          -                    "status": "303",
          -                    "type": "ess",
          -                    "id": "071c7ecf-a11d-45bd-9564-201ceb7cfae3",
          -                    "name": "css-9b36-ess-esn-1-1",
          -                    "specCode": "css.xlarge.2",
          -                    "azCode": "eu-de-01"
          -                }
          -            ],
          -            "updated": "2020-11-13T14:33:24",
          -            "name": "css-9b36",
          -            "created": "2020-11-13T14:33:26",
          -            "id": "cdb26954-c743-47dd-b23a-b693205eb2da",
          -            "status": "303",
          -            "endpoint": null,
          -            "vpcId": "e7daa617-3ee6-4ff1-b042-8cda4a006a46",
          -            "subnetId": "6253dc44-24cd-4c0a-90b3-f965e7f4dcd4",
          -            "securityGroupId": "d478041e-bcbe-4d69-a492-b6122d774b7f",
          -            "httpsEnable": true,
          -            "authorityEnable": true,
          -            "diskEncrypted": false,
          -            "cmkId": "",
          -            "actionProgress": {},
          -            "actions": [],
          -            "tags": []
          -        }
          -    ]
          -}
          -

          -
        -
        -

        Status Code

        Table 8 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - -
        Table 8 Status codes

        Status Code

        -

        Code

        -

        Status Code Description

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        The client should not repeat the request without modifications.

        -

        404

        -

        NotFound

        -

        The requested resource cannot be found.

        -

        The client should not repeat the request without modifications.

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0019.html b/docs/css/api-ref/css_03_0019.html deleted file mode 100644 index 1c8966d2..00000000 --- a/docs/css/api-ref/css_03_0019.html +++ /dev/null @@ -1,611 +0,0 @@ - - -

        Creating a Cluster

        -

        Function

        This API is used to create a cluster.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters
        - -
        - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

        -
        -
        -
        -

        Request

        Table 2 describes the request parameters.

        - -
        - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        cluster

        -

        Yes

        -

        Object

        -

        Cluster. For details about related parameters, see Table 3.

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 3 cluster field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        instance

        -

        Yes

        -

        Object

        -

        Instance. For details about related parameters, see Table 4.

        -

        datastore

        -

        Yes

        -

        Object

        -

        Type of the data search engine. For details about related parameters, see Table 7.

        -

        name

        -

        Yes

        -

        String

        -

        Cluster name. It contains 4 to 32 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed. The value must start with a letter.

        -

        instanceNum

        -

        Yes

        -

        Integer

        -

        Number of clusters. The value range is 1 to 32.

        -

        backupStrategy

        -

        No

        -

        Object

        -

        Automatic snapshot creation. This function is disabled by default. For details about related parameters, see Table 8.

        -
        NOTE:

        The automatic snapshot creation policy is enabled only if this parameter is specified.

        -
        -

        diskEncryption

        -

        Yes

        -

        Object

        -

        Indicates whether disks are encrypted. For details about related parameters, see Table 9.

        -

        httpsEnable

        -

        No

        -

        String

        -
        Indicates whether communication is encrypted on the cluster. Available values include true and false. By default, communication encryption is disabled. When httpsEnable is set to true, authorityEnable must be set to true.
        • true: communication is encrypted on the cluster.
        • false: communication is not encrypted on the cluster.
        -
        -

        authorityEnable

        -

        No

        -

        Boolean

        -

        Indicates whether to enable authentication. Available values include true and false. Authentication is disabled by default. When authentication is enabled, httpsEnable must be set to true.

        -
        • Value true indicates that authentication is enabled for the cluster.
        • Value false indicates that authentication is disabled for the cluster.
          NOTE:

          This parameter is supported in clusters 7.1.1 or later.

          -
          -
        -

        adminPwd

        -

        No

        -

        String

        -

        Password of the cluster user admin in security mode. This parameter is mandatory only when authorityEnable is set to true.

        -
        NOTE:
        • The administrator password must meet the following requirements:
          • The password can contain 8 to 32 characters.
          • Passwords must contain at least 3 of the following character types: uppercase letters, lowercase letters, numbers, and special characters (~!@#$%^&*()-_=+\\|[{}];:,<.>/?).
          -
        • Weak password verification is required for a security cluster. You are advised to set a strong password.
        -
        -

        enterprise_project_id

        -

        No

        -

        String

        -

        Enterprise project ID. When creating a cluster, associate the enterprise project ID with the cluster. The value can contain a maximum of 36 characters. It is string 0 or in UUID format with hyphens (-). Value 0 indicates the default enterprise project.

        -
        NOTE:

        For details about how to obtain enterprise project IDs and features, see the .

        -
        -

        tags

        -

        No

        -

        Array of tag objects

        -

        Tags in a cluster.

        -
        NOTE:

        For details about the tag feature, see the Tag Management Service.

        -
        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 4 instance field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        flavorRef

        -

        Yes

        -

        String

        -

        Instance flavor name. For example:

        -
        • Value range of flavor css.medium.8: 40 GB to 640 GB
        • Value range of flavor css.xlarge.8: 40 GB to 2,560 GB
        • Value range of flavor css.2xlarge.8: 80 GB to 5,120 GB
        • Value range of flavor css.4xlarge.8: 160 GB to 10,240 GB
        • Value range of flavor css.xlarge.4: 40 GB to 1,600 GB
        • Value range of flavor css.2xlarge.4: 80 GB to 3,200 GB
        • Value range of flavor css.4xlarge.4: 100 GB to 6,400 GB
        • Value range of flavor css.8xlarge.4: 160 GB to 10,240 GB
        • Value range of flavor css.xlarge.2: 40 GB to 800 GB
        • Value range of flavor css.2xlarge.2: 80 GB to 1,600 GB
        • Value range of flavor css.4xlarge.2: 100 GB to 3,200 GB
        • Value range of flavor css.8xlarge.2: 320 GB to 10,240 GB
        - -

        volume

        -

        Yes

        -

        Object

        -

        Information about the volume. For details about related parameters, see Table 5.

        -

        nics

        -

        Yes

        -

        Object

        -

        Subnet information. For details about related parameters, see Table 6.

        -

        availability_zone

        -

        No

        -

        String

        -

        Availability zone (AZ). A single AZ is created when this parameter is not specified.

        -

        Separate multiple AZs with commas (,), for example, az1,az2. AZs must be unique and ensure that the number of nodes be at least the number of AZs.

        -

        If the number of nodes is a multiple of the number of AZs, the nodes are evenly distributed to each AZ. If the number of nodes is not a multiple of the number of AZs, the absolute difference between node quantity in any two AZs is 1 at most.

        -
        -
        - -
        - - - - - - - - - - - - - - - - -
        Table 5 volume field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        volume_type

        -

        Yes

        -

        String

        -

        COMMON: Common I/O

        -

        HIGH: High I/O

        -

        ULTRAHIGH: Ultra-high I/O

        -

        size

        -

        Yes

        -

        Integer

        -

        Volume size. The minimum value is 40. The value must be a multiple of 4 and 10.

        -

        Unit: GB

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 6 nics field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        vpcId

        -

        Yes

        -

        String

        -

        VPC ID, which is used for configuring cluster network.

        -

        netId

        -

        Yes

        -

        String

        -

        Subnet ID. All instances in a cluster must have the same subnets and security groups.

        -

        securityGroupId

        -

        Yes

        -

        String

        -

        Security group ID. All instances in a cluster must have the same subnets and security groups.

        -
        -
        - -
        - - - - - - - - - - - - - - - - -
        Table 7 datastore field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        version

        -

        Yes

        -

        String

        -

        Engine version. For details about the supported versions, see Supported Cluster Versions.

        -

        type

        -

        Yes

        -

        String

        -

        Engine type. Elasticsearch and OpenSearch are supported.

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 8 backupStrategy field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        period

        -

        Yes

        -

        String

        -

        Time when a snapshot is created every day. Snapshots can only be created on the hour. The time format is the time followed by the time zone, specifically, HH:mm z. In the format, HH:mm refers to the hour time and z refers to the time zone, for example, 00:00 GMT+08:00 and 01:00 GMT+02:00.

        -

        prefix

        -

        Yes

        -

        String

        -

        Prefix of the name of the snapshot that is automatically created.

        -

        keepday

        -

        Yes

        -

        Integer

        -

        Number of days for which automatically created snapshots are reserved.

        -

        Value range: 1 to 90

        -

        bucket

        -

        No

        -

        String

        -

        OBS bucket used for storing backup. If there is snapshot data in an OBS bucket, only the OBS bucket will be used for backup storage and cannot be changed.

        -

        basePath

        -

        No

        -

        String

        -

        Storage path of the snapshot in the OBS bucket.

        -

        agency

        -

        No

        -

        String

        -

        IAM agency used to access OBS.

        -
        NOTE:

        If none of the bucket, basePath, and agency parameters are specified, the system will automatically create an OBS bucket and an IAM agency.

        -
        -
        -
        - -
        - - - - - - - - - - - - - - - - -
        Table 9 diskEncryption field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        systemEncrypted

        -

        Yes

        -

        String

        -

        Value 1 indicates encryption is performed, and value 0 indicates encryption is not performed.

        -

        systemCmkid

        -

        Yes

        -

        String

        -

        Key ID.

        -
        • The Default Master Keys cannot be used to create grants. Specifically, you cannot use Default Master Keys whose aliases end with /default in KMS to create clusters.
        • After a cluster is created, do not delete the key used by the cluster. Otherwise, the cluster will become unavailable.
        -
        -
        - -
        - - - - - - - - - - - - - - - - -
        Table 10 tags field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        key

        -

        Yes

        -

        String

        -

        Tag key. The value can contain 1 to 36 characters. Only digits, letters, hyphens (-) and underscores (_) are allowed.

        -

        value

        -

        Yes

        -

        String

        -

        Tag value. The value can contain 0 to 43 characters. Only digits, letters, hyphens (-) and underscores (_) are allowed.

        -
        -
        -
        -

        Response

        Table 11 describes the response parameters.

        - -
        - - - - - - - - - -
        Table 11 Parameter description

        Parameter

        -

        Type

        -

        Description

        -

        cluster

        -

        Object

        -

        Cluster. For details, see Table 12.

        -
        -
        - -
        - - - - - - - - - - - - - -
        Table 12 cluster field description

        Parameter

        -

        Type

        -

        Description

        -

        id

        -

        String

        -

        Cluster ID.

        -

        name

        -

        String

        -

        Cluster name

        -
        -
        -
        -

        Examples

        Example request

        -
        POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters
        -{
        -    "cluster": {
        -        "name": "ES-Test",
        -        "instanceNum": 4,
        -        "instance": {
        -            "availability_zone": "eu-du-01",
        -            "flavorRef": "css.large.8",
        -            "volume": {
        -                "volume_type": "COMMON",
        -                "size": 100
        -            },
        -            "nics": {
        -                "vpcId": "fccd753c-91c3-40e2-852f-5ddf76d1a1b2",
        -                "netId": "af1c65ae-c494-4e24-acd8-81d6b355c9f1",
        -                "securityGroupId": "7e3fed21-1a44-4101-ab29-34e57124f614"
        -            }
        -        },
        -        "httpsEnable": "false",
        -        "diskEncryption": {
        -            "systemEncrypted": "1",
        -            "systemCmkid": "42546bb1-8025-4ad1-868f-600729c341ae"
        -        }
        -    }
        -}
        -
        Example response
        {
        -  "cluster": {
        -    "id": "ef683016-871e-48bc-bf93-74a29d60d214",
        -    "name": "ES-Test"
        -  }
        -}
        -
        -
        -

        Status Code

        Table 13 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 13 Status code

        Status Code

        -

        Code

        -

        Status Code Description

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        409

        -

        Conflict

        -

        The request cannot be processed due to a conflict.

        -

        This status code indicates that the resource that the client attempts to create already exits, or the request fails to be processed because of the update of the conflict request.

        -

        412

        -

        Precondition Failed

        -

        The server does not meet one of the preconditions that the requester puts on the request.

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0020.html b/docs/css/api-ref/css_03_0020.html deleted file mode 100644 index f7ca250d..00000000 --- a/docs/css/api-ref/css_03_0020.html +++ /dev/null @@ -1,93 +0,0 @@ - - -

        Deleting a Cluster

        -

        Function

        This API is used to delete a cluster. All resources, including customer data, of the deleted cluster will be released. For data security reasons, create a snapshot for the cluster that you want to delete.

        -
        -

        URI

        DELETE /v1.0/{project_id}/clusters/{cluster_id}
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster to be deleted.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        None

        -
        -

        Examples

        Delete the cluster whose ID is 2a197c4d-5467-4003-931d-83ec49939cf.

        -

        Example request

        -
        DELETE /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/2a197c4d-5467-4003-931d-83ec49939cf
        -

        Example response

        -

        The return value is empty.

        -
        -

        Status Code

        Table 2 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - -
        Table 2 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        404

        -

        NotFound

        -

        The requested resource cannot be found.

        -

        Modify the request instead of retrying.

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0021.html b/docs/css/api-ref/css_03_0021.html deleted file mode 100644 index d9f8d3e8..00000000 --- a/docs/css/api-ref/css_03_0021.html +++ /dev/null @@ -1,89 +0,0 @@ - - -

        Restarting a Cluster

        -

        Function

        This API is used to restart a cluster. Restarting the cluster will interrupt ongoing services.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/restart
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster to be restarted.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        None

        -
        -

        Examples

        None

        -
        -

        Status Code

        Table 2 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - -
        Table 2 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        404

        -

        NotFound

        -

        The requested resource cannot be found.

        -

        Modify the request instead of retrying.

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0024.html b/docs/css/api-ref/css_03_0024.html index b592998e..034e5359 100644 --- a/docs/css/api-ref/css_03_0024.html +++ b/docs/css/api-ref/css_03_0024.html @@ -1,215 +1,227 @@

        Change History

        -
        -

        Released On

        +

        + +
        - - - - - + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/css/api-ref/css_03_0025.html b/docs/css/api-ref/css_03_0025.html deleted file mode 100644 index b2367c45..00000000 --- a/docs/css/api-ref/css_03_0025.html +++ /dev/null @@ -1,146 +0,0 @@ - - -

        Scaling Out a Cluster with only Common Nodes

        -

        Function

        This API is used to scale out a cluster with only common nodes. Clusters with master, client, or cold data nodes cannot use this API.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/extend 
        - -

        Released On

        What's New

        +

        Description

        2024-05-17

        +

        2024-11-20

        Added:

        - -

        Modified:

        - +

        Modified:

        +

        2023-12-15

        +

        2024-09-12

        Delete the following section:

        +

        Deleted the intelligent O&M API.

        +

        2024-05-17

        +

        Added the following API:

        +
        • 13-Intelligent O&M
        • Upgrading the cluster kernel
        • Obtaining a target image ID
        • Obtaining upgrade details
        • Retrying a failed upgrade task
        • Adding Master and Client Nodes
        +

        Modified:

        +
        • Changing the Password
        +

        2023-12-15

        +

        Deleted the following section:

        Intelligent O&M

        2023-9-25

        +

        2023-9-25

        Added:

        - +

        Added the following APIs:

        +
        • Replacing Nodes
        • Changing the Security Mode
        • Changing the Security Group
        • Load balancer APIs
        • Intelligent O&M

        2023-07-04

        +

        2023-07-04

        Update example response in Restarting a Cluster.

        +

        Updated the example response in "Restarting a Cluster".

        2023-04-04

        +

        2023-04-04

        Added the cluster version Opensearch_1.3.6 in Supported Cluster Versions.

        +

        Added the supported cluster version OpenSearch 1.3.6.

        Optimize the parameter description.

        - -

        Update example response in Modifying Public Network Access Bandwidth.

        +
        • Modifying resource specifications
        • Changing the specifications of a specified node type
        • Querying basic log configurations
        +

        Modified the example request: Modifying the public access bandwidth.

        2023-03-28

        +

        2023-03-28

        • Fine-grained authorization: permission policies and actions.
        • Updated the procedure for obtaining the project ID and name.
        • Added the following API:
          • Changing a Cluster Name
          • Changing the Password
          • Changing the specifications of a specified node type
          • Scaling in a Cluster By Removing Specified Nodes
          • Removing Nodes of a Specific Type
          • Kibana public network access APIs
          • Log management APIs
          • Public network access APIs
          • VPC endpoint APIs
          • Parameter configuration APIs

        2023-02-28

        +

        2023-02-28

        Optimized response parameters in Querying Cluster Details.

        +

        Optimized response parameters for querying cluster details.

        2022-09-14

        +

        2022-09-14

        Added:

        - +

        Added:

        +
        • Creating a cluster
        • Querying the cluster list
        • Querying cluster details
        • Setting the automatic snapshot creation policy
        • Querying the automatic snapshot creation policy

        2022-07-28

        +

        2022-07-28

        • Combined "Common Request Parameters" and "Common Response Parameters" into Calling APIs.
        • Added cluster version 7.10.2.
        +
        • Combined "Common Request Parameters" and "Common Response Parameters" into "How to Call an API".
        • Added cluster version 7.10.2.

        2022-06-30

        +

        2022-06-30

        +
        • Optimized API calling methods:
          • Calling APIs
          +
        • Optimized common contents:
          • Supported Cluster Versions
          • Obtaining a Project ID and Name
          +
        • Updated error code IDs.

        2022-05-30

        +

        2022-05-30

        Added cluster version 7.9.3.

        -

        Modified: Scaling Out a Cluster with only Common Nodes.

        -

        Added cluster version 7.9.3.

        +

        Modified response parameters in the API for scaling out a cluster.

        +
        Optimized:
        • Overview
        • Obtaining a Project ID and Name
        • Error codes

        2020-08-30

        +

        2020-08-30

        • Added cluster versions 7.1.1 and 7.6.2.
        • Added the tag function.

          Tag Management APIs

          -
        • Removed "CSS Monitoring Metrics" to Cloud Search Service User Guide.
        +
        • Added cluster versions 7.1.1 and 7.6.2.
        • Added the tagging function.

          Managing tags

          +
        • Removed "CSS Monitoring Metrics" to Cloud Search Service User Guide.

        2019-03-15

        +

        2019-03-15

        • Modified API parameters in the following sections based on software changes:

          Modifying basic configurations of a cluster snapshot

          +

          Querying the automatic snapshot creation policy

          +
        • Added the API used for downloading the certificate file.

          Downloading a Certificate

        2019-02-27

        +

        2019-02-27

        Accepted in OTC-4.0/Agile.

        +

        Accepted in OTC-4.0/Agile.

        2019-01-26

        +

        2019-01-26

        • Accepted in OTC-3.2/Agile-01.2019.
        • Modified the following section based on software changes:

          Creating a cluster

          +

          Querying the cluster list

          +

          Querying cluster details

        2019-01-17

        +

        2019-01-17

        Modified the following section based on software changes:

        -

        Creating a Cluster

        +

        Modified the following section based on software changes:

        +

        Creating a cluster

        2018-12-10

        +

        2018-12-10

        Modify parameter description in the following section based on software function changes:

        -

        Creating a Cluster

        +

        Modified parameter description in the following section based on software functionality changes:

        +

        Creating a cluster

        2018-12-03

        +

        2018-12-03

        Optimized the code example:

        -

        Creating a Cluster

        +

        Optimized the code example:

        +

        Creating a cluster

        2018-11-26

        +

        2018-11-26

        Modified the parameter description.

        -

        Creating a Cluster

        +

        Modified the parameter description.

        +

        Creating a cluster

        2018-11-19

        +

        2018-11-19

        Added parameters in the following section based on software function changes:

        -

        Creating a Cluster

        -

        Querying the List of Clusters

        -

        Querying Cluster Details

        +

        Added parameters based on software functionality changes:

        +

        Creating a cluster

        +

        Querying the cluster list

        +

        Querying cluster details

        2018-11-08

        +

        2018-11-08

        Added parameters in the following section based on software function changes:

        -

        Querying the List of Clusters

        -

        Querying Cluster Details

        +

        Added parameters based on software functionality changes:

        +

        Querying the cluster list

        +

        Querying cluster details

        2018-10-29

        +

        2018-10-29

        • Accepted in OTC-3.2.
        • Modified the API parameter description.

          Manually creating a snapshot

          +

          Restoring a snapshot

          +
        • Added parameters based on software functionality changes:

          Setting the automatic snapshot creation policy

        2018-10-19

        +

        2018-10-19

        • Modified the API parameter description in the following section:

          Creating a Cluster

          -
        • Optimized the content in the "Documentation guide" table in the following section based on the API reference document template requirements:

          Before You Start

          +
        • Modified the API parameter description.

          Creating a cluster

          +
        • Optimized the tables in section "Before You Start" based on the API reference document template requirements.

          Before You Start

        2018-10-12

        +

        2018-10-12

        • Added description about the automatic snapshot deletion time in the following section:

          Setting the automatic snapshot creation policy

          +
        • Modified the parameter description in the following sections:
          • Querying the automatic snapshot creation policy
          • Manually creating a snapshot
          • Restoring a snapshot

        2018-10-08

        +

        2018-10-08

        • Accepted in OTC-3.2.
        • Modified the parameter description in the following sections:

          Restoring a Snapshot

          +
        • Accepted in OTC-3.2.
        • Modified the parameter description in the following sections:

          Restoring a snapshot

        2018-09-29

        +

        2018-09-29

        • Modified the parameter description in the following sections: -
        • Deleted information related to the extendparam parameter and modified the example response.

          Manually Creating a Snapshot

          +
        • Modified the parameter description in the following sections:
          • Creating a cluster
          • CSS Monitoring Metrics
          • Common Response Parameters
          +
        • Deleted information related to the extendparam parameter and modified the example response.

          Manually creating a snapshot

        2018-09-14

        +

        2018-09-14

        • Modified the parameter descriptions in the following section:

          Setting the automatic snapshot creation policy

        • Added the following section:

          14.7-CSS Monitoring Metrics

        2018-09-04

        +

        2018-09-04

        • Modified the parameter descriptions in the following section:

          (Not recommended) Automatically configuring basic settings of a cluster snapshot

          +
        • Modified the examples in the following sections:
          • Obtaining the instance specifications list
          • Restoring a snapshot

        2018-08-21

        +

        2018-08-21

        • Added the status codes returned by the APIs in each section.
          • Creating a cluster
          • Restarting a cluster
          • Scaling out a cluster
          • Modifying basic configurations of a cluster snapshot
          • Setting the automatic snapshot creation policy
          • Querying the automatic snapshot creation policy
          • Deleting a snapshot
          • Disabling the snapshot function
          +
        • Modified the description about the endpoint and actions parameters in the response parameter table. Added the status codes returned by the API for querying the list of clusters.

          Querying the cluster list

          +
        • Modified the description about the actions parameter in the response parameter table. Added the status code returned by the API for querying details about a cluster.

          Querying cluster details

          +
        • Modified the example response. Added the status code returned by the API for deleting a cluster.

          Deleting a cluster

          +
        • Modified the URI format. Added the status code returned by the API for obtaining the list of instance flavors.

          Obtaining the instance specifications list

          +
        • Modified the function description. Modified the example request. Added the status code returned by the API for automatically performing basic configurations for a cluster snapshot.

          (Not recommended) Automatically configuring basic settings of a cluster snapshot

          +
        • Modified the description about the indices parameter in the request parameter table. Changed parameter names bakExpectedStartTime, bakKeepDay, and bakPeriod in the table of backup field data structure description. Modified the example response. Added the status code returned by the API for manually creating a cluster snapshot.

          Manually creating a snapshot

          +
        • Changed parameter names bakExpectedStartTime, bakKeepDay, and bakPeriod in the table of backups field data structure description. Modified the example response. Added the status code returned by the API for querying the list of snapshots.

          Querying the snapshot list

          +
        • Modified the description in the request parameter table. Added the status code returned by the API for restoring snapshots.

          Restoring a snapshot

        • Added the handling method for each error code.

        2018-07-31

        +

        2018-07-31

        This is the first official release.

        +

        This issue is the first official release.

        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster to be scaled out.

        -
        -
        -
        -

        Request

        Table 2 describes the request parameters.

        - -
        - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        grow

        -

        Yes

        -

        Object

        -

        Detailed description about the cluster scale-out request. For details, see Table 3.

        -
        -
        - -
        - - - - - - - - - - - -
        Table 3 grow field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        modifySize

        -

        Yes

        -

        Integer

        -

        Number of instances in a cluster after a scale-out.

        -
        NOTE:

        The total number of existing instances and newly added instances in a cluster cannot exceed 32.

        -
        -
        -
        -
        -

        Response

        None

        -
        -

        Examples

        Example request

        -
        POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/extend
        -{
        -    "grow": 
        -        {
        -            "modifySize": 4
        -        }
        -}
        -

        Example response

        -
        {}
        -
        -

        Status Code

        Table 4 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - -
        Table 4 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        404

        -

        NotFound

        -

        The requested resource cannot be found.

        -

        Modify the request instead of retrying.

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -
        -
        -
        - -
        - -
        - diff --git a/docs/css/api-ref/css_03_0030.html b/docs/css/api-ref/css_03_0030.html deleted file mode 100644 index 7466a020..00000000 --- a/docs/css/api-ref/css_03_0030.html +++ /dev/null @@ -1,153 +0,0 @@ - - -

        Modifying Basic Configurations of a Cluster Snapshot

        -

        Using this API will automatically enable the snapshot function.

        -
        -

        Function

        This API is used to modify the basic configurations of a cluster snapshot. The basic configurations include the OBS bucket and IAM agency.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/setting
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster where index data is to be backed up.

        -
        -
        -
        -

        Request

        Table 2 describes the request parameters.

        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        bucket

        -

        Yes

        -

        String

        -

        OBS bucket used for index data backup. If there is snapshot data in an OBS bucket, only the OBS bucket is used and cannot be changed.

        -

        basePath

        -

        Yes

        -

        String

        -

        Storage path of the snapshot in the OBS bucket.

        -

        agency

        -

        Yes

        -

        String

        -

        IAM agency used to access OBS.

        -

        snapshotCmkId

        -

        No

        -

        String

        -

        Key ID used for snapshot encryption.

        -
        • The Default Master Keys cannot be used to create grants. Specifically, you cannot use Default Master Keys whose aliases end with /default in KMS to encrypt snapshots.
        • If a snapshot has been stored in the OBS bucket, you cannot modify the parameters for encrypting the snapshot.
        • If the key used for encryption is in the Pending deletion or disable state, you cannot perform backup and restoration operations on the cluster. Specifically, new snapshots cannot be created for the cluster, and existing snapshots cannot be used for restoration. In this case, switch to the KMS management console and change the state of the target key to enable so that backup and restore operations are allowed on the cluster.
        • If the key used for encryption is deleted, backup and restore operations are not allowed on the cluster. In addition, the deleted key cannot be restored. Therefore, exercise caution when deleting a key.
        • You are advised to disable the automatic snapshot creation function if the key is deleted or is in the Pending deletion or disable state. In this condition, automatic snapshot creation is allowed based on the configured snapshot policy. However, all automatic snapshot creation tasks will fail, and the failed tasks are displayed in the failed task list in the Failed Tasks dialog box.
        -
        -
        -
        -

        Response

        None

        -
        -

        Examples

        Example request

        -
        POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot/setting
        -{
        -    "bucket":"test-bucket",
        -    "agency":"usearch",
        -    "snapshotCmkId":"42546bb1-8025-4ad1-868f-600729c341aea"
        -}
        -
        -

        Status Code

        Table 3 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 3 Status code

        Status Code

        -

        Code

        -

        Status Code Description

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -

        406

        -

        Not Acceptable

        -

        The server cannot fulfill the request according to the content characteristics of the request.

        -

        412

        -

        Precondition Failed

        -

        The server does not meet one of the preconditions that the requester puts on the request.

        -

        504

        -

        Gateway Timeout

        -

        A gateway timeout error occurred.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0031.html b/docs/css/api-ref/css_03_0031.html deleted file mode 100644 index 0d2f5477..00000000 --- a/docs/css/api-ref/css_03_0031.html +++ /dev/null @@ -1,162 +0,0 @@ - - -

        Setting the Automatic Snapshot Creation Policy

        -

        Function

        This API is used to set parameters related to automatic snapshot creation. By default, a snapshot is created per day.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster where automatic snapshot creation is enabled.

        -
        -
        -
        -

        Request

        Table 2 describes the request parameters.

        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 2 Request body parameter

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        indices

        -

        No

        -

        String

        -

        Name of the index to be backed up. The value * indicates all indexes.

        -

        prefix

        -

        No

        -

        String

        -

        Prefix of automatically generated snapshots. It is manually configured. Enter up to 32 characters and start with a lowercase letter. Lowercase letters, numbers, hyphens (-), and underscores (_) are allowed.

        -
        NOTE:

        This parameter is mandatory when enable is set to true.

        -
        -

        period

        -

        No

        -

        String

        -

        Time when a snapshot is generated every day. Snapshots can only be generated on the hour. The format is HH:mm z: HH:mm refers to the hour time and z refers to the time zone. For example, 00:00 GMT+08:00 and 01:00 GMT+08:00.

        -
        NOTE:

        This parameter is mandatory when enable is set to true.

        -
        -

        keepday

        -

        No

        -

        Integer

        -

        Number of days that a snapshot can be retained. The value ranges from 1 to 90. The system automatically deletes snapshots that have been retained for the maximum allowed duration on the half hour.

        -
        NOTE:

        This parameter is mandatory when enable is set to true.

        -
        -

        enable

        -

        Yes

        -

        String

        -

        Indicates whether to enable the automatic snapshot creation policy.

        -
        • true: enabled.
        • false: disabled.
        -

        deleteAuto

        -

        No

        -

        String

        -

        Indicates whether to delete all automatically created snapshots when the automatic snapshot creation policy is disabled. The default value is false and the automatically created snapshots are not deleted when the automatic snapshot creation function is disabled. If this parameter is set to true, all automatically created snapshots are deleted when the automatic snapshot creation policy is disabled.

        -
        -
        -
        -

        Response

        None

        -
        -

        Examples

        Example request

        -
        POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot/policy
        -{
        -    "prefix":"snapshot",
        -    "period":"16:00 GMT+02:00",
        -    "keepday":7,
        -    "enable":"true"
        -}
        -
        -

        Status Code

        Table 3 describes the status code.

        - -
        - - - - - - - - - - - - - -
        Table 3 Status code

        Status Code

        -

        Code

        -

        Status Code Description

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -

        406

        -

        Not Acceptable

        -

        The server cannot fulfill the request according to the content characteristics of the request.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0032.html b/docs/css/api-ref/css_03_0032.html deleted file mode 100644 index 08c586b7..00000000 --- a/docs/css/api-ref/css_03_0032.html +++ /dev/null @@ -1,162 +0,0 @@ - - -

        Querying the Automatic Snapshot Creation Policy for a Cluster

        -

        Function

        This API is used to query the automatic snapshot creation policy for a cluster.

        -
        -

        URI

        GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster, for which the automatic snapshot creation policy is to be queried.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        Table 2 describes the response parameters.

        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Type

        -

        Description

        -

        keepday

        -

        Integer

        -

        Retention days for a snapshot.

        -

        period

        -

        String

        -

        Time when a snapshot is created every day.

        -

        prefix

        -

        String

        -

        Snapshot name prefix.

        -

        bucket

        -

        String

        -

        OBS bucket for storing snapshots.

        -

        basePath

        -

        String

        -

        Storage path of the snapshot in the OBS bucket.

        -

        agency

        -

        String

        -

        Agency used to access OBS buckets.

        -

        enable

        -

        String

        -

        Indicates whether to enable the automatic snapshot creation policy.

        -

        snapshotCmkId

        -

        String

        -

        Snapshot encryption ID. If the snapshot is not encrypted, value null is returned.

        -
        -
        -
        -

        Examples

        Example request

        -
        GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot/policy
        -

        Example response

        -
        
        -
        -
        {
        -    "keepday":2,
        -    "period":"16:00 GMT+2:00",
        -    "prefix":"snapshot",
        -    "bucket":"es-backup",
        -    "basePath": "css_repository/tests", 
        -    "agency":"usearch",
        -    "enable":"true",
        -    "snapshotCmkId" : "a7d5d58c-0330-4d25-860d-c488a4cb4ba7" 
        -}
        -
        -

        Status Code

        Table 3 describes the status code.

        - -
        - - - - - - - - - - - - - -
        Table 3 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        200

        -

        OK

        -

        The request is processed.

        -

        406

        -

        Not Acceptable

        -

        The server cannot fulfill the request according to the content characteristics of the request.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0033.html b/docs/css/api-ref/css_03_0033.html deleted file mode 100644 index 7a593149..00000000 --- a/docs/css/api-ref/css_03_0033.html +++ /dev/null @@ -1,210 +0,0 @@ - - -

        Manually Creating a Snapshot

        -

        Function

        This API is used to manually create a snapshot.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster where index data is to be backed up.

        -
        -
        -
        -

        Request

        Table 2 describes the request parameters.

        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        name

        -

        Yes

        -

        String

        -

        Snapshot name. The snapshot name must start with a letter and contains 4 to 64 characters consisting of only lowercase letters, digits, hyphens (-), and underscores (_).

        -

        description

        -

        No

        -

        String

        -

        Description of a snapshot. The value contains 0 to 256 characters, and angle brackets (<) and (>) are not allowed.

        -

        indices

        -

        No

        -

        String

        -

        Name of the index to be backed up. Multiple index names are separated by commas (,). By default, data of all indices is backed up. You can use the asterisk (*) to back up data of certain indices. For example, if you enter 2018-06*, then data of indices with the name prefix of 2018-06 will be backed up.

        -

        The value contains 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?) are not allowed.

        -
        -
        -
        -

        Response

        Table 3 describes the response parameters.

        - -
        - - - - - - - - - -
        Table 3 Parameter description

        Parameter

        -

        Type

        -

        Description

        -

        backup

        -

        Object

        -

        Snapshot object. For details, see Table 4.

        -
        -
        - -
        - - - - - - - - - - - - - -
        Table 4 backup field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        id

        -

        String

        -

        ID of the snapshot.

        -

        name

        -

        String

        -

        Snapshot name.

        -
        -
        -
        -

        Examples

        Example request

        -
        POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot
        -{
        -    "name":"snapshot_001",
        -    "indices":"myindex1,myindex2",
        -    "description":""
        -}
        -
        -

        Example response

        -
        {
        -    "backup":{
        -       "id" : "9dc4f5c9-33c0-45c7-9378-ae35ae350682",
        -       "name": "snapshot_101"
        -    }
        -}
        -

        Status Code

        Table 5 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 5 Status code

        Status Code

        -

        Code

        -

        Status Code Description

        -

        201

        -

        Created

        -

        The request for creating a resource has been fulfilled.

        -

        500

        -

        InternalServerError

        -

        The server is able to receive the request but it could not understand the request.

        -

        406

        -

        Not Acceptable

        -

        The server cannot fulfill the request according to the content characteristics of the request.

        -

        501

        -

        Not Implemented

        -

        The server does not support the requested function.

        -

        403

        -

        Forbidden

        -

        The server understood the request, but is refusing to fulfill it.

        -

        The client should not repeat the request without modifications.

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0034.html b/docs/css/api-ref/css_03_0034.html deleted file mode 100644 index 43c2b228..00000000 --- a/docs/css/api-ref/css_03_0034.html +++ /dev/null @@ -1,350 +0,0 @@ - - -

        Querying the List of Snapshots

        -

        Function

        This API is used to query all snapshots of a cluster.

        -
        -

        URI

        GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster, to which the snapshot to be queried belongs.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        -
        - - - - - - - - - -
        Table 2 backups field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        backups

        -

        Array of backup objects

        -

        Snapshot list.

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 3 backups field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        created

        -

        String

        -

        Time when a snapshot is created.

        -

        datastore

        -

        Object

        -

        Type of the data search engine. For details, see Table 4.

        -

        description

        -

        String

        -

        Description of the snapshot.

        -

        id

        -

        String

        -

        ID of the snapshot.

        -

        clusterId

        -

        String

        -

        Cluster ID

        -

        clusterName

        -

        String

        -

        Cluster name

        -

        name

        -

        String

        -

        Snapshot name

        -

        status

        -

        String

        -

        Snapshot status

        -

        updated

        -

        String

        -

        Indicates whether the snapshot status is updated

        -

        backupType

        -

        String

        -

        Value 0 indicates that automatic snapshot creation is enabled. Value 1 indicates that you need to manually create the snapshot.

        -

        backupMethod

        -

        String

        -

        Snapshot creation mode.

        -

        backupExpectedStartTime

        -

        String

        -

        Time when the snapshot starts to be executed.

        -

        backupKeepDay

        -

        Integer

        -

        Snapshot retention period.

        -

        backupPeriod

        -

        String

        -

        Time when a snapshot is executed every day.

        -

        indices

        -

        String

        -

        Indices that need to be backed up.

        -

        totalShards

        -

        Integer

        -

        Total number of shards of the indices to be backed up.

        -

        failedShards

        -

        Integer

        -

        Number of shards that fail to be backed up.

        -

        version

        -

        String

        -

        Version of the snapshot.

        -

        restoreStatus

        -

        String

        -

        Snapshot restoration status.

        -

        startTime

        -

        integer

        -

        Timestamp when the snapshot starts to be executed.

        -

        endTime

        -

        integer

        -

        Timestamp when the snapshot execution ends.

        -

        bucketName

        -

        String

        -

        Bucket for storing snapshot data.

        -
        -
        - -
        - - - - - - - - - - - - - -
        Table 4 datastore field data structure description

        Parameter

        -

        Type

        -

        Description

        -

        type

        -

        String

        -

        Supported type: elasticsearch

        -

        version

        -

        String

        -

        Engine version number.

        -
        -
        -
        -

        Examples

        Example request

        -
        GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshots
        -

        Example response

        -
        {
        -   "backups": [
        -    {
        -      "created": "2018-03-07T07:34:47",
        -      "datastore": {
        -        "type": "elasticsearch",
        -        "version": "*.*.*"
        -      },
        -      "description": "",
        -      "id": "e29d99c1-3d19-4ea4-ae8d-f252df76cbe9",
        -      "clusterId": "37cb1075-c38e-4cd8-81df-442d52df3786",
        -      "clusterName": "Es-xfx",
        -      "name": "snapshot-002",
        -      "status": "COMPLETED",
        -      "updated": "2018-03-07T07:40:12",
        -      "backupType": "1",
        -      "backupMethod": "manual",
        -      "backupExpectedStartTime": null,
        -      "backupKeepDay": null,
        -      "backupPeriod": null,
        -      "indices": ".kibana,website2",
        -      "totalShards": 6,
        -      "failedShards": 0,
        -      "version": "6.2.3",
        -      "restoreStatus": "success",
        -      "startTime": 1520408087099,
        -      "endTime": 1520408412219,
        -      "bucketName": "obs-b8ed"
        -    },
        -    {
        -      "created": "2018-03-06T15:42:37",
        -      "datastore": {
        -        "type": "elasticsearch",
        -        "version": "6.2.3"
        -      },
        -      "description": "",
        -      "id": "29a2254e-947f-4463-b65a-5f0b17515fae",
        -      "clusterId": "37cb1075-c38e-4cd8-81df-442d52df3786",
        -      "clusterName": "Es-xfx",
        -      "name": "snapshot-001",
        -      "status": "COMPLETED",
        -      "updated": "2018-03-06T15:48:04",
        -      "backupType": "1",
        -      "backupMethod": "manual",
        -      "backupExpectedStartTime": null,
        -      "backupKeepDay": null,
        -      "backupPeriod": null,
        -      "indices": ".kibana",
        -      "totalShards": 1,
        -      "failedShards": 0,
        -      "version": "6.2.3",
        -      "restoreStatus": "none",
        -      "startTime": 1520350957275,
        -      "endTime": 1520351284357,
        -      "bucketName": "obs-b8ed"
        -    }
        -  ]
        -}
        -
        -

        Status Code

        Table 5 describes the status code.

        - -
        - - - - - - - - - - - - - -
        Table 5 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -

        406

        -

        Not Acceptable

        -

        The server cannot fulfill the request according to the content characteristics of the request.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0035.html b/docs/css/api-ref/css_03_0035.html deleted file mode 100644 index 0b8404bf..00000000 --- a/docs/css/api-ref/css_03_0035.html +++ /dev/null @@ -1,158 +0,0 @@ - - -

        Restoring a Snapshot

        -

        Function

        This API is used to manually restore a snapshot.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}/restore
        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster to which the snapshot belongs.

        -

        snapshot_id

        -

        Yes

        -

        String

        -

        ID of the snapshot.

        -
        -
        -
        -

        Request

        Table 2 describes the request parameters.

        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        targetCluster

        -

        Yes

        -

        String

        -

        ID of the cluster, to which the snapshot is to be restored.

        -

        indices

        -

        No

        -

        String

        -

        Name of the index to be restored. Multiple index names are separated by commas (,). By default, data of all indices is restored. You can use the asterisk (*) to back up data of certain indices. For example, if you enter 2018-06*, then data of indices with the name prefix of 2018-06 will be restored.

        -

        The value contains 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?) are not allowed.

        -

        renamePattern

        -

        No

        -

        String

        -

        Rule for defining the indices to be restored. The value contains a maximum of 1,024 characters.

        -

        Indices that meet the filtering condition specified by this parameter are restored. The filtering condition must be specified using regular expressions. The value contains 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?,) are not allowed.

        -

        renameReplacement

        -

        No

        -

        String

        -

        Rule for renaming an index. The value contains 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?,) are not allowed. For example, value restored_index_$1 indicates that restored_ is added in front of the names of all restored indices.

        -

        The renamePattern and renameReplacement parameters must be both configured.

        -
        -
        -
        -

        Response

        None

        -
        -

        Examples

        Example request

        -
        POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot/29a2254e-947f-4463-b65a-5f0b17515fae/restore
        -{
        -    "targetCluster":"ea244205-d641-45d9-9dcb-ab2236bcd07e",
        -    "indices":"myindex1,myindex2"
        -}
        -

        Example response

        -

        The return value is empty.

        -
        -

        Status Code

        Table 3 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - -
        Table 3 Status code

        Status Code

        -

        Code

        -

        Status Code Description

        -

        201

        -

        Created

        -

        The request for creating a resource has been fulfilled.

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        403

        -

        Forbidden

        -

        The server understood the request, but is refusing to fulfill it.

        -

        The client should not repeat the request without modifications.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0036.html b/docs/css/api-ref/css_03_0036.html deleted file mode 100644 index d22a6f77..00000000 --- a/docs/css/api-ref/css_03_0036.html +++ /dev/null @@ -1,99 +0,0 @@ - - -

        Deleting a Snapshot

        -

        Function

        This API is used to delete a snapshot.

        -
        -

        URI

        DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}
        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster to which the snapshot belongs.

        -

        snapshot_id

        -

        Yes

        -

        String

        -

        ID of the snapshot to be deleted.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        None

        -
        -

        Examples

        Example request

        -
        DELETE /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot/29a2254e-947f-4463-b65a-5f0b17515fae
        -
        -

        Status Code

        Table 2 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - -
        Table 2 Status code

        Status Code

        -

        Code

        -

        Status Code Description

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        403

        -

        Forbidden

        -

        The server understood the request, but is refusing to fulfill it.

        -

        The client should not repeat the request without modifications.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0037.html b/docs/css/api-ref/css_03_0037.html deleted file mode 100644 index 60fc99a8..00000000 --- a/docs/css/api-ref/css_03_0037.html +++ /dev/null @@ -1,84 +0,0 @@ - - -

        (Not Recommended) Automatically Configuring Basic Settings of a Cluster Snapshot

        -

        The API for automatically configuring a cluster snapshot can automatically create OBS buckets and agencies for storing snapshots. If you have multiple clusters, an OBS bucket will be created for each cluster via this API during automatic configuration and consume your OBS quota. Too many OBS buckets will be difficult to manage. You are advised to perform operations in Modifying Basic Configurations of a Cluster Snapshot.

        -
        -

        Function

        This API is used to automatically set basic configurations for a cluster snapshot, including configuring OBS buckets and IAM agency.

        -
        • OBS Bucket: Enter the location of the OBS bucket used for storing snapshots.
        • IAM Agency: Authorize you to use OBS in IAM so that snapshots must be stored in OBS.
        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/auto_setting
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster where snapshots are to be backed up.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        None

        -
        -

        Examples

        Example request

        -
        POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot/auto_setting
        -
        -

        Status Code

        Table 2 describes the status code.

        - -
        - - - - - - - - - - - - - -
        Table 2 Status code

        Status Code

        -

        Code

        -

        Status Code Description

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -

        406

        -

        Not Acceptable

        -

        The server cannot fulfill the request according to the content characteristics of the request.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0038.html b/docs/css/api-ref/css_03_0038.html deleted file mode 100644 index df7807ed..00000000 --- a/docs/css/api-ref/css_03_0038.html +++ /dev/null @@ -1,198 +0,0 @@ - - -

        Scaling Out a Cluster with Special Nodes

        -

        Function

        This API is used to scale out a cluster with special nodes. That is, if a cluster has master, client, or cold data nodes, this API is used for scale-out.

        -
        -

        URI

        POST /v1.0/{project_id}/clusters/{cluster_id}/role_extend
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster to be scaled out.

        -
        -
        -
        -

        Request

        Table 2 describes the request parameters.

        - -
        - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        grow

        -

        Yes

        -

        Array of object

        -

        Detailed description about the cluster scale-out request. For details, see Table 3.

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - -
        Table 3 grow field description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        type

        -

        Yes

        -

        String

        -

        Type of the instance to be scaled out. Select at least one from ess, ess-cold, ess-master, and ess-client.

        -

        You can only add instances, rather than increase storage capacity, on nodes of the ess-master and ess-client types.

        -

        nodesize

        -

        Yes

        -

        Integer

        -

        Number of instances to be scaled out. The total number of existing instances and newly added instances in a cluster cannot exceed 32.

        -

        disksize

        -

        Yes

        -

        Integer

        -

        Storage capacity of the instance to be expanded. The total storage capacity of existing instances and newly added instances in a cluster cannot exceed the maximum instance storage capacity allowed when a cluster is being created. In addition, you can expand the instance storage capacity for a cluster for up to six times.

        -

        Unit: GB

        -
        -
        -
        -

        Response Parameters

        Table 4 describes the response parameters.

        - -
        - - - - - - - - - -
        Table 4 Parameter description

        Parameter

        -

        Type

        -

        Description

        -

        id

        -

        String

        -

        Cluster ID.

        -
        -
        -
        -

        Examples

        Example request

        -
        POST v1.0/458d905f22da49c39f609e3347d65723/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/role_extend
        -{
        -    "grow": [
        -        {
        -            "type": "ess-master",
        -            "nodesize": 2,
        -            "disksize": 0
        -        },
        -        {
        -            "type": "ess",
        -            "nodesize": 0,
        -            "disksize": 50
        -        },
        -        {
        -            "type": "ess-client",
        -            "nodesize": 1,
        -            "disksize": 0
        -        }
        -    ]
        -}
        -

        Example response

        -
        {
        -    "id": "4f3deec3-efa8-4598-bf91-560aad1377a3"
        -}
        -
        -

        Status Code

        Table 5 describes the status code.

        - -
        - - - - - - - - - - - - - - - - - -
        Table 5 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        404

        -

        NotFound

        -

        The requested resource cannot be found.

        -

        Modify the request instead of retrying.

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0039.html b/docs/css/api-ref/css_03_0039.html deleted file mode 100644 index ab67cc3b..00000000 --- a/docs/css/api-ref/css_03_0039.html +++ /dev/null @@ -1,81 +0,0 @@ - - -

        Disabling the Snapshot Function

        -

        Function

        This API is used to disable the snapshot function.

        -
        -

        URI

        DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots
        - -
        - - - - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Mandatory

        -

        Type

        -

        Description

        -

        project_id

        -

        Yes

        -

        String

        -

        Project ID. For details, see Obtaining a Project ID and Name.

        -

        cluster_id

        -

        Yes

        -

        String

        -

        ID of the cluster to which the snapshot belongs.

        -
        -
        -
        -

        Request

        None

        -
        -

        Response

        None

        -
        -

        Examples

        Example request

        -
        DELETE /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshots
        -
        -

        Status Code

        Table 2 describes the status code.

        - -
        - - - - - - - - - - - - - -
        Table 2 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        200

        -

        OK

        -

        The request is processed successfully.

        -

        406

        -

        Not Acceptable

        -

        The server cannot fulfill the request according to the content characteristics of the request.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0040.html b/docs/css/api-ref/css_03_0040.html index 142f59e7..ba996b93 100644 --- a/docs/css/api-ref/css_03_0040.html +++ b/docs/css/api-ref/css_03_0040.html @@ -1,19 +1,16 @@ - -

        Common Parameters

        - -

        +

        Appendixes

        +

        - diff --git a/docs/css/api-ref/css_03_0050.html b/docs/css/api-ref/css_03_0050.html deleted file mode 100644 index 2eaded4c..00000000 --- a/docs/css/api-ref/css_03_0050.html +++ /dev/null @@ -1,81 +0,0 @@ - - -

        Downloading the Certificate

        -

        Function

        This API is used to download the HTTPS certificate of the server.

        -
        -

        URI

        GET /v1.0/dev/cluster/sslCert
        -
        -

        Request

        None

        -
        -

        Response

        -
        - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Type

        -

        Description

        -

        certBase64

        -

        String

        -

        This string is obtained after the certificate file is transcoded using Base64. You need to run the following command to parse the string into a certificate file. The generated certificate file is saved in the folder where the command to be executed is located. In the following command, "$certBase64" indicates the string returned in the response message. The name of the generated certificate file is CloudSearchService.cert. You can specify another name for the certificate file, but must use .cert as the suffix of the name.

        -

        echo -n "$certBase64" | base64 -d > CloudSearchService.cert

        -
        -
        -
        -

        Examples

        Example request

        -
        GET /v1.0/dev/cluster/sslCert
        -

        Example response

        -
        {   "certBase64":"MIIDnTCCAoWgAwIBAgIEXXdMtTANBgkqhkiG9w0BAQsFADB/MRAwDgYDVQQGEwdHZXJtYW55MQ0wCwYDVQQIEwROb25lMQ0wCwYDVQQHEwROb25lMRkwFwYDVQQKExBPcGVuVGVsZWtvbUNsb3VkMRUwEwYDVQQLEwxEYXRhQW5hbHlzaXMxGzAZBgNVBAMTEkNsb3VkU2VhcmNoU2VydmljZTAeFw0xODExMTcxODE4NDJaFw0xOTAyMTUxODE4NDJaMH8xEDAOBgNVBAYTB0dlcm1hbnkxDTALBgNVBAgTBE5vbmUxDTALBgNVBAcTBE5vbmUxGTAXBgNVBAoTEE9wZW5UZWxla29tQ2xvdWQxFTATBgNVBAsTDERhdGFBbmFseXNpczEbMBkGA1UEAxMSQ2xvdWRTZWFyY2hTZXJ2aWNlMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApHai9+LMoFSlWqI+YodGiFLw597Vuoo7gG3qTCs+szQTn3PTZtbnzy7TNWjn8K41mkBgUY16wtkhH1nu6AmhRLpZA+2fwAz34v/tDOYahPq045bk9S/znJXQeWWeux93I15z7OP/XC68IF2AKl2NXjmm9bAD/DsqaLuJpoE77d71862sD6uRCBQYyZoQaHw+eKuL8/+5PjWvG9mS+Rxp0DcLd1waFkyK4BjB5Ae3og4bAivKo7vQHH79fgnuK0SQnNpxlU8xLIGaKsQ0/yeJrTrlfy3vBQmj949SbCzFjvmXgkbv4I0jcT5Ax1P68tlasUUnCqFTjGTbzeT82CeE6QIDAQABoyEwHzAdBgNVHQ4EFgQUPPZLu9ElUzQgKURRwn8HpzIliEcwDQYJKoZIhvcNAQELBQADggEBAI/e/sGbZ1jB3ao7Car2p7rm1Pg8ro1kSy9o+Jug6XjJpkwITKGkhPYugtGuKgL6oiYkdJhqmfrm/1R7phf1qzBgRoWtR7eCBg4uorNaYvTelAjbIoYGL03D1c5K6e1XwRsdqNWT3TwiHZ5CuiVOsjAtvt3OrvF2YtPUOJpbbvdXlnLKaLHoaklcyyMJ+KmUbkd2XFhzlhwj4eOaloL8XQcAk/urYFFNTymJPnNiEXjLAgGCfE/j8rX26WKvPUGmcuuqBiK7Ob+VfnfpnssDQoBtQsN9eUNxkYkg6eua8U6zR3nSPxXpdn+TZo3HHnUp3x0f1Xev49MHKe/aPMJOTYE="
        -}
        -

        After obtaining the preceding character string, run the following command to obtain the CloudSearchService.cert certificate file:

        -
        echo -n "MIIDnTCCAoWgAwIBAgIEXXdMtTANBgkqhkiG9w0BAQsFADB/MRAwDgYDVQQGEwdHZXJtYW55MQ0wCwYDVQQIEwROb25lMQ0wCwYDVQQHEwROb25lMRkwFwYDVQQKExBPcGVuVGVsZWtvbUNsb3VkMRUwEwYDVQQLEwxEYXRhQW5hbHlzaXMxGzAZBgNVBAMTEkNsb3VkU2VhcmNoU2VydmljZTAeFw0xODExMTcxODE4NDJaFw0xOTAyMTUxODE4NDJaMH8xEDAOBgNVBAYTB0dlcm1hbnkxDTALBgNVBAgTBE5vbmUxDTALBgNVBAcTBE5vbmUxGTAXBgNVBAoTEE9wZW5UZWxla29tQ2xvdWQxFTATBgNVBAsTDERhdGFBbmFseXNpczEbMBkGA1UEAxMSQ2xvdWRTZWFyY2hTZXJ2aWNlMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApHai9+LMoFSlWqI+YodGiFLw597Vuoo7gG3qTCs+szQTn3PTZtbnzy7TNWjn8K41mkBgUY16wtkhH1nu6AmhRLpZA+2fwAz34v/tDOYahPq045bk9S/znJXQeWWeux93I15z7OP/XC68IF2AKl2NXjmm9bAD/DsqaLuJpoE77d71862sD6uRCBQYyZoQaHw+eKuL8/+5PjWvG9mS+Rxp0DcLd1waFkyK4BjB5Ae3og4bAivKo7vQHH79fgnuK0SQnNpxlU8xLIGaKsQ0/yeJrTrlfy3vBQmj949SbCzFjvmXgkbv4I0jcT5Ax1P68tlasUUnCqFTjGTbzeT82CeE6QIDAQABoyEwHzAdBgNVHQ4EFgQUPPZLu9ElUzQgKURRwn8HpzIliEcwDQYJKoZIhvcNAQELBQADggEBAI/e/sGbZ1jB3ao7Car2p7rm1Pg8ro1kSy9o+Jug6XjJpkwITKGkhPYugtGuKgL6oiYkdJhqmfrm/1R7phf1qzBgRoWtR7eCBg4uorNaYvTelAjbIoYGL03D1c5K6e1XwRsdqNWT3TwiHZ5CuiVOsjAtvt3OrvF2YtPUOJpbbvdXlnLKaLHoaklcyyMJ+KmUbkd2XFhzlhwj4eOaloL8XQcAk/urYFFNTymJPnNiEXjLAgGCfE/j8rX26WKvPUGmcuuqBiK7Ob+VfnfpnssDQoBtQsN9eUNxkYkg6eua8U6zR3nSPxXpdn+TZo3HHnUp3x0f1Xev49MHKe/aPMJOTYE=" | base64 -d > CloudSearchService.cert
        -
        -

        Status Code

        -
        - - - - - - - - - - - - - - - - - -
        Table 2 Status codes

        Status Code

        -

        Message

        -

        Description

        -

        400

        -

        BadRequest

        -

        Invalid request.

        -

        Modify the request instead of retrying.

        -

        404

        -

        NotFound

        -

        The requested resource cannot be found.

        -

        Modify the request instead of retrying.

        -

        200

        -

        OK

        -

        The request is processed.

        -
        -
        -
        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0051.html b/docs/css/api-ref/css_03_0051.html deleted file mode 100644 index cba93f16..00000000 --- a/docs/css/api-ref/css_03_0051.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

        Overview

        -

        Welcome to Cloud Search Service API Reference. Cloud Search Service (CSS) provides hosted, distributed search engine services. It is fully compatible with open-source Elasticsearch and supports multi-condition retrieval, statistics, and reporting of structured and unstructured texts.

        -

        This document provides CSS API description, syntax, parameters, and examples. CSS provides APIs for cluster management and snapshot management. You can call these APIs to easily create, query, delete, restart, and scale clusters.

        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0053.html b/docs/css/api-ref/css_03_0053.html deleted file mode 100644 index 72bdcb8d..00000000 --- a/docs/css/api-ref/css_03_0053.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

        Endpoints

        -

        An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For the endpoints of all services, see Regions and Endpoints.

        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0056.html b/docs/css/api-ref/css_03_0056.html deleted file mode 100644 index bc1ffdc0..00000000 --- a/docs/css/api-ref/css_03_0056.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

        Supported Cluster Versions

        -

        In CSS, Elasticsearch 7.6.2, 7.9.3, and 7.10.2 are supported. OpenSearch 1.3.6 and 2.11.0 are supported. Kibana 7.6.2, 7.9.3, and 7.10.2 are supported.

        -
        -
        - -
        - diff --git a/docs/css/api-ref/css_03_0057.html b/docs/css/api-ref/css_03_0057.html index 67f7efeb..9e77fa57 100644 --- a/docs/css/api-ref/css_03_0057.html +++ b/docs/css/api-ref/css_03_0057.html @@ -1,7 +1,7 @@

        API Overview

        -

        The CSS API is a self-developed API that complies with RESTful API design specifications. You can call CSS APIs to implement the CSS functions described in Table 1.

        +

        CSS APIs comply with RESTful API design specifications. You can use the functions described in Table 1 by calling the corresponding APIs.

        @@ -9,38 +9,484 @@ - - - - - - - - - - - - + + + + + + + + +
        Table 1 API description

        Type

        Cluster management APIs

        +

        Cluster Management APIs

        You can call APIs to create clusters, scale out a cluster, view cluster details, and obtain instance specifications.

        +

        Create clusters, scale out clusters, view cluster details, and obtain instance specifications.

        Log management APIs

        +

        Kibana Public Network Access APIs

        You can call APIs to enable, disable, modify, and query logs.

        +

        Enable, disable, and modify Kibana public network access for a security-mode cluster.

        Public network access APIs

        +

        Log Management APIs

        You can call APIs to enable, disable, and modify public network access of a cluster.

        +

        Enable, disable, modify, and query logs.

        Snapshot management APIs

        +

        Public Network Access APIs

        Snapshots can be used to back up and restore data. You can call APIs to create, restore, or delete a snapshot.

        +

        Enable, disable, and modify public network access for a cluster.

        VPC endpoint APIs

        +

        Snapshot Management APIs

        You can call APIs to enable, disable, obtain, and update VPC endpoint connections.

        +

        Snapshots can be used to back up and restore data. You can use snapshot management APIs to create, restore, or delete snapshots.

        Parameter configuration APIs

        +

        VPC Endpoint APIs

        You can call APIs to modify the parameter configurations of a cluster.

        +

        Enable, disable, obtain, and update VPC endpoint connections.

        +

        Parameter Configuration APIs

        +

        Modify the parameter settings of a cluster.

        +

        Load Balancer APIs

        +

        Enable or disable load balancers, or obtain load balancer information.

        +
        +
        + +
        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        Table 2 Cluster management APIs

        API

        +

        Description

        +

        Creating a Cluster

        +

        This API is used to create a cluster.

        +

        Querying the List of Clusters

        +

        This API is used to query and display the cluster list and cluster status.

        +

        Querying Cluster Details

        +

        This API is used to query and display the details of a cluster.

        +

        Deleting a Cluster

        +

        This API is used to delete clusters.

        +

        Changing the Cluster Name

        +

        This API is used to change the name of a cluster.

        +

        Changing the Cluster Password

        +

        This API is used to change the password of a cluster.

        +

        Restarting a Cluster

        +

        This API is used to restart a cluster. Services will be interrupted during the restart.

        +

        Scaling Out a Cluster

        +

        This API is used to add instances (Elasticsearch instances only) to a cluster.

        +

        Adding Instances and Expanding Instance Storage Capacity

        +

        This API is used to add instances of different types and expand instance storage capacity in a cluster.

        +

        Changing Specifications

        +

        This API is used to modify the specifications of a cluster.

        +

        Obtaining the Instance Specifications List

        +

        This API is used to query and display the IDs of supported instance specifications.

        +

        Querying All Tags

        +

        This API is used to query all tags in a specified region.

        +

        Querying Tags of a Specified Cluster

        +

        This API is used to query the tag information about a specified cluster.

        +

        Adding Tags to a Cluster

        +

        This API is used to add tags to a cluster.

        +

        Deleting the Tags of a Cluster

        +

        This API is used to delete the tags of a cluster.

        +

        Adding or Deleting Cluster Tags in Batches

        +

        This API is used to add tags to or delete tags from a cluster in batches.

        +

        Changing the Specifications of a Specified Node Type

        +

        This API is used to modify cluster specifications. Nodes of the ess, ess-cold, ess-client, and ess-master types can be modified.

        +

        Removing Specified Nodes

        +

        This API is used to scale in a cluster by removing specified nodes.

        +

        Scaling In Nodes of a Specific Type

        +

        This API is used to remove instances of different types and reduce instance storage capacity in a cluster.

        +

        Replacing a Node

        +

        This API is used to replace a failed node.

        +

        Changing the Security Group

        +

        This API is used to change the security group after a cluster is created.

        +

        Modifying the Security Mode

        +

        This API is used to switch the security mode of a cluster.

        +

        Adding Master and Client Nodes

        +

        This API is used to add a master or client node.

        +

        Downloading a Security Certificate

        +

        This API is used to download a security certificate.

        +

        Creating a Cluster (V2)

        +

        This API is used to create a cluster with multiple node types (for example, ess, ess-cold, ess-client, and ess-master).

        +

        Restarting a Cluster (V2)

        +

        This API is used to restart nodes of all node types or the combination of some node types in the current cluster.

        +

        Rolling Restart

        +

        This API is used to restart nodes one by one, which requires a long time if the nodes have a large number of indexes.

        +
        +
        + +
        + + + + + + + + + + + + + + + + + + + +
        Table 3 Kibana public network access APIs

        API

        +

        Description

        +

        Enabling Kibana Public Access

        +

        This API is used to enable public network access to Kibana.

        +

        Disabling Kibana Public Access

        +

        This API is used to disable public network access to Kibana.

        +

        Modifying the Kibana Public Network Bandwidth

        +

        This API is used to modify the public network bandwidth of Kibana.

        +

        Modifying Kibana Public Network Access Control

        +

        This API is used to modify the Kibana public network access whitelist.

        +

        Disabling Kibana Public Network Access Control

        +

        This API is used to disable the Kibana public network access whitelist.

        +
        +
        + +
        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        Table 4 Log management APIs

        API

        +

        Description

        +

        Enabling the Log Function

        +

        This API is used to enable the log management function.

        +

        Disabling the Log Function

        +

        This API is used to disable the log management function.

        +

        Querying the Job List

        +

        This API is used to query the job list in the logs of a cluster.

        +

        Querying Basic Log Configurations

        +

        This API is used to query basic log configurations.

        +

        Modifying Basic Log Configurations

        +

        This API is used to modify basic log configurations.

        +

        Enabling the Automatic Log Backup Policy

        +

        This API is used to enable the automatic log backup policy.

        +

        Disabling the Automatic Log Backup Policy

        +

        This API is used to disable the automatic log backup policy.

        +

        Backing Up Logs

        +

        This API is used to back up logs.

        +

        Querying Logs

        +

        This API is used to query log information.

        +
        +
        + +
        + + + + + + + + + + + + + + + + + + + +
        Table 5 Public network access APIs

        API

        +

        Description

        +

        Enabling Public Network Access

        +

        This API is used to enable public network access.

        +

        Disabling Public Network Access

        +

        This API is used to disable public network access.

        +

        Modifying Public Network Access Bandwidth

        +

        This API is used to modify the public network access bandwidth.

        +

        Enabling the Public Network Access Control Whitelist

        +

        This API is used to enable the public network access control whitelist.

        +

        Disabling the Public Network Access Control Whitelist

        +

        This API is used to disable the public network access control whitelist.

        +
        +
        + +
        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        Table 6 Snapshot management APIs

        API

        +

        Description

        +

        (Not Recommended) Automatically Configuring Basic Settings of a Cluster Snapshot

        +

        This API is used to automatically configure basic settings of a cluster snapshot, including configuring OBS buckets and IAM agency.

        +

        Modifying Basic Configurations of a Cluster Snapshot

        +

        This API is used to modify the basic configurations of a cluster snapshot, including OBS buckets and IAM agency.

        +

        Manually Creating a Snapshot

        +

        This API is used to manually create a snapshot.

        +

        Restoring a Snapshot

        +

        This API is used to manually restore a snapshot.

        +

        Deleting a Snapshot

        +

        This API is used to delete a snapshot.

        +

        Setting the Automatic Snapshot Creation Policy

        +

        This API is used to configure automatic snapshot creation. By default, a snapshot is created every day.

        +

        Querying the Automatic Snapshot Creation Policy

        +

        This API is used to query the automatic snapshot creation policy of a cluster.

        +

        Querying the Snapshot List

        +

        This API is used to query the snapshot list of a specified cluster.

        +

        Disabling the Snapshot Function

        +

        This API is used to disable the snapshot function.

        +

        Enabling Automatic Snapshot Creation

        +

        This API is used to enable the automatic snapshot creation function.

        +

        Disabling Automatic Snapshot Creation

        +

        This API is used to disable the automatic snapshot creation function.

        +
        +
        + +
        + + + + + + + + + + + + + + + + + + + +
        Table 7 VPC endpoint APIs

        API

        +

        Description

        +

        Enabling the VPC Endpoint Service

        +

        This API is used to enable the VPC endpoint service.

        +

        Disabling the VPC Endpoint Service

        +

        This API is used to disable the VPC endpoint service.

        +

        Obtaining a VPC Endpoint Connection

        +

        This API is used to obtain a VPC endpoint connection.

        +

        Updating a VPC Endpoint Connection

        +

        This API is used to update a VPC endpoint connection.

        +

        Modifying the Endpoint Service Whitelist

        +

        This API is used to modify the endpoint service whitelist.

        +
        +
        + +
        + + + + + + + + + + + + + +
        Table 8 Parameter configuration APIs

        API

        +

        Description

        +

        Modifying Parameter Settings

        +

        This API is used to modify parameters.

        +

        Obtaining the Task List of Parameter Configurations

        +

        This API is used to obtain the task list of parameter configurations.

        +

        Obtaining the Parameter Configuration List

        +

        This API is used to obtain the parameter configuration list of the current cluster.

        +
        +
        + +
        + + + + + + + + + + + + + + + + + + + +
        Table 9 Load balancer APIs

        API

        +

        Description

        +

        Querying ELB V3 Load Balancers Supported by a Cluster

        +

        This API is used to query the ELB V3 load balancers supported by a cluster.

        +

        Enabling or Disabling the Elasticsearch Load Balancer

        +

        This API is used to enable or disable an Elasticsearch load balancer.

        +

        Configuring an Elasticsearch Listener

        +

        This API is used to configure an Elasticsearch listener.

        +

        Obtaining Elasticsearch ELB Information and Health Check Status

        +

        This API is used to obtain the ELB information and health check status of an Elasticsearch cluster.

        +

        Updating an Elasticsearch Listener

        +

        This API is used to update an Elasticsearch listener.

        +

        Querying the Certificate List

        +

        This API is used to query the certificate list.

        +
        diff --git a/docs/css/api-ref/css_03_0062.html b/docs/css/api-ref/css_03_0062.html index 37bb7222..fa045ad6 100644 --- a/docs/css/api-ref/css_03_0062.html +++ b/docs/css/api-ref/css_03_0062.html @@ -1,55 +1,78 @@ -

        Getting Started

        -

        This section describes how to create a CSS cluster by using APIs. Figure 1 illustrates the API calling process.

        -
        Figure 1 API calling process
        -

        The token obtained on IAM is valid for only 24 hours. If you want to use one token for authentication, you can cache it to avoid frequent calling.

        +

        Creating a Pay-per-Use Elasticsearch Cluster

        +

        This section describes how to create a CSS cluster by using APIs. Figure 1 illustrates the API calling process.

        +
        Figure 1 API calling process
        +

        The token obtained on IAM is valid for only 24 hours. If you want to use one token for authentication, you can cache it to avoid frequent calling.

        -

        Involved APIs

        If you use a token for authentication, you must obtain the token and add X-Auth-Token to the request header of the API when making an API call.

        -
        • API for obtaining tokens from IAM
        • API for creating CSS clusters
        +

        Involved APIs

        If you use a token for authentication, you must obtain the token and add X-Auth-Token to the request header of the API when making an API call.

        +
        • API for obtaining tokens from IAM
        • API for creating CSS clusters
        -

        Procedure

        1. Obtain the token. Send POST https://IAM endpoint/v3/auth/tokens.

          Obtain the token by following instructions in Authentication.

          -

          The value of X-Subject-Token in the response header is the user token.

          -
        2. Add Content-type and X-Auth-Token to the request header.
          • Content-Type: specifies the request body type or format. Its default value is application/json.
          • X-Auth-Token: Enter the user token obtained in 1.
          -
        3. Send a cluster creation request and specify the following parameters in the request body:
          POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters
          -{ 
          -    "cluster": { 
          -        "name": "ES-Test",
          -        "backupStrategy": {
          -            "period": "16:00 GMT+02:00",
          -            "prefix": "snapshot",
          -            "keepday": 7
          -        },
          -        "instanceNum": 3,
          -           "instance": { 
          -               "flavorRef": "css.large.8", 
          -                  "volume": { 
          -                         "volume_type": "COMMON", 
          -                         "size": 100
          -                  }, 
          -                  "nics": { 
          -                         "vpcId": "fccd753c-91c3-40e2-852f-5ddf76d1a1b2",
          -                         "netId": "af1c65ae-c494-4e24-acd8-81d6b355c9f1", 
          -                         "securityGroupId": "7e3fed21-1a44-4101-ab29-34e57124f614" 
          -                  }
          -           },
          -           "httpsEnable": "false",
          -           "diskEncryption" : {
          -		"systemEncrypted" : "1",
          -		"systemCmkid" : "42546bb1-8025-4ad1-868f-600729c341ae"
          -	    }
          -    } 
          +

          Procedure

          1. Obtain the token. Send POST https://IAM endpoint/v3/auth/tokens.

            Obtain the token by following instructions in Authentication.

            +

            The value of X-Subject-Token in the response header is the user token.

            +
          2. Add Content-type and X-Auth-Token to the request header.
            • Content-Type: The request body type or format. Its default value is application/json.
            • X-Auth-Token: Enter the user token obtained in 1.
            +
          3. Send a cluster creation request and specify the following parameters in the request body:

            +
            POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters
            +
            +{
            +  "cluster" : {
            +    "instance" : {
            +      "flavorRef" : "ess.spec-4u16g",
            +      "volume" : {
            +        "volume_type" : "COMMON",
            +        "size" : 120
            +      },
            +      "nics" : {
            +        "vpcId" : "{VPC ID}",
            +        "netId" : "{NET ID}",
            +        "securityGroupId" : "{Security group ID}"
            +      },
            +      "availability_zone" : "{AZ CODE}"
            +    },
            +    "datastore" : {
            +      "version" : "{cluster-version}",
            +      "type" : "elasticsearch"
            +    },
            +    "name" : "cluster-name",
            +    "instanceNum" : 3,
            +    "backupStrategy" : {
            +      "period" : "16:00 GMT+08:00",
            +      "prefix" : "snapshot",
            +      "keepday" : 7,
            +      "frequency" : "DAY",
            +      "bucket" : "css-obs-backup",
            +      "basePath" : "css_repository/obs-path",
            +      "agency" : "css_obs_agency"
            +    },
            +    "httpsEnable" : true,
            +    "authorityEnable" : true,
            +    "adminPwd" : "{password}",
            +    "enterprise_project_id" : "0",
            +    "tags" : [ {
            +      "key" : "k1",
            +      "value" : "v1"
            +    }, {
            +      "key" : "k2",
            +      "value" : "v2"
            +    } ]
            +  }
             }
            -
            View the response message. The following is an example response:
            {
            +

            +
            Check the response message. The following is an example response:
            {
               "cluster": {
                 "id": "ef683016-871e-48bc-bf93-74a29d60d214",
                 "name": "ES-Test"
               }
             }
            -

            If the request is successful, 200 OK is returned.

            -

            If the request fails, an error code and error information are returned. For details, see section Status Code.

            +

            If the request is successful, 200 OK is returned.

            +

            If the request fails, an error code and error information are returned. For details, see section Status Codes.

        +
        + +
        diff --git a/docs/css/api-ref/css_03_0065.html b/docs/css/api-ref/css_03_0065.html index 2ea37cd7..22a13e39 100644 --- a/docs/css/api-ref/css_03_0065.html +++ b/docs/css/api-ref/css_03_0065.html @@ -1,216 +1,249 @@ -

        Permissions Policies and Supported Actions

        -

        This section describes fine-grained permissions management for your CSS. If your cloud account does not need individual IAM users, then you may skip over this chapter.

        -

        By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

        -

        You can grant permissions to a role or by creating a policy. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

        -

        Policy-based authorization is useful if you want to allow or deny the access to an API.

        +

        Permissions and Supported Actions

        +

        This section describes fine-grained permissions management for your CSS. If your account does not need individual IAM users, then you may skip over this chapter.

        +

        By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

        +

        You can grant users permissions by using and . Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

        +

        Policy-based authorization is useful if you want to allow or deny the access to an API.

        -

        An account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully.

        -

        Supported Actions

        CSS provides system-defined policies that can be directly used in IAM. CSS administrators can create custom policies and use them to supplement system-defined policies, implementing more refined access control. Actions supported by policies are specific to APIs. The following are common concepts related to policies:

        -
        • Permissions: Allow or deny operations on specified resources under specific conditions.
        • APIs: REST APIs that can be called by a custom policy.
        • Actions: added to a custom policy to control permissions for specific operations.
        • Dependencies: actions which a specific action depends on. When allowing an action for a user, you also need to allow any existing action dependencies for that user.
        • IAM or enterprise projects: type of projects for which an action will take effect. Policies that contain actions supporting both IAM and enterprise projects can be assigned to user groups and take effect in both IAM and Enterprise Management. Policies that only contain actions supporting IAM projects can be assigned to user groups and only take effect for IAM.

          The check mark (√) indicates that an action takes effect. The cross mark (x) indicates that an action does not take effect.

          +

          An account has all the permissions required to call all APIs, but each IAM user must be assigned the required permissions before they can start calling APIs. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully.

          +

          Supported Actions

          CSS provides system-defined policies that can be directly used in IAM. CSS administrators can create custom policies and use them to supplement system-defined policies, implementing more refined access control. Actions supported by policies are specific to APIs. The following are common concepts related to policies:

          +
          • Permissions: Allow or deny operations on specified resources under specific conditions.
          • APIs: REST APIs that can be called by a custom policy.
          • Actions: added to a custom policy to control permissions for specific operations.
          • Related actions: actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the dependent actions.
          • IAM or enterprise projects: type of projects for which an action will take effect. Policies that contain actions supporting both IAM and enterprise projects can be assigned to user groups and take effect in both IAM and Enterprise Management. Policies that only contain actions supporting IAM projects can be assigned to user groups and only take effect for IAM.

            The check mark (√) indicates that an action takes effect. The cross mark (x) indicates that an action does not take effect.

            -
            Table 1 API actions

            Permission

            +
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + diff --git a/docs/css/api-ref/css_03_0071.html b/docs/css/api-ref/css_03_0071.html index a43987a1..388bdaa7 100644 --- a/docs/css/api-ref/css_03_0071.html +++ b/docs/css/api-ref/css_03_0071.html @@ -1,11 +1,12 @@

            Obtaining a Project ID and Name

            -

            A project ID or project name is required in some API requests. You need to obtain the project ID and name before calling an API.

            -

            Obtaining a Project ID and Name from the Console

            1. Log in to the console.
            2. In the upper right corner of the page, click the username and choose My Credentials from the drop-down list. The My Credentials page is displayed.
            3. In the project list, view the Project ID and Project Name.
            +

            A project ID or project name is required in some API requests. You need to obtain the project ID and name before calling an API.

            +

            Obtaining a Project ID and Name from the Console

            1. Log in to the console.
            2. In the upper right corner of the page, click the username and choose My Credentials from the drop-down list. The API Credentials page is displayed.
            3. In the project list, view the Project ID and Project Name.
              Figure 1 Viewing the project ID and name
              +
            -

            Obtaining a Project ID by Calling an API

            The API for obtaining a project ID is GET https://{iam-endpoint}/v3/projects. {iam-endpoint} indicates the endpoint of IAM, which can be obtained from Endpoints.

            -
            The following is an example response. For example, if CSS is deployed in region xxx, the value of name in the response body is xxx. The value of id in projects is the project ID.
            {
            +

            Obtaining a Project ID by Calling an API

            The API for obtaining a project ID is GET https://{iam-endpoint}/v3/projects. {iam-endpoint} indicates the endpoint of IAM, which can be obtained from Endpoints.

            +
            The following is an example response. For example, if CSS is deployed in region xxx, the value of name in the response body is xxx. The value of id in projects is the project ID.
            {
                 "projects": [
                     {
                         "domain_id": "65382450e8f64ac0870cd180d14exxxx",
            @@ -18,7 +19,7 @@
                             "previous": null,
                             "self": "https://www.example.com/v3/projects/a4a5d4098fb4474fa22cd05f897dxxxx"
                         },
            -            "id": "a4a5d4098fb4474fa22cd05f897dxxxx",    //Project ID
            +            "id": "a4a5d4098fb4474fa22cd05f897dxxxx",    //Project ID
                         "enabled": true
                     }
                 ],
            @@ -33,7 +34,7 @@
             
            diff --git a/docs/css/api-ref/css_03_0075.html b/docs/css/api-ref/css_03_0075.html index f98ef8bf..d2bfa533 100644 --- a/docs/css/api-ref/css_03_0075.html +++ b/docs/css/api-ref/css_03_0075.html @@ -1,320 +1,320 @@ -

            Status Code

            -

            Table 1 describes the status code.

            +

            Status Codes

            +

            Table 1 describes the status codes.

            -
            Table 1 API actions

            Permission

            API

            +

            API

            Action

            -

            +

            Action

            +

            IAM Project

            -

            +

            IAM Project

            +

            (Project)

            Enterprise Project

            -

            +

            Enterprise Project

            +

            (Enterprise Project)

            Creating a cluster

            +

            Creating a cluster

            POST /v1.0/{project_id}/clusters

            +

            POST /v1.0/{project_id}/clusters

            css:cluster:create

            +

            css:cluster:create

            √

            +

            √

            √

            +

            √

            Querying a cluster list

            +

            Querying a cluster list

            GET /v1.0/{project_id}/clusters

            +

            GET /v1.0/{project_id}/clusters

            css:cluster:list

            +

            css:cluster:list

            √

            +

            √

            √

            +

            √

            Querying cluster details

            +

            Querying cluster details

            GET /v1.0/{project_id}/clusters/{cluster_id}

            +

            GET /v1.0/{project_id}/clusters/{cluster_id}

            css:cluster:get

            +

            css:cluster:get

            √

            +

            √

            √

            +

            √

            Deleting a cluster

            +

            Deleting a cluster

            DELETE /v1.0/{project_id}/clusters/{cluster_id}

            +

            DELETE /v1.0/{project_id}/clusters/{cluster_id}

            css:cluster:delete

            +

            css:cluster:delete

            √

            +

            √

            √

            +

            √

            Restarting a cluster

            +

            Restarting a cluster

            POST /v1.0/{project_id}/clusters/{cluster_id}/restart

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/restart

            css:cluster:restart

            +

            css:cluster:restart

            √

            +

            √

            √

            +

            √

            Scaling out a cluster

            +

            Scaling out a cluster

            POST /v1.0/{project_id}/clusters/{cluster_id}/extend

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/extend

            css:cluster:scaleOut

            +

            css:cluster:scaleOut

            √

            +

            √

            √

            +

            √

            Adding instances and expanding instance storage capacity

            +

            Adding instances and expanding instance storage capacity

            POST /v1.0/{project_id}/clusters/{cluster_id}/role_extend

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/role_extend

            css:cluster:expand

            +

            css:cluster:expand

            √

            +

            √

            √

            +

            √

            Querying tags of a specified cluster

            +

            Querying tags of a specified cluster

            GET /v1.0/{project_id}/css-cluster/{cluster_id}/tags

            +

            GET /v1.0/{project_id}/css-cluster/{cluster_id}/tags

            css:tag:get

            +

            css:tag:get

            √

            +

            √

            √

            +

            √

            Automatically setting basic configurations of a cluster snapshot

            +

            Loading a custom word dictionary

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/auto_setting

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/thesaurus

            css:snapshot:enableAtomaticSnapsot

            +

            css:IKThesaurus:load

            √

            +

            √

            √

            +

            √

            Modifying basic configurations of a cluster snapshot

            +

            Querying the status of a custom word dictionary

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/setting

            +

            GET /v1.0/{project_id}/clusters/{cluster_id}/thesaurus

            css:snapshot:setSnapshotContiguration

            +

            css:IKThesaurus:get

            √

            +

            √

            √

            +

            √

            Setting the automatic snapshot creation policy

            +

            Deleting a custom word dictionary

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy

            +

            DELETE /v1.0/{project_id}/clusters/{cluster_id}/thesaurus

            css:snapshot:setSnapshotPolicy

            +

            css:IKThesaurus:delete

            √

            +

            √

            √

            +

            √

            Querying the automatic snapshot creation policy

            +

            Automatically setting basic configurations of a cluster snapshot

            GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/auto_setting

            css:snapshot:getSnapshotPolicy

            +

            css:snapshot:enableAtomaticSnapsot

            √

            +

            √

            √

            +

            √

            Manually creating a snapshot

            +

            Modifying basic configurations of a cluster snapshot

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/setting

            css:snapshot:create

            +

            css:snapshot:setSnapshotContiguration

            √

            +

            √

            √

            +

            √

            Querying the snapshot list

            +

            Setting the automatic snapshot creation policy

            GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy

            css:snapshot:list

            +

            css:snapshot:setSnapshotPolicy

            √

            +

            √

            √

            +

            √

            Restoring a snapshot

            +

            Querying the automatic snapshot creation policy

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}/restore

            +

            GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/policy

            css:snapshot:restore

            +

            css:snapshot:getSnapshotPolicy

            √

            +

            √

            √

            +

            √

            Deleting a snapshot

            +

            Manually creating a snapshot

            DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot

            css:snapshot:delete

            +

            css:snapshot:create

            √

            +

            √

            √

            +

            √

            Disabling the snapshot function

            +

            Querying the snapshot list

            DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots

            +

            GET /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots

            css:snapshot:disableSnapshotFuction

            +

            css:snapshot:list

            √

            +

            √

            √

            +

            √

            +

            Restoring a snapshot

            +

            POST /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}/restore

            +

            css:snapshot:restore

            +

            √

            +

            √

            +

            Deleting a snapshot

            +

            DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshot/{snapshot_id}

            +

            css:snapshot:delete

            +

            √

            +

            √

            +

            Disabling the snapshot function

            +

            DELETE /v1.0/{project_id}/clusters/{cluster_id}/index_snapshots

            +

            css:snapshot:disableSnapshotFuction

            +

            √

            +

            √

            Table 1 Status code description

            Status Code

            +
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -323,7 +323,7 @@
            diff --git a/docs/css/api-ref/css_03_0076.html b/docs/css/api-ref/css_03_0076.html index 63ce17d8..9c31a5f6 100644 --- a/docs/css/api-ref/css_03_0076.html +++ b/docs/css/api-ref/css_03_0076.html @@ -1,467 +1,1886 @@ -

            Error Code

            -

            No data is returned if an API fails to be invoked. You can locate the cause of an error according to the error code of each API. When the API calling fails, HTTPS status code 4xx or 5xx is returned. The returned message body contains the specific error code and error information. If you fail to locate the cause of the error, contact technical support and provide the error code for troubleshooting.

            - -
            Table 1 Status code description

            Status Code

            Code

            +

            Code

            Description

            +

            Description

            100

            +

            100

            Continue

            +

            Continue

            The client continues sending the request.

            -

            This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server.

            +

            The client continues sending the request.

            +

            This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server.

            101

            +

            101

            Switching Protocols

            +

            Switching Protocols

            Switching protocols. The target protocol must be later than the source protocol.

            -

            For example, the current HTTPS protocol is switched to a later version.

            +

            Switching protocols. The target protocol must be later than the source protocol.

            +

            For example, the current HTTPS protocol is switched to a later version.

            200

            +

            200

            OK

            +

            OK

            The request is processed successfully.

            +

            The request is processed successfully.

            201

            +

            201

            Created

            +

            Created

            The request for creating a resource has been fulfilled.

            +

            The request for creating a resource has been fulfilled.

            202

            +

            202

            Accepted

            +

            Accepted

            The request has been accepted, but the processing has not been completed.

            +

            The request has been accepted, but the processing has not been completed.

            203

            +

            203

            Non-Authoritative Information

            +

            Non-Authoritative Information

            The server successfully processed the request, but is returning information that may be from another source.

            +

            The server successfully processed the request, but is returning information that may be from another source.

            204

            +

            204

            NoContent

            +

            NoContent

            The server has successfully processed the request, but has not returned any content.

            -

            The status code is returned in response to an HTTPS OPTIONS request.

            +

            The server has successfully processed the request, but has not returned any content.

            +

            The status code is returned in response to an HTTPS OPTIONS request.

            205

            +

            205

            Reset Content

            +

            Reset Content

            The server has fulfilled the request, but the requester is required to reset the content.

            +

            The server has fulfilled the request, but the requester is required to reset the content.

            206

            +

            206

            Partial Content

            +

            Partial Content

            The server has processed certain GET requests.

            +

            The server has processed certain GET requests.

            300

            +

            300

            Multiple Choices

            +

            Multiple Choices

            There are multiple options for the location of the requested resource. The response contains a list of resource characteristics and addresses from which the user or user agent (such as a browser) can choose the most appropriate one.

            +

            There are multiple options for the location of the requested resource. The response contains a list of resource characteristics and addresses from which the user or user agent (such as a browser) can choose the most appropriate one.

            301

            +

            301

            Moved Permanently

            +

            Moved Permanently

            The requested resource has been assigned a new permanent URI, and the new URI is contained in the response.

            +

            The requested resource has been assigned a new permanent URI, and the new URI is contained in the response.

            302

            +

            302

            Found

            +

            Found

            The requested resource resides temporarily under a different URI.

            +

            The requested resource resides temporarily under a different URI.

            303

            +

            303

            See Other

            +

            See Other

            Retrieve a location.

            -

            The response to the request can be found under a different URI and should be retrieved using a GET or POST method.

            +

            Retrieve a location.

            +

            The response to the request can be found under a different URI and should be retrieved using a GET or POST method.

            304

            +

            304

            Not Modified

            +

            Not Modified

            The requested resource has not been modified. When the server returns this status code, it does not return any resources.

            +

            The requested resource has not been modified. When the server returns this status code, it does not return any resources.

            305

            +

            305

            Use Proxy

            +

            Use Proxy

            The requested resource must be accessed through a proxy.

            +

            The requested resource must be accessed through a proxy.

            306

            +

            306

            Unused

            +

            Unused

            The HTTPS status code is no longer used.

            +

            The HTTPS status code is no longer used.

            400

            +

            400

            BadRequest

            +

            BadRequest

            Invalid request.

            -

            The client should not repeat the request without modifications.

            +

            Invalid request.

            +

            The client should not repeat the request without modifications.

            401

            +

            401

            Unauthorized

            +

            Unauthorized

            The status code is returned after the client provides the authentication information, indicating that the authentication information is incorrect or invalid.

            +

            The status code is returned after the client provides the authentication information, indicating that the authentication information is incorrect or invalid.

            402

            +

            402

            Payment Required

            +

            Payment Required

            This status code is reserved for future use.

            +

            This status code is reserved for future use.

            403

            +

            403

            Forbidden

            +

            Forbidden

            The server understood the request, but is refusing to fulfill it.

            -

            The client should not repeat the request without modifications.

            +

            The server understood the request, but is refusing to fulfill it.

            +

            The client should not repeat the request without modifications.

            404

            +

            404

            NotFound

            +

            NotFound

            The requested resource cannot be found.

            -

            The client should not repeat the request without modifications.

            +

            The requested resource cannot be found.

            +

            The client should not repeat the request without modifications.

            405

            +

            405

            MethodNotAllowed

            +

            MethodNotAllowed

            The method specified in the request is not supported for the requested resource.

            -

            The client should not repeat the request without modifications.

            +

            The method specified in the request is not supported for the requested resource.

            +

            The client should not repeat the request without modifications.

            406

            +

            406

            Not Acceptable

            +

            Not Acceptable

            The server cannot fulfill the request according to the content characteristics of the request.

            +

            The server cannot fulfill the request according to the content characteristics of the request.

            407

            +

            407

            Proxy Authentication Required

            +

            Proxy Authentication Required

            This status code is similar to 401, but indicates that the client must first authenticate itself with the proxy.

            +

            This status code is similar to 401, but indicates that the client must first authenticate itself with the proxy.

            408

            +

            408

            Request Time-out

            +

            Request Time-out

            The request timed out.

            -

            The client may repeat the request without modifications at any later time.

            +

            The request timed out.

            +

            The client may repeat the request without modifications at any later time.

            409

            +

            409

            Conflict

            +

            Conflict

            The request could not be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exits, or the request fails to be processed because of the update of the conflict request.

            +

            The request could not be processed due to a conflict.

            +

            This status code indicates that the resource that the client attempts to create already exits, or the request fails to be processed because of the update of the conflict request.

            410

            +

            410

            Gone

            +

            Gone

            The requested resource is no longer available.

            -

            The status code indicates that the requested resource has been deleted.

            +

            The requested resource is no longer available.

            +

            The status code indicates that the requested resource has been deleted.

            411

            +

            411

            Length Required

            +

            Length Required

            The server refuses to process the request without a defined Content-Length.

            +

            The server refuses to process the request without a defined Content-Length.

            412

            +

            412

            Precondition Failed

            +

            Precondition Failed

            The server does not meet one of the preconditions that the requester puts on the request.

            +

            The server does not meet one of the preconditions that the requester puts on the request.

            413

            +

            413

            Request Entity Too Large

            +

            Request Entity Too Large

            The request is larger than that a server is able to process. The server may close the connection to prevent the client from continuing the request. If the server cannot process the request temporarily, the response will contain a Retry-After header field.

            +

            The request is larger than that a server is able to process. The server may close the connection to prevent the client from continuing the request. If the server cannot process the request temporarily, the response will contain a Retry-After header field.

            414

            +

            414

            Request-URI Too Large

            +

            Request-URI Too Large

            The URI provided was too long for the server to process.

            +

            The URI provided was too long for the server to process.

            415

            +

            415

            Unsupported Media Type

            +

            Unsupported Media Type

            The server is unable to process the media format in the request.

            +

            The server is unable to process the media format in the request.

            416

            +

            416

            Requested range not satisfiable

            +

            Requested range not satisfiable

            The requested range is invalid.

            +

            The requested range is invalid.

            417

            +

            417

            Expectation Failed

            +

            Expectation Failed

            The server fails to meet the requirements of the Expect request-header field.

            +

            The server fails to meet the requirements of the Expect request-header field.

            422

            +

            422

            UnprocessableEntity

            +

            UnprocessableEntity

            The request is well-formed but is unable to be processed due to semantic errors.

            +

            The request is well-formed but is unable to be processed due to semantic errors.

            429

            +

            429

            TooManyRequests

            +

            TooManyRequests

            The client has sent more requests than its rate limit is allowed within a given amount of time, or the server has received more requests than it is able to process within a given amount of time. In this case, it is advisable for the client to re-initiate requests after the time specified in the Retry-After header of the response expires.

            +

            The client has sent more requests than its rate limit is allowed within a given amount of time, or the server has received more requests than it is able to process within a given amount of time. In this case, it is advisable for the client to re-initiate requests after the time specified in the Retry-After header of the response expires.

            500

            +

            500

            InternalServerError

            +

            InternalServerError

            The server is able to receive the request but it could not understand the request.

            +

            The server is able to receive the request but it could not understand the request.

            501

            +

            501

            Not Implemented

            +

            Not Implemented

            The server does not support the requested function.

            +

            The server does not support the requested function.

            502

            +

            502

            Bad Gateway

            +

            Bad Gateway

            The server is acting as a gateway or proxy and receives an invalid request from a remote server.

            +

            The server is acting as a gateway or proxy and receives an invalid request from a remote server.

            503

            +

            503

            ServiceUnavailable

            +

            ServiceUnavailable

            The requested service is invalid.

            -

            The client should not repeat the request without modifications.

            +

            The requested service is invalid.

            +

            The client should not repeat the request without modifications.

            504

            +

            504

            ServerTimeout

            +

            ServerTimeout

            The request cannot be fulfilled within a given time. This status code is returned to the client only when the Timeout parameter is specified in the request.

            +

            The request cannot be fulfilled within a given time. This status code is returned to the client only when the Timeout parameter is specified in the request.

            505

            +

            505

            HTTP Version not supported

            +

            HTTP Version not supported

            The server does not support the HTTPS protocol version used in the request.

            +

            The server does not support the HTTPS protocol version used in the request.

            Status Code

            +

            Error Codes

            +
            +
            - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

            Status Code

            Error Code

            +

            Error Code

            Error Message

            +

            Error Message

            Measure

            +

            Description

            +

            Solution

            400

            +

            202

            CSS.0001

            +

            CSS.0011

            The parameter is incorrect.

            +

            This operation cannot be performed because another operation is being performed on the instance or the instance is faulty. Please try again later.

            Check the parameter settings according to the returned information.

            +

            This operation cannot be performed because another operation is being performed on the instance or the instance is faulty.

            +

            Please try again later.

            500

            +

            400

            CSS.0005

            +

            CSS.0001

            Server error.

            +

            Incorrect parameters.

            Contact technical support.

            +

            Incorrect parameters.

            +

            Change the parameters based on the displayed information.

            400

            +

            400

            CSS.0006

            +

            CSS.0006

            The request body is empty. Enter a request parameter.

            +

            The request is null. Enter the request parameters.

            Enter the request parameters.

            +

            The request is null. Enter a request parameter.

            +

            Enter the request parameters based on the error message.

            202

            +

            400

            CSS.0011

            +

            CSS.0017

            This operation cannot be performed because another operation is being performed on the instance or the instance is faulty. Please try again later.

            +

            Invalid parameter letter case.

            Try again later.

            +

            Invalid parameter letter case.

            +

            Set this parameter based on the naming rules.

            403

            +

            400

            CSS.0015

            +

            CSS.0021

            Resource not found or permission denied.

            +

            The account is frozen.

            Change the resource ID or check the access permission.

            +

            Frozen account.

            +

            Contact technical support.

            404

            +

            400

            CSS.0022

            +

            CSS.0026

            The instance does not exist or has been deleted.

            +

            The log size is too large.

            Change the instance ID.

            +

            The log size is too large.

            +

            Contact technical support.

            403

            +

            400

            CSS.0032

            +

            CSS.0036

            The current user has no operation permissions.

            +

            Internal error.

            Check the permissions.

            +

            An internal error occurred.

            +

            Try again later or contact technical support.

            400

            +

            400

            CSS.0045

            +

            CSS.0047

            The token is incorrect.

            +

            The cluster does not exist or has been deleted.

            Obtain the token again.

            +

            The cluster does not exist or has been deleted.

            +

            The operation cannot be performed because the cluster does not exist.

            400

            +

            400

            CSS.1112

            +

            CSS.0048

            The number of instances has reached the quota.

            +

            The OBS bucket does not exist.

            Delete some clusters or increase the quota.

            +

            The OBS bucket does not exist.

            +

            Check whether the OBS bucket exists or whether the user has the permission to access the bucket.

            400

            +

            400

            CSS.3011

            +

            CSS.0050

            Invalid retention duration of the backup.

            +

            Invalid cluster administrator password.

            Change the allowed retention duration.

            +

            Invalid cluster administrator password.

            +

            Reset the password based on the API description.

            404

            +

            400

            CSS.3027

            +

            CSS.0051

            The cluster does not exist.

            +

            The current policy does not allow the #actionName# operation.

            Check whether the cluster ID is correct.

            +

            The current policy does not allow the #actionName# operation.

            +

            Grant the required permissions to the account.

            400

            +

            400

            CSS.5007

            +

            CSS.0052

            The selected flavor does not exist.

            +

            Insufficient CPU quota.

            Check whether the specifications are correct.

            +

            Insufficient CPU quota.

            +

            Release unused clusters, reduce the number of CPUs, and increase the quota.

            400

            +

            400

            CSS.5009

            +

            CSS.0053

            The hard disk size is beyond the valid range.

            +

            Insufficient resource quota on the node.

            Change the disk size.

            +

            Insufficient resource quota on the node.

            +

            Release unused clusters, reduce the number of new nodes, and increase the quota.

            400

            +

            400

            CSS.5014

            +

            CSS.0054

            Invalid VPC ID.

            +

            Insufficient memory quota.

            Check whether the VPC ID is correct.

            +

            The memory resources are insufficient.

            +

            Release unused clusters, reduce the size of the memory you want to modify, and increase the quota.

            400

            +

            400

            CSS.5015

            +

            CSS.0055

            Invalid subnet ID.

            +

            Insufficient disk quota.

            Check whether the subnet ID is correct.

            +

            Insufficient disk quota.

            +

            Release unused clusters, reduce the size of disks, and increase the quota.

            400

            +

            400

            CSS.5021

            +

            CSS.0060

            The VPC does not exist or does not belong to the user.

            +

            Insufficient disk capacity quota.

            Check whether the VPC is correct.

            +

            Insufficient disk capacity.

            +

            Release unused resources, reduce the disk capacity required, and increase the quota.

            400

            +

            400

            CSS.5023

            +

            CSS.0061

            The security group does not exist or does not belong to the VPC.

            +

            Insufficient EIP quota.

            Check whether the security group is correct.

            +

            Insufficient EIP quota.

            +

            Release unused resources and increase the quota.

            400

            +

            400

            CSS.5157

            +

            CSS.0062

            The CIDR does not exist or is invalid.

            +

            Insufficient ELB quota.

            Check whether there are subnets in the VPC.

            +

            Insufficient ELB quota.

            +

            Release unused resources and increase the quota.

            400

            +

            400

            CSS.5036

            +

            CSS.0063

            The engine does not exist.

            +

            Insufficient VPC endpoint quota.

            Check whether the datastore parameter setting is correct.

            +

            Insufficient VPC endpoint resources.

            +

            Release unused resources and increase the quota.

            400

            +

            400

            CSS.5047

            +

            CSS.0064

            The number of instances is beyond the valid range.

            +

            Insufficient subnet IP address quota.

            Check whether the number of instances is within the range.

            +

            Insufficient subnet IP addresses.

            +

            Release unused resources and increase the quota.

            409

            +

            400

            CSS.5050

            +

            CSS.0065

            The cluster name already exists.

            +

            The disk has been sold out.

            Change the cluster name.

            +

            The disk has been sold out.

            +

            Contact technical support.

            400

            +

            400

            CSS.5052

            +

            CSS.0066

            Invalid value of the AZ.

            +

            Invalid password.

            Change the AZ.

            +

            Invalid password.

            +

            Reset the password based on the API description.

            400

            +

            400

            CSS.5055

            +

            CSS.0068

            Invalid flavor.

            +

            The flavor has been sold out.

            Modify the specifications.

            +

            The flavor has been sold out.

            +

            Release unused resources.

            400

            +

            400

            CSS.5061

            +

            CSS.0069

            The hard disk type is invalid.

            +

            The disk has been sold out.

            Change the hard disk type.

            +

            The disk has been sold out.

            +

            Release resources or increase the quota.

            400

            +

            400

            CSS.5071

            +

            CSS.0070

            The disk type does not match that in the XML configuration file.

            +

            Interconnection with the enterprise project is not supported.

            Change the hard disk type.

            +

            Interconnection with the enterprise project is not supported.

            +

            This site does not support enterprise projects.

            400

            +

            400

            CSS.5072

            +

            CSS.0071

            The security group ID is invalid.

            +

            Invalid bandwidth size.

            Change the security group ID.

            +

            Invalid bandwidth size.

            +

            Change the bandwidth size based on the error information.

            400

            +

            400

            CSS.5074

            +

            CSS.0072

            The subnet does not belong to the VPC.

            +

            Failed to create the SMN agency. Check whether the account has the required permission.

            Change the subnet ID.

            +

            Failed to create the SMN agency. Check whether the account has the permission to create an SMN agency.

            +

            Grant the required permissions to the account.

            400

            +

            400

            CSS.5077

            +

            CSS.0074

            Invalid cluster name.

            +

            The number of data nodes (including cold nodes) must be greater than or equal to three.

            Change the cluster name.

            +

            The number of data nodes (including the cold node) must be greater than or equal to 3.

            +

            Add nodes for the cluster or cancel the backup verification.

            400

            +

            400

            CSS.5078

            +

            CSS.0075

            The hard disk size is beyond the valid range.

            +

            The target flavor is not supported.

            Change the disk size.

            +

            The target flavor is not supported.

            +

            The target flavor must be smaller than the original one.

            400

            +

            400

            CSS.5092

            +

            CSS.0076

            Invalid hard disk information.

            +

            Invalid node role type.

            Modify the hard disk information.

            +

            Invalid node role type.

            +

            Change the role type based on the API parameter description.

            400

            +

            400

            CSS.5093

            +

            CSS.0077

            Invalid specification information.

            +

            The cluster is being scaled out or scaled in.

            Modify the specification information.

            +

            The cluster is being scaled out or scaled in.

            +

            Perform the operation after the cluster status becomes Available.

            412

            +

            400

            CSS.5130

            +

            CSS.0078

            The agency name is invalid.

            +

            The cluster is in a status that does not support upgrade.

            Change the agency name.

            +

            The cluster is in a status that does not support upgrade.

            +

            Perform the operation after the cluster status becomes normal.

            500

            +

            400

            CSS.9999

            +

            CSS.0080

            Request processing failed.

            +

            The default agency already exists. Check whether the agency has the required permissions before using it.

            Contact technical support.

            +

            The default agency already exists. Check whether the agency has the required permissions before using it.

            +

            Check whether the account has the required permissions.

            NA

            +

            400

            CSS.6000

            +

            CSS.0081

            Clusters fail to be created.

            +

            Failed to create the agency. Check whether the account has the permission to create an agency.

            Try again later or contact technical support.

            +

            Failed to create the agency. Check whether the account has the permission to create an agency.

            +

            Grant the required permissions to the account.

            NA

            +

            400

            CSS.6001

            +

            CSS.0082

            Cluster scale-out fails.

            -

            +

            The record does not exist.

            Try again later or contact technical support.

            +

            Record not found.

            +

            Contact technical support.

            NA

            +

            400

            CSS.6002

            +

            CSS.0083

            Failed to bind the elastic IP address to the cluster.

            +

            Some indexes have not been backed up. Perform full index backup in the snapshot module of the cluster.

            Try again later or contact technical support.

            +

            Some indexes have not been backed up. Perform full index backup in the snapshot module of the cluster.

            +

            Perform full index backup in the snapshot module of the cluster.

            N/A

            +

            400

            CSS.6003

            +

            CSS.1111

            Failed to restore the cluster.

            +

            Invalid scale-out parameters.

            Try again later or contact technical support.

            +

            Invalid scale-out parameters.

            +

            Check whether the scale-out parameters are correct.

            N/A

            +

            400

            CSS.6004

            +

            CSS.1112

            Failed to create a node.

            +

            The number of instances has reached the quota.

            Try again later or contact technical support.

            +

            The number of instances has reached the quota.

            +

            Delete some clusters or increase the quota.

            N/A

            +

            400

            CSS.6005

            +

            CSS.1119

            The initialization fails.

            +

            The Kibana public access already exists.

            Perform the initialization again or contact technical support.

            +

            The Kibana public access already exists.

            +

            Do not repeatedly bind an IP address for Kibana public access.

            NA

            +

            400

            CSS.6006

            +

            CSS.1120

            Failed to modify the specifications.

            +

            The Kibana public access does not exist.

            Perform the initialization again or contact technical support.

            +

            The Kibana public access does not exist.

            +

            Bind an IP address for Kibana public access.

            NA

            +

            400

            CSS.6007

            +

            CSS.1122

            Failed to reset the password.

            +

            To change the security mode, disable the public access and try again.

            Reset the password.

            +

            To change the security mode, disable the public access and try again.

            +

            Disable public network access.

            N/A

            +

            400

            CSS.6008

            +

            CSS.1123

            Failed to update the YML file.

            +

            To change the security mode, disable the Kibana public access and try again.

            Update the .yml file again or contact technical support.

            +

            To change the security mode, disable the Kibana public access and try again.

            +

            Disable the Kibana public access.

            N/A

            +

            400

            CSS.6009

            +

            CSS.2026

            Failed to create the snapshot.

            +

            This is a weak password. Enter a strong password.

            Try again later or contact technical support.

            +

            This is a weak password. Enter a strong password.

            +

            Enter a strong password.

            N/A

            +

            400

            CSS.6010

            +

            CSS.3011

            Failed to restore the snapshot because the OBS object does not exist or has been deleted.

            +

            Invalid retention period.

            Check whether the configured OBS object exists.

            +

            Invalid retention period.

            +

            Check whether the value is an integer ranging from 1 to 90.

            N/A

            +

            400

            CSS.6011

            +

            CSS.3016

            Failed to create the snapshot because the OBS bucket you select does not exist or has been deleted.

            +

            The backup file is being deleted. Try again later.

            Check whether the OBS bucket exists.

            +

            The backup file is being deleted. Try again later.

            +

            Perform the operation after the backup file is deleted.

            N/A

            +

            400

            CSS.6012

            +

            CSS.3026

            Failed to restore the snapshot because the OBS object does not exist or has been deleted.

            +

            The backup file does not exist.

            Check whether the OBS bucket exists.

            +

            The backup file does not exist.

            +

            An internal error occurred.

            N/A

            +

            400

            CSS.6013

            +

            CSS.3030

            The parameters cannot be modified because other operations are being performed on the cluster.

            +

            The new instance volume cannot be smaller than the old instance volume.

            Modify parameters when the cluster is available.

            +

            The new instance volume cannot be smaller than the old instance volume.

            +

            Change the parameter values as prompted.

            N/A

            +

            400

            CSS.6014

            +

            CSS.5002

            Some parameters cannot be modified.

            +

            Invalid database type.

            Check whether the submitted parameter modification request contains a parameter value that cannot be modified. If yes, delete the parameter and try again.

            +

            Invalid database type.

            +

            Currently, only Elasticsearch is supported.

            N/A

            +

            400

            CSS.6015

            +

            CSS.5003

            The parameter value is not in YAML format.

            +

            Invalid database version.

            Modify the parameter format and try again.

            +

            Invalid database version.

            +

            Elasticsearch and Kibana support versions 7.6.2 and 7.10.2.

            +

            400

            +

            CSS.5004

            +

            The datastore parameter is not specified.

            +

            The datastore parameter is not specified.

            +

            Set the datastore field.

            +

            400

            +

            CSS.5005

            +

            The database type or version is not supported.

            +

            Database type or version not supported.

            +

            Elasticsearch and Kibana support versions 7.6.2 and 7.10.2.

            +

            400

            +

            CSS.5006

            +

            Flavor is illegal.

            +

            The selected flavors are invalid.

            +

            Change the flavors based on the API parameter description.

            +

            400

            +

            CSS.5007

            +

            The selected flavors do not exist.

            +

            The selected flavor does not exist.

            +

            Change the flavors based on the API parameter description.

            +

            400

            +

            CSS.5008

            +

            Invalid volume type.

            +

            Invalid volume type.

            +

            Select a correct volume type.

            +

            400

            +

            CSS.5009

            +

            Invalid volume size.

            +

            Invalid volume size.

            +

            Enter a valid range.

            +

            400

            +

            CSS.5011

            +

            Invalid AZ.

            +

            Invalid AZ.

            +

            Select a correct AZ.

            +

            400

            +

            CSS.5017

            +

            Invalid retention period of automated backups.

            +

            Invalid retention period of automated backups.

            +

            Check whether the retention period of automated backups is set to 1 to 90 days.

            +

            400

            +

            CSS.5018

            +

            Invalid automated backup period.

            +

            Invalid automated backup period.

            +

            Only the full hour backup is supported. Add the time zone at the end of the time. The format is HH:mm z.

            +

            400

            +

            CSS.5020

            +

            Invalid automated backup start time.

            +

            Invalid automated backup start time.

            +

            Set a valid backup time based on the API parameter description.

            +

            400

            +

            CSS.5021

            +

            The VPC does not exist or does not belong to the user.

            +

            The VPC does not exist or does not belong to the user.

            +

            Check whether the VPC is correct.

            +

            400

            +

            CSS.5023

            +

            The security group does not exist or does not belong to the VPC.

            +

            The security group does not exist or does not belong to the VPC.

            +

            Check whether the security group is correctly configured.

            +

            400

            +

            CSS.5033

            +

            The volume size is not an integer multiple of 10.

            +

            The volume size is not an integer multiple of 10.

            +

            The volume size must be an integral multiple of 4 or 10.

            +

            400

            +

            CSS.5036

            +

            Datastore does not exist.

            +

            Datastore does not exist.

            +

            Currently, only Elasticsearch is supported.

            +

            400

            +

            CSS.5037

            +

            The parameter does not exist.

            +

            The parameter does not exist.

            +

            Check the parameter value range based on the API reference.

            +

            400

            +

            CSS.5038

            +

            The value of the parameter is out of range.

            +

            The parameter value is out of range.

            +

            Change the parameter values as prompted.

            +

            400

            +

            CSS.5039

            +

            Duplicate parameters.

            +

            Duplicate parameters.

            +

            Delete duplicate parameters.

            +

            400

            +

            CSS.5044

            +

            Invalid backup prefix.

            +

            Invalid backup prefix name.

            +

            Reset the backup prefix based on the API parameter description.

            +

            400

            +

            CSS.5046

            +

            NICS is left blank.

            +

            NICS is left blank.

            +

            Enter NICS (VPC and subnet information).

            +

            400

            +

            CSS.5047

            +

            Invalid instance quantity.

            +

            Invalid instance quantity.

            +

            Check the parameter value range based on the API parameter description.

            +

            400

            +

            CSS.5048

            +

            Invalid extended parameters.

            +

            Invalid extended parameters.

            +

            This error code is generated when an internal error occurred.

            +

            400

            +

            CSS.5049

            +

            Invalid cluster name.

            +

            Invalid cluster name.

            +

            Change the cluster name.

            +

            400

            +

            CSS.5050

            +

            The cluster name already exists.

            +

            The cluster name already exists.

            +

            Change the cluster name.

            +

            400

            +

            CSS.5051

            +

            Invalid IP address.

            +

            Invalid IP address.

            +

            Enter a correct IP address.

            +

            400

            +

            CSS.5052

            +

            Available zone is illegal.

            +

            Invalid AZ.

            +

            Select a correct AZ.

            +

            400

            +

            CSS.5055

            +

            Invalid flavor ID.

            +

            Invalid flavor ID.

            +

            Change the flavor ID based on the API parameter description.

            +

            400

            +

            CSS.5056

            +

            Invalid string length.

            +

            The character string length is invalid.

            +

            Check the supported character string length based on the displayed information.

            +

            400

            +

            CSS.5057

            +

            The cluster name contains invalid characters or the name length is not allowed.

            +

            The cluster name contains invalid characters or the name length is invalid.

            +

            Change the cluster name.

            +

            400

            +

            CSS.5059

            +

            Invalid database username.

            +

            Invalid database user name.

            +

            Currently, only Elasticsearch is supported.

            +

            400

            +

            CSS.5061

            +

            Invalid volume type.

            +

            Invalid volume type.

            +

            Check whether the volume type is supported based on the API reference.

            +

            400

            +

            CSS.5063

            +

            Invalid value of the Specific parameter.

            +

            Invalid Specific field.

            +

            Internal error.

            +

            400

            +

            CSS.5068

            +

            Invalid hard disk parameters.

            +

            Invalid hard disk parameters.

            +

            Contact technical support.

            +

            400

            +

            CSS.5069

            +

            Invalid node quantity.

            +

            The number of nodes is invalid.

            +

            Change the number of nodes based on the API parameter description.

            +

            400

            +

            CSS.5073

            +

            Instances of this type cannot be restarted separately.

            +

            Instances of this type cannot be restarted separately.

            +

            Do not select a type that is not contained in the resource.

            +

            400

            +

            CSS.5074

            +

            Subnet does not belong to VPC

            +

            The subnet does not belong to the VPC.

            +

            Check and enter correct subnet parameters.

            +

            400

            +

            CSS.5077

            +

            Invalid cluster name.

            +

            Invalid cluster name.

            +

            Change the cluster name.

            +

            400

            +

            CSS.5078

            +

            Invalid disk size.

            +

            The disk size is beyond the valid range.

            +

            Change the disk size range based on the API parameter description.

            +

            400

            +

            CSS.5087

            +

            Inconsistent disk specifications are used for the same type of instances.

            +

            The same instance type does not meet disk consistency requirements.

            +

            Internal error.

            +

            400

            +

            CSS.5088

            +

            The SSL is not globally consistent.

            +

            The SSL is not globally consistent.

            +

            Internal error.

            +

            400

            +

            CSS.5090

            +

            In this status, the current operation is not allowed.

            +

            In this status, the current operation is not allowed.

            +

            Rectify the fault based on the error information and then perform the operation again.

            +

            400

            +

            CSS.5091

            +

            The number of nodes has reached the upper limit. Contact the administrator.

            +

            The number of nodes has reached the upper limit. Contact the administrator.

            +

            Adjust the number of nodes.

            +

            400

            +

            CSS.5092

            +

            Invalid storage information.

            +

            Invalid storage information.

            +

            Internal error.

            +

            400

            +

            CSS.5093

            +

            Invalid node specifications.

            +

            Invalid node specifications.

            +

            Change the node specifications based on the API used to obtain the instance specifications list.

            +

            400

            +

            CSS.5094

            +

            Invalid node scale-out type.

            +

            The node scale-out type is invalid.

            +

            Check and enter a valid node type.

            +

            400

            +

            CSS.5095

            +

            The current instance type does not support this operation.

            +

            The current instance type does not support this operation.

            +

            The local disk does not support this operation.

            +

            400

            +

            CSS.5098

            +

            Invalid EIP binding type.

            +

            Invalid EIP binding type.

            +

            Change the EIP binding type based on the API parameter description.

            +

            400

            +

            CSS.5106

            +

            Invalid instance type.

            +

            Invalid instance type.

            +

            Enter a correct instance type.

            +

            400

            +

            CSS.5107

            +

            Invalid cluster mode.

            +

            Invalid cluster mode.

            +

            Internal error.

            +

            400

            +

            CSS.5110

            +

            Inconsistent parameter groups are used for the same type of instances.

            +

            Parameter groups of instances of the same type are inconsistent.

            +

            Internal error.

            +

            400

            +

            CSS.5111

            +

            The backup file ID does not exist.

            +

            The backup file ID does not exist.

            +

            Contact technical support.

            +

            400

            +

            CSS.5130

            +

            Invalid agency name.

            +

            Invalid agency name.

            +

            Perform operations based on the error information.

            +

            400

            +

            CSS.5134

            +

            The total number of master nodes must be an odd number.

            +

            The total number of master nodes must be an odd number.

            +

            Change the parameters based on the error information.

            +

            400

            +

            CSS.5135

            +

            The disk size must be a multiple of 20.

            +

            The disk size must be a multiple of 20.

            +

            Change the parameters based on the error information.

            +

            400

            +

            CSS.5137

            +

            Invalid tag key.

            +

            Invalid tag key.

            +

            Change the parameter based on the error information.

            +

            400

            +

            CSS.5138

            +

            Invalid tag value.

            +

            Invalid tag value.

            +

            Change the parameter based on the error information.

            +

            400

            +

            CSS.5140

            +

            The cluster does not support this operation.

            +

            The cluster does not support the operation.

            +

            Perform this operation after the cluster status becomes normal.

            +

            400

            +

            CSS.5141

            +

            Tag not found.

            +

            The label does not exist.

            +

            Check whether the tag in the request body belongs to the cluster.

            +

            400

            +

            CSS.5158

            +

            Only bound public IP addresses can be unbound from clusters.

            +

            Only bound public IP addresses can be unbound from clusters.

            +

            Check the public access binding status.

            +

            400

            +

            CSS.5159

            +

            Only unbound public IP addresses can be bound to clusters.

            +

            Only unbound public IP addresses can be bound to clusters.

            +

            Check the public access binding status.

            +

            400

            +

            CSS.5160

            +

            Failed to bind the public IP address. Please try again.

            +

            Failed to bind the public IP address. Please try again.

            +

            Try again later or contact technical support.

            +

            400

            +

            CSS.5164

            +

            Failed to update the public network access whitelist. Please try again.

            +

            Failed to update the public network access whitelist. Please try again.

            +

            Try again later or contact technical support.

            +

            400

            +

            CSS.5167

            +

            No data nodes are selected.

            +

            No data nodes are selected.

            +

            Select at least one data node.

            +

            400

            +

            CSS.5169

            +

            The selected version does not support the security mode.

            +

            The selected version does not support the security mode.

            +

            For details about how to create a security cluster, see the Cloud Search Service User Guide.

            +

            400

            +

            CSS.5170

            +

            The volume parameter is not required for local disk specifications.

            +

            The volume parameter is not required when configuring the local disk specifications.

            +

            Delete the specified volume value based on the error information.

            +

            400

            +

            CSS.5171

            +

            If httpsEnable is set to true, authorityEnable cannot be set to false.

            +

            If httpsEnable is set to true, authorityEnable cannot be set to false.

            +

            If httpsEnable is set to true, authorityEnable cannot be set to false.

            +

            400

            +

            CSS.5172

            +

            The number of instances must be greater than or equal to the number of AZs.

            +

            The number of instances must be greater than or equal to the number of AZs.

            +

            Increase the number of instances.

            +

            400

            +

            CSS.5174

            +

            Failed to obtain VPC information. Try again later.

            +

            Failed to obtain VPC information. Try again later.

            +

            Check whether the VPC exists and the network is normal.

            +

            400

            +

            CSS.5177

            +

            The https enable parameter is not specified.

            +

            The https enable parameter is not specified.

            +

            The httpsEnable parameter is mandatory.

            +

            400

            +

            CSS.5178

            +

            Invalid time zone.

            +

            Invalid time zone.

            +

            Change the time zone format based on the API parameter description.

            +

            400

            +

            CSS.5180

            +

            Kibana public access is not enabled.

            +

            Kibana public access is not enabled.

            +

            Enable Kibana public access.

            +

            400

            +

            CSS.5181

            +

            The whitelist does not exist.

            +

            The trustlist does not exist.

            +

            The current whitelist is empty. Add content to the whitelist and then perform related operations.

            +

            400

            +

            CSS.5182

            +

            The VPC endpoint service is not enabled.

            +

            The VPC endpoint service is not enabled.

            +

            Enable the VPC endpoint service and then perform related operations.

            +

            400

            +

            CSS.5300

            +

            This operation is not allowed for yearly/monthly clusters.

            +

            This operation is not allowed for yearly/monthly clusters.

            +

            This operation is forbidden. (Internal error)

            +

            400

            +

            CSS.5301

            +

            This operation is not allowed because the cluster has been frozen.

            +

            This operation is not allowed because the cluster has been frozen.

            +

            If the account is frozen due to arrears, renew the account.

            +

            400

            +

            CSS.5302

            +

            Invalid subscription period type.

            +

            Invalid subscription type.

            +

            Modify the subscription period type based on the API parameter description.

            +

            400

            +

            CSS.5303

            +

            Invalid subscription period.

            +

            Invalid subscription period.

            +

            Modify the subscription period based on the API parameter description.

            +

            400

            +

            CSS.5304

            +

            Invalid auto-renewal parameter.

            +

            Invalid auto-renewal parameter.

            +

            Modify the renewal parameters based on the API parameter description.

            +

            400

            +

            CSS.5305

            +

            Invalid automated payment parameters.

            +

            Invalid automatic payment parameters.

            +

            Modify the automatic payment parameters based on the API parameter description.

            +

            400

            +

            CSS.5306

            +

            An unpaid order exists.

            +

            An unpaid order exists.

            +

            Pay for or cancel the order.

            +

            400

            +

            CSS.5307

            +

            An order is being processed.

            +

            An order is being processed.

            +

            Wait until the order is processed.

            +

            400

            +

            CSS.5308

            +

            The bandwidth exceeds the limit.

            +

            The bandwidth exceeds the limit.

            +

            Reduce the bandwidth.

            +

            400

            +

            CSS.5310

            +

            If httpsEnable is set to false, public network access cannot be enabled. If authorityEnable is set to false, Kibana public network access cannot be enabled.

            +

            If httpsEnable is set to false, public network access cannot be enabled. If authorityEnable is set to false, Kibana public network access cannot be enabled.

            +

            Enable the related functions based on the error information.

            +

            400

            +

            CSS.5312

            +

            Nodes and disks cannot be scaled out at the same time in a cluster billed in yearly/monthly mode.

            +

            Nodes and disks cannot be scaled out at the same time in a cluster billed in yearly/monthly mode.

            +

            Operation not supported.

            +

            400

            +

            CSS.5313

            +

            Insufficient permissions on the VPC endpoint. Check whether the user has the VPC endpoint administrator role.

            +

            Insufficient permissions on the VPC endpoint. Check whether the user has the VPC Endpoint administrator role.

            +

            Check related permissions based on the error information.

            +

            400

            +

            CSS.6000

            +

            Failed to create the cluster. Contact technical support or try again later.

            +

            Failed to create the cluster. Contact technical support or try again later.

            +

            Try again later. If the fault persists, contact technical support.

            +

            400

            +

            CSS.6001

            +

            Failed to scale out the cluster. Contact technical support or try again later.

            +

            Failed to scale out the cluster. Contact technical support or try again later.

            +

            Try again later. If the fault persists, contact technical support.

            +

            400

            +

            CSS.6003

            +

            Failed to restore the cluster. Contact technical support or try again later.

            +

            Failed to restore the cluster. Contact technical support or try again later.

            +

            Try again later. If the fault persists, contact technical support.

            +

            400

            +

            CSS.6004

            +

            Failed to create the node due to an ECS exception. Contact technical support or try again later. Error code: #failedReason#.

            +

            Failed to create the node due to ECS exception. Error code: #failedReason#! Contact technical support or try again later.

            +

            Try again later. If the fault persists, contact technical support.

            +

            400

            +

            CSS.6009

            +

            Failed to create the snapshot. Contact technical support or try again later.

            +

            Failed to create the snapshot. Contact technical support or try again later.

            +

            Try again later. If the fault persists, contact technical support.

            +

            400

            +

            CSS.6012

            +

            Failed to restore the snapshot because the OBS object does not exist or has been deleted.

            +

            Failed to restore the snapshot because the OBS object does not exist or has been deleted.

            +

            Ensure that the OBS bucket exists.

            +

            400

            +

            CSS.6013

            +

            Parameters cannot be modified because another operation is being performed on the cluster.

            +

            Parameters cannot be modified because another operation is being performed on the cluster.

            +

            Ensure that the cluster is available before modifying parameters.

            +

            400

            +

            CSS.6014

            +

            Unchangeable parameters are contained.

            +

            Some parameters cannot be modified.

            +

            Delete the unchangeable parameters if any and try again.

            +

            400

            +

            CSS.6015

            +

            Parameters are not in the YAML format.

            +

            The parameter value is not in YAML format.

            +

            Modify the parameter format and try again.

            +

            403

            +

            CSS.0010

            +

            The instance ID or user ID may be null, or the operation is not authorized.

            +

            The DB instance ID or user ID may be null, or the operation is not authorized.

            +

            Check your permissions.

            +

            403

            +

            CSS.0015

            +

            No resources are found or the access is denied.

            +

            No resources are found or access is denied.

            +

            Insufficient permission. Add the permission and try again.

            +

            403

            +

            CSS.5045

            +

            The current tenant is not allowed to perform this operation.

            +

            The current tenant is not allowed to perform this operation.

            +

            Check whether the tenant is frozen or has required permissions.

            +

            404

            +

            CSS.0002

            +

            The instance does not exist.

            +

            The instance does not exist.

            +

            Check whether the permission and resource exist.

            +

            404

            +

            CSS.0007

            +

            The VM information of the DB instance cannot be found.

            +

            The VM information of the DB instance cannot be found.

            +

            Try again later or contact technical support.

            +

            404

            +

            CSS.0016

            +

            Resource not found.

            +

            The resource is not found.

            +

            Check whether the resource exists based on the displayed information.

            +

            404

            +

            CSS.0022

            +

            The instance does not exist or has been deleted.

            +

            The instance does not exist or has been deleted.

            +

            Check whether the resource exists.

            +

            404

            +

            CSS.0028

            +

            The object does not exist.

            +

            The object does not exist.

            +

            Check whether the current resource exists based on the displayed information.

            +

            404

            +

            CSS.1103

            +

            The instance does not exist!

            +

            The instance does not exist.

            +

            Check whether the cluster exists.

            +

            404

            +

            CSS.3027

            +

            The cluster does not exist!

            +

            The cluster does not exist.

            +

            The cluster does not exist. No operations are supported.

            +

            404

            +

            CSS.5012

            +

            The region or AZ does not exist.

            +

            The region or AZ does not exist.

            +

            Select a correct region or AZ.

            +

            404

            +

            CSS.5022

            +

            The subnet does not exist or does not belong to the VPC.

            +

            The subnet does not exist or does not belong to the VPC.

            +

            Check whether the subnet exists and belongs to the VPC.

            +

            404

            +

            CSS.5042

            +

            The source instance does not exist.

            +

            The source instance does not exist.

            +

            The request body contains an instance that does not exist in the cluster.

            +

            409

            +

            CSS.0012

            +

            Operation is not allowed because the cluster has a standby instance.

            +

            Operation is not allowed because the cluster has a standby instance.

            +

            Perform the operation after the cluster backup is complete.

            +

            409

            +

            CSS.0029

            +

            The object is being created. Please wait.

            +

            The object is being created. Please wait.

            +

            The cluster or snapshot is being created. Do not perform other operations.

            +

            409

            +

            CSS.0031

            +

            The object already exists.

            +

            The object already exists.

            +

            Change the object name.

            +

            409

            +

            CSS.0043

            +

            The snapshot name already exists.

            +

            The snapshot name already exists.

            +

            Change the snapshot name.

            +

            409

            +

            CSS.1102

            +

            The instance name already exists.

            +

            The instance name already exists.

            +

            Change the instance name.

            +

            409

            +

            CSS.3004

            +

            Backup is in progress.

            +

            Backup is in progress.

            +

            Perform the operation after the cluster status is successful.

            +

            413

            +

            CSS.0030

            +

            The number of snapshots reaches the quota.

            +

            The number of snapshots reaches the quota.

            +

            Release the resources that do not need to be backed up.

            +

            415

            +

            CSS.0004

            +

            Invalid operation.

            +

            Invalid operation.

            +

            Change the parameters based on the error information.

            +

            415

            +

            CSS.5108

            +

            The operation is not supported.

            +

            Operation not supported.

            +

            Operation not supported.

            +

            419

            +

            CSS.0023

            +

            Insufficient resource.

            +

            Resources are insufficient.

            +

            Contact technical support.

            +

            422

            +

            CSS.0040

            +

            The parameter cannot be processed.

            +

            The parameter cannot be processed.

            +

            Try again later or contact technical support.

            +

            500

            +

            CSS.0005

            +

            Server error.

            +

            Server error.

            +

            Internal error. Contact technical support.

            +

            500

            +

            CSS.1004

            +

            Database service error.

            +

            The database service is abnormal.

            +

            Try again later or contact technical support.

            +

            500

            +

            CSS.9999

            +

            Failed to process the request.

            +

            Request processing failed.

            +

            Check whether the request path and request body are correct as prompted.

            +

            diff --git a/docs/css/api-ref/css_03_0077.html b/docs/css/api-ref/css_03_0077.html index 18115f67..3fb929c0 100644 --- a/docs/css/api-ref/css_03_0077.html +++ b/docs/css/api-ref/css_03_0077.html @@ -1,27 +1,15 @@ - -

            Tag Management APIs

            - -

            -
            - +

            Calling APIs

            +
            diff --git a/docs/css/api-ref/css_03_0078.html b/docs/css/api-ref/css_03_0078.html index 6861d524..990dd3b4 100644 --- a/docs/css/api-ref/css_03_0078.html +++ b/docs/css/api-ref/css_03_0078.html @@ -1,148 +1,149 @@ -

            Querying Tags of a Specified Cluster

            -

            Function

            This API is used to query the tag information about a specified cluster.

            -
            -

            URI

            GET /v1.0/{project_id}/css-cluster/{cluster_id}/tags
            +

            Making an API Request

            +

            This section describes the structure of a RESTful API request, and uses the IAM API for obtain a user token as an example to describe how to call an API.

            +

            Request URI

            A request URI is in the following format:

            +

            {URI-scheme}://{Endpoint}/{resource-path}?{query-string}

            -
            Table 1 Parameter description

            Parameter

            +
            - - - - - - - - - - + - + + +
            Table 1 Request URL

            Parameter

            Mandatory

            -

            Type

            -

            Description

            +

            Description

            project_id

            +

            URI-scheme

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            +

            Protocol used to transmit requests. All APIs use HTTPS.

            cluster_id

            +

            Endpoint

            Yes

            +

            Domain name or IP address of the server running the REST service. The endpoint varies between services in different regions. It can be obtained from Endpoints.

            String

            +

            resource-path

            ID of the cluster to be queried.

            +

            API access path for performing a specified operation. Obtain the value from the URI of an API. For example, the resource-path of the API for obtaining a user token is /v3/auth/tokens.

            +

            query-string

            +

            Query parameter, which is optional. Ensure that a question mark (?) is included before a query parameter that is in the format of "Parameter name=Parameter value". For example, limit=10 indicates that a maximum of 10 pieces of data is to be viewed.

            +
            For example, to obtain an IAM token in a region, obtain the endpoint of IAM for this region and the resource-path (/v3/auth/tokens) in the URI of the API used to obtain a user token. Then, construct the URI as follows:
            https://<iam-endpoint>/v3/auth/tokens
            -

            Request

            None

            +

            To simplify the URI display, each API is provided with only a resource-path and a request method. The URI-scheme of all APIs is HTTPS, and the endpoints of all APIs in the same region are identical.

            +
            -

            Response

            Table 2 describes the response parameters.

            +

            Request Methods

            HTTP-based request methods, which are also called operations or actions, specify the type of operations that you are requesting.

            +
            • GET: requests the server to return specified resources.
            • PUT: requests the server to update specified resources.
            • POST: requests the server to add resources or perform special operations.
            • DELETE: requests the server to delete specified resources, for example, an object.
            • HEAD: requests a server resource header.
            • PATCH: requests the server to update partial content of a specified resource. If the target resource does not exist, PATCH may create a resource.
            +

            For example, in the URI of the API for obtaining a user token, the request method is POST. The request is as follows:

            +
            +POST https://{iam-endpoint}/v3/auth/tokens
            +
            +

            Request Header

            You can also add additional fields to a request, such as the fields required by a specified URI or an HTTP method. For example, add Content-Type that defines a request body type to request for the authentication information.

            +

            Table 2 lists common request header fields.

            -
            Table 2 Response

            Parameter

            +
            - - - - - + + + + + + + + + + + + + + + + + + + +
            Table 2 Common request headers

            Parameter

            Type

            +

            Mandatory

            Description

            +

            Description

            tags

            +

            Content-Type

            Array of tag objects

            +

            Yes

            Tags in a cluster.

            +

            Message body type (or format). You are advised to use the default value application/json.

            +

            X-Auth-Token

            +

            Mandatory for token authentication

            +

            User token. It is the response to the API for obtaining a user token (only this API does not require authentication). After the request is processed, the value of X-Subject-Token in the response header (Header) is the token value.

            +

            X-Project-Id

            +

            No

            +

            Subproject ID, which is used in multi-project scenarios. The X-Project-ID field is mandatory in the request header for accessing resources in a subproject through AK/SK-based authentication.

            +

            X-Sdk-Date

            +

            Mandatory for AK/SK authentication

            +

            Request sending time. When AK/SK authentication is enabled, this field is automatically specified when SDK is used to sign the request.

            +

            For details, see Authentication.

            +

            The format is YYYYMMDD'T'HHMMSS'Z'. The value is the current GMT time of the system.

            +

            Authorization

            +

            Mandatory for AK/SK authentication

            +

            Signature authentication information, When AK/SK authentication is enabled, this field is automatically specified when SDK is used to sign the request.

            +

            For details, see Authentication.

            +

            X-Language

            +

            No

            +

            Request language

            - -
            - - - - - - - - - - - - - -
            Table 3 tags field description

            Parameter

            -

            Type

            -

            Description

            -

            key

            -

            String

            -

            Tag key.

            -

            value

            -

            String

            -

            Tag value.

            -
            +

            The API used to obtain a user token does not require authentication. Therefore, only the Content-Type field needs to be added to requests for calling the API. An example of such requests is as follows:

            +
            POST https://{iam-endpoint}/v3/auth/tokens
            +Content-Type: application/json
            - -

            Examples

            Example request

            -
            GET v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/tags
            -

            Example response

            -
            {
            -    "tags": [
            -        {
            -            "key": "key1",
            -            "value": "value1"
            +

            Request Body

            A request body conveys information other than the request header and is generally sent in a structured format defined by the request header field Content-Type.

            +

            The request body varies between APIs. Some APIs do not require the request body, such as the APIs requested using the GET and DELETE methods.

            +

            In the case of the API used to obtain a user token, the request parameters and parameter description can be obtained from the API request. The following provides an example request with a body included. Replace username, domainname, ******** (login password), and xxxxxxxxxxxxxxxxxx (project ID) with the actual values. To learn how to obtain a project ID, see Obtaining a Project ID and Name.

            +

            The scope parameter defines the application scope of the token, indicating that the obtained token can access only the resources in the specified project.

            +
            +
            POST https://{iam-endpoint}/v3/auth/tokens
            +Content-Type: application/json
            +{
            +    "auth": {
            +        "identity": {
            +            "methods": [
            +                "password"
            +            ],
            +            "password": {
            +                "user": {
            +                    "name": "username",    //Username
            +                    "password": "********",    //Login password
            +                    "domain": {
            +                        "name": "domainname "    //Name of the account to which the user belongs
            +                    }
            +                }
            +            }
                     },
            -        {
            -            "key": "key2",
            -            "value": "value3"
            +        "scope": {
            +            "project": {
            +                "id": "xxxxxxxxxxxxxxxxxx"    //Project ID
            +            }
                     }
            -    ]
            +    }
             }
            -
            -

            Status Code

            Table 4 describes the status code.

            - -
            - - - - - - - - - - - - - - - - - -
            Table 4 Status code

            Status Code

            -

            Message

            -

            Description

            -

            400

            -

            BadRequest

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            404

            -

            NotFound

            -

            The requested resource cannot be found.

            -

            Modify the request instead of retrying.

            -

            200

            -

            OK

            -

            The request is processed successfully.

            -
            -
            +

            If all data required for the API request is available, you can send the request to call the API through curl, Postman, or coding. For the API of obtaining a user token, x-subject-token in the response header is the desired user token. Then, you can use the token to authenticate the calling of other APIs.

            diff --git a/docs/css/api-ref/css_03_0079.html b/docs/css/api-ref/css_03_0079.html index 78fd3850..4f4806cf 100644 --- a/docs/css/api-ref/css_03_0079.html +++ b/docs/css/api-ref/css_03_0079.html @@ -1,145 +1,116 @@ -

            Querying All Tags

            -

            Function

            This API is used to query all tags in a specified region.

            +

            Authentication

            +

            You can use either of the following authentication methods when calling APIs:

            +
            • AK/SK-based authentication: Requests are encrypted using AK/SK pairs.
            • Token authentication: Requests are authenticated using a token.
            +

            AK/SK-based Authentication

            An AK/SK is used to verify the identity of a request sender. In AK/SK-based authentication, a signature needs to be obtained and then added to the request header.

            +

            AK: access key ID, which is a unique identifier used in conjunction with a secret access key to sign requests cryptographically.

            +

            SK: secret access key used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.

            +
            +

            The following uses a demo project to show how to sign a request and use an HTTP client to send an HTTPS request.

            +

            Download the demo from https://github.com/api-gate-way/SdkDemo.

            +

            If you do not need the demo project, directly download the API Gateway signing SDK at

            +

            Obtain the API Gateway signing SDK from the enterprise administrator.

            +

            Decompress the downloaded demo package to obtain a JAR file and reference the obtained JAR files as dependencies, as highlighted in the following figure.

            +

            +
            1. Generate an AK/SK pair. (If an AK/SK file has already been created, skip this step and locate the downloaded AK/SK file. Generally, the file name will be credentials.csv.)

              1. Log in to the console.
              2. Hover over the username and select My Credentials from the drop-down list.
              3. In the navigation pane, click Access Keys.
              4. Click Create Access Key. The Create Access Key dialog box is displayed.
              5. Enter your login password.
              6. Enter the verification code sent to your email or mobile phone.

                For users created in IAM, if no email address or phone number was specified during the user creation, only a login password is required.

                +
                +
              7. Click OK to download the AK/SK.

                Anyone who possesses your access keys can decrypt your login information. Therefore, keep your access keys secure.

                +
                +
              +

            2. Decompress the demo project.
            3. Import the demo project to Eclipse.

              Figure 1 Selecting Existing Projects into Workspace
              +
              Figure 2 Selecting the demo project
              +
              Figure 3 Structure of the demo project
              +

            4. Sign a request.

              The request signing method is integrated in the JAR files imported in 3. The request needs to be signed before it is sent. The signature will then be added as part of the HTTP header to the request.

              +

              The demo code is classified into the following classes to demonstrate how to sign and send an HTTP request:

              +
              • AccessService: abstract class that merges the GET, POST, PUT, and DELETE methods into the access method.
              • Demo: execution entry used to simulate the sending of GET, POST, PUT, and DELETE requests.
              • AccessServiceImpl: implements the access method, which contains the code required for communication with API Gateway.
              +
              1. (Optional) Add request header fields.

                Note: For some services, custom request headers, such as X-Project-Id and X-Domain-Id, may need to be added. To add them, modify the AccessServiceImpl.java file.

                +

                Uncomment the following code snippet in the AccessServiceImpl.java file, and replace the variables with the actual sub-project ID and account ID.

                +
                //TODO: Add special headers.
                //request.addHeader("X-Project-Id", "
                +xxxxx");
                //request.addHeader("X-Domain-Id", "
                +xxxxx");
                +
              2. Edit the main() method in the Demo.java file and replace the bold text with actual values.

                If you use other methods such as POST, PUT, and DELETE, see the corresponding comment.

                +

                Replace region, serviceName, AK/SK, and URL. In the demo, the URL for obtaining the VPC is used. Replace it with the required URL. For details on how to obtain the project ID in the URL, see Obtaining a Project ID and Name. For details about the endpoint, see Endpoints.

                +
                //TODO: Replace region with the name of the region in which the service to be accessed is located.
                
                +private static final String region = ""; 
                 
                +
                //
                +TODO: Replace vpc with the name of the service you want to access. For example, ecs, vpc, iam, and elb.
                
                +private static final String serviceName = ""; 
                 
                +
                
                +public static void main(String[] args) throws UnsupportedEncodingException 
                { 
                +
                //
                +TODO: Replace the AK and SK with those obtained on the My Credential page.
                String ak = "
                +ZIRRKMTWP******1WKNKB";
                String sk = "
                +Us0mdMNHk******YrRCnW0ecfzl";
                 
                +
                //
                +TODO: To specify a project ID (multi-project scenarios), add the X-Project-Id header.
                //
                +TODO: To access a global service, such as IAM, DNS, CDN, and TMS, add the X-Domain-Id header to specify an account ID.
                //
                +TODO: To add a header, find "Add special headers" in the AccessServiceImple.java file.
                 
                +
                //
                +TODO: Test the API
                String url = "
                +https://{Endpoint}/v1/{project_id}/vpcs";
                
                +get(ak, sk, url); 
                 
                +
                //
                +TODO: When creating a VPC, replace {project_id} in postUrl with the actual value.
                //String postUrl = "https://serviceEndpoint/v1/{project_id}/cloudservers"; 
                +
                //String postbody ="{\"
                +vpc\": {\"name\": \"vpc\",\"cidr\": \"192.168.0.0/16\"}}";
                //post(ak, sk, postUrl, postbody); 
                +
                 
                +
                //
                +TODO: When querying a VPC, replace {project_id} in url with the actual value.
                //String url = "https://serviceEndpoint/v1/{project_id}/vpcs/{vpc_id}"; 
                +
                //get(ak, sk, url); 
                +
                 
                +
                //
                +TODO: When updating a VPC, replace {project_id} and {vpc_id} in putUrl with the actual values.
                //String putUrl = "https://serviceEndpoint/v1/{project_id}/vpcs/{vpc_id}"; 
                +
                //String putbody ="{\"vpc\":{\"name\": \"vpc1\",\"cidr\": \"192.168.0.0/16\"}}"; 
                +
                //put(ak, sk, putUrl, putbody); 
                +
                 
                +
                //
                +TODO: When deleting a VPC, replace {project_id} and {vpc_id} in deleteUrl with the actual values.
                //String deleteUrl = "https://serviceEndpoint/v1/{project_id}/vpcs/{vpc_id}"; 
                +
                //delete(ak, sk, deleteUrl); 
                +
                }
                -

                URI

                GET /v1.0/{project_id}/css-cluster/tags
                - -
                - - - - - - - - - - - -
                Table 1 Parameter description

                Parameter

                -

                Mandatory

                -

                Type

                -

                Description

                -

                project_id

                -

                Yes

                -

                String

                -

                Project ID. For details, see Obtaining a Project ID and Name.

                -
                +
              3. Compile and run the code to call an API.

                In the Package Explorer area on the left, right-click Demo.java and choose Run AS > Java Application from the shortcut menu to run the demo code.

                +

                You can view API calling logs on the console.

                +
              +

            -
            -

            Request

            None

            -
            -

            Response

            Table 2 describes the response parameters.

            - -
            - - - - - - - - - -
            Table 2 Response parameters

            Parameter

            -

            Type

            -

            Description

            -

            tags

            -

            Array of tag objects

            -

            Tags in a cluster. For details, see Table 3.

            -
            -
            - -
            - - - - - - - - - - - - - -
            Table 3 tags field description

            Parameter

            -

            Type

            -

            Description

            -

            key

            -

            String

            -

            Tag key.

            -

            values

            -

            Array of strings

            -

            Tag value.

            -
            -
            -
            -

            Examples

            Example request

            -
            GET v1.0/458d905f22da49c39f609e3347d65723/css-cluster/tags
            -

            Example response

            -
            {
            -    "tags": [
            -        {
            -            "key": "key1",
            -            "values": [
            -                "value1",
            -                "value2"
            -            ]
            -        },
            -        {
            -            "key": "key2",
            -            "values": [
            -                "value1",
            -                "value2"
            -            ]
            -        }
            -    ]
            +

            Authentication Using Tokens

            • The validity period of a token is 24 hours. When using a token for authentication, cache it to prevent frequently calling the IAM API.
            • Ensure that the token is valid while you use it. Using a token that will soon expire may cause API calling failures.
            +
            +

            A token specifies certain permissions in a computer system. Authentication using a token adds the token to a request as its header during API calling to obtain permissions to operate APIs through IAM.

            +

            The API for obtaining a token is POST https://{IAM endpoint}/v3/auth/tokens. For details about how to obtain IAM endpoints, see Endpoints.

            +
            {
            +	"auth": {
            +		"identity": {
            +			"methods": [
            +				"password"
            +			],
            +			"password": {
            +				"user": {
            +					"name": "username",    //Username
            +					"password": "********",    //Login password
            +					"domain": {
            +						"name": "domainname"    //Name of the account to which the user belongs
            +					}
            +				}
            +			}
            +		},
            +		"scope": {
            +			"project": {
            +				"name": "xxxxxxxx"    //Project name
            +			}
            +		}
            +	}
             }
            -
            -

            Status Code

            Table 4 describes the status code.

            - -
            - - - - - - - - - - - - - - - - - -
            Table 4 Status code

            Status Code

            -

            Message

            -

            Description

            -

            400

            -

            BadRequest

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            404

            -

            NotFound

            -

            The requested resource cannot be found.

            -

            Modify the request instead of retrying.

            -

            200

            -

            OK

            -

            The request is processed successfully.

            -
            -
            +

            After a token is obtained, the X-Auth-Token header field must be added to requests to specify the token when calling other APIs. For example, if the token is ABCDEFJ...., X-Auth-Token: ABCDEFJ.... can be added to a request as follows:

            +
            +POST https://{endpoint}/v3/auth/projects
            +Content-Type: application/json
            +X-Auth-Token: ABCDEFJ....
            diff --git a/docs/css/api-ref/css_03_0080.html b/docs/css/api-ref/css_03_0080.html new file mode 100644 index 00000000..d4e54531 --- /dev/null +++ b/docs/css/api-ref/css_03_0080.html @@ -0,0 +1,39 @@ + + +

            Returned Values

            +

            After sending a request, you will receive a response containing the status code, response header, and response body.

            +

            Status Code

            A status code is a group of digits, ranging from 1xx to 5xx. It indicates the status of a request. For more information, see Status Codes.

            +

            If status code 201 is returned for the API for obtaining a user token, the request is successful.

            +
            +

            Response Header

            A response header corresponds to a request header, for example, Content-Type.

            +
            Figure 1 shows the response header for the API of obtaining a user token, where x-subject-token is the desired user token. Then, you can use the token to authenticate the calling of other APIs.
            Figure 1 Header of the response to the request for obtaining a user token
            +
            +
            +

            Response Body

            A response body is generally returned in a structured format, corresponding to the Content-Type in the response header, and is used to transfer content other than the response header.

            +

            The following is part of the response body for the API used to obtain a user token. The following is only part of the response body.

            +
            {
            +    "token": {
            +        "expires_at": "2019-02-13T06:52:13.855000Z",
            +        "methods": [
            +            "password"
            +        ],
            +        "catalog": [
            +            {
            +                "endpoints": [
            +                    {
            +                        "region_id": "xxx",
            +......
            +

            If an error occurs during API calling, the system returns an error code and a message to you. The following shows the format of an error response body:

            +
            {
            +    "error_msg": "The format of message is error",
            +    "error_code": "AS.0001"
            +}
            +

            In the preceding information, error_code is an error code, and error_msg describes the error.

            +
            +
            +
            + +
            + diff --git a/docs/css/api-ref/css_03_0081.html b/docs/css/api-ref/css_03_0081.html deleted file mode 100644 index c9b94838..00000000 --- a/docs/css/api-ref/css_03_0081.html +++ /dev/null @@ -1,180 +0,0 @@ - - -

            Adding or Deleting Cluster Tags in Batches

            -

            Function

            This API is used to add or delete tags to or from a specified cluster in batches. Tag Management Service (TMS) uses this API to batch manage tags of a cluster. A cluster can have a maximum of 10 tags.

            -
            • This API is an idempotent API. If the request body contains duplicate keys during tag creation, an error is reported.
            • When a tag is added:
              • The key cannot be left blank or be an empty string. It cannot contain the following characters: Non-printable ASCII characters (0-31), =, *, <, >, \, ,, |, /, letters, digits, hyphens (-), and underscores (_).
              • The value cannot be left blank but can be an empty string. It cannot contain the following characters: Non-printable ASCII characters (0-31), =, *, <, >, \, ,, |, /, letters, digits, hyphens (-), and underscores (_).
              • The key cannot be duplicate. If the key already exists in the database, the value will be overwritten.
              -
            • When a tag is deleted:
              • If a to-be-deleted tag does not exist, the operation is considered successful by default. The value range of the tag character set is not verified.
              • The tag structure body cannot be missing, and the key cannot be left blank or be an empty string.
              -
            -
            -

            -
            -

            URI

            POST /v1.0/{project_id}/css-cluster/{cluster_id}/tags/action
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Parameter description

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            IDs of clusters to which tags are to be added or deleted in batches

            -
            -
            -

            Request

            -
            - - - - - - - - - - - - - - - - -
            Table 2 Request parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            tags

            -

            No

            -

            Array of tag objects

            -

            Tag list

            -

            action

            -

            Yes

            -

            String

            -

            Operation to be performed. The value can be set to create or delete only.

            -
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 3 resource_tag field description

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            key

            -

            Yes

            -

            String

            -

            Tag key. The value can contain up to 36 characters.

            -

            value

            -

            This parameter is mandatory when action is set to create and optional when action is set to delete.

            -

            String

            -

            Tag value. The value contains up to 43 characters.

            -

            If value is not empty, delete tags by key/value. If value is empty, delete tags by key.

            -
            -
            -
            -

            Response

            None

            -
            -

            Example

            • Example request
            -
            POST /v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/tags/action
            -

            This API is used to add tags in batches.

            -
            {
            -    "action": "create",
            -    "tags": [
            -        {
            -            "key": "key1",
            -            "value": "value1"
            -        }
            -    ]
            -}
            -
            -
            This API is used to delete tags in batches.
            {
            -    "action": "delete",
            -    "tags": [
            -        {
            -            "key": "key1"
            -        }
            -    ]
            -}
            -
            -
            • Response example

              None

              -
            -

            Status Code

            Table 4 describes the status code.

            - -
            - - - - - - - - - - - - - - - - - -
            Table 4 Status code

            Status Code

            -

            Encoding

            -

            Description

            -

            400

            -

            BadRequest

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            404

            -

            NotFound

            -

            The requested resource cannot be found.

            -

            Modify the request instead of retrying.

            -

            204

            -

            OK

            -

            The request is processed successfully.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0082.html b/docs/css/api-ref/css_03_0082.html deleted file mode 100644 index b5511e52..00000000 --- a/docs/css/api-ref/css_03_0082.html +++ /dev/null @@ -1,101 +0,0 @@ - - -

            Deleting Specified Cluster Tags

            -

            Function

            This API is used to delete specified cluster tags.

            -
            -

            URI

            DELETE /v1.0/{project_id}/css-cluster/{cluster_id}/tags/{key}
            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 1 Parameter description

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to which a tag is to be deleted

            -

            key

            -

            Yes

            -

            String

            -

            Tag key

            -

            The field cannot be left blank or be an empty character string.

            -
            -
            -
            -

            Request

            None

            -
            -

            Response

            None

            -
            -

            Example

            • Example request
              DELETE /v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/tags/key1
              -
            • Response example

              None

              -
            -
            -

            Status Codes

            Table 2 describes the status code.

            - -
            - - - - - - - - - - - - - - - - - -
            Table 2 Status codes

            Status Code

            -

            Message

            -

            Description

            -

            400

            -

            BadRequest

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            404

            -

            NotFound

            -

            The requested resource cannot be found.

            -

            Modify the request instead of retrying.

            -

            204

            -

            OK

            -

            The request is processed.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0083.html b/docs/css/api-ref/css_03_0083.html deleted file mode 100644 index a8ffe69d..00000000 --- a/docs/css/api-ref/css_03_0083.html +++ /dev/null @@ -1,130 +0,0 @@ - - -

            Adding Tags to a Cluster

            -

            Function

            This API is used to add tags to a cluster. A cluster can have a maximum of 10 tags.

            -
            -

            URI

            POST /v1.0/{project_id}/css-cluster/{cluster_id}/tags
            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Parameter description

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to which a tag is to be added

            -
            -
            -
            -

            Request

            -
            - - - - - - - - - - - - - - - - -
            Table 2 tag field description

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            key

            -

            Yes

            -

            String

            -

            Tag key. The value can contain up to 36 characters.

            -

            value

            -

            Yes

            -

            String

            -

            Tag value. The value contains up to 43 characters.

            -

            If value is not empty, delete tags by key/value. If value is empty, delete tags by key.

            -
            -
            -
            -

            Response

            None

            -
            -

            Example

            • Example request
              POST /v1.0/458d905f22da49c39f609e3347d65723/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/tags
              -{
              -    "tag": {
              -        "key": "DEV",
              -        "value": "DEV1"
              -    }
              -}
              -

              -
            • Example response

              None

              -
            -
            -

            Status Codes

            Table 3 describes the status code.

            - -
            - - - - - - - - - - - - - - - - - -
            Table 3 Status codes

            Status Code

            -

            Message

            -

            Description

            -

            400

            -

            BadRequest

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            404

            -

            NotFound

            -

            The requested resource cannot be found.

            -

            Modify the request instead of retrying.

            -

            204

            -

            OK

            -

            The request is processed.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0084.html b/docs/css/api-ref/css_03_0084.html deleted file mode 100644 index da0549cf..00000000 --- a/docs/css/api-ref/css_03_0084.html +++ /dev/null @@ -1,111 +0,0 @@ - - -

            Changing a Cluster Name

            -

            Function

            This API is used to change the name of a cluster.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/changename

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to rename

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            displayName

            -

            Yes

            -

            String

            -

            New cluster name

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "displayName" : "ES-Test-new"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0086.html b/docs/css/api-ref/css_03_0086.html deleted file mode 100644 index d933b544..00000000 --- a/docs/css/api-ref/css_03_0086.html +++ /dev/null @@ -1,130 +0,0 @@ - - -

            Modifying Cluster Specifications

            -

            Function

            This API is used to modify the specifications of a cluster. Only the specifications of ESS nodes can be modified.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/flavor

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to modify specifications

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            needCheckReplica

            -

            No

            -

            Boolean

            -

            Indicates whether to verify replicas. Its value can be true or false. Replica verification is enabled by default.

            -
            • true: Replica verification is enabled.
            • false: Replica verification is disabled.
            -

            newFlavorId

            -

            Yes

            -

            String

            -

            ID of the new flavor. This parameter is obtained by calling the Obtaining the Instance Specifications List API. The API compares the values of the name attribute and obtains the ID of the flavor higher than the current flavor. Only the node specifications of the same Elasticsearch engine version can be changed.

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            • {
              -  "needCheckReplica" : false,
              -  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2",
              -  "isAutoPay" : 1
              -}
              -
            • {
              -  "needCheckReplica" : false,
              -  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2"
              -}
              -
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0087.html b/docs/css/api-ref/css_03_0087.html deleted file mode 100644 index 3abfca23..00000000 --- a/docs/css/api-ref/css_03_0087.html +++ /dev/null @@ -1,143 +0,0 @@ - - -

            Changing the Specifications of a Specified Node Type

            -

            Function

            This API is used to change the specifications of a specified node type. The following node types are supported:

            -
            • ess: data node
            • ess-cold: cold data node
            • ess-client: client node
            • ess-master: master node
            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/{types}/flavor

            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to modify specifications

            -

            types

            -

            Yes

            -

            String

            -

            Type of the cluster node you want to modify.

            -
            • ess: data node
            • ess-cold: cold data node
            • ess-client: Client node
            • ess-master: Master node
            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            needCheckReplica

            -

            No

            -

            Boolean

            -

            Indicates whether to verify replicas. Its value can be true or false. Replica verification is enabled by default.

            -
            • true: Replica verification is enabled.
            • false: Replica verification is disabled.
            -
            NOTE:

            Master and client nodes are not data nodes, so they do not need to check replicas no matter this parameter is set to true or false.

            -
            -

            newFlavorId

            -

            Yes

            -

            String

            -

            ID of the new flavor. This parameter is obtained by calling the Obtaining the Instance Specifications List API. The API compares the values of the name attribute and obtains the ID of the flavor higher than the current flavor. Only the node specifications of the same Elasticsearch engine version can be changed.

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            • {
              -  "needCheckReplica" : false,
              -  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2",
              -  "isAutoPay" : 1
              -}
              -
            • {
              -  "needCheckReplica" : false,
              -  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2"
              -}
              -
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0088.html b/docs/css/api-ref/css_03_0088.html deleted file mode 100644 index 5916c84d..00000000 --- a/docs/css/api-ref/css_03_0088.html +++ /dev/null @@ -1,114 +0,0 @@ - - -

            Scaling in a Cluster By Removing Specified Nodes

            -

            Function

            This API is used to scale in a cluster by removing specified nodes. Yearly/Monthly clusters do not support the removal of specified nodes by calling this API.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/node/offline

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster you want to scale in

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            shrinkNodes

            -

            Yes

            -

            Array of strings

            -

            ID of the node you want to remove.

            -

            Obtain the ID attribute in instances by referring to Querying Cluster Details.

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "shrinkNodes" : [ "2077bdf3-b90d-412e-b460-635b9b159c11" ]
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0089.html b/docs/css/api-ref/css_03_0089.html deleted file mode 100644 index 415e7ab5..00000000 --- a/docs/css/api-ref/css_03_0089.html +++ /dev/null @@ -1,153 +0,0 @@ - - -

            Removing Nodes of a Specific Type

            -

            Function

            This API is used to remove instances of specific types and reduce instance storage capacity in a cluster.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/extend/{project_id}/clusters/{cluster_id}/role/shrink

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster you want to scale in

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            shrink

            -

            Yes

            -

            Array of ShrinkNodeReq objects

            -

            Type and quantity of nodes you want to remove

            -
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 3 ShrinkNodeReq

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            reducedNodeNum

            -

            Yes

            -

            Integer

            -

            Number of nodes you want to remove.

            -

            - After the scale-in, there has to be at least one node in each AZ under each node type.

            -

            - In a cross-AZ cluster, the difference between the numbers of the same type nodes in different AZs cannot exceed 1.

            -

            - For a cluster with no Master nodes, the number of removed data nodes (including cold data nodes and other types of nodes) in a scale-in must be fewer than half of the original data node number, and the number of remaining data nodes after a scale-in must be greater than the maximum number of index replicas.

            -

            - For a cluster with Master nodes, the number of removed master nodes in a scale-in must be fewer than half of the original master node number. After scale-in, there has to be an odd number of master nodes, and there has to be at least three of them.

            -

            type

            -

            Yes

            -

            String

            -

            Node type.

            -
            • ess: data node
            • ess-cold: cold data node
            • ess-client: Client node
            • ess-master: Master node
            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "shrink" : [ {
            -    "type" : "ess",
            -    "reducedNodeNum" : 1
            -  } ]
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0090.html b/docs/css/api-ref/css_03_0090.html deleted file mode 100644 index e5e48e13..00000000 --- a/docs/css/api-ref/css_03_0090.html +++ /dev/null @@ -1,93 +0,0 @@ - - -

            Replacing a Node

            -

            Function

            This API is used to replace a failed node.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/instance/{instance_id}/replace

            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster where nodes are to be replaced

            -

            instance_id

            -

            Yes

            -

            String

            -

            ID of the node to be replaced

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            PUT /v1.0/{project_id}/clusters/{cluster_id}/instance/{instance_id}/replace
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            404

            -

            The requested resource cannot be found.

            -

            Modify the request instead of retrying.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0091.html b/docs/css/api-ref/css_03_0091.html deleted file mode 100644 index 32262c21..00000000 --- a/docs/css/api-ref/css_03_0091.html +++ /dev/null @@ -1,132 +0,0 @@ - - -

            Changing the Security Mode

            -

            Function

            This API is used to change the security mode of a cluster.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/mode/change

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to change the security mode

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            authorityEnable

            -

            Yes

            -

            Boolean

            -

            Indicates whether to enable the security mode.

            -
            • true: enabled.
            • false: disabled. The default value is true.
            -

            adminPwd

            -

            No

            -

            String

            -

            Cluster password in security mode

            -

            httpsEnable

            -

            Yes

            -

            Boolean

            -

            Indicates whether to enable HTTPS. Its value can be:

            -
            • true: enabled.
            • false: disabled. The default value is true.
            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            POST /v1.0/{project_id}/clusters/{cluster_id}/mode/change
            -
            -{
            -  "authorityEnable" : true,
            -  "adminPwd" : "xxxx1234",
            -  "httpsEnable" : true
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            404

            -

            The requested resource cannot be found.

            -

            Modify the request instead of retrying.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0092.html b/docs/css/api-ref/css_03_0092.html deleted file mode 100644 index 928c97e5..00000000 --- a/docs/css/api-ref/css_03_0092.html +++ /dev/null @@ -1,109 +0,0 @@ - - -

            Changing the Security Group

            -

            Function

            This API is used to change the security group after a cluster is created.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/sg/change

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to change the security group

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            security_group_ids

            -

            Yes

            -

            String

            -

            Security group ID

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/sg/change
            -
            -{
            -  "security_group_ids" : "b1038649-1f77-4ae9-b64d-9af56e42xxxx"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            403

            -

            The request is rejected. The server has received and understood the request, but refused to respond to it. Modify the request directly and do not attempt to retry it.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0093.html b/docs/css/api-ref/css_03_0093.html deleted file mode 100644 index 53880aeb..00000000 --- a/docs/css/api-ref/css_03_0093.html +++ /dev/null @@ -1,31 +0,0 @@ - - - -

            Log Management

            - -

            -
            - - - diff --git a/docs/css/api-ref/css_03_0094.html b/docs/css/api-ref/css_03_0094.html deleted file mode 100644 index 8f9398ad..00000000 --- a/docs/css/api-ref/css_03_0094.html +++ /dev/null @@ -1,133 +0,0 @@ - - -

            Enabling the Log Function

            -

            Function

            This API is used to enable the log function.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/logs/open

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to enable the log function

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            agency

            -

            Yes

            -

            String

            -

            Agency name. You can create an agency to allow CSS to call other cloud services.

            -

            logBasePath

            -

            Yes

            -

            String

            -

            Storage path of backup logs in the OBS bucket

            -

            logBucket

            -

            Yes

            -

            String

            -

            Name of the OBS bucket for storing logs

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "agency" : "css_obs_agency",
            -  "logBasePath" : "css/log",
            -  "logBucket" : "000-words"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0095.html b/docs/css/api-ref/css_03_0095.html deleted file mode 100644 index 8e5acced..00000000 --- a/docs/css/api-ref/css_03_0095.html +++ /dev/null @@ -1,89 +0,0 @@ - - -

            Disabling the Log Function

            -

            Function

            This API is used to disable the log function.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/close

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to disable the log function

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            None

            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0096.html b/docs/css/api-ref/css_03_0096.html deleted file mode 100644 index cb2319b1..00000000 --- a/docs/css/api-ref/css_03_0096.html +++ /dev/null @@ -1,148 +0,0 @@ - - -

            Viewing the Job List

            -

            Function

            This API is used to query the job list in the logs of a cluster.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/logs/records

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            clusterLogRecord

            -

            Array of clusterLogRecord objects

            -

            Entity object of cluster log records

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 3 clusterLogRecord

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Log task ID, which is generated based on the system UUID.

            -

            clusterId

            -

            String

            -

            Cluster ID

            -

            createAt

            -

            String

            -

            Creation time. Format: Unix timestamp.

            -

            logPath

            -

            String

            -

            Storage path of backup logs in the OBS bucket

            -

            status

            -

            String

            -

            Task status. The value can be:

            -
            • RUNNING: The backup is in progress.
            • SUCCESS: The backup is successful.
            • FAIL: The backup fails.
            -

            finishedAt

            -

            Long

            -

            End time. If the creation has not been completed, the end time is null. Format: Unix timestamp.

            -

            jobTypes

            -

            String

            -

            Task type. The value can be:

            -
            • Manual
            • Auto
            -

            failedMsg

            -

            String

            -

            Error message. If the task is not failed, the value of this parameter is null.

            -

            jobId

            -

            String

            -

            Task ID

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0097.html b/docs/css/api-ref/css_03_0097.html index 11a9b720..4651cd52 100644 --- a/docs/css/api-ref/css_03_0097.html +++ b/docs/css/api-ref/css_03_0097.html @@ -1,166 +1,26 @@ -

            Querying Basic Log Configurations

            -

            Function

            This API is used to query basic log configurations.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/logs/settings

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            logConfiguration

            -

            logConfiguration object

            -

            Log configuration entity object

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 3 logConfiguration

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Log backup ID, which is generated based on the system UUID.

            -

            clusterId

            -

            String

            -

            Cluster ID

            -

            obsBucket

            -

            String

            -

            Name of the OBS bucket for storing logs

            -

            agency

            -

            String

            -

            Agency name. You can create an agency to allow CSS to call other cloud services.

            -

            updateAt

            -

            Long

            -

            Update time. Format: Unix timestamp.

            -

            basePath

            -

            String

            -

            Storage path of backup logs in the OBS bucket

            -

            autoEnable

            -

            Boolean

            -

            Indicates whether to enable automatic backup.

            -
            • true: enabled
            • false: disabled
            -

            period

            -

            String

            -

            Start time of automatic log backup. When autoEnable is set to false, the value of this parameter is null. Format: GMT

            -

            logSwitch

            -

            Boolean

            -

            Indicates whether to enable the log function.

            -
            • true: enabled
            • false: disabled
            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "logConfiguration" : {
            -    "id" : "d455a541-597e-4846-a6be-baad0ea361b1",
            -    "clusterId" : "4213d908-f5dc-4633-8401-cfd7175fca0c",
            -    "obsBucket" : "css-auto-test",
            -    "agency" : "css_obs_agency",
            -    "updateAt" : 1633663681055,
            -    "basePath" : "css/log",
            -    "autoEnable" : false,
            -    "period" : "00:00 GMT+08:00",
            -    "logSwitch" : true
            -  }
            -}
            -
            +

            APIs

            +

            diff --git a/docs/css/api-ref/css_03_0098.html b/docs/css/api-ref/css_03_0098.html deleted file mode 100644 index 2546475c..00000000 --- a/docs/css/api-ref/css_03_0098.html +++ /dev/null @@ -1,133 +0,0 @@ - - -

            Modifying Basic Log Configurations

            -

            Function

            This API is used to modify basic log configurations.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/logs/settings

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to change the basic log configurations

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            agency

            -

            Yes

            -

            String

            -

            Agency name. You can create an agency to allow CSS to call other cloud services.

            -

            logBasePath

            -

            Yes

            -

            String

            -

            Storage path of backup logs in the OBS bucket

            -

            logBucket

            -

            Yes

            -

            String

            -

            Name of the OBS bucket for storing logs

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "agency" : "css_obs_agency",
            -  "logBasePath" : "css/log",
            -  "logBucket" : "000-words"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0099.html b/docs/css/api-ref/css_03_0099.html deleted file mode 100644 index d9f4d284..00000000 --- a/docs/css/api-ref/css_03_0099.html +++ /dev/null @@ -1,113 +0,0 @@ - - -

            Enabling the Automatic Log Backup Policy

            -

            Function

            This API is used to enable the automatic log backup policy.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/update

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to enable the log backup function

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            period

            -

            Yes

            -

            String

            -

            Start time of a backup job. Format: GMT

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "period" : "00:00 GMT+08:00"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0100.html b/docs/css/api-ref/css_03_0100.html deleted file mode 100644 index 74f9a679..00000000 --- a/docs/css/api-ref/css_03_0100.html +++ /dev/null @@ -1,89 +0,0 @@ - - -

            Disabling the Automatic Log Backup Policy

            -

            Function

            This API is used to disable the automatic log backup policy.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/logs/policy/close

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to disable the automatic log backup policy

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            None

            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0101.html b/docs/css/api-ref/css_03_0101.html deleted file mode 100644 index a22e4e06..00000000 --- a/docs/css/api-ref/css_03_0101.html +++ /dev/null @@ -1,89 +0,0 @@ - - -

            Backing Up Logs

            -

            Function

            This API is used to back up logs.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/logs/collect

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to back up logs

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            None

            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0102.html b/docs/css/api-ref/css_03_0102.html deleted file mode 100644 index 4ee7ad16..00000000 --- a/docs/css/api-ref/css_03_0102.html +++ /dev/null @@ -1,193 +0,0 @@ - - -

            Querying Logs

            -

            Function

            This API is used to query log information.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/logs/search

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            instanceName

            -

            Yes

            -

            String

            -

            Node name. Obtain the Name attribute in instances by referring to Querying Cluster Details.

            -

            level

            -

            Yes

            -

            String

            -

            Log level. The log levels that can be queried are INFO, ERROR, DEBUG, and WARN.

            -

            logType

            -

            Yes

            -

            String

            -

            Log type. The log types that can be queried are deprecation, indexingSlow, searchSlow, and instance.

            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 3 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            logList

            -

            Array of logList objects

            -

            Log list

            -
            -
            - -
            - - - - - - - - - - - - - - - - - -
            Table 4 logList

            Parameter

            -

            Type

            -

            Description

            -

            content

            -

            String

            -

            Log content

            -

            date

            -

            String

            -

            Date

            -

            level

            -

            String

            -

            Log level

            -
            -
            -
            -

            Request Example

            {
            -  "instanceName" : "css-4312-ess-esn-1-1",
            -  "level" : "INFO",
            -  "logType" : "instance"
            -}
            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "logList" : [ {
            -    "content" : "xxxxxx",
            -    "date" : "2021-10-08T03:55:54,718",
            -    "level" : "INFO"
            -  } ]
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0103.html b/docs/css/api-ref/css_03_0103.html deleted file mode 100644 index 0d1c5663..00000000 --- a/docs/css/api-ref/css_03_0103.html +++ /dev/null @@ -1,23 +0,0 @@ - - - -

            Public Network Access

            - -

            -
            - - - diff --git a/docs/css/api-ref/css_03_0104.html b/docs/css/api-ref/css_03_0104.html deleted file mode 100644 index de3f3458..00000000 --- a/docs/css/api-ref/css_03_0104.html +++ /dev/null @@ -1,187 +0,0 @@ - - -

            Enabling Public Network Access

            -

            Function

            This API is used to enable public network access.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/public/open

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to enable public network access

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            eip

            -

            Yes

            -

            BindPublicReqEip object

            -

            EIP information

            -
            -
            - -
            - - - - - - - - - - - -
            Table 3 BindPublicReqEip

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            bandWidth

            -

            Yes

            -

            BindPublicReqEipBandWidth object

            -

            EIP bandwidth information

            -
            -
            - -
            - - - - - - - - - - - -
            Table 4 BindPublicReqEipBandWidth

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            size

            -

            Yes

            -

            Integer

            -

            Bandwidth. Unit: Mbit/s

            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 5 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            action

            -

            String

            -

            Operation. The fixed value is bindZone, indicating that the binding is successful.

            -
            -
            -
            -

            Request Example

            {
            -  "eip" : {
            -    "bandWidth" : {
            -      "size" : 5
            -    }
            -  },
            -  "isAutoPay" : 1
            -}
            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "action" : "bindZone"
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0105.html b/docs/css/api-ref/css_03_0105.html deleted file mode 100644 index cbe37d75..00000000 --- a/docs/css/api-ref/css_03_0105.html +++ /dev/null @@ -1,186 +0,0 @@ - - -

            Disabling Public Network Access

            -

            Function

            This API is used to disable public network access.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/public/close

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to disable public network access

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            eip

            -

            No

            -

            UnBindPublicReqEipReq object

            -

            EIP information

            -
            -
            - -
            - - - - - - - - - - - -
            Table 3 UnBindPublicReqEipReq

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            bandWidth

            -

            No

            -

            BindPublicReqEipBandWidth object

            -

            EIP bandwidth information

            -
            -
            - -
            - - - - - - - - - - - -
            Table 4 BindPublicReqEipBandWidth

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            size

            -

            Yes

            -

            Integer

            -

            Bandwidth. Unit: Mbit/s

            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 5 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            action

            -

            String

            -

            Operation. The fixed value is unbindZone, indicating that the unbinding is successful.

            -
            -
            -
            -

            Request Example

            {
            -  "eip" : {
            -    "bandWidth" : {
            -      "size" : 5
            -    }
            -  }
            -}
            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "action" : "unbindZone"
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0106.html b/docs/css/api-ref/css_03_0106.html deleted file mode 100644 index bffabc49..00000000 --- a/docs/css/api-ref/css_03_0106.html +++ /dev/null @@ -1,139 +0,0 @@ - - -

            Modifying Public Network Access Bandwidth

            -

            Function

            This API is used to modify the public network access bandwidth.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/public/bandwidth

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to modify the public network access bandwidth

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            bandWidth

            -

            Yes

            -

            BindPublicReqEipBandWidth object

            -

            EIP bandwidth information

            -
            -
            - -
            - - - - - - - - - - - -
            Table 3 BindPublicReqEipBandWidth

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            size

            -

            Yes

            -

            Integer

            -

            Bandwidth. Unit: Mbit/s

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "bandWidth" : {
            -    "size" : 5
            -  },
            -  "isAutoPay" : 1
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0107.html b/docs/css/api-ref/css_03_0107.html deleted file mode 100644 index 057d8d36..00000000 --- a/docs/css/api-ref/css_03_0107.html +++ /dev/null @@ -1,113 +0,0 @@ - - -

            Enabling the Public Network Access Whitelist

            -

            Function

            This API is used to enable the public network access whitelist.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/update

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to enable the public network access whitelist

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            whiteList

            -

            Yes

            -

            String

            -

            IP address of the user that enabled public network access whitelist

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "whiteList" : "192.168.0.xx"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the preconditions that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0108.html b/docs/css/api-ref/css_03_0108.html deleted file mode 100644 index d0905588..00000000 --- a/docs/css/api-ref/css_03_0108.html +++ /dev/null @@ -1,89 +0,0 @@ - - -

            Disabling the Public Network Access Whitelist

            -

            Function

            This API is used to disable the public network access whitelist.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/public/whitelist/close

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to disable the public network access whitelist

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            None

            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0109.html b/docs/css/api-ref/css_03_0109.html deleted file mode 100644 index 3369c607..00000000 --- a/docs/css/api-ref/css_03_0109.html +++ /dev/null @@ -1,23 +0,0 @@ - - - -

            VPC Endpoint

            - -

            -
            - - - diff --git a/docs/css/api-ref/css_03_0110.html b/docs/css/api-ref/css_03_0110.html deleted file mode 100644 index f85a9ea9..00000000 --- a/docs/css/api-ref/css_03_0110.html +++ /dev/null @@ -1,137 +0,0 @@ - - -

            Enabling the VPC Endpoint Service

            -

            Function

            This API is used to enable the VPC endpoint service.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/open

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to enable the VPC endpoint

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            endpointWithDnsName

            -

            No

            -

            Boolean

            -

            Indicates whether to enable the private domain name.

            -
            • true: enabled
            • false: disabled
            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 3 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            action

            -

            String

            -

            Operation. The fixed value is createVpcepservice, indicating that the VPC endpoint is enabled.

            -
            -
            -
            -

            Request Example

            {
            -  "endpointWithDnsName" : true
            -}
            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "action" : "createVpcepservice"
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0111.html b/docs/css/api-ref/css_03_0111.html deleted file mode 100644 index e9f112a8..00000000 --- a/docs/css/api-ref/css_03_0111.html +++ /dev/null @@ -1,112 +0,0 @@ - - -

            Disabling the VPC Endpoint Service

            -

            Function

            This API is used to disable the VPC endpoint service.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/close

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to disable the VPC endpoint service

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            action

            -

            String

            -

            Operation. The fixed value is deleteVpcepservice, indicating that the VPC endpoint has been disabled.

            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "action" : "deleteVpcepservice"
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0112.html b/docs/css/api-ref/css_03_0112.html deleted file mode 100644 index e3f9a574..00000000 --- a/docs/css/api-ref/css_03_0112.html +++ /dev/null @@ -1,199 +0,0 @@ - - -

            Obtaining a VPC Endpoint Connection

            -

            Function

            This API is used to obtain a VPC endpoint connection.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connections

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            connections

            -

            Array of connections objects

            -

            Connection information

            -

            vpcepUpdateSwitch

            -

            Boolean

            -

            Indicates whether the endpoint update function is enabled.

            -
            • true: enabled
            • false: disabled
            -

            total_count

            -

            Integer

            -

            Number of endpoints

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 3 connections

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Endpoint ID

            -

            status

            -

            String

            -

            Endpoint status.

            -
            • accepted: The VPC endpoint connection is enabled.
            • rejected: The VPC endpoint connection is disabled.
            -

            maxSession

            -

            String

            -

            Maximum number of connections

            -

            specificationName

            -

            String

            -

            Endpoint name

            -

            created_at

            -

            String

            -

            Time when a cluster is created. The format is ISO8601: CCYY-MM-DDThh:mm:ss.

            -

            update_at

            -

            String

            -

            Update time. The default value is null.

            -

            domain_id

            -

            String

            -

            Owner

            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "connections" : [ {
            -    "id" : "connectionsID",
            -    "status" : "accepted",
            -    "maxSession" : "3000",
            -    "specificationName" : "default",
            -    "created_at" : "2021-09-17T08:00:07Z",
            -    "update_at" : null,
            -    "domain_id" : "domainID"
            -  } ],
            -  "vpcepUpdateSwitch" : "false",
            -  "total_count" : 1
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0113.html b/docs/css/api-ref/css_03_0113.html deleted file mode 100644 index 7643fa06..00000000 --- a/docs/css/api-ref/css_03_0113.html +++ /dev/null @@ -1,124 +0,0 @@ - - -

            Updating a VPC Endpoint Connection

            -

            Function

            This API is used to update a VPC endpoint connection.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connections

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to update the VPC endpoint

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            action

            -

            Yes

            -

            String

            -

            Expected operation.

            -
            • receive: accept the VPC endpoint connection
            • reject: reject the VPC endpoint connection
            -

            endpointIdList

            -

            Yes

            -

            Array of strings

            -

            VPC endpoint IDs list

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "action" : "receive",
            -  "endpointIdList" : [ "f132bb14-e1d5-4f25-9f7c-a29e4c8effd4" ]
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0114.html b/docs/css/api-ref/css_03_0114.html deleted file mode 100644 index 048f9859..00000000 --- a/docs/css/api-ref/css_03_0114.html +++ /dev/null @@ -1,113 +0,0 @@ - - -

            Modifying the Endpoint Service Whitelist

            -

            Function

            This API is used to modify the endpoint service whitelist.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/permissions

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to modify the endpoint service whitelist

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            vpcPermissions

            -

            Yes

            -

            Array of strings

            -

            Whitelist (user account ID)

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            {
            -  "vpcPermissions" : [ "dffef70c1db243cbb373e45791165281" ]
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0115.html b/docs/css/api-ref/css_03_0115.html deleted file mode 100644 index 66c3aba2..00000000 --- a/docs/css/api-ref/css_03_0115.html +++ /dev/null @@ -1,19 +0,0 @@ - - - -

            Parameter Configuration

            - -

            -
            - - - diff --git a/docs/css/api-ref/css_03_0116.html b/docs/css/api-ref/css_03_0116.html deleted file mode 100644 index b1a8af14..00000000 --- a/docs/css/api-ref/css_03_0116.html +++ /dev/null @@ -1,206 +0,0 @@ - - -

            Modifying Parameter Configurations

            -

            Function

            This API is used to modify parameter configurations.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/ymls/update

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to modify the parameter configurations

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            edit

            -

            Yes

            -

            UpdateYmlsReqEdit object

            -

            Configuration file information

            -
            -
            - -
            - - - - - - - - - - - -
            Table 3 UpdateYmlsReqEdit

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            modify

            -

            Yes

            -

            UpdateYmlsReqEditModify object

            -

            Operations performed on parameter configurations. The value can be:

            -
            • modify
            • delete
            • reset
            -
            -
            - -
            - - - - - - - - - - - -
            Table 4 UpdateYmlsReqEditModify

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            elasticsearch.yml

            -

            Yes

            -

            Object

            -

            Parameter configuration list. The value is the JSON data you want to modify.

            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - - - - - - - - - -
            Table 5 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            acknowledged

            -

            Boolean

            -

            Indicates whether the modification is successful.

            -
            • true: The modification is successful.
            • false: The modification failed.
            -

            externalMessage

            -

            String

            -

            Error message. If acknowledged is set to true, null is returned for this field.

            -

            httpErrorResponse

            -

            String

            -

            HTTP error information. The default value is null.

            -
            -
            -
            -

            Request Example

            {
            -  "edit" : {
            -    "modify" : {
            -      "elasticsearch.yml" : {
            -        "thread_pool.force_merge.size" : 1
            -      }
            -    }
            -  }
            -}
            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "acknowledged" : true,
            -  "externalMessage" : null,
            -  "httpErrorResponse" : null
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0117.html b/docs/css/api-ref/css_03_0117.html deleted file mode 100644 index 76051394..00000000 --- a/docs/css/api-ref/css_03_0117.html +++ /dev/null @@ -1,182 +0,0 @@ - - -

            Obtaining the Task List of Parameter Configurations

            -

            Function

            This API is used to obtain the task list of parameter configurations.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/joblists

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            configList

            -

            Array of configListRsp objects

            -

            List of historical configuration changes

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 3 configListRsp

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Action ID

            -

            clusterId

            -

            String

            -

            Cluster ID

            -

            createAt

            -

            String

            -

            Creation time. Format: Unix timestamp.

            -

            status

            -

            String

            -

            Task execution status.

            -
            • true: The operation is successful.
            • false: The execution failed.
            -

            finishedAt

            -

            String

            -

            End time. If the creation has not been completed, the end time is null. Format: Unix timestamp.

            -

            modifyDeleteReset

            -

            String

            -

            History of parameter configuration modifications

            -

            failedMsg

            -

            String

            -

            Returned error message. If the status is success, the value of this parameter is null.

            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "configList" : [ {
            -    "id" : "7ed7258a-60a8-46fe-8814-52819d491b80",
            -    "clusterId" : "4213d908-f5dc-4633-8401-cfd7175fca0c",
            -    "createAt" : 1633658735000,
            -    "status" : "success",
            -    "finishedAt" : null,
            -    "modifyDeleteReset" : "{\"modify\":{\"elasticsearch.yml\":{\"thread_pool.force_merge.size\":\"1\"}}}",
            -    "failedMsg" : ""
            -  } ]
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0118.html b/docs/css/api-ref/css_03_0118.html deleted file mode 100644 index 3c061450..00000000 --- a/docs/css/api-ref/css_03_0118.html +++ /dev/null @@ -1,131 +0,0 @@ - - -

            Obtaining the Parameter Configuration List

            -

            Function

            This API is used to obtain the parameter configuration list of the current cluster.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/ymls/template

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            configurations

            -

            Object

            -

            Cluster parameter configuration list. The key value in the object is subject to the actual situation. The value has the following attributes:

            -
            • id: parameter ID.
            • key: parameter name.
            • value: parameter value.
            • defaultValue: parameter default value.
            • regex: parameter constraint.
            • desc: parameter description in Chinese.
            • type: parameter type description.
            • moduleDesc: parameter function description in Chinese.
            • modifyEnable: indicates whether a parameter can be modified. The value can be true (parameter value can be changed) and false (parameter value cannot be changed).
            • enableValue: parameter value that can be changed.
            • fileName: name of the file where parameters exist. The default value is elasticsearch.yml.
            • version: version information.
            • descENG: parameter description in English.
            • moduleDescENG: parameter function description in English.
            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "configurations" : {
            -    "http.cors.allow-credentials" : {
            -      "id" : "b462d13c-294b-4e0f-91d3-58be2ad02b99",
            -      "key" : "http.cors.allow-credentials",
            -      "value" : "false",
            -      "defaultValue" : "false",
            -      "regex" : "^(true|false)$",
            -      "desc" : "Indicates whether to return Access-Control-Allow-Credentials in the header during cross-domain access. The value is of the Boolean type and can be true or false.
            -      "type" : "Boolean",
            -      "moduleDesc" : "Cross-domain access",
            -      "modifyEnable" : "true",
            -      "enableValue" : "true,false",
            -      "fileName" : "elasticsearch.yml",
            -      "version" : null,
            -      "descENG" : "Whether to return the Access-Control-Allow-Credentials of the header during cross-domain access. The value is a Boolean value and the options are true and false.",
            -      "moduleDescENG" : "Cross-domain Access"
            -    }
            -  }
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0119.html b/docs/css/api-ref/css_03_0119.html deleted file mode 100644 index 1a0e10ae..00000000 --- a/docs/css/api-ref/css_03_0119.html +++ /dev/null @@ -1,23 +0,0 @@ - - - -

            Kibana Public Network Access

            - -

            -
            - - - diff --git a/docs/css/api-ref/css_03_0120.html b/docs/css/api-ref/css_03_0120.html deleted file mode 100644 index a9e6c483..00000000 --- a/docs/css/api-ref/css_03_0120.html +++ /dev/null @@ -1,168 +0,0 @@ - - -

            Enabling Kibana Public Access

            -

            Function

            This API is used to enable Kibana public network access.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/open

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to enable Kibana public access

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            eipSize

            -

            Yes

            -

            Integer

            -

            Bandwidth. Unit: Mbit/s

            -

            elbWhiteList

            -

            Yes

            -

            StartKibanaPublicReqElbWhitelist object

            -

            ELB whitelist

            -
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 3 StartKibanaPublicReqElbWhitelist

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            enableWhiteList

            -

            Yes

            -

            Boolean

            -

            Indicates whether to enable the whitelist.

            -
            • true: The whitelist is enabled.
            • false: The whitelist is disabled.
            -

            whiteList

            -

            Yes

            -

            String

            -

            Whitelist

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            • {
              -  "eipSize" : 5,
              -  "elbWhiteList" : {
              -    "enableWhiteList" : true,
              -    "whiteList" : "192.168.0.xx"
              -  },
              -  "isAutoPay" : 1
              -}
              -
            • {
              -  "eipSize" : 5,
              -  "elbWhiteList" : {
              -    "enableWhiteList" : true,
              -    "whiteList" : "192.168.0.xx"
              -  }
              -}
              -
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0121.html b/docs/css/api-ref/css_03_0121.html deleted file mode 100644 index 24bb7e7d..00000000 --- a/docs/css/api-ref/css_03_0121.html +++ /dev/null @@ -1,161 +0,0 @@ - - -

            Disabling Kibana Public Access

            -

            Function

            This API is used to disable Kibana public network access.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/publickibana/close

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to disable Kibana public access

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            eipSize

            -

            No

            -

            Integer

            -

            Bandwidth. Unit: Mbit/s

            -

            elbWhiteList

            -

            No

            -

            StartKibanaPublicReqElbWhitelist object

            -

            ELB whitelist

            -
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 3 StartKibanaPublicReqElbWhitelist

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            enableWhiteList

            -

            Yes

            -

            Boolean

            -

            Indicates whether to enable the whitelist.

            -
            • true: The whitelist is enabled.
            • false: The whitelist is disabled.
            -

            whiteList

            -

            Yes

            -

            String

            -

            Whitelist

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/publickibana/close
            -
            -{
            -  "eipSize" : 5,
            -  "elbWhiteList" : {
            -    "enableWhiteList" : true,
            -    "whiteList" : "192.168.0.xx"
            -  }
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0122.html b/docs/css/api-ref/css_03_0122.html deleted file mode 100644 index 66d91d81..00000000 --- a/docs/css/api-ref/css_03_0122.html +++ /dev/null @@ -1,145 +0,0 @@ - - -

            Modifying the Kibana Public Network Bandwidth

            -

            Function

            This API is used to modify the Kibana public network bandwidth.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/bandwidth

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to modify the Kibana public network bandwidth.

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            bandWidth

            -

            Yes

            -

            UpdatePublicKibanaBandwidthReqBandWidth object

            -

            Bandwidth

            -
            -
            - -
            - - - - - - - - - - - -
            Table 3 UpdatePublicKibanaBandwidthReqBandWidth

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            size

            -

            Yes

            -

            Integer

            -

            New bandwidth size

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            • {
              -  "bandWidth" : {
              -    "size" : 5
              -  },
              -  "isAutoPay" : 1
              -}
              -
            • {
              -  "bandWidth" : {
              -    "size" : 5
              -  }
              -}
              -
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0123.html b/docs/css/api-ref/css_03_0123.html deleted file mode 100644 index ec5afb42..00000000 --- a/docs/css/api-ref/css_03_0123.html +++ /dev/null @@ -1,114 +0,0 @@ - - -

            Modifying Kibana Public Access Control

            -

            Function

            This API is used to modify the Kibana public network access whitelist.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/update

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to change Kibana access control

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            whiteList

            -

            Yes

            -

            String

            -

            Whitelisted IP addresses or network segments that can access Kibana. Separate them with commas (,), and each IP address or network segment must be unique.

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            The latest whitelist is displayed as follows.

            -
            {
            -  "whiteList" : "192.168.0.21"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0124.html b/docs/css/api-ref/css_03_0124.html deleted file mode 100644 index c8461004..00000000 --- a/docs/css/api-ref/css_03_0124.html +++ /dev/null @@ -1,89 +0,0 @@ - - -

            Disabling Kibana Public Network Access Control

            -

            Function

            This API is used to disable the Kibana public network access control.

            -
            -

            Debugging

            You can debug this API in . Automatic authentication is supported.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/close

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to disable the Kibana public network access control.

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            None

            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0125.html b/docs/css/api-ref/css_03_0125.html deleted file mode 100644 index 89ad272a..00000000 --- a/docs/css/api-ref/css_03_0125.html +++ /dev/null @@ -1,21 +0,0 @@ - - -

            Load Balancing

            -
            - - diff --git a/docs/css/api-ref/css_03_0126.html b/docs/css/api-ref/css_03_0126.html deleted file mode 100644 index 5f279161..00000000 --- a/docs/css/api-ref/css_03_0126.html +++ /dev/null @@ -1,162 +0,0 @@ - - -

            Querying ELB V3 Load Balancer Supported by a Cluster

            -

            Function

            This API is used to query the ELB V3 load balancers supported by a cluster.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            loadbalancers

            -

            Array of LoadbalancersResource objects

            -

            Load balancer list

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 3 LoadbalancersResource

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Load balancer ID

            -

            name

            -

            String

            -

            Load balancer name

            -

            l7_flavor_id

            -

            String

            -

            Layer 7 protocol ID

            -

            ip_target_enable

            -

            Boolean

            -

            Indicates whether to enable the cross-VPC backend

            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "loadbalancers" : [ {
            -    "id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6268",
            -    "name" : "elb-css",
            -    "l7_flavor_id" : "9c8c2425-e061-4bf8-ac65-cd1db92b18e1",
            -    "ip_target_enable" : true
            -  }, {
            -    "id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6269",
            -    "name" : "elb-b832",
            -    "l7_flavor_id" : "9c8c2425-e061-4bf8-ac65-cd1db92b18e1",
            -    "ip_target_enable" : true
            -  } ]
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            See Error Codes.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0127.html b/docs/css/api-ref/css_03_0127.html deleted file mode 100644 index f1fa5466..00000000 --- a/docs/css/api-ref/css_03_0127.html +++ /dev/null @@ -1,156 +0,0 @@ - - -

            Enabling or Disabling the ES Load Balancer

            -

            Function

            This API is used to enable or disable the ES load balancer.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/loadbalancers/es-switch

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the target cluster

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            enable

            -

            Yes

            -

            Boolean

            -

            Indicates whether the ES load balancer is enabled.

            -
            • true: enabled
            • false: disable
            -

            agency

            -

            No

            -

            String

            -

            Agency name

            -

            elb_id

            -

            No

            -

            String

            -

            Load balancer ID

            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 3 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            elb_id

            -

            String

            -

            Load balancer ID

            -
            -
            -
            -

            Request Example

            Enable the load balancer.

            -
            POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/58ee0f27-70b3-47e0-ac72-9e3df6cd15cd/loadbalancers/es-switch
            -
            -{
            -  "enable" : true,
            -  "elb_id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6268",
            -  "agency" : "css_elb_agency"
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            See Error Codes.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0128.html b/docs/css/api-ref/css_03_0128.html deleted file mode 100644 index b64ec5c0..00000000 --- a/docs/css/api-ref/css_03_0128.html +++ /dev/null @@ -1,168 +0,0 @@ - - -

            Configuring the ES Listener

            -

            Function

            This API is used to configure the ES listener.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/es-listeners

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the target cluster

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            protocol

            -

            Yes

            -

            String

            -

            Protocol type. HTTP and HTTPS are supported.

            -

            protocol_port

            -

            Yes

            -

            Integer

            -

            Port

            -

            server_cert_id

            -

            No

            -

            String

            -

            Server certificate ID. This parameter is mandatory when protocol is set to HTTPS.

            -

            ca_cert_id

            -

            No

            -

            String

            -

            CA certificate ID. This parameter is mandatory when protocol is set to HTTPS and bidirectional authentication is used.

            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 3 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            elb_id

            -

            String

            -

            Load balancer ID

            -
            -
            -
            -

            Request Example

            POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/es-listeners
            -
            -{
            -  "protocol" : "HTTPS",
            -  "protocol_port" : "9200",
            -  "server_cert_id" : "1b74ae4afad741e6bc9497429d3d0838",
            -  "ca_cert_id" : "2a7b050f598e4ea8a61cffbe2bdb312f"
            -}
            -
            -

            Response Example

            Status code: 200

            -

            The request is processed.

            -
            {
            -  "elb_id" : "56a83547-a55a-407a-8245-7f9b3a0606c0"
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            See Error Codes.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0129.html b/docs/css/api-ref/css_03_0129.html deleted file mode 100644 index c1c8070d..00000000 --- a/docs/css/api-ref/css_03_0129.html +++ /dev/null @@ -1,408 +0,0 @@ - - -

            Obtaining the ELB Information and Health Check Status

            -

            Function

            This API is used to obtain the ES ELB information and health check status.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/es-listeners

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            serverCertName

            -

            String

            -

            Server certificate name

            -

            serverCertId

            -

            String

            -

            Server certificate ID

            -

            cacertName

            -

            String

            -

            CA certificate name

            -

            cacertId

            -

            String

            -

            CA certificate ID

            -

            elb_enable

            -

            Boolean

            -

            Indicates whether ELB is enabled.

            -

            authentication_type

            -

            String

            -

            Authentication mode

            -

            loadBalancer

            -

            EsLoadBalancerResource object

            -

            Load balancer object information

            -

            healthmonitors

            -

            EsHealthmonitorsResource object

            -

            Health check result set

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 3 EsLoadBalancerResource

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Load balancer ID

            -

            name

            -

            String

            -

            Load balancer name

            -

            guaranteed

            -

            String

            -

            Indicates whether the load balancer is of the dedicated type.

            -
            • false: shared load balancer
            • true: dedicated load balancer
            -

            description

            -

            String

            -

            Template description

            -

            vpc_id

            -

            String

            -

            ID of the VPC where the load balancer resides

            -

            provisioning_status

            -

            String

            -

            Status of the load balancer

            -

            listeners

            -

            EsListenersResource object

            -

            Associated listeners.

            -

            vip_address

            -

            String

            -

            IPv4 virtual IP address bound to the load balancer

            -

            publicips

            -

            EsPublicipsResource object

            -

            EIP bound to the load balancer

            -
            -
            - -
            - - - - - - - - - -
            Table 4 EsListenersResource

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Listener ID

            -
            -
            - -
            - - - - - - - - - - - - - - - - - -
            Table 5 EsPublicipsResource

            Parameter

            -

            Type

            -

            Description

            -

            publicip_id

            -

            String

            -

            EIP configuration ID

            -

            publicip_address

            -

            String

            -

            IP address

            -

            ip_version

            -

            String

            -

            IP address version.

            -
            • 4: IPv4
            • 6: IPv6
            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 6 EsHealthmonitorsResource

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Backend server ID

            -

            name

            -

            String

            -

            Backend server name

            -

            protocol_port

            -

            String

            -

            Frontend listening port of the backend service

            -

            ipgroup

            -

            EsHealthIpgroupResource object

            -

            Access control information of the listener object

            -
            -
            - -
            - - - - - - - - - - - - - - - - - -
            Table 7 EsHealthIpgroupResource

            Parameter

            -

            Type

            -

            Description

            -

            ipgroup_id

            -

            String

            -

            ID of the access control group associated with the listener

            -

            enable_ipgroup

            -

            Boolean

            -

            Access control group status

            -

            type

            -

            String

            -

            Access control group type

            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "loadBalancer" : {
            -    "id" : "5d45faad-6cb3-479b-96b8-3e2de0cc6268",
            -    "name" : "elb-css",
            -    "guaranteed" : "true",
            -    "description" : "",
            -    "listeners" : [ {
            -      "id" : "011d14fa-908b-4cd9-b0d6-0768ddc6cb71"
            -    }, {
            -      "id" : "04b86029-c281-4490-a3bd-5ea1266658ba"
            -    } ],
            -    "publicips" : [ {
            -      "publicip_id" : "f678e23c-96a5-49e8-8ea2-bd8b47d41e78",
            -      "publicip_address" : "100.1.1.1",
            -      "ip_version" : 4
            -    } ],
            -    "billing_info" : null,
            -    "vpc_id" : "4f3deec3-efa8-4598-bf91-560aad1377a3",
            -    "provisioning_status" : "ACTIVE",
            -    "vip_address" : "10.0.0.1"
            -  },
            -  "listener" : {
            -    "id" : "41ff041d-c7b9-4142-9167-fa93d54f97da",
            -    "name" : "css-searchServer",
            -    "protocol" : "HTTPS",
            -    "ipgroup" : null,
            -    "protocol_port" : 9265
            -  },
            -  "healthmonitors" : [ {
            -    "id" : "bac86342-2222-43e6-817f-57f040a174a6",
            -    "name" : "",
            -    "address" : "10.0.0.87",
            -    "protocol_port" : 9200,
            -    "operating_status" : "ONLINE"
            -  }, {
            -    "id" : "d935b82c-f94b-4ae0-9997-ddc90885d8c6",
            -    "name" : "",
            -    "address" : "10.0.0.61",
            -    "protocol_port" : 9200,
            -    "operating_status" : "ONLINE"
            -  } ],
            -  "serverCertName" : "server1",
            -  "serverCertId" : "82375af01c0d40f6a44c15962c570625",
            -  "cacertName" : null,
            -  "cacertId" : null,
            -  "elb_enable" : true,
            -  "authentication_type" : "single"
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            See Error Codes.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0130.html b/docs/css/api-ref/css_03_0130.html deleted file mode 100644 index a55551b6..00000000 --- a/docs/css/api-ref/css_03_0130.html +++ /dev/null @@ -1,257 +0,0 @@ - - -

            Updating an ES Listener

            -

            Function

            This API is used to update an ES listener.

            -
            -

            URI

            PUT /v1.0/{project_id}/clusters/{cluster_id}/es-listeners/{listener_id}

            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the target cluster

            -

            listener_id

            -

            Yes

            -

            String

            -

            ID of the listener to be updated

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            listener

            -

            Yes

            -

            EsListenerRequest object

            -

            Listener object

            -
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 3 EsListenerRequest

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            default_tls_container_ref

            -

            Yes

            -

            String

            -

            ID of the server certificate used by the listener

            -

            client_ca_tls_container_ref

            -

            No

            -

            String

            -

            ID of the CA certificate used by the listener. This parameter is mandatory when bidirectional authentication is to be updated.

            -
            -
            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 4 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            listener

            -

            EsListenerResponse object

            -

            Listener object

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 5 EsListenerResponse

            Parameter

            -

            Type

            -

            Description

            -

            protocol

            -

            String

            -

            Protocol used by the listener

            -

            id

            -

            String

            -

            Listener ID

            -

            name

            -

            String

            -

            Listener name

            -

            protocol_port

            -

            String

            -

            Port used by the listener

            -

            ipgroup

            -

            EsIpgroupResource object

            -

            Access control information of the listener object

            -
            -
            - -
            - - - - - - - - - - - - - - - - - -
            Table 6 EsIpgroupResource

            Parameter

            -

            Type

            -

            Description

            -

            ipgroup_id

            -

            String

            -

            ID of the access control group associated with the listener

            -

            enable_ipgroup

            -

            Boolean

            -

            Access control group status

            -

            type

            -

            String

            -

            Access control group type

            -
            -
            -
            -

            Request Example

            PUT /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/58ee0f27-70b3-47e0-ac72-9e3df6cd15cd/es-listeners/4425eb63-78ce-4c63-b60e-492befdac0e7
            -
            -{
            -  "listener" : {
            -    "default_tls_container_ref" : "9c82320a8dd049eba49b28e70a2c0c3e"
            -  }
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            See Error Codes.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0131.html b/docs/css/api-ref/css_03_0131.html deleted file mode 100644 index 46a40afd..00000000 --- a/docs/css/api-ref/css_03_0131.html +++ /dev/null @@ -1,157 +0,0 @@ - - -

            Querying the Certificate List

            -

            Function

            This API is used to query the certificate list.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/elb/certificates

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            certificates

            -

            CertificatesResource object

            -

            Certificate list information

            -
            -
            - -
            - - - - - - - - - - - - - - - - - -
            Table 3 CertificatesResource

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Certificate ID

            -

            name

            -

            String

            -

            Certificate name

            -

            type

            -

            String

            -

            SL certificate type. The value can be server (server certificate) or client (CA certificates).

            -
            -
            -
            -

            Request Example

            None

            -
            -

            Response Example

            Status code: 200

            -

            The request is processed successfully.

            -
            {
            -  "certificates" : [ {
            -    "id" : "8c415d2e2f4c4fdbbfc9c21c98d7832b",
            -    "name" : "server1",
            -    "type" : "server"
            -  }, {
            -    "id" : "8c415d2e2f4c4fdbbfc9c21c98d7832b",
            -    "name" : "ca1",
            -    "type" : "client"
            -  }, {
            -    "id" : "8c415d2e2f4c4fdbbfc9c21c98d7832b",
            -    "name" : "server-css",
            -    "type" : "server"
            -  } ]
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            See Error Codes.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0132.html b/docs/css/api-ref/css_03_0132.html deleted file mode 100644 index a710a986..00000000 --- a/docs/css/api-ref/css_03_0132.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

            Intelligent O&M

            -
            - - diff --git a/docs/css/api-ref/css_03_0133.html b/docs/css/api-ref/css_03_0133.html deleted file mode 100644 index adfdd1c5..00000000 --- a/docs/css/api-ref/css_03_0133.html +++ /dev/null @@ -1,196 +0,0 @@ - - -

            Creating a Cluster Detection Task

            -

            Function

            This API is used to create a cluster detection task.

            -
            -

            URI

            POST /v1.0/{project_id}/clusters/{cluster_id}/ai-ops

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the target cluster

            -
            -
            -
            -

            Request Parameters

            -
            - - - - - - - - - - - -
            Table 2 Request header parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            X-Language

            -

            No

            -

            String

            -

            Language

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 3 Request body parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            name

            -

            Yes

            -

            String

            -

            Detection task name

            -

            description

            -

            No

            -

            String

            -

            Detection task description

            -

            alarm

            -

            No

            -

            alarm object

            -

            After the detection task is complete, an SMN alarm message is sent.

            -
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 4 alarm

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            level

            -

            Yes

            -

            String

            -

            Sensitivity of an SMN alarm message.

            -
            • high
            • medium
            • suggestion
            • norisk
            -

            smn_topic

            -

            Yes

            -

            String

            -

            SMN topic name

            -
            -
            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            Create a cluster detection task.

            -
            POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/ai-ops
            -
            -{
            -    "name": " aiops-test ",
            -"description": " Create a cluster checking task.
            - ",
            -    "alarm":{
            -        "level":"high",
            -        "smn_topic":"aiops-test"
            -    }
            -}
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            For details, see Error Code.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0134.html b/docs/css/api-ref/css_03_0134.html deleted file mode 100644 index d23e15b8..00000000 --- a/docs/css/api-ref/css_03_0134.html +++ /dev/null @@ -1,328 +0,0 @@ - - -

            Obtaining the Intelligent O&M Task List and Details

            -

            Function

            This API is used to obtain the intelligent O&M task list and details.

            -
            -

            URI

            GET /v1.0/{project_id}/clusters/{cluster_id}/ai-ops

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            - -
            - - - - - - - - - - - - - - - - -
            Table 2 Query parameter

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            limit

            -

            No

            -

            Integer

            -

            Maximum number of records displayed on a page

            -

            start

            -

            No

            -

            Integer

            -

            Offset. All VPC endpoint services after this offset will be queried. The offset must be an integer greater than 0 but less than the number of VPC endpoint services.

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - - - - - -
            Table 3 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            total_size

            -

            Integer

            -

            Number of cluster detection tasks

            -

            aiops_list

            -

            Array of aiops_list objects

            -

            Detection task list

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 4 aiops_list

            Parameter

            -

            Type

            -

            Description

            -

            id

            -

            String

            -

            Detection task ID

            -

            name

            -

            String

            -

            Detection task name

            -

            desc

            -

            String

            -

            Detection task description

            -

            status

            -

            Integer

            -

            Task execution status.

            -
            • 150: Disabled
            • 200: Enabled
            • 300: Sent
            -

            summary

            -

            summary object

            -

            Risk summary

            -

            create_time

            -

            String

            -

            Timestamp when a detection task is created

            -

            smn_status

            -

            String

            -

            Status of SMN alarm messages.

            -
            • not_open
            • not_trigger
            • sent
            • send_fail
            -

            smn_fail_reason

            -

            String

            -

            Cause of the message sending failure

            -

            task_risks

            -

            Array of AIOpsRiskInfo objects

            -

            Risk item details

            -
            -
            - -
            - - - - - - - - - - - - - - - - - -
            Table 5 summary

            Parameter

            -

            Type

            -

            Description

            -

            high

            -

            Integer

            -

            Number of high-risk items

            -

            medium

            -

            Integer

            -

            Number of medium-risk items

            -

            suggestion

            -

            Integer

            -

            Number of suggestion items

            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 6 AIOpsRiskInfo

            Parameter

            -

            Type

            -

            Description

            -

            riskType

            -

            String

            -

            Check item description

            -

            level

            -

            String

            -

            Severity.

            -
            • high
            • medium
            • suggestion
            -

            desc

            -

            String

            -

            Risk description

            -

            suggestion

            -

            String

            -

            Suggestions for the risks

            -
            -
            -
            -

            Request Example

            Obtain the intelligent O&M task list and details.

            -
            GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/ai-ops
            -
            -

            Response Example

            Status code: 200

            -

            Request sent.

            -
            {
            -  "aiops_list" : [ {
            -    "id" : "7381a80b-68cb-4b9e-8226-37d686b18b1d",
            -    "name" : "aiops-test",
            -    "desc" : "",
            -    "status" : 200,
            -    "summary" : {
            -      "high" : 1,
            -      "medium" : 0,
            -      "suggestion" : 1
            -    },
            -    "create_time" : 1687944156750,
            -    "smn_status" : "not_open",
            -    "smn_fail_reason" : null,
            -    "task_risks" : [ {
            -      "riskType" : "Check whether the cluster has snapshot backup failures or no snapshot backup records in the last seven days."
            -      "level" : "suggestion",
            -      "desc" : "The cluster has no snapshot backup records in the last seven days."
            -      "suggestion" : "You are advised to enable the cluster snapshot function and ensure that snapshots generated in the last seven days are successfully backed up. If snapshot creation fails, click the cluster name, and check the failure details on the Cluster Snapshots and Logs pages."
            -    }, {
            -      "riskType" : "Check the number of nodes in the cluster and the number of AZs to evaluate the high availability of the distributed Elasticsearch cluster."
            -      "level" : "high",
            -      "desc" : "The current cluster has one or two nodes. If a node is faulty, the entire cluster may become unavailable. The service availability risk is high."
            -      "suggestion" : "You are advised to change the cluster to a multi-AZ cluster. Procedure: On the CSS cluster console, choose Clusters > Elasticsearch. In the Operation column of a cluster, choose More > Modify Configuration. Click the Change AZ tab and add AZs. Click the Scale Cluster tab and change the number of nodes.
            -    } ]
            -  } ],
            -  "total_size" : 1
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            Request sent.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            For details, see Error Code.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0135.html b/docs/css/api-ref/css_03_0135.html deleted file mode 100644 index dc19d096..00000000 --- a/docs/css/api-ref/css_03_0135.html +++ /dev/null @@ -1,99 +0,0 @@ - - -

            Deleting a Detection Task Record

            -

            Function

            This API is used to delete a detection task record.

            -
            -

            URI

            DELETE /v1.0/{project_id}/clusters/{cluster_id}/ai-ops/{aiops_id}

            - -
            - - - - - - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

            -

            cluster_id

            -

            Yes

            -

            String

            -

            ID of the cluster that you want to delete a detection task record

            -

            aiops_id

            -

            Yes

            -

            String

            -

            Detection task ID

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            None

            -
            -

            Request Example

            Delete a detection task record.

            -
            DELETE /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/ai-ops/e19c9298-465e-42ad-a0ae-b6b552222925
            -
            -

            Response Example

            None

            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            The request is processed successfully.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            For details, see Error Code.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0136.html b/docs/css/api-ref/css_03_0136.html deleted file mode 100644 index 2312c111..00000000 --- a/docs/css/api-ref/css_03_0136.html +++ /dev/null @@ -1,138 +0,0 @@ - - -

            Obtaining SMN Topics Available for Intelligent O&M Alarms

            -

            Function

            This API is used to obtain SMN topics available for intelligent O&M alarms.

            -
            -

            URI

            GET /v1.0/{project_id}/domains/{domain_id}/ai-ops/smn-topics

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Path parameters

            Parameter

            -

            Mandatory

            -

            Type

            -

            Description

            -

            project_id

            -

            Yes

            -

            String

            -

            Project ID. For details about how to obtain a project ID, see Obtaining a Project ID and Name.

            -

            domain_id

            -

            Yes

            -

            String

            -

            ID of the cluster to be queried

            -
            -
            -
            -

            Request Parameters

            None

            -
            -

            Response Parameters

            Status code: 200

            - -
            - - - - - - - - - -
            Table 2 Response body parameter

            Parameter

            -

            Type

            -

            Description

            -

            topicsName

            -

            Array of strings

            -

            SMN topic name list

            -
            -
            -
            -

            Request Example

            Obtain the intelligent O&M task list and details.

            -
            GET /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/ai-ops
            -
            -

            Response Example

            Status code: 200

            -

            Request sent.

            -
            {
            -  "aiops_list" : [ {
            -    "id" : "7381a80b-68cb-4b9e-8226-37d686b18b1d",
            -    "name" : "aiops-test",
            -    "desc" : "",
            -    "status" : 200,
            -    "summary" : {
            -      "high" : 1,
            -      "medium" : 0,
            -      "suggestion" : 1
            -    },
            -    "create_time" : 1687944156750,
            -    "smn_status" : "not_open",
            -    "smn_fail_reason" : null,
            -    "task_risks" : [ {
            -      "riskType" : "Check whether the cluster has snapshot backup failures or no snapshot backup records in the last seven days.",
            -      "level" : "suggestion",
            -      "desc" : "The cluster has no snapshot backup records in the last seven days.",
            -      "suggestion" : "You are advised to enable the cluster snapshot function and ensure that snapshots generated in the last seven days are successfully backed up. If snapshot creation fails, click the cluster name, and check the failure details on the Cluster Snapshots and Logs pages."
            -    }, {
            -      "riskType" : "Check the number of nodes in the cluster and the number of AZs to evaluate the high availability of the distributed Elasticsearch cluster."
            -      "level" : "high",
            -      "desc" : "The current cluster has one or two nodes. If a node is faulty, the entire cluster may become unavailable. The service availability risk is high."
            -      "suggestion" : "You are advised to change the cluster to a multi-AZ cluster. Procedure: On the CSS cluster console, choose Clusters > Elasticsearch. In the Operation column of a cluster, choose More > Modify Configuration. Click the Change AZ tab and add AZs. Click the Scale Cluster tab and change the number of nodes.
            -    } ]
            -  } ],
            -  "total_size" : 1
            -}
            -
            -

            Status Codes

            -
            - - - - - - - - - - - - - - - - -

            Status Code

            -

            Description

            -

            200

            -

            Request sent.

            -

            400

            -

            Invalid request.

            -

            Modify the request instead of retrying.

            -

            409

            -

            The request cannot be processed due to a conflict.

            -

            This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.

            -

            412

            -

            The server does not meet one of the requirements that the requester puts on the request.

            -
            -
            -
            -

            Error Codes

            For details, see Error Code.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0137.html b/docs/css/api-ref/css_03_0137.html deleted file mode 100644 index 3c02759c..00000000 --- a/docs/css/api-ref/css_03_0137.html +++ /dev/null @@ -1,15 +0,0 @@ - - -

            Calling APIs

            -
            - - diff --git a/docs/css/api-ref/css_03_0138.html b/docs/css/api-ref/css_03_0138.html deleted file mode 100644 index fcda3965..00000000 --- a/docs/css/api-ref/css_03_0138.html +++ /dev/null @@ -1,127 +0,0 @@ - - -

            Making an API Request

            -

            This section describes the structure of a RESTful API request, and uses the API for Obtaining a User Token as an example to describe how to call an API. A token is a user's access credential, which contains the user identity and permission information. The obtained token is used to authenticate the calling of other APIs.

            -

            Request URI

            A request URI is in the following format:

            -

            {URI-scheme}://{Endpoint}/{resource-path}?{query-string}

            - -
            - - - - - - - - - - - - - - - - -
            Table 1 Request URL

            Parameter

            -

            Description

            -

            URI-scheme

            -

            Protocol used to transmit requests. All APIs use HTTPS.

            -

            Endpoint

            -

            Domain name or IP address of the server running the REST service. The endpoint varies between services in different regions. It can be obtained from Endpoints.

            -

            resource-path

            -

            API access path for performing a specified operation. Obtain the value from the URI of the API. For example, the resource-path of the API for obtaining a user token is /v3/auth/tokens.

            -

            query-string

            -

            Query parameter, which is optional. Ensure that a question mark (?) is included before a query parameter that is in the format of "Parameter name=Parameter value". For example, limit=10 indicates that a maximum of 10 pieces of data is to be viewed.

            -
            -
            -
            
            -
            For example, to obtain an IAM token in a region, obtain the endpoint of IAM for this region and the resource-path (/v3/auth/tokens) in the URI of the API used to obtain a user token. Then, construct the URI as follows:
            https://<iam-endpoint>/v3/auth/tokens
            -
            -

            To simplify the URI display, each API is provided with only a resource-path and a request method. This is because the URI-scheme value of all APIs is HTTPS, and the endpoints in a region are the same. Therefore, the two parts are omitted.

            -
            -
            -

            Request Methods

            HTTP-based request methods, which are also called operations or actions, specify the type of operations that you are requesting.

            -
            • GET: requests the server to return specified resources.
            • PUT: requests the server to update specified resources.
            • POST: requests the server to add resources or perform special operations.
            • DELETE: requests the server to delete specified resources, for example, an object.
            • HEAD: requests a server resource header.
            • PATCH: requests the server to update partial content of a specified resource. If the target resource does not exist, PATCH may create a resource.
            -

            If POST is displayed in the URI of the API for obtaining a user token, the request is as follows:

            -
            -POST https://{iam-endpoint}/v3/auth/tokens
            -
            -

            Request Header

            You can also add additional fields to a request, such as the fields required by a specified URI or an HTTP method. For example, to request for the authentication information, add Content-Type, which specifies the request body type.

            -

            Table 2 lists common request header fields.

            - -
            - - - - - - - - - - - - - - - - - -
            Table 2 Common request headers

            Parameter

            -

            Mandatory

            -

            Description

            -

            Content-Type

            -

            Yes

            -

            Message body type (or format). You are advised to use the default value application/json.

            -

            X-Auth-Token

            -

            No (Mandatory for token-based authentication)

            -

            User token.

            -

            Response for calling the "Obtaining a User Token" API. This API is the only one that does not require authentication. After the request is processed, the value of X-Subject-Token in the response header (Header) is the token value.

            -

            X-Language

            -

            No

            -

            Request language

            -
            -
            -

            The API used to obtain a user token does not require authentication. Therefore, only the Content-Type field needs to be added to requests for calling the API. An example of such requests is as follows:

            -
            POST https://{iam-endpoint}/v3/auth/tokens
            -Content-Type: application/json
            -
            -

            Request Body

            A request body conveys information other than the request header and is generally sent in a structured format defined by the request header field Content-Type.

            -

            The request body varies according to the APIs. Certain APIs do not require the request body, such as the GET and DELETE APIs.

            -

            In the case of the API used to obtain a user token, the request parameters and parameter description can be obtained from the API request. The following provides an example request with a body included. Replace username, domainname, ******** (login password), and xxxxxxxxxxxxxxxxxx (project ID) with the actual values. To learn how to obtain a project ID, see Obtaining a Project ID and Name.

            -

            The scope parameter defines the application scope of the token, indicating that the obtained token can access only the resources in the specified project.

            -
            -
            POST https://{iam-endpoint}/v3/auth/tokens
            -Content-Type: application/json
            -{
            -    "auth": {
            -        "identity": {
            -            "methods": [
            -                "password"
            -            ],
            -            "password": {
            -                "user": {
            -                    "name": "username",    //Username
            -                    "password": "********",    //Login password
            -                    "domain": {
            -                        "name": "domainname "    //Name of the account to which the user belongs
            -                    }
            -                }
            -            }
            -        },
            -        "scope": {
            -            "project": {
            -                "id": "xxxxxxxxxxxxxxxxxx"    //Project ID
            -            }
            -        }
            -    }
            -}
            -

            If all data required by a request is available, you can send the request to call an API through curl, Postman, or coding. For the API of obtaining a user token, x-subject-token in the response header is the desired user token. Then, you can use the token to authenticate the calling of other APIs.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0139.html b/docs/css/api-ref/css_03_0139.html deleted file mode 100644 index 0b573091..00000000 --- a/docs/css/api-ref/css_03_0139.html +++ /dev/null @@ -1,43 +0,0 @@ - - -

            Authentication

            -

            CSS supports token authentication.

            -

            Authentication Using Tokens

            The validity period of a token is 24 hours. When using a token for authentication, cache it to prevent frequently calling the IAM API.

            -
            -

            A token specifies certain permissions in a computer system. Authentication using a token adds the token to a request as its header during API calling to obtain permissions to operate APIs through IAM.

            -

            The API for obtaining a token is POST https://{IAM endpoint}/v3/auth/tokens. For details about how to obtain IAM endpoints, see Endpoints.

            -
            {
            -	"auth": {
            -		"identity": {
            -			"methods": [
            -				"password"
            -			],
            -			"password": {
            -				"user": {
            -					"name": "username",    //Username
            -					"password": "********",    //Login password
            -					"domain": {
            -						"name": "domainname"    //Name of the account that the user belongs to
            -					}
            -				}
            -			}
            -		},
            -		"scope": {
            -			"project": {
            -				"name": "xxxxxxxx"    //Project name
            -			}
            -		}
            -	}
            -}
            -

            After a token is obtained, the X-Auth-Token header field must be added to requests to specify the token when calling other APIs. For example, if the token is ABCDEFJ...., X-Auth-Token: ABCDEFJ.... can be added to a request as follows:

            -
            POST https://{endpoint}/v3/auth/projects
            -Content-Type: application/json
            -X-Auth-Token: ABCDEFJ....
            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/css_03_0140.html b/docs/css/api-ref/css_03_0140.html deleted file mode 100644 index 880d0bd8..00000000 --- a/docs/css/api-ref/css_03_0140.html +++ /dev/null @@ -1,39 +0,0 @@ - - -

            Returned Values

            -

            Status Code

            After sending a request, you will receive a response containing the status code, response header, and response body.

            -

            A status code is a group of digits, ranging from 1xx to 5xx. It indicates the status of a request. For more information, see Status Code.

            -

            If status code 201 is returned for the calling of the API for obtaining a user token, the request is successful.

            -
            -

            Response Header

            A response header corresponds to a request header, for example, Content-Type.

            -

            Figure 1 shows the response header for the API of obtaining a user token, where x-subject-token is the desired user token. Then, you can use the token to authenticate the calling of other APIs.

            -
            Figure 1 Header of the response to the request for obtaining a user token
            -
            -

            Response Body

            A response body is generally returned in a structured format, corresponding to the Content-Type in the response header, and is used to transfer content other than the response header.

            -

            The following shows part of the response body for the API of obtaining a user token.

            -
            {
            -    "token": {
            -        "expires_at": "2019-02-13T06:52:13.855000Z",
            -        "methods": [
            -            "password"
            -        ],
            -        "catalog": [
            -            {
            -                "endpoints": [
            -                    {
            -                        "region_id": "xxx",
            -......
            -

            If an error occurs during API calling, the system returns an error code and a message to you. The following shows the format of an error response body:

            -
            {
            -    "error_msg": "The format of message is error",
            -    "error_code": "AS.0001"
            -}
            -

            In the preceding information, error_code is an error code, and error_msg describes the error.

            -
            -
            -
            - -
            - diff --git a/docs/css/api-ref/en-us_image_0000001554710113.png b/docs/css/api-ref/en-us_image_0000002083397766.png similarity index 100% rename from docs/css/api-ref/en-us_image_0000001554710113.png rename to docs/css/api-ref/en-us_image_0000002083397766.png diff --git a/docs/css/api-ref/en-us_image_0000002083397786.png b/docs/css/api-ref/en-us_image_0000002083397786.png new file mode 100644 index 00000000..94736e3a Binary files /dev/null and b/docs/css/api-ref/en-us_image_0000002083397786.png differ diff --git a/docs/css/api-ref/en-us_image_0000002083557630.png b/docs/css/api-ref/en-us_image_0000002083557630.png new file mode 100644 index 00000000..e892e305 Binary files /dev/null and b/docs/css/api-ref/en-us_image_0000002083557630.png differ diff --git a/docs/css/api-ref/en-us_image_0000002083557722.png b/docs/css/api-ref/en-us_image_0000002083557722.png new file mode 100644 index 00000000..508f4c13 Binary files /dev/null and b/docs/css/api-ref/en-us_image_0000002083557722.png differ diff --git a/docs/css/api-ref/en-us_image_0000002119077481.png b/docs/css/api-ref/en-us_image_0000002119077481.png new file mode 100644 index 00000000..0adf514b Binary files /dev/null and b/docs/css/api-ref/en-us_image_0000002119077481.png differ diff --git a/docs/css/api-ref/en-us_image_0000002119077517.png b/docs/css/api-ref/en-us_image_0000002119077517.png new file mode 100644 index 00000000..829989a9 Binary files /dev/null and b/docs/css/api-ref/en-us_image_0000002119077517.png differ diff --git a/docs/css/api-ref/en-us_image_0000002119077729.png b/docs/css/api-ref/en-us_image_0000002119077729.png new file mode 100644 index 00000000..82ae02d8 Binary files /dev/null and b/docs/css/api-ref/en-us_image_0000002119077729.png differ diff --git a/docs/css/api-ref/en-us_image_0000001554910161.png b/docs/css/api-ref/en-us_image_0000002119117513.png similarity index 100% rename from docs/css/api-ref/en-us_image_0000001554910161.png rename to docs/css/api-ref/en-us_image_0000002119117513.png diff --git a/docs/css/api-ref/en-us_topic_0000002083557490.html b/docs/css/api-ref/en-us_topic_0000002083557490.html new file mode 100644 index 00000000..f557563f --- /dev/null +++ b/docs/css/api-ref/en-us_topic_0000002083557490.html @@ -0,0 +1,15 @@ + + + +

            Examples

            + +

            +
            + + + diff --git a/docs/css/api-ref/kibana_public_network_access.html b/docs/css/api-ref/kibana_public_network_access.html new file mode 100644 index 00000000..398afb10 --- /dev/null +++ b/docs/css/api-ref/kibana_public_network_access.html @@ -0,0 +1,24 @@ + + +

            Kibana Public Network Access

            +

            +
            + + diff --git a/docs/css/api-ref/log_management.html b/docs/css/api-ref/log_management.html new file mode 100644 index 00000000..0fcf6d7d --- /dev/null +++ b/docs/css/api-ref/log_management.html @@ -0,0 +1,34 @@ + + +

            Log Management

            +

            +
            + + diff --git a/docs/css/api-ref/public_network_access.html b/docs/css/api-ref/public_network_access.html new file mode 100644 index 00000000..cde68844 --- /dev/null +++ b/docs/css/api-ref/public_network_access.html @@ -0,0 +1,24 @@ + + +

            Public Network Access

            +

            +
            + + diff --git a/docs/css/api-ref/snapshot_management.html b/docs/css/api-ref/snapshot_management.html new file mode 100644 index 00000000..fe913171 --- /dev/null +++ b/docs/css/api-ref/snapshot_management.html @@ -0,0 +1,36 @@ + + +

            Snapshot Management

            +

            +
            + + diff --git a/docs/css/api-ref/topic_300000010.html b/docs/css/api-ref/topic_300000010.html new file mode 100644 index 00000000..9a276ee1 --- /dev/null +++ b/docs/css/api-ref/topic_300000010.html @@ -0,0 +1,26 @@ + + +

            Load Balancing

            +

            +
            + + diff --git a/docs/css/api-ref/vpecp_management.html b/docs/css/api-ref/vpecp_management.html new file mode 100644 index 00000000..f02c08e1 --- /dev/null +++ b/docs/css/api-ref/vpecp_management.html @@ -0,0 +1,24 @@ + + +

            VPC Endpoint

            +

            +
            + + diff --git a/docs/css/api-ref/ymls_management.html b/docs/css/api-ref/ymls_management.html new file mode 100644 index 00000000..9f691eb3 --- /dev/null +++ b/docs/css/api-ref/ymls_management.html @@ -0,0 +1,20 @@ + + +

            Parameter Configuration

            +

            +
            + +