Skip to main content
To make sure that GPU capacity is always available for your nodes (virtual machines, VMs), you can reserve GPUs. A reservation represents a capacity block group, and it reserves a specific number of GPUs that are allocated to your infrastructure. GPUs from a reservation remain available, even if a VM is stopped. Without reservations, GPU capacity is taken from a shared pool and returned when a VM is stopped (for example, by you or a maintenance event). To start using reservations, send a request to your Nebius manager. In this request, specify how many GPUs you would like to reserve and for what period. If you are not in contact with a Nebius manager, you can ask technical support to connect you with one. After reservations are ready, you can add them to your existing node groups or create new ones with reservations. You can also check your capacity block groups on the Limits page and get detailed information about them. For more information, see List of capacity block groups.
GPUs allocated from reservations do not count towards quotas on the number of GPUs.

​
How to add reservations to node groups

Node groups of a regular type with GPUs support reservations. Preemptible node groups and node groups without GPUs do not support reservations.
If you want to create a node group, in the creation form, under Computing resources, select With GPU and a regular VM type. After that, specify the Reservation usage settings.If you want to modify an existing node group, go to its Settings tab on the node group page. Next, update the Reservation usage settings.The Reservation usage settings are only displayed if you have capacity block groups.Available Reservation usage options:
  • With reservations: Resources are allocated from reservations. You can use one of the following reservation types:
    • Any (default): You do not need to select reservations. The service uses the reservations that are most suitable for the configuration of your VM.
    • Specific: Select specific reservations. Make sure to select reservations that have enough capacity and that do not expire in several days.
    If there are no reservations available during the VM lifecycle, you can run your VM without reservations. Resources for it will be taken from the common pool. To configure this behavior, enable the Start without a reservation when reservation capacity is exhausted option.
  • Without reservations: Resources are allocated from the common pool, and no reservations are used for the node group.

​
What’s next

To find information about reservations, check the pages of your VMs (nodes). The VM page and the list of VMs show what reservation policy you have configured and what reservations currently apply. For more information, see How to find information about reservations for an already configured VM. For details about how billing works when you use reservations, see Billing for reservations.

​
See also