Allocation policy
When creating an instance group, you can choose the Nebius Israel regions and availability zones to host your VM instances and list tags for VM instances within each availability zone.
A region is a location where you deploy your VM instances. Each region consists of one or more zones. Only one region is currently available.
Region | Zones | Location |
---|---|---|
il1 |
il1-a il1-b il1-c |
Lod, Jerusalem, Tirat Carmel (Israel). |
You cannot directly migrate VM instances to other availability zones; however, you can update a group with new zone values.
Tags are used for logical labeling of VM instances within an availability zone. You can transfer a list of tags to an instance group using a YAML specification. After you do that, each VM instance in the availability zone will be assigned a unique tag from the list.
Using tags, you can ensure more granular declarative management of instances in the group. You can use tags as system variables, such as in a VM name. If you remove a tag from the list in the YAML specification, applying the configuration will also remove the instance labeled with this tag from the group. This will not change the group size, as a new instance will be created with the next available tag from the list. Tags also help keep the configuration defined when resizing the group: each VM instance will be assigned sequential tags from the list based on the number of VM instances in the availability zone.
The allocation policy is set in the allocation-policy
key in the YAML specification. Availability zones are listed in the zones
key and tags are listed in the instance_tags_pool
key. You can specify any available zones: instances in the group will be evenly distributed across them.
Here is how a YAML specification entry may look like:
...
allocation_policy:
zones:
- zone_id: il1-a
instance_tags_pool:
- first-tag
- second-tag
- zone_id: il1-b
instance_tags_pool:
- third-tag
- fourth-tag
- zone_id: il1-c
instance_tags_pool:
- fifth-tag
- sixth-tag
...
Where:
Key | Value |
---|---|
zones |
Zone list, with each zone defined in the zone_id key as a key-value pair |
zone_id |
Zone ID |
instance_tags_pool |
(Optional) List of group instance tags. Restrictions:
|
Example
In the example, a YAML specification describes a group of fixed-size instances. The instances are hosted in the same availability zone and their names include tags from the instance_tags_pool
list.
name: first-fixed-group
service_account_id: ajeujptarqa4********
description: "This instance group was created from YAML config."
instance_template:
name: production-{instance.tag}
platform_id: standard-v3
resources_spec:
memory: 2g
cores: 2
boot_disk_spec:
mode: READ_WRITE
disk_spec:
image_id: fd8v80pep5m9********
type_id: network-hdd
size: 5g
network_interface_specs:
- network_id: enpgf5vu9dd7********
primary_v4_address_spec: {}
scheduling_policy:
preemptible: false
deploy_policy:
max_unavailable: 1
max_expansion: 0
scale_policy:
fixed_scale:
size: 3
allocation_policy:
zones:
- zone_id: il1-a
instance_tags_pool:
- first
- second
- third