Making a VM preemptible
You can create a preemptible VM or change the type of an existing one.
Warning
VMs with NVIDIA® Hopper® H100 GPUs cannot be preemptible.
Creating a preemptible VM
To create a preemptible VM:
-
In the management console
, select the folder to create your VM in. -
In the list of services, select Compute Cloud.
-
Click Create VM at the top right.
-
Under Basic parameters:
-
Enter a name and description for the VM. The naming requirements are as follows:
- The length can be from 3 to 63 characters.
- It may contain lowercase Latin letters, numbers, and hyphens.
- The first character must be a letter. The last character can't be a hyphen.
Note
The VM name is used to generate an internal FQDN only once: when creating a VM. If the internal FQDN is important to you, choose an appropriate name for the VM at the creation stage.
-
Select an availability zone to place your VM in.
-
-
Under Image/boot disk selection, select one of the images.
-
(Optional) Under Disks, select the Disks tab and configure a boot disk:
-
Select the disk type.
-
Specify the required disk size.
If you want to create a VM from an existing disk, under Disks, add a disk:
- Click Add disk.
- Enter the disk name.
- Select the disk type.
- Specify the desired block size.
- Specify the desired disk size.
-
(Optional) Enable the Delete with the VM option if you need to automatically delete the disk when deleting the VM it will be attached to.
-
Select
Disk
as content. -
Click Add.
-
-
(Optional) Under Disks and file storages, select the File storages tab and attach the file storage:
- Click Attach file storage.
- In the window that opens, select a file store.
- Enter the device name.
- Click Attach file storage.
-
Under Computing resources:
- Choose a platform.
- Specify the guaranteed share and the required number of vCPUs, as well as the amount of RAM.
- Enable Preemptible.
- (Optional) Enable a software-accelerated network.
-
Under Network settings:
-
Enter a subnet ID or select a cloud network from the list.
If you do not have a network, click Create network to create one:- In the window that opens, enter the network name and specify the folder to host the network.
- (Optional) To automatically create subnets, select the Create subnets option.
- Click Create.
Each network must have at least one subnet. If there is no subnet, create one by selecting
-
In the Public IP field, choose a method for assigning an IP address:
Auto
: Assign a random IP address from the Nebius Israel IP pool.List
: Select a public IP address from the list of previously reserved static addresses. For more information, see Converting a dynamic public IP address to static.No address
: Do not assign a public IP address.
-
In the Internal IPv4 address field, select the method for assigning internal addresses:
Auto
orManual
. -
(Optional) Create records for the VM in the DNS zone:
- Expand the DNS settings for internal addresses section and click Add record.
- Specify the zone, FQDN, and TTL for the record. When setting the FQDN, you can select
Detect automatically
for the zone.
You can add multiple records to internal DNS zones. For more information, see Cloud DNS integration with Compute Cloud. - To create another record, click Add record.
-
Select the appropriate security groups.
-
-
Under Access, specify the information required to access the instance:
-
(Optional) Select or create a service account. With a service account, you can flexibly configure access rights for your resources.
-
Enter the username in the Login field.
Alert
Do not use the
root
username or other names reserved by the operating system. To perform operations that require superuser permissions, use thesudo
command. -
In the SSH key field, paste the contents of the public key file.
-
If required, grant access to the serial console.
In public Linux images provided by Nebius Israel, the functionality of connecting over SSH using login and password is disabled by default.
-
-
Click Create VM.
The VM appears in the list.
If you don't have the Nebius Israel command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
-
View a description of the CLI create VM command:
yc compute instance create --help
-
Prepare a key pair (public and private keys) for SSH access to the VM.
-
Select a Linux-based public image from Cloud Marketplace, e.g., CentOS 7.
To get a list of available images using the Nebius Israel CLI, run this command:
yc compute image list --folder-id standard-images
Result:
+----------------------+-------------------------------------+--------------------------+----------------------+--------+ | ID | NAME | FAMILY | PRODUCT IDS | STATUS | +----------------------+-------------------------------------+--------------------------+----------------------+--------+ ... | fdvk34al8k5n******** | centos-7-1549279494 | centos-7 | dqni65lfhvv2den5gtv9 | READY | | fdv7ooobjfl3******** | windows-2016-gvlk-1548913814 | windows-2016-gvlk | dqnnc72gj2ist3ktjj1p | READY | | fdv4f5kv5cvf******** | ubuntu-1604-lts-1549457823 | ubuntu-1604-lts | dqnnb6dc7640c5i968ro | READY | ... +----------------------+-------------------------------------+--------------------------+----------------------+--------+
-
Create a VM in the default folder:
yc compute instance create \ --name first-preemptible-instance \ --zone il1-a \ --network-interface subnet-name=default-a,nat-ip-version=ipv4 \ --preemptible \ --create-boot-disk image-folder-id=standard-images,image-family=centos-7 \ --ssh-key ~/.ssh/id_ed25519.pub
Note
If you are using the CLI version 0.92.0 or lower, then in the command, you must also specify the VM platform:
--platform standard-v3
. You can find out the CLI version using theyc version
command and install the latest version using theyc components update
command.This command creates a preemptible VM with the following characteristics:
- Named
first-preemptible-instance
. - Running CentOS 7.
- In the
il1-a
availability zone. - In the
default-a
subnet. - With a public IP address.
To create a VM without a public IP address, disable the
nat-ip-version=ipv4
option.VM naming requirements:
- The length can be from 3 to 63 characters.
- It may contain lowercase Latin letters, numbers, and hyphens.
- The first character must be a letter. The last character can't be a hyphen.
Note
The VM name is used to generate an internal FQDN only once: when creating a VM. If the internal FQDN is important to you, choose an appropriate name for the VM at the creation stage.
- Named
Use the create REST API method for the Instance resource or the InstanceService/Create gRPC API call.
If you do not have Terraform yet, install it and configure the Nebius Israel provider.
-
In the configuration file, describe the parameters of the resources you want to create:
resource "yandex_compute_instance" "vm-1" { name = "preemptible-vm" allow_stopping_for_update = true platform_id = "standard-v3" zone = "<availability_zone>" resources { cores = <number_of_vCPU_cores> memory = <amount_of_RAM_in_GB> } boot_disk { initialize_params { image_id = "<image_ID>" } } network_interface { subnet_id = "${yandex_vpc_subnet.subnet-1.id}" nat = true } metadata = { ssh-keys = "<username>:<SSH_key_contents>" } scheduling_policy { preemptible = true } } resource "yandex_vpc_network" "network-1" { name = "network1" } resource "yandex_vpc_subnet" "subnet-1" { name = "subnet1" zone = "<availability_zone>" network_id = "${yandex_vpc_network.network-1.id}" }
Where:
yandex_compute_instance
: Description of the VM:name
: VM name.-
allow_stopping_for_update
: Allow a VM instance to stop to make changes. Settrue
if you plan to change the network settings, computing resources, disks, or file storage for your VM using Terraform. The default value isfalse
. platform_id
: Platform.zone
: ID of the availability zone that will host your VM.resources
: Number of vCPU cores and the amount of RAM available to the VM. The values must match the selected platform.boot_disk
: Boot disk settings. Specify the ID of the selected image. You can get the image ID from the list of public images.network_interface
: Network settings. Specify the ID of the selected subnet. To automatically assign a public IP address to the VM, setnat = true
.metadata
: In metadata, provide the public key for accessing the VM via SSH. For more information, see VM metadata.scheduling_policy
: Scheduling policy. To create a preemptible VM, setpreemptible = true
.
yandex_vpc_network
: Description of the cloud network.yandex_vpc_subnet
: Description of the subnet your VM will connect to.
Note
If you already have suitable resources, such as a cloud network and subnet, you do not need to describe them again. Use their names and IDs in the appropriate parameters.
For more information on resources that you can create with Terraform, see the provider documentation
. -
Create resources:
-
In the terminal, change to the folder where you edited the configuration file.
-
Make sure the configuration file is correct using the command:
terraform validate
If the configuration is correct, the following message is returned:
Success! The configuration is valid.
-
Run the command:
terraform plan
The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.
-
Apply the configuration changes:
terraform apply
-
Confirm the changes: type
yes
in the terminal and press Enter.
All the resources you need will then be created in the specified folder. You can check the new resources and their configuration using the management console
. -
When a VM is created, it is assigned an IP address and hostname (FQDN). This data can be used for SSH access.
You can make a public IP address static. For more information, see Making a VM's public IP address static.
Changing a VM's type
To change the type of a VM, for example, make it preemptible:
- In the management console
, select the folder where the VM is located. - In the list of services, select Compute Cloud.
- In the line with the appropriate VM, click
- In the window that opens, click Stop. The VM status changes to
Stopped
. - In the line with the appropriate VM, click
- Under Computing resources, disable the Preemptible option.
- Click Save changes.
- At the top right, click Start.
- In the window that opens, click Start.
If you don't have the Nebius Israel command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
-
View a description of the CLI command to stop a VM:
yc compute instance stop --help
-
Get a list of all VMs in the default folder:
yc compute instance list
Result:
+----------------------+-----------------+---------------+---------+----------------------+ | ID | NAME | ZONE ID | STATUS | DESCRIPTION | +----------------------+-----------------+---------------+---------+----------------------+ | fhm0b28lgfp4tkoa3jl6 | first-instance | il1-a | RUNNING | my first vm via CLI | | fhm9gk85nj7gcoji2f8s | second-instance | il1-a | RUNNING | my second vm via CLI | +----------------------+-----------------+---------------+---------+----------------------+
-
Select the VM
ID
orNAME
(for example,first-instance
). -
Stop the VM:
yc compute instance stop <VM ID or name>
Result:
done (15s)
-
Edit the VM parameters:
yc compute instance update <VM ID or name> \ --preemptible=false
Result:
done (1s) id: fhm0b28lgfp4tkoa3jl6 folder_id: b1ghgf288nvg541tgu73 ... network_settings: type: STANDARD placement_policy: {}
-
Start the VM again:
yc compute instance start <VM ID or name>
Result:
done (11s) id: fhm0b28lgfp4tkoa3jl6 folder_id: b1ghgf288nvg541tgu73 ... network_settings: type: STANDARD placement_policy: {}
Use the update REST API method for the Instance resource or the InstanceService/Update gRPC API call. In the request body, set "preemptible": false
in schedulingPolicy
.
If you do not have Terraform yet, install it and configure the Nebius Israel provider.
-
In the configuration file, find a description of the scheduling policy of the VM you want to make preemptible:
scheduling_policy { preemptible = true }
-
Delete the
scheduling_policy
field set topreemptible = true
:For more information on resources you can create with Terraform, see the provider documentation
. -
Make sure the configuration files are valid.
-
In the command line, go to the directory where you created the configuration file.
-
Run the check using this command:
terraform plan
If the configuration is described correctly, the terminal will display a list of created resources and their parameters. If the configuration contains any errors, Terraform will point them out.
-
-
Deploy cloud resources.
-
If the configuration does not contain any errors, run this command:
terraform apply
-
Confirm that you want to create the resources.
All the resources you need will then be created in the specified folder. You can check that the resources are there and their settings are correct using the management console
. -
This will affect your bill for the VM usage. More about VM pricing.