Create a fixed configuration Redis cluster via Terraform

We recommend creating resources sequentially. If you create all resources at the same time, Terraform will take into account the 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 example, a resource required to create another resource may not be created yet.

Optional: configure providers.
Create a private network and subnet.
Create a cluster.

Configuration files

Example file for configuring providers

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

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

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

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 
  }
}

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"
}

Example file for creating a Redis cluster with a fixed configuration

resource "openstack_networking_network_v2" "network_1" {
  name           = "private-network"
  admin_state_up = "true"
}

resource "openstack_networking_subnet_v2" "subnet_1" {
  network_id = openstack_networking_network_v2.network_1.id
  cidr       = "192.168.199.0/24"
}

data "servercore_dbaas_datastore_type_v1" "datastore_type_1" {
  project_id = servercore_project_v2.project_1.id
  region     = "uz-1"
  filter {
    engine  = "redis"
    version = "6"
  }
}

data "servercore_dbaas_flavor_v1" "flavor_1" {
  project_id = servercore_project_v2.project_1.id
  region     = "uz-1"
  filter {
    datastore_type_id = data.servercore_dbaas_datastore_type_v1.datastore_type_1.datastore_types[0].id
    fl_size           = "standard"
    vcpus             = 2
    ram               = 6144
    disk              = 50
  }
}

  resource "servercore_dbaas_redis_datastore_v1" "datastore_1" {
  name           = "datastore-1"
  project_id     = servercore_project_v2.project_1.id
  region         = "uz-1"
  type_id        = data.servercore_dbaas_datastore_type_v1.datastore_type_1.datastore_types[0].id
  subnet_id      = openstack_networking_subnet_v2.subnet_1.id
  node_count     = 2
  flavor_id      = data.servercore_dbaas_flavor_v1.flavor_1.flavors[0].id
  redis_password = "secret"
}

1. Optional: configure providers

If you configured providers for Servercore and OpenStack, skip this step.

Make sure that in the control panel you have created a service user with the member roles in the Account scope and iam.admin.
Create a directory to store configuration files and a separate file with the .tf extension to configure providers.
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 provider versions. You can check the current version of the OpenStack provider 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 instructions.
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 roles in the Account scope and iam.admin. You can find it in the control panel: in the top menu, click IAM → Service Users (the section is available only to the Account Owner and a user with the iam.admin role);
- password — password of the service user. 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 check the list of available pools in the Product Availability by Location instructions.
Create a project:
```
resource "servercore_project_v2" "project_1" {
  name = "project"
}
```
See the detailed description of the servercore_project_v2 resource.
Create a service user to access the project and assign them the member role in the Project 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 IAM → Projects → in the row of the desired project, click .
See the detailed description of the servercore_iam_serviceuser_v1 resource.

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. You can check the list of available pools in the Product Availability by Location instructions.

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
  ]
}

Open the CLI.
Initialize the Terraform configuration in the directory:
```
terraform init
```
Verify that the configuration files are syntactically correct:
```
terraform validate
```
Format the configuration files:
```
terraform fmt
```
Check which resources will be created:
```
terraform plan
```
Apply the changes and create the resources:
```
terraform apply
```
Confirm the creation — enter yes and press Enter. The created resources will appear in the control panel.
If there are not enough quotas to create resources, increase quotas.

2. Create a private network and subnet

resource "openstack_networking_network_v2" "network_1" {
  name           = "private-network"
  admin_state_up = "true"
}

resource "openstack_networking_subnet_v2" "subnet_1" {
  name       = "private-subnet"
  network_id = openstack_networking_network_v2.network_1.id
  cidr       = "192.168.199.0/24"
}

Here, cidr is the CIDR of the private subnet, for example, 192.168.199.0/24.

See the detailed resource description:

3. Create a fixed configuration cluster

data "servercore_dbaas_datastore_type_v1" "datastore_type_1" {
  project_id = servercore_project_v2.project_1.id
  region     = "uz-1"
  filter {
    engine  = "redis"
    version = "6"
  }
}

data "servercore_dbaas_flavor_v1" "flavor_1" {
  project_id = servercore_project_v2.project_1.id
  region     = "uz-1"
  filter {
    datastore_type_id = data.servercore_dbaas_datastore_type_v1.datastore_type_1.datastore_types[0].id
    fl_size           = "standard"
    vcpus             = 2
    ram               = 6144
    disk              = 50
  }
}

resource "servercore_dbaas_redis_datastore_v1" "datastore_1" {
  name           = "datastore-1"
  project_id     = servercore_project_v2.project_1.id
  region         = "uz-1"
  type_id        = data.servercore_dbaas_datastore_type_v1.datastore_type_1.datastore_types[0].id
  subnet_id      = openstack_networking_subnet_v2.subnet_1.id
  node_count     = 2
  flavor_id      = data.servercore_dbaas_flavor_v1.flavor_1.flavors[0].id
  redis_password = "secret"
}

Where:

region — pool, for example, uz-1. You can find the list of available pools in the Product availability by location instructions;
filter — filter for managed database types:
- engine — managed database type;
- version — managed database version. You can find the list of available versions in the Versions and configurations instructions;
filter — filter for fixed cluster configurations. You can find the list of available configurations in the Versions and configurations instructions;
- fl_size — fixed configuration line. Available values — standard and high_freq;
- vcpus — number of vCPUs;
- ram — amount of RAM in MB;
- disk — disk size in GB;
nodes_count — number of nodes. The maximum number of nodes is 3;
redis_password — database password. Password length is between 32 and 64 characters, including uppercase letters, digits, and special characters.

See a detailed description of data sources and resources: