Sign in
Reservations

End a reservation now (platform admin)

Returns the GPU units to the public pool immediately. Workloads the tenant is already running keep running; the node's owning org terminates them when it needs the capacity.

post/v1/nodes/{nodeId}/reservations/{id}/cancel

Path parameters

nodeIdstring required
idstring required

Response

OK

allowedOrgIdsstring[] required

The audience: orgs that may place workloads on the reserved units.

contractRefstring
createdAtstring
endsAtstring

Absent = open-ended until cancelled

idstring required
managingOrgIdsstring[]

Orgs that may release these units to the market, reclaim them, and terminate the spot workloads on them, on the node owner's behalf. Being in the audience does not confer this.

nodeIdstring required
reasonstring
releasedUnitIdsstring[]

The subset of reservedUnitIds currently on the spot market (double sell). Still this reservation's capacity, sellable to anyone at tier=spot only, and reclaimable at any time.

reservedUnitIdsstring[] required
skippedstring[]

Reclaim only: VM ids left running because they are not spot.

startsAtstring required
status'pending' | 'active' | 'expired' | 'cancelled' | 'needs-review' required

needs-review means the node's GPU topology changed under the reservation: it grants nothing (and withholds its units from everyone) until an operator re-affirms it.

terminatedstring[]

Reclaim only: spot VM ids terminated to free the reclaimed units.

topologyGeninteger

Node topology generation this reservation was written against

updatedAtstring
wouldSkipstring[]

Reclaim dry run only: VM ids that would be left running.

wouldTerminatestring[]

Reclaim dry run only: the spot VM ids this call would terminate.

Changes

Changed in 1 of the 19 revisions of this API.6

  • 138b4ef69d2f6See the full diff
    • ○

      added the optional property managingOrgIds to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property releasedUnitIds to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property skipped to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property terminated to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property wouldSkip to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property wouldTerminate to the response with the 200 status

      response-optional-property-added