Configuring Access to a Replica Set Across CIDR Blocks
Function
This API is used to configure access to a replica set across CIDR blocks.
Constraints
This API supports the following types of instances:
- GeminiDB Mongo
This operation is not supported for frozen or abnormal instances.
URI
POST https://{Endpoint}/v3/{project_id}/instances/{instance_id}/client-network
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID of a tenant in a region. To obtain this value, see Obtaining a Project ID. |
instance_id |
Yes |
String |
Instance ID, which can be obtained by calling the API described in Querying Instances and Details. If there are no instances available, call the API described in Creating an Instance to create one. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
User token. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
client_network_ranges |
Yes |
Array of strings |
CIDR block where the client is located.
|
Response Parameters
Status code: 202
Parameter |
Type |
Description |
---|---|---|
job_id |
String |
Task ID. |
Example Requests
- URI example
POST https://gaussdb-nosql.ap-southeast-1.myhuaweicloud.com/v3/619d3e78f61b4be68bc5aa0b59edcf7b/instances/9136fd2a9fcd405ea4674276ce36dae8in10/client-network
- Changing the CIDR block where the client is located to 192.168.0.0/16
{ "client_network_ranges" : [ "192.168.0.0/16" ] }
Example Responses
Status code: 202
Accepted
{ "job_id" : "89638f5e-0780-497c-b3c0-4d0968383e19" }
Status Codes
For details, see Status Codes.
Error Codes
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot