Configure the environment for working with Terraform

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

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 or Project scope — this role is required to initialize the Servercore provider and create resources. The scope affects available operations; you can view them in the member section of the Roles Reference guide;
• and iam.admin — to create additional users and manage access within projects.

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

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. After creating the user, the password cannot be viewed — you can only change it. The password must be at least 20 characters long and contain 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 for iam.admin by selecting:

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

   5.2. Click Add permission.

   5.3. Configure the permission for member by selecting:

   • scope — Account or Project;
   • role — member.

   5.4. 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 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 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 — 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 uz-1 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 "servercore_project_v2" "project_1" {
     name = "project"
   }

   See the detailed resource description for servercore_project_v2.

6. Create a service user for project access 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 — 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 servercore_iam_serviceuser_v1.

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 upper right corner;
   • region — pool, for example uz-1. 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 = [
       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 the creation: enter yes and press Enter. The created resources will be displayed in the Control panel.

16. If there are not enough quotas to create resources, increase 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 provider versions.

   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 upper right corner;
   • username — name of the service user with the member role in the Account scope and the iam.admin role. You can find it in the control panel: in the top menu, click IAM → the Service Users section (the section is available only 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 in the uz-1 format; do not use pools in the SPB-2 format. The pool for authorization may differ from the pool where you create resources. You can view the list of available pools in the Product availability by location.

5. Create a project:

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

   See the detailed description of the servercore_project_v2 resource.

6. Open the CLI.

7. Initialize the Terraform configuration in the directory:

   terraform init

8. Check that the configuration files are free of errors:

   terraform validate

9. Format the configuration files:

   terraform fmt

10. Check which resources will be created:

    terraform plan

11. Apply the changes and create the resources:

    terraform apply

12. Confirm creation — enter yes and press Enter. The created resources will be displayed in the control panel.

13. If there are insufficient quotas to create the resources, increase the quotas.