Querying VPC Channels
Function
This API is used to query the VPC channels.
URI
GET /v2/{project_id}/apic/instances/{instance_id}/vpc-channels
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID. For details about how to obtain the project ID, see Appendix > Obtaining a Project ID in the ROMA Connect API Reference. |
|
instance_id |
Yes |
String |
Instance ID. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
offset |
No |
Long |
Offset from which the query starts. If the offset is less than 0, the value is automatically converted to 0. Default: 0 |
|
limit |
No |
Integer |
Number of items displayed on each page. Minimum: 1 Maximum: 500 Default: 20 |
|
id |
No |
String |
VPC channel ID. |
|
name |
No |
String |
VPC channel name. |
|
dict_code |
No |
String |
The dictionary code of a VPC channel. The value can contain letters, digits, and special characters (-_). Not supported currently. Minimum: 3 Maximum: 64 |
|
precise_search |
No |
String |
Parameter name for exact matching. If multiple parameters need to support exact match, separate them with commas (,). Currently, name and member_group_name are supported. |
|
member_host |
No |
String |
Backend server address. By default, exact query is supported and fuzzy query is not supported.] |
|
member_port |
No |
Integer |
Backend server port. Minimum: 0 Maximum: 65535 |
|
member_group_name |
No |
String |
Name of the backend server group. |
|
member_group_id |
No |
String |
ID of the backend server group. |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Auth-Token |
Yes |
String |
User token, which can be obtained by calling the IAM API (value of X-Subject-Token in the response header). |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
size |
Integer |
Length of the returned resource list. |
|
total |
Long |
Number of resources that match the query conditions. |
|
vpc_channels |
Array of VpcChannelInfo objects |
VPC channel list. |
|
Parameter |
Type |
Description |
|---|---|---|
|
name |
String |
VPC channel name. The value is a string of 3 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed. The value must start with an English letter.
NOTE:
Characters must be encoded using UTF-8 or Unicode. |
|
port |
Integer |
Port number of the host in the VPC channel. The value ranges from 1 to 65535. |
|
balance_strategy |
Integer |
Distribution algorithm.
Default: 1 |
|
member_type |
String |
Member type of the VPC channel.
Default: ecs |
|
dict_code |
String |
The dictionary code of a VPC channel. The value can contain letters, digits, and special characters (-_). Not supported currently. Minimum: 3 Maximum: 64 |
|
create_time |
String |
Time when the VPC channel is created. |
|
id |
String |
VPC channel ID. |
|
status |
Integer |
VPC channel status.
|
|
member_groups |
Array of MemberGroupInfo objects |
List of backend cloud server groups. |
|
Parameter |
Type |
Description |
|---|---|---|
|
member_group_name |
String |
Name of the backend server group of the VPC channel. |
|
member_group_remark |
String |
Description of the backend server group of the VPC channel. |
|
member_group_weight |
Integer |
Weight of the backend server group of the VPC channel. If servers exist in the current server group and the weight value exists, the weight value is automatically used to assign weights. Minimum: 0 Maximum: 100 |
|
dict_code |
String |
Dictionary code of the backend server group of the VPC channel. The code can contain letters, digits, and special characters (-_). Not supported currently. Minimum: 3 Maximum: 64 |
|
member_group_id |
String |
ID of the backend server group of the VPC channel. |
|
create_time |
String |
Time when the backend server group of the VPC channel was created. |
|
update_time |
String |
Time when the backend server group of the VPC channel was updated. |
Status code: 400
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 401
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 403
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 404
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 500
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Example Requests
None
Example Responses
Status code: 200
OK
{
"total" : 2,
"size" : 2,
"vpc_channels" : [ {
"member_type" : "instance",
"balance_strategy" : 1,
"create_time" : "2020-07-23T07:24:33Z",
"port" : 8080,
"name" : "channel 1",
"id" : "105c6902457144a4820dff8b1ad63331",
"type" : 1,
"status" : 1
}, {
"member_type" : "ip",
"balance_strategy" : 2,
"create_time" : "2020-07-23T07:11:57Z",
"port" : 8088,
"name" : "channel 2",
"id" : "56a7d7358e1b42459c9d730d65b14e59",
"type" : 2,
"status" : 1
} ]
}
Status code: 400
Bad Request
{
"error_code" : "APIG.2011",
"error_msg" : "The request parameters must be specified,parameterName:name. Please refer to the support documentation"
}
Status code: 401
Unauthorized
{
"error_code" : "APIG.1002",
"error_msg" : "Incorrect token or token resolution failed"
}
Status code: 403
Forbidden
{
"error_code" : "APIG.1005",
"error_msg" : "No permissions to request this method"
}
Status code: 404
Not Found
{
"error_code" : "APIG.3030",
"error_msg" : "The instance does not exist;id:f0fa1789-3b76-433b-a787-9892951c620e"
}
Status code: 500
Internal Server Error
{
"error_code" : "APIG.9999",
"error_msg" : "System error"
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
OK |
|
400 |
Bad Request |
|
401 |
Unauthorized |
|
403 |
Forbidden |
|
404 |
Not Found |
|
500 |
Internal Server Error |
Error Codes
See Error Codes.
Last Article: Querying Details of a VPC Channel
Next Article: Adding or Updating Backend Servers
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.