Cloud server configurations
When creating a cloud server, you can select the required number of virtual CPU cores (vCPU), memory (RAM) and local disk size (optional).
Two types of configurations are available:
- fixed-configurations — several lineups that differ in resource ratio and specifications;
- arbitrary configurations — any resource ratio can be specified.
Once the cloud server is created, you can change configuration.
A cloud server of any configuration can be made preemptible.
GPUs can be added to configurations — see the Create a cloud server with GPUs instructions for details.
Available processors
The prebuilt and custom configuration lines differentiate the available processors.
You can view the availability of configurations in regions in the [Cloud Servers] availability matrix(/control-panel-actions/availability-matrix.mdx#cloud-servers).
- Standard Line
- Memory Line
- CPU Line
- GPU Line
- Shared Line
- HighFreq Line
- SGX Line
- Custom configurations
Processors with DDR4 REG 2133-2933 MHz.
Processors with DDR4 REG 2133-2933 MHz.
Processors with DDR4 REG 2133-2933 MHz.
Processors with DDR4 REG 2133-2933 MHz.
Processors with DDR4 REG 2133-2933 MHz.
Processors with DDR4 REG 3200 MHz.
* When the cloud server load is 100%, the processor operates 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.
Processors with DDR4 REG 3200 MHz.
Processors with DDR4 REG 2133-2933 MHz.
Fixed configurations
You can view the availability of configurations in regions in the [Cloud Servers] availability matrix(/control-panel-actions/availability-matrix.mdx#cloud-servers).
Standard Line
A line of fixed cloud server configurations with balanced 1:4 vCPU:RAM resource allocation (except for entry-level and maximum configurations).
Suitable for most tasks, such as executing code for web services and applications, hosting online stores, and creating test environments.
Available from 1 to 36 vCPUs, 1 GB to 128 GB RAM, 8 GB to 1.25 TB local disk.
CPU Line
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 Line
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 Line
Fixed cloud server configurations with dedicated GPUs.
Optimized for GPU computing, such as video transcoding, training neural networks, or creating remote workstations.
Use only with a network boot disk.
Available from 4 to 32 vCPUs, 1 to 4 GPUs, 32 GB to 320 GB RAM.
See the Create a cloud server with GPU instructions for more details.
Shared Line
Fixed cloud server configurations with the ability to use and pay for only part of the core.
Shared Line configurations are less expensive than other lines and are suitable for tasks that do not require constant and full core utilization, such as running staging, a website, bringing up a network, or training.
In Shared Line, a single core can be used by multiple clients at the same time. When creating this configuration, you must specify the proportion of vCPUs that will be reserved for your server: 10%, 20%, or 50%. Cloud server performance will never fall below this fraction and may temporarily go up to 100% if other clients are not maximizing resources or part of the core is not leased.
Use 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 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 that require high speed processing and response.
Use only with a local boot disk — this helps avoid network latency.
Available from 1 to 8 vCPUs, 2 GB to 64 GB RAM, 30 GB to 960 GB local disk.
SGX Line
Fixed cloud server configurations that support SGX technology. The technology allows an application to create protected areas in RAM.
Suitable for storing and processing sensitive data, including personal and payment information.
Available from 1 to 24 vCPUs, 4 GB to 96 GB RAM, 2 GB to 64 GB EPC, 32 GB to 1 TB local disk.
See the Create SGX cloud server instructions for details.
List of fixed configuration flavor IDs
You can use the IDs of ready-made fixed configuration flavors when creating a cloud server through Terraform.
The availability of configurations depends on region.
The Name field contains the names of the flavors:
m1.XX— OpenStack base flavors, similar to arbitrary configurations;SL1.XX— fixed configurations of the Standard Line;CPU1.XX— CPU Line;RAM1.XX— Memory Line;GL2.XX— GPU Line;PRC10.XX— Shared Line with a core share of 10%;PRC20.XX— Shared Line with a core share of 20%;PRC50.XX— Shared Line with a core share of 50%;HFL1.XX— HighFreq Line;SGX1.XX— SGX Line.
- Saint Petersburg
- Moscow
- Novosibirsk
- Tashkent
- Almaty
- Nairobi
- ru-3
- ru-1
- ru-9
- ru-2
- ru-7
- gis-1
- ru-8
- uz-1
- uz-2
- kz-1
- ke-1
Arbitrary configurations
You can view the availability of configurations in regions in the [Cloud Servers] availability matrix(/control-panel-actions/availability-matrix.mdx#cloud-servers).
Arbitrary configuration can be configured in the control panel at create server or create custom flavor using OpenStack CLI or Terraform (a flavor is a server configuration in OpenStack terminology).
In arbitrary cloud server configurations, you can choose any ratio of resources: vCPU, RAM, and local disk size (if local disk is used to create the server). GPUs can be added.
* If the configuration has more than 8 vCPU cores, the vCPU:RAM ratio must be at least 1:2. For example, for 10 vCPUs, you need at least 20 GB of RAM.
** If the configuration has more than 8 vCPU cores, the vCPU:Local Disk ratio must be at least 1:32. For example, a 10 vCPU requires a disk size of at least 320 GB.
If fixed and random cloud server configurations are not suitable, order a suitable configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM — at least 1:2;
- vCPU:RAM:Local disk — at least 1:2:16.
Create a flavor
- OpenStack CLI
- Terraform
-
Create a flavor:
openstack flavor create \
--private --vcpus <vcpu> \
--ram <ram_size> \
--disk <disk_size> \
<flavor_name>Specify:
--private— the key specifies that the flavor will be visible within only one account;<vcpu>is the number of vCPUs;<ram_size>— size of RAM in MB;- optional:
<disk_size>— local disk size in GB; <flavor_name>— the name of the flavor, must be unique (including not matching the names of deleted flavor). You can view the flavor list by using theopenstack flavor listcommand.
Example of creating a flavor with 1 vCPU, 1 GB RAM, local disk size of 5 GB:
openstack flavor create --private --vcpus 1 --ram 1024 --disk 5 NEW_FLAVOR
View a list of configurations
A list of all available configurations can be viewed in the control panel when creating a cloud server or via the OpenStack CLI (ready-made flavors and self-created flavors will be displayed).
-
Check out the list of available flavors:
openstack flavor listA list will appear in the response:
+------------+---------------------+--------+------+-----------+-------+-----------+
| ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public |
+------------+---------------------+--------+------+-----------+-------+-----------+
| 1 | m1.tiny | 512 | 0 | 0 | 0 | 1 | True |
| 2 | m1.small | 2048 | 0 | 0 | 0 | 0 | 1 | True |
| 3 | m1.medium | 4096 | 0 | 0 | 0 | 2 | True |
| 1011 | SL1.1-1024 | 1024 | 0 | 0 | 0 | 1 | True |
| 1012 | SL1.1-2048 | 2048 | 0 | 0 | 0 | 1 | True |
| 2011 | CPU1.4-8192 | 8192 | 0 | 0 | 0 | 4 | True |
| 2012 | CPU1.8-16384 | 16384 | 0 | 0 | 0 | 8 | True |
| 4011 | RAM1.2-16384 | 16384 | 0 | 0 | 0 | 2 | True |
| 4012 | RAM1.4-32768 | 32768 | 0 | 0 | 4 | True |
| 8311 | HFL1.1-2048-30 | 2048 | 30 | 0 | 0 | 1 | True |
| 8312 | HFL1.1-4096-80 | 4096 | 80 | 0 | 0 | 1 | True |
| 3021 | GL2.8-24576-0-1GPU | 24576 | 0 | 0 | 8 | True |
| 3022 | GL2.14-49152-0-2GPU | 49152 | 0 | 0 | 0 | 0 | 14 | True |
| 9011 | PRC10.1-512 | 512 | 0 | 0 | 0 | 1 | True |
| 9021 | PRC20.1-512 | 512 | 0 | 0 | 1 | True |
| 9051 | PRC50.1-512 | 512 | 512 | 0 | 0 | 0 | 1 | True |
| 9587d840-b | myflavor | 1024 | 0 | 0 | 0 | 1 | False |
| fe0-4fce-a | | | | | | | | | | | | |
| f3f-69b7de | | | | | | | | | | | | | | |
| b8d623 | | | | | | | | | | | | | |
+------------+---------------------+--------+------+-----------+-------+-----------+-------+-----------+-----------+The margins indicate:
IDis the ID of the flavor;Nameis the name of the flavor of the view:m1.XX— OpenStack base flavors, similar to arbitrary configurations;SL1.XX— fixed configurations of the Standard Line;CPU1.XX— CPU Line;RAM1.XX— Memory Line;GL2.XX— GPU Line;PRC10.XX— Shared Line with a core share of 10%;PRC20.XX— Shared Line with a core share of 20%;PRC50.XX— Shared Line with a core share of 50%;HFL1.XX— HighFreq Line;SGX1.XX— SGX Line;
RAM— size of RAM in MB;Disk— the size of the local disk in GB;VCPUs— the number of vCPUs;Is Public— visibility scope of the flavor:True— public ready flavors,False— private flavors.