Create a network volume using Terraform

Last update: September 07 2026Open in Markdown

We recommend creating resources in order. If you create all resources at once, Terraform will account for dependencies between resources that you specified in the configuration file. If dependencies are not specified, resources will be created in parallel, which may lead to errors. For instance, a resource required for creating another resource might not have been created yet.

1. Optional: configure providers.

2. Create a network volume.

   For all network volume types, except for the Universal v2 type, the amount of IOPS is fixed and depends on the volume type. For Universal v2 network volumes, you can change the total volume IOPS by increasing or decreasing it. You can change the number of IOPS an unlimited number of times. The available number of IOPS for different volume types can be viewed in the Network volume limits.

   You can create a volume:

   • from an image — can be used as a boot volume for a cloud server;
   • or empty — can be used as an additional volume.

Configuration files

Example file for configuring providers

terraform {
  required_providers {
    selectel  = {
      source  = "selectel/selectel"
      version = "~> 6.0"
    }
    openstack = {
      source  = "terraform-provider-openstack/openstack"
      version = "2.1.0"
    }
  }
}

provider "selectel" {
  domain_name = "123456"
  username    = "user"
  password    = "password"
  auth_region = "ru-9"
  auth_url    = "https://cloud.api.selcloud.ru/identity/v3/"
}

resource "selectel_vpc_project_v2" "project_1" {
  name = "project"
}

resource "selectel_iam_serviceuser_v1" "serviceuser_1" {
  name         = "username"
  password     = "password"
  role {
    role_name  = "member"
    scope      = "project"
    project_id = selectel_vpc_project_v2.project_1.id 
  }
}

provider "openstack" {
  auth_url    = "https://cloud.api.selcloud.ru/identity/v3"
  domain_name = "123456"
  tenant_id   = selectel_vpc_project_v2.project_1.id
  user_name   = selectel_iam_serviceuser_v1.serviceuser_1.name
  password    = selectel_iam_serviceuser_v1.serviceuser_1.password
  region      = "ru-9"
}

Example file for creating a network volume from an image

data "openstack_images_image_v2" "image_1" {
  name        = "Ubuntu 20.04 LTS 64-bit"
  most_recent = true
  visibility  = "public"
}

resource "openstack_blockstorage_volume_v3" "volume_1" {
  name                 = "boot-volume-for-server"
  size                 = "5"
  image_id             = data.openstack_images_image_v2.image_1.id
  volume_type          = "fast.ru-9a"
  availability_zone    = "ru-9a"
  enable_online_resize = true

  lifecycle {
    ignore_changes = [image_id]
  }

}

Example file for creating an empty network volume

resource "openstack_blockstorage_volume_v3" "volume_2" {
  name                 = "additional-volume-for-server"
  size                 = "7"
  volume_type          = "universal.ru-9a"
  availability_zone    = "ru-9a"
  enable_online_resize = true
}

1. Optional: configure providers

If you have configured the Selectel and OpenStack providers, skip this step.

1. Make sure you have created a service user in the control panel member with roles in the Account access scope and iam.admin.

2. Create a directory to store configuration files and a separate file with the .tf extension to configure providers.

3. Add the Selectel and OpenStack providers to the file for provider configuration:

   terraform {
     required_providers {
       selectel  = {
         source  = "selectel/selectel"
         version = "~> 7.1.0"
       }
       openstack = {
         source  = "terraform-provider-openstack/openstack"
         version = "2.1.0"
       }
     }
   }

   Here version is the provider version. The current version can be found in the Selectel documentation (in Terraform Registry and GitHub) and OpenStack (in Terraform Registry and GitHub).

   For more information about products, services, and features that can be managed using providers, see the Selectel and OpenStack Providers guide.

4. Initialize the Selectel provider:

   provider "selectel" {
     domain_name = "123456"
     username    = "user"
     password    = "password"
     auth_region = "ru-9"
     auth_url    = "https://cloud.api.selcloud.ru/identity/v3/"
   }

   Where:

   • domain_name — Selectel account number. You can find it in the control panel in the top-right corner;
   • username — the name of the service user with the member role in the Account access scope and iam.admin. You can view it in the control panel: in the top menu, click IAM → Service Users section (this section is only available to the account owner and users with the iam.admin role);
   • password — service user password. You can view it when creating the user or change it to a new one;
   • auth_region — pool for authorization in the ru-9 format; do not use pools in the SPB-2 format. The authorization pool might not match the pool in which you create resources. The list of available pools can be viewed in the guide Product availability by location.

5. Create a project:

   resource "selectel_vpc_project_v2" "project_1" {
     name = "project"
   }

   See the detailed resource description for selectel_vpc_project_v2.

6. Create a service user for project access and assign the member role in the Project access scope:

   resource "selectel_iam_serviceuser_v1" "serviceuser_1" {
     name         = "username"
     password     = "password"
     role {
       role_name  = "member"
       scope      = "project"
       project_id = selectel_vpc_project_v2.project_1.id
     }
   }

   Where:

   • username — user name;

   • password — user password. The password must be at least 20 characters long and include at least:

     • one uppercase and one lowercase Latin letter (A-Z, a-z);
     • one digit (0-9);
     • one special character from the ASCII Printable 7-Bit Special Characters list:
       !"#$%&'()*+,-./:;<=>?@[]^_{|}~;

   • project_id — project ID. You can find it in the Control panel: in the top menu, click IAM → the Projects section → in the line of the required project, click .

   View the detailed description of the resource selectel_iam_serviceuser_v1.

7. Initialize the OpenStack provider:

   provider "openstack" {
     auth_url    = "https://cloud.api.selcloud.ru/identity/v3"
     domain_name = "123456"
     tenant_id   = selectel_vpc_project_v2.project_1.id
     user_name   = selectel_iam_serviceuser_v1.serviceuser_1.name
     password    = selectel_iam_serviceuser_v1.serviceuser_1.password
     region      = "ru-9"
   }

   Where:

   • domain_name — Selectel account number. You can find it in the Control panel in the upper right corner;
   • region — pool, for example ru-9. All resources will be created in this pool. The list of available pools can be viewed in the guide Product availability by location.

8. If you create resources at the same time as configuring providers, add the depends_on argument for OpenStack resources. For example, for the openstack_networking_network_v2 resource:

   resource "openstack_networking_network_v2" "network_1" {
     name           = "private-network"
     admin_state_up = "true"
   
     depends_on = [
       selectel_vpc_project_v2.project_1,
       selectel_iam_serviceuser_v1.serviceuser_1
     ]
   }

9. Optional: if you want to use a mirror, create a separate Terraform CLI configuration file and add the following block to it:

   provider_installation {
     network_mirror {
       url = "https://tf-proxy.selectel.ru/mirror/v1/"
       include = ["registry.terraform.io/*/*"]
     }
     direct {
       exclude = ["registry.terraform.io/*/*"]
     }
   }

   Learn more about mirror settings in the CLI Configuration File HashiCorp documentation.

10. Open the CLI.

11. Initialize the Terraform configuration in the directory:

    terraform init

12. Verify that the configuration files are syntactically correct:

    terraform validate

13. Format the configuration files:

    terraform fmt

14. Check which resources will be created:

    terraform plan

15. Apply the changes and create the resources:

    terraform apply

16. Confirm the creation: enter yes and press Enter. The created resources will be displayed in the Control panel.

17. If there are not enough quotas to create resources, increase quotas.

2. Create a network volume

Network volume with fixed IOPS

For all network volume types, except for the Universal v2 type, the amount of IOPS is fixed and depends on the volume type. The available number of IOPS for different volume types can be viewed in the Network volume limits.

Network volume from an image

1. Get an image.
2. Create a network volume.

1. Get an image

data "openstack_images_image_v2" "image_1" {
  name        = "Ubuntu 20.04 LTS 64-bit"
  most_recent = true
  visibility  = "public"
}

See the detailed description of the openstack_images_image_v2 data source.

2. Create a network volume from an image

resource "openstack_blockstorage_volume_v3" "volume_1" {
  name                 = "boot-volume-for-server"
  size                 = "5"
  image_id             = data.openstack_images_image_v2.image_1.id
  volume_type          = "fast.ru-9a"
  availability_zone    = "ru-9a"
  enable_online_resize = true

  lifecycle {
    ignore_changes = [image_id]
  }

}

