Create a cloud server

Last update: April 16 2025

Create a cloud server

Control panel

1. in control panels from the top menu, press Products and select Cloud servers.

2. Click Create a server.

3. Fill in the blocks:

   • Name and location
   • Source
   • Configuration
   • Disks
   • Network
   • Access
   • optional: Additional settings

4. Check the price of the cloud server.

5. Click Create.

Name and location⁠

1. Enter the server name. This will be set as the host name in the operating system.
2. Select region and pool segment The pool segment determines the list of available server configurations and the cost of resources. The list of available server configurations and the cost of resources depends on the pool segment. Once the server is created, the pool segment cannot be changed.

Source⁠

You can create a server from finished image with a pre-installed and customized operating system, appendices, own image, network drive or snapshot.

Finished image

1. Click on the default source name.

2. Open the tab Ready-made images.

3. Optional: check the checkbox GPU optimized imagesto filter out GPU-optimized OS images.

4. Select an image. Ready images are available in all pool segments.

5. If you are creating a server with a non-GPU configuration, uncheck the box. GPU image auto-selectionso that when you change to a GPU configuration, the optimized OS image is not automatically selected.

6. Click Select.

appendix

1. Click on the default source name.

2. Open the tab Appendices.

3. Select an application. Applications are available in all pool segments.

4. Click Select

Own image

1. Click on the default source name.

2. Open the tab My images.

3. Select an image. The image must be in the same pool as the server.

4. Click Select.

Network disk

1. Click on the default source name.

2. Open the tab Disks.

3. Select a disk. The disk must be in the same pool segment as the server.

4. Click Select.

Snapshot

1. Click on the default source name.

2. Open the tab Snapshots.

3. Select a snapshot. The snapshot must be in the same pool segment as the server.

4. Click Select.

Configuration⁠

Two types of configurations are available for the server:

• fixed configurations — several ranges with different specifications, in which the resource ratio is fixed;
• custom configurations In which any ratio of resources can be specified.

The configurations use different processors depending on the line and segment of the pool. After the server is created, you can reconfigure.

Fixed configuration

1. Click Fixed.

2. Open the tab with the desired ruler.

3. Select a configuration.

4. If both local and network disks are available in the selected configuration, select the disk to be used as the boot disk:

   • local disk — check the box Local SSD NVMe disk. A server with a local disk can only be created from images and applications;
   • network drive — don't check the box.

   The amount of RAM that is allocated to the server may be less than specified in the configuration — the operating system kernel reserves some RAM depending on the kernel version and distribution. You can check the allocated amount on the server using the command sudo dmesg | grep Memory.

custom configuration

1. Click custom.

2. Specify the number of vCPUs and the size of RAM.

3. If you want to add GPUs to the server, click Add GPUselect GPU type and specify the number of GPUs. If the block has sources you have selected an image without GPU optimization and you have the checkbox marked GPU image auto-selectionThe selected image will automatically change to a GPU-optimized image.

4. If both local and network disks are available in the selected configuration, select the disk to be used as the boot disk:

   • local disk — check the box Local SSD NVMe disk. A server with a local disk can only be created from images and applications;
   • network drive — don't check the box.

   The amount of RAM that is allocated to the server may be less than specified in the configuration — the operating system kernel reserves some RAM depending on the kernel version and distribution. You can check the allocated amount on the server using the command sudo dmesg | grep Memory.

Disks⁠

1. If you did not check the checkbox when setting up the configuration Local SSD NVMe diskThe first specified network drive will be used as the server boot disk. To configure it:

   1.1 Select network boot disk type.

   1.2 Specify the size of the network boot disk in GB or TB. Take into account network disk limits to the maximum size.

   1.3 If you selected the Universal v2 disk type, specify the total number of read and write operations in IOPS. After creating the disk, you can change the number of IOPS — decrease or increase. There is no limit to the number of IOPS changes.

2. Optional: to add additional network drives of the server:

   2.1. Press Add.

   2.2 Select network boot disk type.

   2.3 Specify the size of the network boot disk in GB or TB. Take into account network disk limits to the maximum size.

   2.4 If you selected the Universal v2 disk type, specify the total number of read and write operations in IOPS. After creating the disk, you can change the number of IOPS — decrease or increase. There is no limit to the number of IOPS changes.

   Once the server is created, you can disconnect additional disks from it or connect new ones.

Network⁠

A server can be added to a new subnet or to an existing subnet. The subnet can be:

• private — a subnet without access from the Internet or with a single static public IP address. The IP address connects to a server that will be accessible from the Internet;
• public — a subnet in which all addresses are accessible from the Internet.

Private subnet

1. Click Private subnet.

2. In the field Public IP address for access from the Internet select the subnet type:

   • The new public IP address is a private subnet with a static public IP address. Only the server to which the public IP address is connected will be accessible from the Internet;
   • No public IP address — a private subnet with no access from the Internet. You cannot connect to the server from the Internet, including via SSH or RDP.

3. To add a server to an existing private subnet:

   3.1 Expand the private subnet settings block.

   3.2 In the field Subnetwork select an existing subnet.

   3.3 In the field Private IP specify the private IP address of the server. For a private subnet with a public IP address, the public address will be automatically connected to the private address;

