Skip to main content
Cloud Server configurations
Last update:

Cloud Server configurations

When creating a cloud server, you can select the number of vCPUs, RAM, local disk size (optional) and add GPUs.

There are two types of configurations available:

After creating a cloud server, you can change the configuration.

Processors

The available processors differ in fixed and custom configurations.

Processors with DDR4 REG 2133-2933 MHz.

St. PetersburgMoscowNovosibirskTashkentAlmatyNairobi
Intel® Xeon® Processor E5-2670 v3 @ 2.30 GHzru-1aru-2a
Intel® Xeon® Processor E5-2680 v4 @ 2.40 GHzru-1b
ru-1c
Intel® Xeon® Processor E5-2699 v4 @ 2.20 GHzru-1b
Intel® Xeon® Gold 5218 @ 2.30 GHzru-1c
Intel® Xeon® Gold 6140 @ 2.30 GHzru-3a
ru-1a
ru-1b
ru-1c
ru-2b
Intel® Xeon® Gold 6240 @ 2.60 GHzru-9Aru-7aru-8akz-1ake-1a
Intel® Xeon® Gold 6240R @ 2.40 GHzru-3b
ru-9a
ru-2cuz-1akz-1ake-1a
Intel® Xeon® Gold 6336Y @ 2.40 GHzru-3b
ru-9a
ru-2c
ru-7a
gis-1a
AMD EPYC™ 7742 @ 2.25 GHzru-7auz-1a
AMD EPYC™ 7763 @ 2.45 GHzru-3b
ru-9a
ru-2c
ru-7a
ru-7b

Fixed configurations

You can view the availability of configurations in regions in the availability matrix Cloud servers.

You can select a fixed configuration when creating a cloud server in the control panel. If you are creating a cloud server via the OpenStack CLI and Terraform, use the table List of flavors of fixed configuration in all pools.

Standard Line

A line of fixed cloud server configurations with a balanced distribution of vCPU:RAM resources in a ratio of 1:4 (except for entry-level and maximum configuration configurations).

It is suitable for solving most tasks, for example, executing code for web services and applications, hosting online stores, and creating test environments.

Available from 1 to 36 vCPUs, from 1 GB to 128 GB RAM, from 8 GB to 1.25 TB local disk.

CPU Line

A range of fixed configurations in which vCPU:RAM resources are balanced in a 1:2 ratio.

They are suitable for video transcoding, machine learning, data processing, building CI/CD systems and other tasks that require performance and computing speed on a vCPU.

Available from 4 to 24 vCPUs, from 8 GB to 48 GB RAM, from 128 GB to 512 GB local disk.

Memory Line

A range of fixed configurations in which vCPU:RAM resources are balanced in a ratio of 1:8.

Configurations provide high performance under workloads associated with processing large data packages to accommodate demanding databases or SAP and 1C enterprise applications.

Available from 2 to 16 vCPUs, from 16 GB to 128 GB RAM, from 64 GB to 512 GB local disk.

GPU Line

Fixed configurations of cloud servers with dedicated GPUs.

Optimized for GPU computing, such as video transcoding, neural network training, or remote workstation creation.

They are used only with a network boot disk.

Available from 4 to 32 vCPUs, from 1 to 4 GPUs, from 32 GB to 320 GB RAM.

For more information, see the instructions Create a cloud server with GPU.

Shared Line

Fixed configurations of cloud servers with the ability to use and pay for only part of the vCPU.

Shared Line configurations are cheaper than other lines and are suitable for tasks that do not require constant and full loading of the virtual core, such as launching a staging, a website, raising a network or training.

In Shared Line, one virtual core can be used by several clients at once. When creating such a configuration, you need to specify the vCPU share that is reserved for your server: 10%, 20% or 50%. The performance of a cloud server will never fall below the specified percentage and may temporarily reach 100% if other clients do not use resources to the maximum or part of the virtual core is not rented.