Here:

• size — network volume size in GB. Observe the network volume limits for the maximum size;
• volume_type — ID or name of the network volume type. For example, fast.ru-9a — name to create a network volume with the Fast SSD type in the pool segment ru-9a. You can check the list of types in the table List of network volume types in all pool segments;
• availability_zone — pool segment where the network volume will be created, for example, ru-9a. You can check the list of available pool segments in the instructions Product availability by location.

See the detailed resource description in openstack_blockstorage_volume_v3.

Empty network volume

resource "openstack_blockstorage_volume_v3" "volume_2" {
  name                 = "additional-volume-for-server"
  size                 = "7"
  volume_type          = "universal.ru-9a"
  availability_zone    = "ru-9a"
  enable_online_resize = true
}

Where:

• size — network volume size in GB. Observe the network volume limits for the maximum size;
• volume_type — ID or name of the network volume type. For example, universal.ru-9a — name for creating a network volume with the Universal SSD type in the pool segment ru-9a. You can find the list of types in the table List of network volume types in all pool segments;
• availability_zone — pool segment where the network volume will be created, for example, ru-9a. You can view the list of available pool segments in the instructions Product availability by location.

See the detailed resource description openstack_blockstorage_volume_v3.

Network volume with adjustable IOPS

For Universal v2 network volume types you can change the total number of IOPS by decreasing or increasing it. Available values range from 2 000 to 16 000 IOPS. You can change the number of IOPS an unlimited number of times.

Network volume from an image

1. Get an image.
2. Create a network volume.

1. Get an image

data "openstack_images_image_v2" "image_1" {
  name        = "Ubuntu 20.04 LTS 64-bit"
  most_recent = true
  visibility  = "public"
}

See the detailed description of the openstack_images_image_v2 data source.

2. Create a network volume from an image

resource "openstack_blockstorage_volume_v3" "volume_1" {
  name                 = "boot-volume-for-server"
  size                 = "5"
  image_id             = data.openstack_images_image_v2.image_1.id
  volume_type          = "universal2.ru-9a"
  availability_zone    = "ru-9a"
  enable_online_resize = true
  metadata             = {"total_iops_sec": "4500"}

  lifecycle {
    ignore_changes = [image_id]
  }

}

Where:

• size — volume size in GB. Observe the network volume limits for the maximum size;

• volume_type — ID or name of the network volume type. For example, universal2.ru-9a is the name to create a network volume with the Universal SSD v2 type in the pool segment ru-9a. You can view the list of types in the table List of network volume types in all pool segments;

• availability_zone — pool segment where the network volume will be created, for example ru-9a. You can view the list of available pool segments in the instructions Product availability by location;

• metadata — key/value pairs for storing additional volume information:

  • total_iops_sec — total number of read and write operations in IOPS. Available values range from 2 000 to 16 000 IOPS. If no value is specified, the default of 2 000 IOPS will be used.

See the detailed resource description for openstack_blockstorage_volume_v3.

Empty network volume

resource "openstack_blockstorage_volume_v3" "volume_3" {
  name                 = "volume-with-custom-iops"
  size                 = "7"
  volume_type          = "universal2.ru-9a"
  availability_zone    = "ru-9a"
  enable_online_resize = true
  metadata             = {"total_iops_sec": "4500"}
}

Where:

• size — volume size in GB. Observe the network volume limits for the maximum size;

• volume_type — ID or name of the network volume type Universal v2. For example, universal2.ru-9a is the name to create a network volume with the Universal SSD v2 type in the pool segment ru-9a. You can view the list of types in the table List of network volume types in all pool segments;

• availability_zone — pool segment where the network volume will be created, for example ru-9a. You can view the list of available pool segments in the instructions Product availability by location;

• metadata — key/value pairs for storing additional volume information:

  • total_iops_sec — total number of read and write operations in IOPS. Available values range from 2 000 to 16 000 IOPS. If no value is specified, the default of 2 000 IOPS will be used.

See the detailed resource description for openstack_blockstorage_volume_v3.