4. To add a server to a new private subnet on an existing network:

   4.1 Expand the private subnet settings block.

   4.2 In the field Subnetwork select New subnet.

   4.3 Optional: Change the CIDR of the subnet.

   4.4 Optionally: switch on the toggle switch DHCP.

   4.5 Optionally: in the field Gateway change the IP address of the default gateway.

   4.6 In the field Network select an existing network on which to create a subnet, or New network. A router will automatically be created for a private subnet with a public IP address router-<network_name>where <network_name> — network name.

   4.7 If you have chosen New network, enter the name of the network.

5. To add a server to a new network and private subnet:

   5.1 Expand the private subnet settings block.

   5.2 Optional: Change the CIDR of the subnet.

   5.3 Optionally: activate the toggle switch DHCP.

   5.4 Optionally: in the field Gateway change the IP address of the default gateway.

   5.5 In the field Network select New networkto create a new network and a private subnet.

   5.6 Maintain the network name. A router will automatically be created for a private subnet with a public IP address router-<network_name>where <network_name> — network name.

Public subnet

1. Click Public subnet.

2. In the field Subnet size select the subnet size.

Access⁠

1. Put it on the server SSH key for the project for a secure connection:

   1.1 If the SSH key for the project has not been added to the cloud platform, click Add an SSH key, enter the key name, insert the public key in OpenSSH format, and press Add.

   1.2 If the SSH key for the project is added to the cloud platform, in the field SSH key select an existing key. The SSH key is available only in the pool in which it is placed.

2. Optional: in the field Password for "root":

   2.1 Copy the user password root — user with unlimited rights for all actions on the system.

   2.2 Save the password in a safe place and do not transmit it in public.

Optional: additional settings⁠

1. To create interrupted server and check the box Interruptible server.

2. If you plan to create multiple servers and want to improve the fault tolerance of your infrastructure, add a server to the placement group:

   2.1 To create a new group, in the field Accommodation group select New group, enter a group name, and select a policy for hosting on different hosts:

   • preferably soft-anti-affinity. The system will try to place servers on different hosts. If there is no suitable host when creating a server, it will be created on the same host;
   • anti-affinity is mandatory. Servers in a group must be located on different hosts. If there is no suitable host when creating a server, the server will not be created.

   2.2 If the group is created, in the field Accommodation group select a placement group.

3. To add more information or filter the servers in the list, add tags servers. Operating system and configuration tags are automatically added. To add a new tag, in the Tags enter tag.

4. To add a script to be executed by the agent cloud-init at the first startup of the operating system, in the block Automation in the field User data:

   • tab Text and paste the script with text;
   • or open the tab File and upload the script file.

   Examples of scripts and supported formats can be found in the manual User data.

OpenStack CLI

1. Open the OpenStack CLI.

2. Create a cloud server:

   openstack server create \
       [--image <image> | --volume <volume> | --snapshot <snapshot>] \
       --flavor <flavor> \
       --availability-zone <pool_segment> \
       --nic net-id=<net_uuid> \
       --key-name <key_name> \
       <server_name>

   Specify:

   • source type:
     • --image <image> — to create a server from ready or own image. Parameter <image> — The ID or name of the image. The image must be in the same pool as the server. You can view the list of images by openstack image list;
     • --volume <volume> — to create a server from network drive. Parameter <volume> — The ID or name of the disk. The disk must be in the same pool segment as the server. You can view the list of network disks by openstack volume list;
     • --snapshot <snapshot> — to create a server from snapshot. Parameter <snapshot> — The ID or name of the snapshot. The snapshot must be in the same pool segment as the server. The list of snapshots can be viewed with openstack snapshot list;
   • <flavor> — The ID or name of the flavor. The flavors correspond to cloud server configurations and determine the number of vCPUs, RAM, and local disk size (optional) of the server. You can use fixed-configuration flavors or flavor. For example, 4011 — ID to create a Memory Line fixed configuration server with 2 vCPUs, 16GB RAM in a ru-9 pool. The list of flavors can be viewed with openstack flavor list or in a table List of fixed-configuration flavorings in all pools;
   • <pool_segment> — pool segment where the cloud server will be created, e.g. ru-9a. The list of available pool segments can be found in the instructions Availability matrices;
   • <net_uuid> — The ID of the private or public network to which the server will be connected. The list can be viewed by openstack network list;
   • <key_name> — the name of the SSH key pair for the service user. If SSH keys have not been created, generate them. The list can be viewed with openstack keypair list;
   • optional: --block-device-mapping vdb=<extra_volume> — ID or name of the additional disk. The list can be viewed with openstack volume list;
   • optional: --tag <tag_name> --os-compute-api-version 2.52 — tag to add more information about the server;
   • optional: --tag preemptible --os-compute-api-version 2.72 — creation tag of an interrupted server;
   • optional: --user-data <user_data.file> — path to the script with data encoded in Base64. Scripts and tasks from the script will be executed at the first boot of the operating system. Examples of scripts can be found in the instructions User data;
   • <server_name> — server name.

Terraform

Use the instructions Create a server of custom configuration with a bootable network drive and an additional network drive in the Terraform documentation.