Create a preemptible server

carefully

A preemptible server will be stopped by Selectel at any time within 24 hours of creation. If the preemptible server has a local disk, the data on it will be deleted.

For more information about how preemptible servers work, see the Preemptible servers instructions.

Control panel
OpenStack CLI

In the Control Panel, in the top menu, click Products and select Cloud Servers.
Click Create server.
In the Additional settings section, select the Preemptible server checkbox.
Configure the remaining server settings — for details, see the Create a cloud server instructions.
Click Create.

Open the OpenStack CLI.
Create a cloud server:
```
openstack server create \
    [--image <image> | --volume <volume> | --snapshot <snapshot>] \
    --flavor <flavor> \
    --availability-zone <pool_segment> \
    --nic net-id=<net_uuid> \
    --security-group <security_group> \
    --key-name <key_name> \
    --tag preemptible --os-compute-api-version 2.72 \
    <server_name>
```
Specify:
- source type:
  - --image <image> — to create a server from a pre-built or custom image. The <image> parameter is the image ID or name. You can view the list of images using openstack image list;
  - --volume <volume> — to create a server from a network volume. The <volume> parameter is the volume ID or name. You can view the list of network volumes using openstack volume list;
  - --snapshot <snapshot> — to create a server from a snapshot. The <snapshot> parameter is the snapshot ID or name. You can view the list of snapshots using openstack snapshot list;
- <flavor> — flavor ID or name. Flavors correspond to cloud server configurations and determine the number of vCPUs, RAM, and the server's local disk size (optional). You can use fixed configuration flavors or create a flavor. For example, 1015 is the ID for creating a server with a fixed Standard line configuration with 4 vCPUs, 16 GB RAM in the ru-7 pool. You can view the list of flavors using openstack flavor list or in the List of fixed configuration flavors across all pools table;
- <pool_segment> — the pool segment where the cloud server will be created, for example, ru-7a. You can view the list of available pool segments in the Cloud server availability by location instructions;
- <net_uuid> — ID of the private or public network the server will connect to. You can view the list using openstack network list;
- <security_group> — security group ID or name. To create a server with a security group, traffic filtering (port security) must be enabled on the network. You can view the list of groups using the openstack security group list command;
- <key_name> — SSH key pair name for the service user. If SSH keys have not been created, generate them. You can view the list using openstack keypair list;
- --tag preemptible --os-compute-api-version 2.72 — tag to create a preemptible server;
- optional: --block-device-mapping vdb=<extra_volume> — ID or name of an additional volume. You can view the list using openstack volume list;
- optional: --property x_cloud_smt_enabled=false — disables Hyper-Threading (SMT). If the parameter is not specified, Hyper-Threading (SMT) is enabled by default. Can only be used with flavors that support dedicated cores. You can view the list of flavors in the List of fixed configuration flavors across all pools table;
- optional: --property x_cloud_numa_nodes=1 — places resources on a single NUMA node. Can only be used with flavors that support dedicated cores. You can view the list of flavors in the List of fixed configuration flavors across all pools table;
- optional: --tag <tag_name> --os-compute-api-version 2.52 — a tag to add additional information about the server;
- optional: --user-data <user_data.file> — path to the script with Base64-encoded data. Scripts and tasks from the file are executed upon the first boot of the operating system. Example scripts can be found in the User data instructions;
- <server_name> — server name.