They are used only with a network boot disk.

Available from 1 to 4 vCPUs, 512 MB to 8 GB RAM.

HighFreq Line

Fixed configurations of high—performance cloud servers with processor frequency up to 3.6 GHz, memory — 3,200 MHz.

They are suitable for databases, such as 1C Bitrix, game servers and other tasks that require high processing speed and response.

They are used only with a local boot disk — this helps to avoid network delays.

Available from 1 to 8 vCPUs, from 2 GB to 64 GB of RAM, from 30 GB to 960 GB of local disk.

SGX Line

Fixed configurations of cloud servers that support SGX technology. The technology allows the application to create protected areas in RAM.

They are suitable for storing and processing confidential data, including personal and payment information.

Available from 1 to 24 vCPUs, from 4 GB to 96 GB RAM, from 2 GB to 64 GB EPC, from 32 GB to 1 TB local disk.

For more information, see the instructions Create an SGX cloud server.

Custom configurations

You can view the availability of configurations in regions in the availability matrix Cloud servers.

Any configuration can be selected when creating a cloud server in the control panel. If you are creating a cloud server via the OpenStack CLI and Terraform and fixed configurations are not suitable, create flavor. Flavors determine the number of vCPUs, RAM and the size of the local disk (optional) of the server.

Custom configuration values

In custom configurations, you can select any resource ratio and add GPUs. The available values depend on the pool segment.

In the pool segments
ru-1a, ru-1b, ru-1c,
ru-2a, ru-2b,
ru-2c,
gis-1a,
uz-1a,
kz-1a,
ke-1a
In the pool segments
ru-3a, ru-3b,
ru-9a,
ru-7a, ru-7b,
ru-8a
Number of vCPUs1-81—32
RAM512 MB — 64 GB512 MB — 256 GB*
Local disk size5 GB — 512 GB5 GB — 1.23 TB**
GPU1—81—8

* If there are more than 8 vCPUs in the configuration, the vCPU:RAM ratio must be at least 1:2. For example, 10 vCPUs need at least 20 GB of RAM.

** If there are more than 8 vCPUs in the configuration, the vCPU ratio:The local disk must be at least 1:32. For example, for 10 vCPUs, you need a disk of at least 320 GB in size.

If custom configurations are not suitable, you can order a custom configuration. Create a ticket and specify the resource ratio:

  • vCPU:RAM — at least 1:2;
  • vCPU:RAM:The local disk is at least 1:2:16.

Create a flavor

To create cloud servers through the OpenStack CLI and Terraform, flavors are used that determine the number of vCPUs, RAM and the size of the local disk (optional) of the server. You can create a flavor that will match any configuration. Using the OpenStack API, you can create a flavor with a GPU.

Flavor will be available only for one project and pool for which you have configured authorization in the OpenStack API.

  1. Open the OpenStack CLI.

  2. Create a flavor:

    openstack flavor create \
    --private \
    --vcpus <vcpu> \
    --ram <ram_size> \
    --disk <disk_size> \
    <flavor_name>

    Specify:

    • <vcpu> — the number of vCPUs;
    • <ram_size> — the size of RAM in MB;
    • optional: <disk_size> — the size of the local disk in GB;
    • <flavor_name> is the name of the flavor. It must be unique and not match the names of previously deleted flavors. The list of existing flavors can be viewed using the openstack flavor list

    Example of creating a flavor with 1 vCPU, 1 GB RAM, 5 GB local disk size:

    openstack flavor create --private --vcpus 1 --ram 1024 --disk 5 new_flavor

List of flavors of the cloud server

The flavors correspond to the configurations of the cloud server and determine the number of vCPUs, RAM and the size of the local disk (optional) of the server.

To create cloud servers via the OpenStack CLI and Terraform, flavor IDs or names are used. The IDs differ in pools.

note

