Cloud server configurations
When creating a cloud server, you can select the number of vCPUs, RAM, local disk size (optional) and add GPUs. Depending on the tasks for which you need a cloud server, you can choose a specific lineup configuration that is suitable for those tasks.
The process of selecting a configuration depends on the pool.
ru-3b, ru-7a and ru-7b
Other pools
Two types of server configurations are available for all rulers except Shared and Dedicated:
- fixed configurations - configurations of lines with different technical characteristics in which the resource ratio is fixed;
- arbitrary configurations - configurations in which any resource ratio can be specified.
The configurations use different processors depending on the line and pool segment. You can customize the selected configuration. After you create a cloud server, you can change the configuration.
Two types of configurations are available for the server:
- fixed configurations - Several ranges with different specifications in which the resource ratio is fixed;
- arbitrary configurations where any resource ratio can be specified.
The configurations use different processors depending on the line and pool segment. After the server is created, you can change the configuration.
Processors
The linacs differ in the processors available.
Standard
CPU
Memory
GPU
Shared
HighFreq
10G Net
Dedicated
Arbitrary configurations
Processor with DDR4 REG 2450 MHz for cloud servers with dedicated cores.
Processors with DDR4 REG 2133-2633 MHz for configurations without dedicated cores.
Processors with DDR4 REG 2133-2933 MHz.
Processors with DDR4 REG 2133-2933 MHz.
Processors with DDR4 REG 2133-2633 MHz and processors with DDR5 REG 3600-4050 MHz.
Processors with DDR4 REG 2250-2433 MHz.
Processor with DDR5 REG 4050 MHz for cloud servers with dedicated cores.
DDR4 REG 3000 MHz processors and DDR5 REG 3100-3750 MHz processors for configurations without dedicated cores.
* When the cloud server load is 100%, the processor is running with Turbo Boost technology and a maximum frequency of 3.60 GHz. Since the processor is emulated, only the 3.00 GHz frequency will be displayed when testing inside the cloud server.
Processor with DDR4 ECC 3200 MHz.
Processor with DDR5 ECC 3200 MHz.
Processors with DDR4 REG 2133-2933 MHz.
Rulers
To see the availability of configurations in the regions, see the Cloud Servers availability matrix.
You can select the configuration when creating a cloud server in the Control Panel. If you want to create a fixed-configuration cloud server through the OpenStack CLI and Terraform, use the Fixed Configuration Flavor List table in all pools. If fixed configurations are not suitable, create a flavor. Through the OpenStack API, you can create a GPU flavor.
Depending on the lineup, up to 64 vCPUs, 1000 GB RAM and 2 TB of local disk are available in fixed configurations, and up to 232 vCPUs, 900 GB RAM and 2 TB of local disk are available in random configurations.
Standard
Fixed configuration
Arbitrary configuration
Fixed configurations of the cloud server lineup with balanced vCPU:RAM resource allocation. Suitable for most tasks, such as running code for web services and applications, hosting online stores, and creating test environments.
A local or network boot disk is available in the Standard line.
The lineup includes cloud server configurations with dedicated cores in pool segments ru-3b, ru-7a and ru-7b. Cloud servers with dedicated cores are available from 2 to 32 vCPUs, from 4 GB to 256 GB RAM, from 32 GB to 1 TB of local disk.
For basic cloud servers, 1 to 32 vCPUs, 1 GB to 128 GB RAM, 16 GB to 1.25 TB local disk are available.
Arbitrary line configuration can be configured in pool segments ru-3b, ru-7a and ru-7b.
In arbitrary configurations, you can select any resource ratio within the available values. The available values depend on the pool segment and the utilization of the allocated cores.
Available resource values for building cloud servers with dedicated cores.
Available resource values for building cloud servers without dedicated cores.
If the configuration has more than 8 vCPUs, the vCPU:RAM ratio must be at least 1:2 and the vCPU:Local Disk ratio must be 1:32. For example, 10 vCPUs requires at least 20 GB of RAM and a disk size of at least 320 GB.
If arbitrary configurations are not suitable, you can order your own configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM - at least 1:2;
- vCPU:RAM:Local disk - at least 1:2:16.
In private pool segments, the limits on arbitrary configurations depend on the pool parameters and the agreed upon number of resources when the service is ordered.
CPU
A line of fixed configurations in which vCPU:RAM resources are balanced in a 1:2 ratio.
Suitable for video transcoding, machine learning, data processing, building CI/CD systems and other tasks that require performance and compute speed on vCPUs.
Available from 4 to 24 vCPUs, 8 GB to 48 GB RAM, 128 GB to 512 GB local disk.
Memory
A line of fixed configurations in which vCPU:RAM resources are balanced at a 1:8 ratio.
The configurations provide high performance for workloads handling large data packages to accommodate demanding databases or SAP and 1C enterprise applications.
Available from 2 to 16 vCPUs, 16 GB to 128 GB RAM, 64 GB to 512 GB local disk.
GPU
Fixed configuration
Arbitrary configuration
Fixed cloud server configurations with dedicated GPUs.
Optimized for GPU computing, such as video transcoding, training neural networks, or creating remote workstations.
Available from 4 to 48 vCPUs, 1 to 8 GPUs, 16 GB to 450 GB RAM.
Local or network boot disks are available across the GPU lineup. Only NVIDIA® A100 40Gb, NVIDIA® A100 80Gb, NVIDIA® A30, or NVIDIA® RTX 6000 Ada in the ru-7a and ru-7b pool segment and NVIDIA® A5000 in the uz-2a and kz-1a pool segments can be used for cloud servers with a local disk.
Learn more about dedicated GPUs in the Graphics Processing Units (GPUs) instruction.
Arbitrary line configuration can be configured in pool segments ru-3b, ru-7a and ru-7b.
In arbitrary configurations, you can select any resource ratio within the available values. The available values depend on the pool segment.
If the configuration has more than 8 vCPUs, the vCPU:RAM ratio must be at least 1:2 and the vCPU:Local Disk ratio must be 1:32. For example, 10 vCPUs requires at least 20 GB of RAM and a disk size of at least 320 GB.
If arbitrary configurations are not suitable, you can order your own configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM - at least 1:2;
- vCPU:RAM:Local disk - at least 1:2:16.
In private pool segments, the limits on arbitrary configurations depend on the pool parameters and the agreed upon number of resources when the service is ordered.
Shared
Fixed cloud server configurations with the ability to use and pay for only a portion of the vCPU.
Shared lineup configurations are less expensive than other lineups and are suitable for tasks that do not require constant and full utilization of the virtual core, such as running staging, a website, bringing up a network, or training.
In the Shared line, a single virtual core can be used by multiple clients. When creating such a configuration, you need to specify the share of vCPU that will be reserved for your server: 10%, 20% or 50%. Cloud server performance will never go below this percentage and may temporarily go up to 100% if other clients are not maximizing resources or a portion of the virtual core is not leased.
Only network boot disks are available in the Shared lineup.
Available from 1 to 4 vCPUs, 512 MB to 8 GB RAM.
Arbitrary configurations in pool segments ru-3b, ru-7a and ru-7b are not available.
HighFreq
Fixed configuration
Arbitrary configuration
Fixed configurations of high-performance cloud servers with CPU speeds up to 3.6 GHz and memory speeds up to 3,200 MHz. Suitable for databases such as 1C Bitrix, game servers and other tasks requiring high processing and response speeds.
Local or network boot disks are available in the HighFreq line.
Fixed configurations are available in the lineup to support the operation of cloud servers with dedicated cores in the ru-3b, ru-7a and ru-7b pool segments. Cloud servers with dedicated cores are available from 2 to 64 vCPUs, from 4 GB to 256 GB RAM, from 30 GB to 1 TB of local disk.
For basic cloud servers, 1 to 64 vCPUs, 2 GB to 256 GB RAM, 30 GB to 1.5 TB local disk are available.
Arbitrary line configuration can be configured in pool segments ru-3b, ru-7a and ru-7b.
In arbitrary configurations, you can select any resource ratio within the available values. The available values depend on the pool segment and the utilization of the allocated cores.
Available resource values for building cloud servers with dedicated cores.
Available resource values for building cloud servers without dedicated cores.
If the configuration has more than 8 vCPUs, the vCPU:RAM ratio must be at least 1:2 and the vCPU:Local Disk ratio must be 1:32. For example, 10 vCPUs requires at least 20 GB of RAM and a disk size of at least 320 GB.
If arbitrary configurations are not suitable, you can order your own configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM - at least 1:2;
- vCPU:RAM:Local disk - at least 1:2:16.
In private pool segments, the limits on arbitrary configurations depend on the pool parameters and the agreed upon number of resources when the service is ordered.
10G Net
Fixed configuration
Arbitrary configuration
Fixed line configurations with support for fast 10 Gbps networks in pool segments ru-3b, ru-7a and ru-7b. Line configurations are available only with support for cloud servers with dedicated cores.
Suitable for high-load web applications, network services, game servers, and other applications that require high network bandwidth while transferring large amounts of data.
16 vCPUs, 32 GB to 128 GB RAM, 256 GB to 2 TB of local disk are available.
Arbitrary line configuration can be configured in the pool segments ru-3b, ru-7a and ru-7bIn arbitrary configurations, any resource ratio can be selected within the available values.
The lineup configurations are only available with support for running cloud servers with dedicated cores.
If the configuration has more than 8 vCPUs, the vCPU:RAM ratio must be at least 1:2 and the vCPU:Local Disk ratio must be 1:32. For example, 10 vCPUs requires at least 20 GB of RAM and a disk size of at least 320 GB.
If arbitrary configurations are not suitable, you can order your own configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM - at least 1:2;
- vCPU:RAM:Local disk - at least 1:2:16.
In private pool segments, the limits on arbitrary configurations depend on the pool parameters and the agreed upon number of resources when the service is ordered.
Dedicated
Fixed line configurations with support for cloud server operation on a dedicated host in the ru-3b pool segment. Line configurations are available only with support for cloud servers with dedicated cores.
Suitable for software that is tied to physical hardware, applications and services with computational load isolation requirements, and loaded services.
Available with 14 vCPUs, 64GB or 86GB RAM.
Arbitrary configurations in pool segments ru-3b, ru-7a and ru-7b are not available.
Arbitrary configurations
To see the availability of arbitrary configurations in regions, see the Cloud Servers availability matrix.
You can select an arbitrary configuration when you create a cloud server in the control panel. If you are creating a cloud server through the OpenStack CLI and Terraform and fixed configurations are not suitable, create a flavor. Flavors determine the number of vCPUs, RAM, and local disk size (optional) of the server. Through the OpenStack API, you can create a GPU flavor.
Values of arbitrary configurations
In arbitrary configurations, you can select any resource ratio and add GPUs. The available values depend on the pool segment.
* If there are more than 8 vCPUs in a configuration, the vCPU:RAM ratio must be at least 1:2. For example, 10 vCPUs require at least 20 GB of RAM.
** If the configuration has more than 8 vCPUs, the vCPU:Local Disk ratio must be at least 1:32. For example, 10 vCPUs require a disk size of at least 320 GB.
If arbitrary configurations are not suitable, you can order your own configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM - at least 1:2;
- vCPU:RAM:Local disk - at least 1:2:16.
In private pool segments, the limits on arbitrary configurations depend on the pool parameters and the agreed upon number of resources when the service is ordered.
List of cloud server lineup flavors
Flavors correspond to cloud server configurations and define the number of vCPUs, RAM, and local disk size (optional) of the server.
Flavor IDs or names are used to create cloud servers through the OpenStack CLI and Terraform. The IDs differ between pools.
For example, 1015 is the ID and SL1.4-16384 is the name of the flavor, which corresponds to a fixed Standard line configuration with 4 vCPUs, 16GB RAM in a ru-9 pool.
If a fixed lineup configuration flavor with the right number of vCPUs, RAM, and local disk size is not available, you can create a flavor.
You can view a list of fixed-configuration flavors in all pools in the table or view a list of all configuration flavors in a specific pool through the OpenStack CLI.
List of fixed-configuration flavorings in all pools
St. Petersburg
Moscow
Novosibirsk
Tashkent
Almaty
Nairobi
ru-3
ru-1
ru-9
gis-2
ru-2
ru-7
gis-1
ru-8
uz-1
uz-2
kz-1
ke-1
Here:
Ruler- The name of a fixed configuration ruler;ID- The flavor ID of the cloud server;Name- The name of the flavor that corresponds to the fixed configuration of the ruler;vCPU- number of vCPUs;RAM, MB- RAM size in MB;Local disk size, GB- local disk size in GB.
View a list of the flavor list of all lineup configurations in a particular pool
Through the OpenStack CLI, you can see a list of flavors that match fixed configurations and flavors that you have created.
-
Check out the list of flavors:
openstack flavor listExample answer for pool ru-9 (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 |
| 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- The name of the flavor that corresponds to the configuration:m1.XX- OpenStack base configurations;SLX.XX- fixed configurations of the Standard line;GLX.XX.- fixed configurations of the GPU lineup;PRC10.XX- Shared line fixed configurations with vCPU share of 10%;PRC20.XX- Shared line fixed configurations with vCPU share of 20%;PRC50.XX- Shared line fixed configurations with vCPU share of 50%;HFLX.XX- fixed configurations of the HighFreq range;
RAM- RAM size in MB;Disk- is the size of the local disk in GB;vCPUs- number of vCPUs;Is Public- flavor scope:True- Public flavors,False- private flavors.