Reservations
Crusoe Cloud is currently in private beta. If you do not currently have access, please request access to continue.
Crusoe Cloud offers competitive on-demand pricing along with the ability to purchase longer-term reserved instance agreements in exchange for discounted pricing, by working with Crusoe Cloud sales.
If you have signed a reserved instance agreement, you can view its details and manage utilization through reservations. A reservation represents an active reserved instance agreement, typically for a fixed quantity of a specific instance type (e.g. 128 A100-80GB GPUs) valid for a defined period of time.
Once you have an active reservation in your organization, VMs are automatically associated with this reservation upon creation (details below). You also have the option to explicitly associate VMs with active reservations, either during or post creation. All VMs associated with a reservation are covered under the payment terms of your reserved instance agreement.
VM <-> Reservation Association
If you have reservations in your organization, VMs are automatically placed in one during provisioning if they match the reservation type and there is adequate capacity. Once associated, VMs take up capacity equivalent to the number of GPUs they have (or the number of vCPUs for CPU VMs). For example, an l40s-48gb.10x VM associated with an empty 100 GPU reservation will occupy 10/100 spaces in the reservation, reducing available capacity to 90 GPUs post VM provisioning. You can also target a specific reservation when provisioning a VM, opt to provision the VM on-demand and associate a VM with a reservation post provisioning. A few other noteworthy points:
- Only running VMs occupy space in a reservation. Stopping a VM releases the equivalent amount of capacity on the reservation. The stopped VM will attempt to be placed back in the same reservation when restarted.
- When there are multiple available reservations, VMs are placed in the reservation with the lowest unit price. If unit prices match for multiple reservations, VMs will be provisioned in the reservation that has the least amount of available capacity.
- If you have no available reservation capacity when provisioning a VM and you have not specified a reservation explicitly, the VM will be provisioned on-demand.
Reservation Fields
Each reservation in your organization contains the following fields:
| Field Name | Description |
|---|---|
Reservation UUID | A unique UUID identifying a reservation, used across programmatic surfaces to specify a reservation. |
Reservation Name | A display name used to identify a reservation through the quantity, type, unit price and the first 8 UUID characters. e.g. '10 A100 GPUs - $1.35/hr - 06a2d842' |
Status | The state of the reservation. Can take any of the following values - 'Awaiting Delivery', 'Active' or 'Expired' |
Contract Start Date | The contract start date specified in your reserved instance agreement. |
Contract End Date | The contract end date specified in your reserved instance agreement. |
Usage | Reflects the total capacity of your reservation, along with how much is currently consumed by VMs associated with it. |
Unit Price | The unit price associated with the reservation GPU / vCPUs in your reserved instance agreement. |
Type | The instance type covered by the reservation. e.g. a100-80gb, c1a, h100, etc. |
Location Constraint | Specifies whether your reservation is constrained to a specific Crusoe Cloud region. |