For example, 4011 is the ID, and RAM1.2-16384 is the name of the flavor, which corresponds to the fixed configuration of the Memory Line with 2 vCPUs, 16 GB RAM in the ru-9 pool.

You can view a list of flavors of a fixed configuration in all pools in the table or view a list of flavors of all configurations in a specific pool via the OpenStack CLI.

List of flavors of fixed configuration in all pools

IDNameNumber of vCPUsRAM, MBLocal disk size, GB
1m1.tiny15120
1000BL1.1-51215120
1001BL1.1-1024110240
1002BL1.1-2048120480
1003BL1.2-4096240960
1004BL1.2-8192281920
1005BL1.4-163844163840
1006BL1.6-327686327680
1007BL1.8-491528491520
1008BL1.10-6553610655360
1011SL1.1-1024110240
1012SL1.1-2048120480
1013SL1.2-4096240960
1014SL1.2-8192281920
1015SL1.4-163844163840
1016SL1.6-327686327680
1017SL1.8-327688327680
1018SL1.12-4915212491520
1019SL1.16-6553616655360
1020SL1.24-9830424983040
11011SGX1.1-4096-0-2034EPC140960
11012SGX1.2-8192-0-4071EPC281920
11013SGX1.4-16384-0-8143EPC4163840
11014SGX1.8-32768-0-16286EPC8327680
11015SGX1.16-65536-0-32572EPC16655360
11016SGX1.24-98304-0-65144EPC24983040
11311SGX1.1-4096-32-2034EPC1409632
11312SGX1.2-8192-64-4071EPC2819264
11313SGX1.4-16384-128-8143EPC416384128
11314SGX1.8-32768-256-16286EPC832768256
11315SGX1.16-65536-512-32572EPC1665536512
11316SGX1.24-98304-1024-65144EPC24983041024
1300BL1.1-512-515125
1301BL1.1-1024-8110248
1302BL1.1-2048-161204816
1303BL1.2-4096-322409632
1304BL1.2-8192-642819264
1305BL1.4-16384-128416384128
1306BL1.6-32768-256632768256
1307BL1.8-49152-384849152384
1308BL1.10-65536-5121065536512
1311SL1.1-1024-8110248
1312SL1.1-2048-161204816
1313SL1.2-4096-322409632
1314SL1.2-8192-642819264
1315SL1.4-16384-128416384128
1316SL1.6-32768-256632768256
1317SL1.8-32768-384832768384
1318SL1.12-49152-5121249152512
1319SL1.16-65536-7681665536768
1320SL1.24-98304-102424983041024
1321SL1.36-131072-1280361310721280
2m1.small120480
2000PL2.12-9830412983040
2001PL2.14-131072141310720
2002PL2.16-163840161638400
2003PL2.20-196608201966080
2004PL2.24-229376242293760
2010PL2.32-327680323276800
2011CPU1.4-8192481920
2012CPU1.8-163848163840
2013CPU1.16-3276816327680
2014CPU1.24-4915224491520
2015CPU1.12-2457612245760
2300PL2.12-98304-7681298304768
2301PL2.14-131072-1024141310721024
2302PL2.16-163840-1280161638401280
2303PL2.20-196608-1536201966081536
2304PL2.24-229376-1952242293761952
2311CPU1.4-8192-12848192128
2312CPU1.8-16384-192816384192
2313CPU1.16-32768-3841632768384
2314CPU1.24-49152-5122449152512
2315CPU1.12-24576-2561224576256
3m1.medium240960
3021GL2.8-24576-0-1GPU8245760
3022GL2.14-49152-0-2GPU14491520
3023GL2.28-98304-0-4GPU28983040
4m1.large481920
4011RAM1.2-163842163840
4012RAM1.4-327684327680
4013RAM1.8-655368655360
4014RAM1.16-131072161310720
4311RAM1.2-16384-6421638464
4312RAM1.4-32768-128432768128
4313RAM1.8-65536-256865536256
4314RAM1.16-131072-51216131072512
5m1.xlarge8163840
9011PRC10.1-51215120
9012PRC10.1-1024110240
9013PRC10.2-2048220480
9014PRC10.2-4096240960
9015PRC10.4-8192481920
9021PRC20.1-51215120
9022PRC20.1-1024110240
9023PRC20.2-2048220480
9024PRC20.2-4096240960
9025PRC20.4-8192481920
9051PRC50.1-51215120
9052PRC50.1-1024110240
9053PRC50.2-2048220480
9054PRC50.2-4096240960
9055PRC50.4-8192481920

