Deploy Attach Volume
Application Scenario
Bare Metal Server (BMS) volume attachment is an important storage expansion function provided by the BMS service. When you need to expand the storage capacity of a BMS instance, you can increase the instance's storage space by attaching a cloud disk. Automating volume attachment operations through Terraform can ensure standardized and consistent storage resource management, improving operational efficiency. This best practice will introduce how to use Terraform to automatically attach a cloud disk to a BMS instance.
Related Resources/Data Sources
This best practice involves the following main resources:
Resources
Resource/Data Source Dependencies
huaweicloud_bms_volume_attachOperation Steps
1. Script Preparation
Prepare the TF file (e.g., main.tf) in the specified workspace for writing the current best practice script, ensuring that it (or other TF files in the same directory) contains the provider version declaration and Huawei Cloud authentication information required for deploying resources. Refer to the "Preparation Before Deploying Huawei Cloud Resources" document for configuration introduction.
2. Create BMS Instance Volume Attachment Resource
Add the following script to the TF file (e.g., main.tf) to instruct Terraform to create a BMS instance volume attachment resource:
Parameter Description:
server_id: The BMS instance ID, assigned by referencing the input variable server_id
volume_id: The ID of the cloud disk to be attached to the BMS instance, assigned by referencing the input variable volume_id
device: The mount point, such as /dev/sda, /dev/sdb, etc., assigned by referencing the input variable device, default value is null (system automatically assigns)
3. Preset Input Parameters Required for Resource Deployment (Optional)
In this practice, the resource uses input variables to assign configuration content. These input parameters need to be manually entered during subsequent deployment. At the same time, Terraform provides a method to preset these configurations through tfvars files, which can avoid repeated input during each execution.
Create a terraform.tfvars file in the working directory with the following example content:
Usage:
Save the above content as a
terraform.tfvarsfile in the working directory (this filename allows users to automatically import the content of thistfvarsfile when executing terraform commands. For other naming, you need to add.autobefore tfvars, such asvariables.auto.tfvars)Modify parameter values according to actual needs
When executing
terraform planorterraform apply, Terraform will automatically read the variable values in this file
In addition to using the terraform.tfvars file, you can also set variable values in the following ways:
Command line parameters:
terraform apply -var="server_id=your-server-id" -var="volume_id=your-volume-id" -var="device=/dev/sdb"Environment variables:
export TF_VAR_server_id=your-server-idandexport TF_VAR_volume_id=your-volume-idandexport TF_VAR_device=/dev/sdbCustom named variable file:
terraform apply -var-file="custom.tfvars"
Note: If the same variable is set through multiple methods, Terraform will use variable values according to the following priority: command line parameters > variable file > environment variables > default values.
4. Initialize and Apply Terraform Configuration
After completing the above script configuration, execute the following steps to attach a cloud disk to a BMS instance:
Run
terraform initto initialize the environmentRun
terraform planto view the resource creation planAfter confirming that the resource plan is correct, run
terraform applyto start attaching the cloud disk to the BMS instanceRun
terraform showto view the details of the created BMS instance volume attachment resource
Note: Destroying this resource will detach the volume from the BMS instance.
Reference Information
Last updated