diff --git a/docs/bms/api-ref/ALL_META.TXT.json b/docs/bms/api-ref/ALL_META.TXT.json index 7b91d0c41..4df73732e 100644 --- a/docs/bms/api-ref/ALL_META.TXT.json +++ b/docs/bms/api-ref/ALL_META.TXT.json @@ -1168,7 +1168,7 @@ "code":"64", "des":"This API is used to query BMS flavors.The flavors you obtained using this API are all the flavors in the system. The flavors whose names starting with physical are BMS fl", "doc_type":"api", - "kw":"QueryingBMS Flavors,BMS Flavor Query (OpenStack Nova APIs),API Reference", + "kw":"Querying BMS Flavors,BMS Flavor Query (OpenStack Nova APIs),API Reference", "search_title":"", "metedata":[ { @@ -1177,7 +1177,7 @@ "opensource":"false;true" } ], - "title":"QueryingBMS Flavors", + "title":"Querying BMS Flavors", "githuburl":"" }, { diff --git a/docs/bms/api-ref/CLASS.TXT.json b/docs/bms/api-ref/CLASS.TXT.json index 1dfc12352..616cacfb3 100644 --- a/docs/bms/api-ref/CLASS.TXT.json +++ b/docs/bms/api-ref/CLASS.TXT.json @@ -569,7 +569,7 @@ { "desc":"This API is used to query BMS flavors.The flavors you obtained using this API are all the flavors in the system. The flavors whose names starting with physical are BMS fl", "product_code":"bms", - "title":"QueryingBMS Flavors", + "title":"Querying BMS Flavors", "uri":"en-us_topic_0000002374101029.html", "doc_type":"api", "p_code":"63", diff --git a/docs/bms/api-ref/en-us_topic_0000002340063012.html b/docs/bms/api-ref/en-us_topic_0000002340063012.html index cc97e7f39..6379b01ee 100644 --- a/docs/bms/api-ref/en-us_topic_0000002340063012.html +++ b/docs/bms/api-ref/en-us_topic_0000002340063012.html @@ -66,7 +66,7 @@

String

Specifies the flavor ID.

-

You can obtain the flavor ID from the BMS console or using the QueryingBMS Flavors API.

+

You can obtain the flavor ID from the BMS console or using the Querying BMS Flavors API.

name

diff --git a/docs/bms/api-ref/en-us_topic_0000002340063032.html b/docs/bms/api-ref/en-us_topic_0000002340063032.html index 1e4f34512..6c560bfdb 100644 --- a/docs/bms/api-ref/en-us_topic_0000002340063032.html +++ b/docs/bms/api-ref/en-us_topic_0000002340063032.html @@ -4,7 +4,7 @@

Request Parameters

None

-

Example Request

Deleting tags from a BMS (ID: 53206ed0-56de-4d6b-b7ee-ffc62ca26f43)
- @@ -54,7 +54,7 @@ - @@ -73,7 +73,7 @@ - - @@ -164,7 +164,7 @@ diff --git a/docs/bms/api-ref/en-us_topic_0000002340222816.html b/docs/bms/api-ref/en-us_topic_0000002340222816.html index 5ebff9ac1..a87b7e3f5 100644 --- a/docs/bms/api-ref/en-us_topic_0000002340222816.html +++ b/docs/bms/api-ref/en-us_topic_0000002340222816.html @@ -29,7 +29,7 @@ - diff --git a/docs/bms/api-ref/en-us_topic_0000002374101005.html b/docs/bms/api-ref/en-us_topic_0000002374101005.html index bf49edcfe..e169e3ffc 100644 --- a/docs/bms/api-ref/en-us_topic_0000002374101005.html +++ b/docs/bms/api-ref/en-us_topic_0000002374101005.html @@ -1,7 +1,7 @@

Creating a BMS

-

Function

This API is used to create a BMS.

+

Function

This API is used to create a BMS.

Constraints

  • This API cannot be used to create BMSs in a batch.
  • When you create a BMS using an image that supports Cloud-Init or Cloudbase-Init, only parameter key_name can be configured. (Parameter adminPass is invalid.) The password of a Linux BMS can be injected only using parameter user_data. The password of a Windows BMS can be injected only using metadata admin_pass.
  • When you create a BMS using an image that does not support Cloud-Init or Cloudbase-Init, both parameters adminPass and key_name are invalid. You need to use the password or certificate of the image to log in to the BMS.
  • File injection is not supported.
  • BMS creation from a system volume is not supported.
  • Parameter port in the three network parameters (port, uuid, and fixed_ip) has the highest priority. If parameter fixed_ip is set, you must specify the UUID.
  • After a BMS is created, it is recommended that you add the __type_baremetal tag for it. This tag specifies that the created server is a BMS. Otherwise, the BMS may not be displayed in the BMS list on the management console.
  • A BMS can have a maximum of two VPCs. The first VPC will be used by the primary NIC of the BMS.
diff --git a/docs/bms/api-ref/en-us_topic_0000002374101009.html b/docs/bms/api-ref/en-us_topic_0000002374101009.html index 30e3f457d..5c9ca653d 100644 --- a/docs/bms/api-ref/en-us_topic_0000002374101009.html +++ b/docs/bms/api-ref/en-us_topic_0000002374101009.html @@ -1,6 +1,6 @@ -

Querying Details About BMSs

+

Querying Details About BMSs

Function

This API is used to query details about BMSs.

Constraints

  • The query result returned by this API includes both ECSs and BMSs. You need to filter out the BMSs using the flavor used to create the BMSs or the tags added to the BMSs during BMS creation.
  • If the image is used as the search criteria, other search criteria and pagination criteria are not supported. If both the image and other filter criteria are specified, the image filter criterion is used. If the query criteria do not contain the image filter criterion, API functions are not restricted.
@@ -66,7 +66,7 @@
- diff --git a/docs/bms/api-ref/en-us_topic_0000002374101029.html b/docs/bms/api-ref/en-us_topic_0000002374101029.html index 37dcdde9d..9c5b14295 100644 --- a/docs/bms/api-ref/en-us_topic_0000002374101029.html +++ b/docs/bms/api-ref/en-us_topic_0000002374101029.html @@ -1,6 +1,6 @@ -

QueryingBMS Flavors

+

Querying BMS Flavors

Function

This API is used to query BMS flavors.

Constraints

The flavors you obtained using this API are all the flavors in the system. The flavors whose names starting with physical are BMS flavors and can be used to create BMSs.

diff --git a/docs/bms/api-ref/en-us_topic_0000002374260885.html b/docs/bms/api-ref/en-us_topic_0000002374260885.html index 8d8f18393..bd5be3908 100644 --- a/docs/bms/api-ref/en-us_topic_0000002374260885.html +++ b/docs/bms/api-ref/en-us_topic_0000002374260885.html @@ -136,7 +136,7 @@
diff --git a/docs/bms/api-ref/en-us_topic_0000002374260889.html b/docs/bms/api-ref/en-us_topic_0000002374260889.html index 63e7db011..699555970 100644 --- a/docs/bms/api-ref/en-us_topic_0000002374260889.html +++ b/docs/bms/api-ref/en-us_topic_0000002374260889.html @@ -64,7 +64,7 @@ 
1
DELETE https://{ECS Endpoint}/v2.1/bbf1946d374b44a0a2a95533562ba954/servers/53206ed0-56de-4d6b-b7ee-ffc62ca26f43/tags
+
Example Request
Deleting tags from a BMS (ID: 53206ed0-56de-4d6b-b7ee-ffc62ca26f43)
1
DELETE https://{ECS Endpoint}/v2.1/bbf1946d374b44a0a2a95533562ba954/servers/53206ed0-56de-4d6b-b7ee-ffc62ca26f43/tags
 

 

 

diff --git a/docs/bms/api-ref/en-us_topic_0000002340222784.html b/docs/bms/api-ref/en-us_topic_0000002340222784.html
index 4c1e203ea..6194c6c5c 100644
--- a/docs/bms/api-ref/en-us_topic_0000002340222784.html
+++ b/docs/bms/api-ref/en-us_topic_0000002340222784.html
@@ -1,7 +1,7 @@
 
 
-
Querying Details About a BMS

-
Function
This API is used to query details about a BMS based on the BMS ID.

+
Querying Details About a BMS

+
Function
This API is used to query details about a BMS based on the BMS ID.

 

 
URI
GET /v2.1/{project_id}/servers/{server_id}

 
Table 1 lists the parameters.

@@ -26,7 +26,7 @@

Yes

Specifies the BMS ID.

+

Specifies the BMS ID.

You can obtain the BMS ID from the BMS console or by calling the API Querying BMSs.

Object

Specifies BMS information. For details, see Table 2.

+

Specifies BMS information. For details, see Table 2.

String

Specifies the BMS name.

+

Specifies the BMS name.

id

@@ -126,7 +126,7 @@

String

Specifies the ID of the tenant owning the BMS. The value is in UUID format.

+

Specifies the ID of the tenant owning the BMS. The value is in UUID format.

This parameter specifies the same meaning as project_id.

Map<String,Array of address objects>

Specifies BMS network addresses. Specifies the VPC used by the BMS.

-
  • key: indicates the ID of the VPC used by the BMS.
  • value indicates the VPC details.
+
  • key: indicates the ID of the VPC used by the BMS.
  • value indicates the VPC details.

security_groups

diff --git a/docs/bms/api-ref/en-us_topic_0000002340222808.html b/docs/bms/api-ref/en-us_topic_0000002340222808.html index 0ea629f38..59feb44a9 100644 --- a/docs/bms/api-ref/en-us_topic_0000002340222808.html +++ b/docs/bms/api-ref/en-us_topic_0000002340222808.html @@ -27,7 +27,7 @@

Yes

Specifies the flavor ID.

-

You can obtain the flavor ID from the BMS console or using the QueryingBMS Flavors API.

+

You can obtain the flavor ID from the BMS console or using the Querying BMS Flavors API.

Yes

Specifies the BMS ID.

+

Specifies the BMS ID.

You can obtain the BMS ID from the BMS console or by calling the API Querying BMSs.

String

Specifies the flavor ID.

-

You can obtain the flavor ID from the BMS console or using the QueryingBMS Flavors API.

+

You can obtain the flavor ID from the BMS console or using the Querying BMS Flavors API.

name

@@ -449,7 +449,7 @@

String

Specifies the status of theBMS host.

+

Specifies the status of the host that accommodates the BMS.

  • UP: The host is normal.
  • UNKNOWN: The host status is unknown.
  • DOWN: the host is abnormal.
  • MAINTENANCE: The host is being maintained.
  • Empty string: There is no BMS host information.

This is a new parameter in micro version 2.16.

String

Specifies the key and value pair of the metadata.

-
  • Each key or value contains fewer than 256 characters.
  • The value does not support the following special characters:

    \"

    +
    • Each key or value contains fewer than 256 characters and cannot be left blank.
    • The value does not support the following special characters:

      \"
-
Table 2 address parameter structure description

Parameter

+
diff --git a/docs/bms/api-ref/en-us_topic_0000002374260893.html b/docs/bms/api-ref/en-us_topic_0000002374260893.html index 447730bfe..1e3f7a909 100644 --- a/docs/bms/api-ref/en-us_topic_0000002374260893.html +++ b/docs/bms/api-ref/en-us_topic_0000002374260893.html @@ -1,6 +1,6 @@ -

Querying Details About a BMS Flavor

+

Querying Details About a BMS Flavor

Function

This API is used to query details about a BMS flavor, such as the flavor name, CPU cores, and memory.

URI

GET /v2.1/{project_id}/flavors/{flavor_id}

@@ -27,7 +27,7 @@
diff --git a/docs/bms/api-ref/en-us_topic_0000002374260901.html b/docs/bms/api-ref/en-us_topic_0000002374260901.html index 846262b86..be4527c3b 100644 --- a/docs/bms/api-ref/en-us_topic_0000002374260901.html +++ b/docs/bms/api-ref/en-us_topic_0000002374260901.html @@ -3,7 +3,7 @@

Attaching an EVS Disk to a BMS

Function

This API is used to attach an EVS disk to a BMS.

-

Constraints

  • A bootable disk cannot be attached to a BMS.
  • A disk cannot be attached to a BMS when the BMS is in the PAUSED state, which is specified using the OS-EXT-STS:vm_state parameter.
  • Only a shared disk or a disk in the available state can be attached to a BMS.
  • Only EVS disks whose device type is SCSI can be attached to a BMS.
+

Constraints

  • A bootable disk cannot be attached to a BMS.
  • A disk cannot be attached to a BMS when the BMS is in the PAUSED state, which is specified using the OS-EXT-STS:vm_state parameter.
  • Only a shared disk or a disk in the available state can be attached to a BMS.
  • Only EVS disks whose device type is SCSI can be attached to a BMS.

URI

POST /v2.1/{project_id}/servers/{server_id}/os-volume_attachments

Table 1 lists the parameters.

diff --git a/docs/bms/api-ref/en-us_topic_0106040941.html b/docs/bms/api-ref/en-us_topic_0106040941.html index 1a0ce9fd3..0f3213af4 100644 --- a/docs/bms/api-ref/en-us_topic_0106040941.html +++ b/docs/bms/api-ref/en-us_topic_0106040941.html @@ -104,7 +104,7 @@
- diff --git a/docs/bms/api-ref/en-us_topic_0107541808.html b/docs/bms/api-ref/en-us_topic_0107541808.html index b4e250850..bffd87a40 100644 --- a/docs/bms/api-ref/en-us_topic_0107541808.html +++ b/docs/bms/api-ref/en-us_topic_0107541808.html @@ -4,1250 +4,1250 @@

Context

  • An error code returned by an API does not correspond to one error message. The following table lists only common error messages.
  • Most BMS APIs are asynchronous. Some error codes are displayed in the returned messages for task viewing requests. HTTP status codes may not be accurate.
  • The BMS service is strongly dependent on other services, such as network and storage. When error messages are provided for the BMS-depended services, contact technical support for troubleshooting.

Error Code Description

-
Table 2 address parameter structure description

Parameter

Type

Yes

Specifies the flavor ID.

-

You can obtain the flavor ID from the BMS console or using the QueryingBMS Flavors API.

+

You can obtain the flavor ID from the BMS console or using the Querying BMS Flavors API.

Specifies the BMS name.

Value range:

-
  • The value can contain a maximum of 63 characters consisting of letters (case-insensitive), digits, underscores (_), hyphens (-), and periods (.).
  • If more than one BMS is to be created, suffixes similar to -0000 will be automatically added to the end of the BMS names during the BMS creation. In this case, the BMS name contains 1 to 58 characters.
+
  • The value can contain 1 to 63 characters, consisting of letters, digits, underscores (_), hyphens (-), and periods (.).
  • If more than one BMS is to be created, suffixes similar to -0000 will be automatically added to the end of the BMS names during the BMS creation. In this case, the BMS name contains 1 to 58 characters.

metadata

@@ -166,7 +166,7 @@

String

Specifies the name of a key pair. This is an extended attribute. To log in to a BMS using an SSH key pair, set the value to the name of an existing private key.

+

Specifies the name of a key pair. This is an extended attribute. To log in to a BMS using an SSH key pair, set the value to the name of an existing private key.

You can create a key pair using the Creating or Importing an SSH Key Pair (Native OpenStack API) API, or query existing key pairs using the Querying SSH Key Pairs (Native OpenStack API) API.

Constraints:

  • If both key_name and user_data are specified, user_data only injects user data.
@@ -251,7 +251,7 @@

Specifies data disk details of the BMS. Each data structure represents a data disk to be created. For details, see Table 8.

Constraints:

-

A maximum of 40 EVS disks (including the system disk and data disks) can be attached to a BMS.

+

A maximum of 40 EVS disks (including the system disk and data disks) can be attached to a BMS.

extendparam

@@ -358,7 +358,7 @@

String

Specifies a security group ID, which takes effect for all NICs configured for the BMS.

-
  • If this parameter is not specified, the default security group is bound to the BMS.
  • If this parameter is required (in UUID format), use the ID of an existing security group. For details about how to obtain existing security groups, see "Querying Security Groups" in Virtual Private Cloud API Reference.
+
  • If this parameter is not specified, the default security group is bound to the BMS.
  • If this parameter is required (in UUID format), use the ID of an existing security group. For details about how to obtain existing security groups, see "Querying Security Groups" in Virtual Private Cloud API Reference.

HTTP Status Code

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/bms/api-ref/en-us_topic_0107654006.html b/docs/bms/api-ref/en-us_topic_0107654006.html index dea711ba5..e041d5e51 100644 --- a/docs/bms/api-ref/en-us_topic_0107654006.html +++ b/docs/bms/api-ref/en-us_topic_0107654006.html @@ -666,7 +666,8 @@ -

Status Code

Returned Value

+

Error Code

Description

+

Error Message

Error Message

+

Description

Handling Measure

+

Solution

400

+

400

BMS.0001

+

BMS.0001

Request error.

+

Fail to parse request, reason: %s.

Fail to parse request, reason: %s.

+

Request error.

Check the request body according to the returned error message.

+

Check the request body according to the returned error message.

400

+

400

BMS.0002

+

BMS.0002

BMS has not been launched.

+

The BMS service is unavailable.

The BMS service is unavailable.

+

BMS has not been launched.

Select a region where the BMS service is available.

+

Select a region where the BMS service is available.

400

+

400

BMS.0003

+

BMS.0003

Request error.

+

Create BareMetal Server error, request is null.

Create BareMetal Server error, request is null.

+

Request error.

Check the request body according to the returned error message.

+

Check the request body according to the returned error message.

400

+

400

BMS.0004

+

BMS.0004

Insufficient permission.

+

Role check fail, reason: %s.

Role check fail, reason: %s.

+

Insufficient permission.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0005

+

BMS.0005

Insufficient permission.

+

Role check fail, reason: You do not have permission or your balance is insufficient.

Role check fail, reason: You do not have permission or your balance is insufficient.

+

Insufficient permission.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0008

+

BMS.0008

Failed to query a flavor.

+

Fail to query flavor [%s], reason: %s.

Fail to query flavor [%s], reason: %s.

+

Failed to query a flavor.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0006

+

BMS.0006

Failed to create the task.

+

Fail to operate baremetal server.

Fail to operate baremetal server.

+

Failed to create the task.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0009

+

BMS.0009

Failed to query flavor attributes.

+

Fail to query flavor extra specs[%s], reason: %s.

Fail to query flavor extra specs[%s], reason: %s.

+

Failed to query flavor attributes.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0010

+

BMS.0010

Failed to query an image.

+

Fail to query image [%s], reason: %s.

Fail to query image [%s], reason: %s.

+

Failed to query an image.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0011

+

BMS.0011

The images do not support BMS.

+

The selected images cannot be used to apply for BMSs, %s.

The selected images cannot be used to apply for BMSs, %s.

+

The images do not support BMS.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0012

+

BMS.0012

Insufficient IP addresses in the selected subnet.

+

The number of IP addresses in the selected subnet[%s] is insufficient.

The number of IP addresses in the selected subnet[%s] is insufficient.

+

Insufficient IP addresses in the selected subnet.

Check whether the IP addresses of the subnet are used up.

+

Check whether the IP addresses of the subnet are used up.

400

+

400

BMS.0013

+

BMS.0013

Failed to query the port.

+

Fail to query ports by subnet [%s], reason: %s.

Fail to query ports by subnet [%s], reason: %s.

+

Failed to query the port.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0014

+

BMS.0014

IP address conflict.

+

The specified IP address conflicts with an existing IP address in subnet[%s].

The specified IP address conflicts with an existing IP address in subnet[%s].

+

IP address conflict.

Modify the NIC IP address.

+

Modify the NIC IP address.

400

+

400

BMS.0015

+

BMS.0015

Failed to query the NIC.

+

Fail to query subnet, reason: %s.

Fail to query subnet, reason: %s.

+

Failed to query the NIC.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0017

+

BMS.0017

The EIP quota is insufficient.

+

The number[%d] of EIPs has reached the maximum[%d] allowed. Apply for a higher quota and try again.

The number[%d] of EIPs has reached the maximum[%d] allowed. Apply for a higher quota and try again.

+

The EIP quota is insufficient.

Apply for a higher EIP quota.

+

Apply for a higher EIP quota.

400

+

400

BMS.0218

+

BMS.0218

Failed to create the order.

+

Fail to create order, reason: %s.

Fail to create order, reason: %s.

+

Failed to create the order.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0219

+

BMS.0219

Failed to change the BMS name.

+

OpenStack nova change ServerName fail.

OpenStack nova change ServerName fail.

+

Failed to change the BMS name.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.0018

+

BMS.0018

Invalid request parameters.

+

Request parameter is invalid.

Request parameter is invalid.

+

Invalid request parameters.

Modify the request parameters based on the returned error message.

+

Modify the request parameters based on the returned error message.

400

+

400

BMS.0019

+

BMS.0019

Invalid NIC parameters.

+

publicIp parameter is illegal, reason: %s.

publicIp parameter is illegal, reason: %s.

+

Invalid NIC parameters.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0021

+

BMS.0021

The flavor is invalid for creating the BMS. Select another flavor.

+

Flavor parameter is illegal, reason: %s.

Flavor parameter is illegal, reason: %s.

+

The flavor is invalid for creating the BMS. Select another flavor.

Select a valid flavor.

+

Select a valid flavor.

400

+

400

BMS.0022

+

BMS.0022

Invalid request parameters.

+

Request parameter is invalid.

Request parameter is invalid.

+

Invalid request parameters.

Modify the request parameters based on the returned error message.

+

Modify the request parameters based on the returned error message.

400

+

400

BMS.0023

+

BMS.0023

Failed to query the quota.

+

Fail to query limits, reason: %s

Fail to query limits, reason: %s

+

Failed to query the quota.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0025

+

BMS.0025

The number of BMSs exceeds the quota.

+

The number of cloud servers has reached the maximum allowed.

The number of cloud servers has reached the maximum allowed.

+

The number of BMSs exceeds the quota.

Apply for a higher quota.

+

Apply for a higher quota.

400

+

400

BMS.0026

+

BMS.0026

The number of BMS CPUs exceeds the quota.

+

The number of CPU cores used by all cloud servers has reached the maximum allowed.

The number of CPU cores used by all cloud servers has reached the maximum allowed.

+

The number of BMS CPUs exceeds the quota.

Apply for a higher quota.

+

Apply for a higher quota.

400

+

400

BMS.0027

+

BMS.0027

The BMS memory exceeds the quota.

+

The memory space used by all cloud servers has reached the maximum allowed.

The memory space used by all cloud servers has reached the maximum allowed.

+

The BMS memory exceeds the quota.

Apply for a higher quota.

+

Apply for a higher quota.

400

+

400

BMS.0028

+

BMS.0028

The number of BMSs and that of CPUs exceed the quotas.

+

The number of CPU cores used by all cloud servers and that of cloud servers have reached the maximum allowed.

The number of CPU cores used by all cloud servers and that of cloud servers have reached the maximum allowed.

+

The number of BMSs and that of CPUs exceed the quotas.

Apply for a higher quota.

+

Apply for a higher quota.

400

+

400

BMS.0029

+

BMS.0029

The number of BMSs and the memory exceed the quotas.

+

The memory space used by all cloud servers and the number of cloud servers have reached the maximum allowed.

The memory space used by all cloud servers and the number of cloud servers have reached the maximum allowed.

+

The number of BMSs and the memory exceed the quotas.

Apply for a higher quota.

+

Apply for a higher quota.

400

+

400

BMS.0030

+

BMS.0030

The BMS memory and the number of CPUs exceed the quotas.

+

The memory space and number of CPU cores used by all cloud servers have reached the maximum allowed.

The memory space and number of CPU cores used by all cloud servers have reached the maximum allowed.

+

The BMS memory and the number of CPUs exceed the quotas.

Apply for a higher quota.

+

Apply for a higher quota.

400

+

400

BMS.0031

+

BMS.0031

The number of BMSs, the number of CPUs, and the memory exceed the quotas.

+

The number of cloud servers, the memory space used by all cloud servers, and the number of CPU cores used by all cloud servers have reached the maximum allowed.

The number of cloud servers, the memory space used by all cloud servers, and the number of CPU cores used by all cloud servers have reached the maximum allowed.

+

The number of BMSs, the number of CPUs, and the memory exceed the quotas.

Apply for a higher quota.

+

Apply for a higher quota.

400

+

400

BMS.0032

+

BMS.0032

Contact technical support to apply for a BMS.

+

Token check fail.

Token check fail.

+

Contact technical support to apply for a BMS.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

403

+

403

BMS.0033

+

BMS.0033

You do not have operation rights. Contact technical support.

+

Fail to check roles, reason: %s.

Fail to check roles, reason: %s.

+

You do not have operation rights. Contact technical support.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0034

+

BMS.0034

Currently, BMSs cannot be automatically provisioned.

+

Not support create Bare Metal Server.

Not support create Bare Metal Server.

+

Currently, BMSs cannot be automatically provisioned.

This operation is not supported.

+

This operation is not supported.

400

+

400

BMS.0047

+

BMS.0047

Invalid system disk.

+

Root volume is illegal, reason: %s.

Root volume is illegal, reason: %s.

+

Invalid system disk.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0049

+

BMS.0049

Failed to query key_name.

+

Query keypair fail, reason is: %s.

Query keypair fail, reason is: %s.

+

Failed to query key_name.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0102

+

BMS.0102

This image does not support volume attaching.

+

The image does not support attach volume.

The image does not support attach volume.

+

This image does not support volume attaching.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.0103

+

BMS.0103

The disk does not exist.

+

Attach volume %s fail, volume info is null.

Attach volume %s fail, volume info is null.

+

The disk does not exist.

Check whether the disk information is correct.

+

Check whether the disk information is correct.

400

+

400

BMS.0104

+

BMS.0104

The data volume cannot be attached to the mount point of the system volume.

+

Attach volume %s fail, data volume can not attach in root volume device.

Attach volume %s fail, data volume can not attach in root volume device.

+

The data volume cannot be attached to the mount point of the system volume.

Select another mount point.

+

Select another mount point.

400

+

400

BMS.0105

+

BMS.0105

The mount point is invalid.

+

Attach volume %s fail, device is illegal.

Attach volume %s fail, device is illegal.

+

The mount point is invalid.

Check whether the mount point is valid.

+

Check whether the mount point is valid.

400

+

400

BMS.0106

+

BMS.0106

The AZ of data disks is different from that of the BMS.

+

Attach volume %s fail, volume's az is not equal with server's az.

Attach volume %s fail, volume's az is not equal with server's az.

+

The AZ of data disks is different from that of the BMS.

Ensure that the AZ of data disks is the same as that of the BMS.

+

Ensure that the AZ of data disks is the same as that of the BMS.

400

+

400

BMS.0108

+

BMS.0108

The system disk does not match the BMS.

+

Attach volume %s fail, root volume does not match the VM, do not change image.

Attach volume %s fail, root volume does not match the VM, do not change image.

+

The system disk does not match the BMS.

Attach a matching system disk to the BMS.

+

Attach a matching system disk to the BMS.

400

+

400

BMS.1001

+

BMS.1001

This operation can be performed only when the BMS is in running or stopped.

+

Volume can only be attached when server %s stopped or active.

Volume can only be attached when server %s stopped or active.

+

This operation can be performed only when the BMS is in running or stopped.

Try again later or contact technical support.

+

Try again later or contact technical support.

400

+

400

BMS.1002

+

BMS.1002

The number of data disks that can be attached to the BMS exceeds the quota.

+

Attach volume fail, server %s attachment num over limit.

Attach volume fail, server %s attachment num over limit.

+

The number of data disks that can be attached to the BMS exceeds the quota.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.1003

+

BMS.1003

The disk status is invalid.

+

Attach shareable volume %s fail, volume status is %s, not available or inuse.

Attach shareable volume %s fail, volume status is %s, not available or inuse.

+

The disk status is invalid.

Check whether the disk is in attached or other unavailable status.

+

Check whether the disk is in attached or other unavailable status.

400

+

400

BMS.1004

+

BMS.1004

The number of shared data disks that can be attached to the BMS exceeds the quota.

+

Attach shareable volume %s fail, volume status is %s, not available or inuse.

Attach shareable volume %s fail, volume status is %s, not available or inuse.

+

The number of shared data disks that can be attached to the BMS exceeds the quota.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.1006

+

BMS.1006

The running status of the BMS cannot be obtained.

+

Server %s info is null or its status or its metadata is null.

Server %s info is null or its status or its metadata is null.

+

The running status of the BMS cannot be obtained.

Try again later or contact technical support.

+

Try again later or contact technical support.

400

+

400

BMS.1007

+

BMS.1007

Failed to call the API.

+

Calling interface failed

Calling interface failed

+

Failed to call the API.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.1008

+

BMS.1008

The disk type does not match the BMS.

+

The server[%s] is not HANA server, volume[%s] does not match the server.

The server[%s] is not HANA server, volume[%s] does not match the server.

+

The disk type does not match the BMS.

Check whether the disk type matches the BMS or contact the technical support.

+

Check whether the disk type matches the BMS or contact the technical support.

400

+

400

BMS.1009

+

BMS.1009

The data disk has been attached to the BMS.

+

Attach shareable volume %s fail, volume status is %s, the volume has been attached to the server.

Attach shareable volume %s fail, volume status is %s, the volume has been attached to the server.

+

The data disk has been attached to the BMS.

Select another data disk.

+

Select another data disk.

400

+

400

BMS.1011

+

BMS.1011

The data disk is being attached.

+

Attach shareable volume %s fail, volume status is %s, not available or inuse.

Attach shareable volume %s fail, volume status is %s, not available or inuse.

+

The data disk is being attached.

Do not repeatedly attach the data disk.

+

Do not repeatedly attach the data disk.

400

+

400

BMS.3001

+

BMS.3001

Failed to query the security group or subnet.

+

Query security group failed: %s.

+

or

+

Query vpcId for subnet failed: %s.

Query security group failed: %s.

-

or

-

Query vpcId for subnet failed: %s.

+

Failed to query the security group or subnet.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.3011

+

BMS.3011

System error.

+

Decoded token is null.

Decoded token is null.

+

System error.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.3025

+

BMS.3025

The EVS disk type is incorrect.

+

Not support create shareable data volumes.

Not support create shareable data volumes.

+

The EVS disk type is incorrect.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.3035

+

BMS.3035

No matching disk is found for the BMS.

+

Attach volume fail: the bmsid [%s] in volume metadata is not the same with bmsid [%s] in url.

Attach volume fail: the bmsid [%s] in volume metadata is not the same with bmsid [%s] in url.

+

No matching disk is found for the BMS.

Ensure that the disk matches the BMS or contact technical support.

+

Ensure that the disk matches the BMS or contact technical support.

400

+

400

BMS.3039

+

BMS.3039

Failed to verify password complexity.

+

The password is illegal, reason: %s.

The password is illegal, reason: %s.

+

Failed to verify password complexity.

See the password rules.

+

See the password rules.

400

+

400

BMS.0246

+

BMS.0246

Failed to query the VPC.

+

The vpcId[%s] is invalid or not-existing.

The vpcId[%s] is invalid or not-existing.

+

Failed to query the VPC.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0201

+

BMS.0201

The parameters for creating the BMS are incorrectly configured.

+

Fail to check the baremetal server params, reason: %s.

Fail to check the baremetal server params, reason: %s.

+

The parameters for creating the BMS are incorrectly configured.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0202

+

BMS.0202

The data disk type is invalid.

+

All volumes must be in same type.

All volumes must be in same type.

+

The data disk type is invalid.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0203

+

BMS.0203

Parameter Volume is invalid.

+

Volume is illegal, %s.

Volume is illegal, %s.

+

Parameter Volume is invalid.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0204

+

BMS.0204

The number of data disks exceeds the upper limit.

+

The num of datavolume is illegal, the num is %d, max num allow is %d.

The number of data volumes is illegal. The number is %d, but maximum number allow is %d.

+

The number of data disks exceeds the upper limit.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0205

+

BMS.0205

The BMS quantity is invalid.

+

The number of baremetal servers is out of range for one REquest.

The number of baremetal servers is out of range for one quest.

+

The BMS quantity is invalid.

Change or delete the BMS quantity.

+

Change or delete the BMS quantity.

400

+

400

BMS.0206

+

BMS.0206

The name contains invalid characters.

+

The baremetal server name [%s] is include invalid char.

The baremetal server name [%s] is include invalid char.

+

The name contains invalid characters.

Change the name as prompted.

+

Change the name as prompted.

400

+

400

BMS.0207

+

BMS.0207

No IP address can be specified when BMSs are created in a batch.

+

VPC is illegal, reason: %s.

VPC is illegal, reason: %s.

+

No IP address can be specified when BMSs are created in a batch.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0208

+

BMS.0208

Failed to query the AZ.

+

Fail to get RegionInfo by tenant [%s], reason: %s.

Fail to get RegionInfo by tenant [%s], reason: %s.

+

Failed to query the AZ.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0210

+

BMS.0210

The length of the injected data exceeds the upper limit.

+

The size of userdata [%d] is over quota limits [%d].

The size of userdata [%d] is over quota limits [%d].

+

The length of the injected data exceeds the upper limit.

Modify the injected data.

+

Modify the injected data.

400

+

400

BMS.0211

+

BMS.0211

Invalid key.

+

The image platform is [%s], support publicKey, reason: the publicKey is illegal, null is not allowed.

The image platform is [%s], support publicKey, reason: the publicKey is illegal, null is not allowed.

+

Invalid key.

Select a valid key.

+

Select a valid key.

400

+

400

BMS.0114

+

BMS.0114

The disk to be detached is not in the disk list of the BMS.

+

Volume %s is not in server %s attach volume list.

Volume %s is not in server %s attach volume list.

+

The disk to be detached is not in the disk list of the BMS.

Check whether the disk exists.

+

Check whether the disk exists.

400

+

400

BMS.0212

+

BMS.0212

The system is overloaded.

+

System is overloaded, please try again later.

System is overloaded, please try again later.

+

The system is overloaded.

Try again later.

+

Try again later.

400

+

400

BMS.0213

+

BMS.0213

Insufficient permission.

+

OBTAZ role verify fail: not allowed role.

OBTAZ role verify fail: not allowed role.

+

Insufficient permission.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0214

+

BMS.0214

Failed to query the NIC.

+

Query subnet[%s] failed: response is null.

Query subnet[%s] failed: response is null.

+

Failed to query the NIC.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0215

+

BMS.0215

Failed to create the order.

+

The response of inquiry order info is null or invalid.

The response of inquiry order info is null or invalid.

+

Failed to create the order.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0216

+

BMS.0216

Failed to submit the order.

+

Submit order[%s] failed: %s.

Submit order[%s] failed: %s.

+

Failed to submit the order.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0217

+

BMS.0217

Failed to verify metadata.

+

Create server fail, reason: metaData is illegal.

Create server fail, reason: metaData is illegal.

+

Failed to verify metadata.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0222

+

BMS.0222

The primary NIC cannot be deleted.

+

primary port can not be deleted.

primary port can not be deleted.

+

The primary NIC cannot be deleted.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0223

+

BMS.0223

Currently, only SCSI disks are supported.

+

Only SCSI disks are supported.

Only SCSI disks are supported.

+

Currently, only SCSI disks are supported.

Select the SCSI disk type.

+

Select the SCSI disk type.

400

+

400

BMS.0039

+

BMS.0039

The BMS has been shut down.

+

Server is stopped, not allow to stop.

Server is stopped, not allow to stop.

+

The BMS has been shut down.

Do not stop the BMS again.

+

Do not stop the BMS again.

400

+

400

BMS.0040

+

BMS.0040

The BMS does not exist.

+

The server does not exist.

The server does not exist.

+

The BMS does not exist.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0035

+

BMS.0035

The BMS is being powered on and no other operations are allowed.

+

Server is powering on, not allow to %s.

Server is powering on, not allow to %s.

+

The BMS is being powered on and no other operations are allowed.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0036

+

BMS.0036

The BMS is being powered off and no other operations are allowed.

+

Server is powering off, not allow to %s.

Server is powering off, not allow to %s.

+

The BMS is being powered off and no other operations are allowed.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0038

+

BMS.0038

The BMS is running and cannot be started.

+

Server is running, not allow to start.

Server is running, not allow to start.

+

The BMS is running and cannot be started.

Do not start the BMS again.

+

Do not start the BMS again.

400

+

400

BMS.0037

+

BMS.0037

The BMS is being restarted and no other operations are allowed.

+

Server is rebooting, not allow to %s.

Server is rebooting, not allow to %s.

+

The BMS is being restarted and no other operations are allowed.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

403

+

403

BMS.0288

+

BMS.0288

You do not have permissions to perform this operation.

+

Policy doesn't allow %s to be performed.

Policy doesn't allow %s to be performed.

+

You do not have permissions to perform this operation.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0290

+

BMS.0290

The disk is not a shared disk and cannot be attached to multiple BMSs.

+

Batch attach volume type must be shareable.

Batch attach volume type must be sharable.

+

The disk is not a shared disk and cannot be attached to multiple BMSs.

Select a shared disk.

+

Select a shared disk.

400

+

400

BMS.0071

+

BMS.0071

If an EIP has been specified for creating the BMS, no other EIP can be created for the BMS.

+

Using an existing EIP and creating a new EIP can't be used at the same time.

Using an existing EIP and creating a new EIP can't be used at the same time.

+

If an EIP has been specified for creating the BMS, no other EIP can be created for the BMS.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0072

+

BMS.0072

An EIP cannot be used to create multiple BMSs.

+

An existing EIP cannot be assigned to the ECSs created in batches.

An existing EIP cannot be assigned to the ECSs created in batches.

+

An EIP cannot be used to create multiple BMSs.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0073

+

BMS.0073

The bandwidth parameter is empty.

+

Bandwidth info in EIP is null.

Bandwidth info in eip is null.

+

The bandwidth parameter is empty.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0074

+

BMS.0074

The EIP extension parameter is unavailable.

+

Parameter extendparam or chargingMode is null.

Parameter exetendparam or chargingMode is null.

+

The EIP extension parameter is unavailable.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0075

+

BMS.0075

The bandwidth ID is empty.

+

Bandwidth info in EIP is null.

Bandwidth info in eip is null.

+

The bandwidth ID is empty.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0077

+

BMS.0077

Invalid bandwidth size.

+

PublicIp parameter is illegal, reason: %s.

PublicIp parameter is illegal, reason: %s.

+

Invalid bandwidth size.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0078

+

BMS.0078

EIP quota is insufficient.

+

Shared bandwidth has been bound to %d EIPs, quota is %d.

Shared bandwidth has been bound to %d EIPs, quota is %d.

+

EIP quota is insufficient.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0079

+

BMS.0079

The EIP bandwidth type is unavailable.

+

Specifies the bandwidth of the shared type and the id cannot be empty.

Specifies the bandwidth of the shared type and the id cannot be empty.

+

The EIP bandwidth type is unavailable.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0080

+

BMS.0080

The subnet status is unavailable.

+

Check subnet status failed.

Check subnet status failed.

+

The subnet status is unavailable.

Check whether the subnet exists or whether it is in ACTIVE state.

+

Check whether the subnet exists or whether it is in ACTIVE state.

400

+

400

BMS.0297

+

BMS.0297

The submitted EVS disk order has not been paid. The EVS disk cannot be attached to or detached from the BMS.

+

Fail to attach volume[%s]: volume is locked.

Fail to attach volume[%s]: volume is locked.

+

The submitted EVS disk order has not been paid. The EVS disk cannot be attached to or detached from the BMS.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0054

+

BMS.0054

Failed to verify the capacity.

+

Check capacity fail, the number of capacity is: [%d], and req num is: [%d].

Check capacity fail, the number of capacity is: [%d], and req num is: [%d].

+

Failed to verify the capacity.

The capacity is insufficient. Contact technical support.

+

The capacity is insufficient. Contact technical support.

400

+

400

BMS.0055

+

BMS.0055

Failed to query the quota.

+

Query capacity fail, Flavor id is [%s], reason: [%s].

Query capacity fail, Flavor id is [%s], reason: [%s].

+

Failed to query the quota.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.2005

+

BMS.2005

Failed to query the network.

+

Network could not be found.

Network could not be found.

+

Failed to query the network.

Check the network information or contact technical support.

+

Check the network information or contact technical support.

400

+

400

BMS.3037

+

BMS.3037

Insufficient resources or failed to start the BMS.

+

Insufficient resources or failed to start the BMS.

Insufficient resources or failed to start the BMS.

+

Insufficient resources or failed to start the BMS.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3004

+

BMS.3004

Failed to create the BMS due to an internal system error.

+

Failed to create the BMS due to an internal system error.

Failed to create the BMS due to an internal system error.

+

Failed to create the BMS due to an internal system error.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3005

+

BMS.3005

Failed to create the port.

+

Failed to create the port.

Failed to create the port.

+

Failed to create the port.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3033

+

BMS.3033

Failed to create the system disk.

+

Failed to create the system disk.

Failed to create the system disk.

+

Failed to create the system disk.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3029

+

BMS.3029

Failed to create the system disk. The disk status is abnormal.

+

Failed to create the system disk. The disk status is abnormal.

Failed to create the system disk. The disk status is abnormal.

+

Failed to create the system disk. The disk status is abnormal.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3006

+

BMS.3006

Failed to assign the EIP.

+

Failed to assign the floating IP address.

Failed to assign the floating IP address.

+

Failed to assign the EIP.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3021

+

BMS.3021

Failed to create the data disk.

+

Failed to create the data disk.

Failed to create the data disk.

+

Failed to create the data disk.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3019

+

BMS.3019

Failed to attach the data disk.

+

Failed to attach the data disk.

Failed to attach the data disk.

+

Failed to attach the data disk.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.3038

+

BMS.3038

Failed to assign an EIP.

+

Failed to assign the EIP.

Failed to assign the EIP.

+

Failed to assign an EIP.

Contact technical support.

+

Contact technical support.

400

+

400

BMS.0315

+

BMS.0315

Disks cannot be attached to a BMS using this flavor.

+

Disks cannot be attached to a BMS using this flavor[%s].

Disks cannot be attached to a BMS using this flavor[%s].

+

Disks cannot be attached to a BMS using this flavor.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.0360

+

BMS.0360

The disk has been frozen and cannot be operated for the BMS.

+

This operation cannot be performed because EVS Disk %s is frozen.

This operation cannot be performed because EVS Disk %s is frozen.

+

The disk has been frozen and cannot be operated for the BMS.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.3026

+

BMS.3026

The password does not meet requirements.

+

Password does not meet the requirements of the rule.

Password does not meet the requirements of the rule.

+

The password does not meet requirements.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.3027

+

BMS.3027

Invalid VPC parameters.

+

VPC parameter is illegal.

VPC parameter is illegal.

+

Invalid VPC parameters.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

BMS.3028

+

BMS.3028

Disk quota is abnormal.

+

cinder quota check fail.

cinder quota check fail.

+

Disk quota is abnormal.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

400

+

400

Common.0018

+

Common.0018

tenant_id in the token is different from that in the URL.

+

tenantId in token is not the same with in URL.

tenantId in token is not the same with in URL.

+

tenant_id in the token is different from that in the URL.

Check whether the tenant token is correct.

+

Check whether the tenant token is correct.

400

+

400

BMS.0111

+

BMS.0111

Password or key pair is not specified, or both specified.

+

none or multiple passwords specified, please specify one.

none or multiple passwords specified, please specify one.

+

Password or key pair is not specified, or both specified.

The password and key pair cannot be specified at the same time. Select one of them based on the login mode.

+

The password and key pair cannot be specified at the same time. Select one of them based on the login mode.

400

+

400

BMS.0395

+

BMS.0395

Windows BMSs do not support remote login.

+

The server[%s] is windows system and cannot support remote login.

The server[%s] is windows system and can not support remote login.

+

Windows BMSs do not support remote login.

See the returned error message or contact technical support.

+

See the returned error message or contact technical support.

String

Specifies the IP address assignment mode. This is an extended attribute.

+

Specifies the IP address allocation type. This is an extended attribute.

+
  • fixed: A fixed private IP address is allocated to the BMS.
  • floating: A floating IP address is allocated to the BMS.

OS-EXT-IPS:port_id

diff --git a/docs/bms/api-ref/en-us_topic_0107658564.html b/docs/bms/api-ref/en-us_topic_0107658564.html index c89323b0a..e243197ce 100644 --- a/docs/bms/api-ref/en-us_topic_0107658564.html +++ b/docs/bms/api-ref/en-us_topic_0107658564.html @@ -1,9 +1,9 @@ -

Attaching an EVS Disk to a BMS

-

Function

This API is used to attach EVS disks to a BMS as data disks after the BMS is created if existing data disks are insufficient or cannot meet requirements.

+

Attaching an EVS Disk to a BMS

+

Function

This API is used to attach EVS disks to a BMS as data disks after the BMS is created if existing data disks are insufficient or cannot meet requirements.

-

Constraints

  • EVS disks cannot be attached to a BMS in a batch.
  • A maximum of 40 EVS disks can be attached to a BMS.
  • A bootable disk cannot be attached to a BMS.
  • A disk cannot be attached to a BMS in the PAUSED state, which is specified using the OS-EXT-STS:vm_state parameter.
  • Only a shared disk or a disk in the available state can be attached to a BMS.
  • Only EVS disks whose device type is SCSI can be attached to a BMS.
+

Constraints

  • EVS disks cannot be attached to a BMS in a batch.
  • A maximum of 40 EVS disks can be attached to a BMS.
  • A bootable disk cannot be attached to a BMS.
  • A disk cannot be attached to a BMS in the PAUSED state, which is specified using the OS-EXT-STS:vm_state parameter.
  • Only a shared disk or a disk in the available state can be attached to a BMS.
  • Only EVS disks whose device type is SCSI can be attached to a BMS.

URI

POST /v1/{project_id}/baremetalservers/{server_id}/attachvolume

Table 1 lists the parameters.

diff --git a/docs/bms/api-ref/en-us_topic_0113746488.html b/docs/bms/api-ref/en-us_topic_0113746488.html index 6224d7a87..bf7124ed0 100644 --- a/docs/bms/api-ref/en-us_topic_0113746488.html +++ b/docs/bms/api-ref/en-us_topic_0113746488.html @@ -1,6 +1,6 @@ -

BMS Lifecycle Management

+

BMS Lifecycle Management

    diff --git a/docs/bms/api-ref/en-us_topic_0129082263.html b/docs/bms/api-ref/en-us_topic_0129082263.html index 08ea63d84..1f9be6816 100644 --- a/docs/bms/api-ref/en-us_topic_0129082263.html +++ b/docs/bms/api-ref/en-us_topic_0129082263.html @@ -28,7 +28,7 @@
-
Table 2 Parameters for querying BMS details

Parameter

+
diff --git a/docs/bms/api-ref/en-us_topic_0131326852.html b/docs/bms/api-ref/en-us_topic_0131326852.html index 2358c5c78..8ca344b56 100644 --- a/docs/bms/api-ref/en-us_topic_0131326852.html +++ b/docs/bms/api-ref/en-us_topic_0131326852.html @@ -51,7 +51,7 @@

Request Parameters

None

-

Example Request

Querying BMS flavor details and extended flavor information in the az1 AZ
Table 2 Query parameters

Parameter

Mandatory
-
1
GET https://{BMS Endpoint}/v1/c685484a8cc2416b97260938705deb65/baremetalservers/flavors?availability_zone=az1
+
Example Request
Querying BMS flavor details and extended flavor information in the az1 AZ
1
GET https://{BMS Endpoint}/v1/c685484a8cc2416b97260938705deb65/baremetalservers/flavors?availability_zone=az1
 

 

 

diff --git a/docs/bms/api-ref/en-us_topic_0131356391.html b/docs/bms/api-ref/en-us_topic_0131356391.html
index a6be6872f..96bf7f0bf 100644
--- a/docs/bms/api-ref/en-us_topic_0131356391.html
+++ b/docs/bms/api-ref/en-us_topic_0131356391.html
@@ -1,6 +1,6 @@
 
 
-
Starting BMSs

+
Starting BMSs

 
Function
This API is used to start BMSs of specified IDs. You can start a maximum of 1000 BMSs at a time.

 
 
This is an asynchronous API. Calling the API successfully indicates that the task is delivered successfully. To check whether the task is successful, call the Querying Task Statuses API.

 

diff --git a/docs/bms/api-ref/en-us_topic_0131356393.html b/docs/bms/api-ref/en-us_topic_0131356393.html
index caa727e12..032fc6b37 100644
--- a/docs/bms/api-ref/en-us_topic_0131356393.html
+++ b/docs/bms/api-ref/en-us_topic_0131356393.html
@@ -79,8 +79,9 @@

String

Specifies the BMS stop type.

-
  • SOFT: soft stop (invalid)
  • HARD: hard stop (default)
+

Specifies how BMSs are stopped. The default value is HARD.

+

Value:

+

HARD: forcible stop