Create a cloud server
Control panel
OpenStack CLI
Terraform
-
В control panels go to Cloud platform → Servers.
-
Click Create a server.
-
In the block Name and location:
3.1 In the field Name enter the server name. This will be set as the host name in the operating system.
3.2 In the fields Region и Poole 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.
-
In the block Source click the default source name and select the source from which to create the server:
4.1 To create a server from finished image with the operating system pre-installed and configured, open the tab Ready-made images, select an image and press Select. Ready images are available in all segments of the pool.
4.2 To create a server with annex open the tab Appendices, select an application, and press Select. Applications are available in all segments of the pool.
4.3 To create a server from own image that you have downloaded to the image repository yourself, open the tab My images, select an image and press Select. The image must be in the same pool segment as the server.
4.4 To create a server from a created server network drive open the tab Disks, select a disk and press Select. The disk must be in the same pool segment as the server.
4.5 To create a server from snapshot of the network drive, open the Snapshots, select a snapshot, and press Select. The snapshot must be in the same pool segment as the server.
-
In the block Configuration select a server configuration:
- fixed configuration — rulers in which the ratio of resources is fixed;
- or arbitrary configuration, where any resource ratio can be specified.
The configurations use different processors depending on the lineup and pool segment.
5.1. To select a fixed configuration, press FixedOpen the tab with the desired ruler and select the configuration.
5.2 To select an arbitrary configuration, press ArbitrarySpecify the number of vCPUs and the RAM size. If you want to add GPUs to the server, click Add GPUselect GPU type and specify the number of GPUs.
5.3. To select the following as the server boot disk local disk and check the box Local SSD NVMe disk. A server with a local disk can only be created from images and applications. To select a local disk as the boot disk network disk 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
.Once the server is created, you can reconfigure.
-
If you have not checked the checkbox Local SSD NVMe disk in step 5.3, the first specified network disk will be used as the server boot disk. In the block Disks:
6.1 In the field Disk type select network boot disk type.
6.2 Specify the size of the network boot disk in GB or TB. Take into account network disk limits to the maximum size.
-
Optional: add additional network drives of the server. In the block Disks:
7.1 In the field Disk type select network drive type.
7.2 Specify the size of the network disk in GB or TB. Take into account network disk limits to the maximum size.
7.3 To add another additional drive, press AddSelect the type of disk and specify its size.
Once the server is created, you can disconnect additional disks from it or connect new ones.
-
In the block Network select the subnet to which the server will be connected:
- private — a subnet without access from the Internet;
- private + 1 public IP — a private subnet with a static public IP address. By default, only the server to which the public IP address connects will be accessible from the Internet in the subnet;
- public — a subnet in which all addresses are accessible from the Internet.
8.1 To create a private subnet without access from the Internet, in the field Subnetwork select Private. Optional: change the default network settings by entering the following in the field CIDR subnets Specify the CIDR of the subnet, turn the toggle switch on or off DHCPin the field Gateway Specify the IP address of the default gateway, in the field A sub-network will be established on the network select New network and enter the name of the network.
If a private subnet is created, in the field Subnetwork select an existing subnet and in the Private IP specify the private IP address of the server.
8.2 To create a private subnet and a static public IP address, in the field Subnetwork select Private + 1 public IP. A private network will be automatically created
nat
, private subnet, router.router-nat
and a public IP address.If a private subnet and a cloud router connected to an external network are created, in the field Subnetwork select Private + 1 public IPin the field Private subnet select the created subnet, in the Private IP specify the private IP address of the server. If a public IP address is created, click Connect existing and select a public IP address.
8.3 To create a public subnet, in the field Subnetwork select Public and in the field Subnet size select the number of IP addresses in the subnet.
If a public subnet is created, in the Subnetwork select an existing subnet and in the Public IP specify the public IP address of the server.
-
In the block Access:
9.1 Place on the server SSH key for the project for a secure connection.
To add a new SSH key for a project to the cloud platform, click Add an SSH keyenter the key name, insert the public SSH key in OpenSSH format, and then click Add.
If an SSH key is added to the cloud platform, in the field SSH key select an existing key.
The SSH key is only available in the pool in which it is hosted.
9.2 Optionally: in the field Password for "root" copy the user's password
root
(a user with unlimited rights to all system operations). Save the password in a safe place and do not share it in public. -
In the block Additional settings:
10.1 Optionally: to create a preemptible server and check the box Preemptible server.
10.2 Optionally, if you plan to create multiple servers and want to increase the fault tolerance of your infrastructure, add a server in the placement group. To create a new group, press Create a 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.
If the group is created, in the field Accommodation group select a placement group.
10.3 Optional: add tags servers to add additional information or filter the servers in the list. Operating system and configuration tags are automatically added. To add a new tag, in the Tags enter tag.
-
Optional: in the unit Automation in the field User data insert a script to be executed by the agent cloud-init the first time you start the operating system. Open the tab Text and paste the script or open a tab File and upload the file. Examples of scripts and supported formats can be found in the instructions User data.
-
Check the price of the cloud server.
-
Click Create.
-
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 finished or own image. Parameter<image>
— ID or image name. You can view the list of images usingopenstack image list
;--volume <volume>
— to create a server from network drive. Parameter<volume>
— ID or disk name. You can view the list of network drives byopenstack volume list
;--snapshot <snapshot>
— to create a server from snapshot. Parameter<snapshot>
— ID or name of the snapshot. You can view the list of snapshots withopenstack 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 withopenstack 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 byopenstack 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 withopenstack keypair list
;- optional:
--block-device-mapping vdb=<extra_volume>
— ID or name of the additional disk. The list can be viewed withopenstack 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 a preemptible 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.
- source type:
Use the instructions Create a server of arbitrary configuration with a bootable network drive and an additional network drive in the Terraform documentation.