Here:

  • ID — The flavor ID of the cloud server;
  • Name — the name of the flavor, which corresponds to the fixed configuration line:
  • `m1.XX' — basic OpenStack configurations;
    • `SL1.XX' — fixed configurations of the Standard Line;
    • CPU1.XX — fixed configurations of the CPU Line;
    • RAM1.XX — fixed configurations of the Memory Line;
    • GL2.XX — fixed configurations of the GPU Line;
    • PRC10.XX — fixed configurations of the Shared Line with a vCPU share of 10%;
    • PRC20.XX — fixed configurations of the Shared Line with a vCPU share of 20%;
    • PRC50.XX — fixed configurations of the Shared Line with a vCPU share of 50%;
    • HFL1.XX — fixed configurations of the HighFreq Line;
    • SGX1.XX — fixed configurations of the SGX Line;
  • vCPU — the number of vCPUs;
  • RAM, MB — the size of RAM in MB;
  • Local disk size, GB — the size of the local disk in GB.

View a list of flavors of all configurations in a specific pool

Through the OpenStack CLI, you can view a list of flavors that correspond to fixed configurations and flavors that you have created.

  1. Open the OpenStack CLI.

  2. Look at the list of flavors:

    openstack flavor list

    Sample response for the ru-9 pool (abbreviated):

    +------------+-----------------------+--------+------+-----------+-------+-----------+
    | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public |
    +------------+-----------------------+--------+------+-----------+-------+-----------+
    | 1 | m1.tiny | 512 | 0 | 0 | 1 | True |
    | 1011 | SL1.1-1024 | 1024 | 0 | 0 | 1 | True |
    | 2011 | CPU1.4-8192 | 8192 | 0 | 0 | 4 | True |
    | 4011 | RAM1.2-16384 | 16384 | 0 | 0 | 2 | True |
    | 3021 | GL2.6-24576-0-1GPU | 24576 | 0 | 0 | 6 | True |
    | 9011 | PRC10.1-512 | 512 | 0 | 0 | 1 | True |
    | 9021 | PRC20.1-512 | 512 | 0 | 0 | 1 | True |
    | 9051 | PRC50.1-512 | 512 | 0 | 0 | 1 | True |
    | 8301 | HFL1.1-2048-30 | 2048 | 30 | 0 | 1 | True |
    +------------+-----------------------+--------+------+-----------+-------+-----------+

    Here:

    • ID — The flavor ID of the cloud server;
    • Name — flavor name that corresponds to the configuration:
  • m1.XX — basic OpenStack configurations;
    • `SL1.XX' — fixed configurations of the Standard Line;
    • CPU1.XX — fixed configurations of the CPU Line;
    • RAM1.XX — fixed configurations of the Memory Line;
    • GL2.XX — fixed configurations of the GPU Line;
    • PRC10.XX — fixed configurations of the Shared Line with a vCPU share of 10%;
    • PRC20.XX — fixed configurations of the Shared Line with a vCPU share of 20%;
    • PRC50.XX — fixed configurations of the Shared Line with a vCPU share of 50%;
    • HFL1.XX — fixed configurations of the HighFreq Line;
    • RAM — the size of RAM in MB;
    • Disk — the size of the local disk in GB;
  • `vCPUs' — the number of vCPUs;
    • Is Public — flavor scope: True — public flavors, False — private flavors.