OpenAPI 3.1.02026-08-13140162205.6 KB

138b4ef69d2f

Reservations

List a node's GPU units, so you can reserve or release them

The allocatable GPU units on one node, with the ids that create, release, and reclaim take. Without this those calls are unusable: they are unit-scoped by design, and nothing else on the API returns a unit id, so the first reservation on a node could not be written at all. Each unit is one IOMMU group and is indivisible: a paired unit sells its GPUs together. Only vfio-group units are reservable, and the response says which, and why not, rather than leaving the caller to infer it from a rejection. Readable by a platform operator, the org that owns the node, and any org managing a reservation on it. Anyone else gets 404, so the fleet stays unenumerable.

get/v1/nodes/{nodeId}/reservations/units

Path parameters

nodeIdstring required

Response

OK

allocClassstring required

vfio-group is the VM passthrough path and the only reservable one. device-request is scheduled by Nomad, so exclusivity cannot be enforced.

claimedBystring

What holds it, e.g. vm:<id>. Present when claimed.

gpuModelIdstring required
gpuModelNamestring
idstring required

Unit id, e.g. 0000:04:00.0. Pass this to create/release/reclaim.

notReservableReasonstring

Why not, when reservable is false.

releasedboolean

On the spot market right now (double sell).

reservableboolean required

Whether this unit can be put in a reservation.

reservationIdstring

The reservation governing it, when any.

sellableGpusinteger required

GPUs this unit sells; indivisible, they go together

statestring required

free | claimed