Detaching an EVS Disk from a BMS
Function
This API is used to detach a disk from a BMS.
- A disk attached to /dev/sda functions as the system disk. You can only detach the system disk from a stopped BMS.
- Disks attached to a mount point other than /dev/sda function as data disks and can be detached from a running or stopped BMS.
Stopped and Running indicate that the BMS is running or stopped.
Constraints
If a BMS is stopped, disks can be detached from it without any limitation on the OS. If a BMS is running, the constraints are as follows:
- Before detaching an EVS disk from a Linux BMS, log in to the BMS, run the unmount command to disassociate the disk to be detached from the file system, and ensure that no program is reading data from or writing data to the disk. Otherwise, the disk will fail to be detached.
- Before detaching an EVS disk from a Windows BMS, ensure that no program is reading data from or writing data to the disk. Otherwise, data will be lost.
URI
DELETE /v1/{project_id}/baremetalservers/{server_id}/detachvolume/{attachment_id}
Table 1 lists the parameters.
Parameter |
Mandatory |
Description |
---|---|---|
project_id |
Yes |
Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID. |
server_id |
Yes |
Specifies the BMS ID. You can obtain the BMS ID from the BMS console or using the Querying BMSs (Native OpenStack API) API. |
attachment_id |
Yes |
Specifies the IDs of the EVS disks attached to the BMS. |
Request Message
Response Message
See Task ID Response.
Returned Values
Returned Value |
Description |
---|---|
202 |
The request has been accepted, but the processing has been delayed. |
For details about other returned values, see Status Codes.
Error Codes
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