Creating a Subnet
Function
This API is used to create a subnet.
URI
POST /v1/{project_id}/subnets
Name |
Mandatory |
Description |
---|---|---|
project_id |
Yes |
Specifies the project ID. For details about how to obtain a project ID, see Obtaining a Project ID. |
Request Message
- Request parameter
Table 2 Request parameter Name
Mandatory
Type
Description
subnet
Yes
Object
Specifies the subnet objects.
Table 3 subnet objects Name
Mandatory
Type
Description
name
Yes
String
- Specifies the subnet name.
- The value is a string of 1 to 64 characters that can contain letters, digits, underscores (_), hyphens (-), and periods (.).
description
No
String
- Provides supplementary information about the subnet.
- The value is a string of no more than 255 characters and cannot contain angle brackets (< or >).
cidr
Yes
String
- Specifies the subnet CIDR block.
- The value must be within the VPC CIDR block.
- The value must be in CIDR format. The subnet mask cannot be greater than 28.
gateway_ip
Yes
String
- Specifies the gateway of the subnet.
- The value must be an IP address in the subnet.
- The value must be a valid IP address.
dhcp_enable
No
Boolean
- Specifies whether DHCP is enabled for the subnet.
- The value can be true (enabled) or false (disabled).
- If this parameter is left blank, the system automatically sets it to true by default. If this parameter is set to false, newly created ECSs cannot obtain IP addresses, and usernames and passwords cannot be injected using Cloud-init. Exercise caution when performing this operation.
primary_dns
No
String
- Specifies the IP address of DNS server 1 on the subnet.
- The value must be an IP address. If the value is not specified, the default value will be left blank.
secondary_dns
No
String
- Specifies the IP address of DNS server 2 on the subnet.
- The value must be an IP address. If the value is not specified, the default value will be left blank.
dnsList
No
Array of strings
- Specifies the DNS server address list of a subnet. This field is required if you need to use more than two DNS servers.
- This parameter value is the superset of both DNS server address 1 and DNS server address 2. If the value is not specified, the default value will be left blank.
availability_zone
No
String
- Specifies the AZ to which the subnet belongs, which can be obtained from endpoints.
- The value must be an existing AZ in the system. If the value is not specified, the default value will be left blank.
vpc_id
Yes
String
Specifies the ID of the VPC to which the subnet belongs.
- Example request
POST https://{Endpoint}/v1/{project_id}/subnets { "subnet": { "name": "subnet", "description": "", "cidr": "192.168.20.0/24", "gateway_ip": "192.168.20.1", "dhcp_enable": true, "primary_dns": "114.xx.xx.114", "secondary_dns": "114.xx.xx.115", "dnsList": [ "114.xx.xx.114", "114.xx.xx.115" ], "availability_zone": "aa-bb-cc",//For example, the AZ is aa-bb-cc. "vpc_id": "3ec3b33f-ac1c-4630-ad1c-7dba1ed79d85" } }
Response Message
- Response parameter
Table 4 Response parameter Name
Type
Description
subnet
Object
Specifies the subnet objects.
- Example response
{ "subnet": { "id": "4779ab1c-7c1a-44b1-a02e-93dfc361b32d", "name": "subnet", "description": "", "cidr": "192.168.20.0/24", "dnsList": [ "114.xx.xx.114", "1114.xx.xx.115" ], "status": "UNKNOWN", "vpc_id": "3ec3b33f-ac1c-4630-ad1c-7dba1ed79d85", "gateway_ip": "192.168.20.1", "dhcp_enable": true, "primary_dns": "114.xx.xx.114", "secondary_dns": "114.xx.xx.115", "availability_zone": "aa-bb-cc",//For example, the AZ is aa-bb-cc. "neutron_network_id": "4779ab1c-7c1a-44b1-a02e-93dfc361b32d", "neutron_subnet_id": "213cb9d-3122-2ac1-1a29-91ffc1231a12" } }
Status Code
See Status Codes.
Error Code
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