Terraform: Quick Start

1. Install Terraform.
2. Create a service user.
3. Configure providers.

All resources created with Terraform are billed according to the service payment model. Resource billing begins after resource creation.

The cost of resources created with Terraform is the same as the cost of resources created via the control panel.

1. Install Terraform

1. Download the Terraform distribution for your operating system from the HashiCorp website. We recommend downloading Terraform version 1.9.
2. Install Terraform. For Linux and macOS, follow the Install Terraform instructions in the HashiCorp documentation.

2. Create a service user

To work with the examples, you need to create a service user with two roles:

• member in the Account access scope — the role is required to initialize the Servercore provider and create resources; ;
• and iam.admin — for creating additional users and restricting access within projects.

1. In the control panel, on the top menu, click IAM.

2. Go to the Service Users section.

3. Click Add service user.

4. In the Service User Details block:

   4.1. Enter the username. It will be used for authorization.

   4.2. Enter a password for the user or generate one. Once the user is created, the password cannot be viewed, only changed. 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:
     !"#$%&'()*+,-./:;<=>?@[]^_{|}~.

5. In the Account Access block:

   5.1. Configure the permission; to do this, select:

   • access scope — Account; ;
   • role — iam.admin.

   5.2. Optional: to assign an additional permission to the user, click Add permission and repeat step 5.1.

   5.3. Optional: select a group for the user.

6. Click Add user. They will be added to the list on the Service users page. The account will be active immediately.

3. Configure providers

Servercore and OpenStack providers

1. Make sure that in the control panel you have created a service user with the member role 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 Servercore and OpenStack providers to the file for provider configuration:

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

   Here version is the provider version. The current version of the OpenStack provider can be found in the Terraform Registry and GitHub.

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

4. Initialize the Servercore provider:

   provider "servercore" {
     domain_name = "123456"
     username    = "user"
     password    = "password"
     auth_region = "uz-1"
     auth_url    = "https://cloud.api.servercore.com/identity/v3/"
   }

   Where:

   • domain_name — Servercore account number. You can find it in the control panel in the top-right corner;
   • username — 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 (the section is only available to the Account Owner and a user 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, for example, uz-1. You can create resources in other pools. A list of available pools can be found in the Availability Matrix guide.

5. Create a project:

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

   See a detailed description of the servercore_project_v2 resource.

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

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

   Where:

   • username — username;

   • 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 Products and select Cloud Servers → open the projects menu → in the row of the target project, click .

   See a detailed description of the servercore_iam_serviceuser_v1 resource.

7. Initialize the OpenStack provider:

   provider "openstack" {
     auth_url    = "https://cloud.api.servercore.com/identity/v3"
     domain_name = "123456"
     tenant_id   = servercore_project_v2.project_1.id
     user_name   = servercore_iam_serviceuser_v1.serviceuser_1.name
     password    = servercore_iam_serviceuser_v1.serviceuser_1.password
     region      = "uz-1"
   }

   Where:

   • domain_name — Servercore account number. You can find it in the control panel in the top-right corner;
   • region — pool, for example, uz-1. All resources will be created in this pool. A list of available pools can be found in the Availability Matrix guide.

8. If you are creating resources while 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 = [
       servercore_project_v2.project_1,
       servercore_iam_serviceuser_v1.serviceuser_1
     ]
   }

9. Open the CLI.

10. Initialize the Terraform configuration in the directory:

    terraform init

11. Verify that the configuration files are syntactically correct:

    terraform validate

12. Format the configuration files:

    terraform fmt

13. Check which resources will be created:

    terraform plan

14. Apply the changes and create the resources:

    terraform apply

15. Confirm creation — enter yes and press Enter. The created resources will appear in the control panel.

16. If quotas were insufficient to create the resources, increase the quotas.

Servercore provider

1. Make sure that in the control panel you have created a service user with the member role 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 Servercore provider to the provider configuration file:

   terraform {
     required_providers {
       servercore  = {
         source  = "terraform.servercore.com/servercore/servercore"
         version = "~> 7.1.0"
       }
     }
   }

   Here version is the provider version.

   Learn more about products, services, and features that can be managed using providers in the Servercore and OpenStack Providers guide.

4. Initialize the Servercore provider:

   provider "servercore" {
     domain_name = "123456"
     username    = "user"
     password    = "password"
     auth_region = "uz-1"
     auth_url    = "https://cloud.api.servercore.com/identity/v3/"
   }

   Where:

   • domain_name — Servercore account number. You can find it in the control panel in the top-right corner;
   • username — username of a service user with the member role in the Account access scope and iam.admin. You can find it in the control panel: in the top menu, click IAM → Service users section (this section is available only to the account owner and to 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, for example uz-1. You can create resources in other pools. The list of available pools can be viewed in the Availability Matrix.

5. Create a project:

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

   See the detailed description of the servercore_project_v2 resource.

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

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

   Where:

   • username — username;

   • 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 list of ASCII Printable 7-Bit Special Characters:
       !"#$%&'()*+,-./:;<=>?@[]^_{|}~;

   • project_id — project ID. You can find it in the control panel: in the top menu, click Products and select Cloud Servers → open the projects menu → in the row of the required project, click .

   See the detailed description of the servercore_iam_serviceuser_v1 resource.

7. Open the CLI.

8. Initialize the Terraform configuration in the directory:

   terraform init

9. Verify that the configuration files contain no errors:

   terraform validate

10. Format the configuration files:

    terraform fmt

11. Check which resources will be created:

    terraform plan

12. Apply the changes and create the resources:

    terraform apply

13. Confirm the creation — type yes and press Enter. Created resources will be displayed in the control panel.

14. If you do not have enough quota to create resources, increase your quotas.