SC26AI agents lab + dinner on the river · Nov 17
Parallel Works
View as Markdown
Share:

Capacity Reservations

Requiresorg:adminororg:settings

Navigation

From the Organizations list, select your organization. In the sidebar, under Cloud, click Reservations.

Overview

Map capacity reservation IDs to a budget so their charges are billed correctly. Reservation and capacity block fees carry no resource tags, so this mapping is the only way to attribute them.

  • On the flexible allocation system, each reservation maps to an Allocation.
  • On the legacy system, each reservation maps to a Group.

A mapped reservation takes priority over tags: usage that runs on the reservation, and the reservation's own charges, bill the mapped allocation or group, even if the resource that used it belongs to a different resource group. See Cost Attribution.

Prerequisites

Before adding a capacity reservation on ACTIVATE, you must first create the reservation in your CSP's management console:

Adding a Reservation

  1. Click Add reservation.
  2. Select the Cloud provider.
  3. Enter the Reservation ID from your CSP's management console:
    • AWS — the capacity reservation ID (cr-…) or capacity block extension ID (cbe-…).
    • Azure — the capacity reservation group resource ID.
    • Google — the reservation name, or projects/<project>/reservations/<name> for a shared reservation.
  4. Select the Allocation (flexible system) or Group (legacy system) that pays for the reservation. On the legacy system, access is limited to that group's members.
  5. Optionally, enter a Description and an Instance Type. When an instance type is set, cluster partitions that use this reservation are locked to it; leave it empty to let users pick any instance type.
  6. Click Add.

Reservation IDs are matched without regard to case.

Managing Reservations

Reservations appear in a table with their Reservation ID, Description, Instance Type, Cloud Provider, and Allocation or Group. Use the row menu to edit or delete a reservation.

Billing Behavior

  • New charges for a mapped reservation bill its allocation as soon as they are imported.
  • Earlier charges: after you map an AWS or Azure reservation, the reservation's own charges that were already imported are re-attributed to its allocation. Usage that ran on the reservation before it was mapped keeps its original attribution. For Google reservations, only charges imported after mapping are affected.
  • If a reservation's allocation is deleted, the reservation falls back to the allocation of the group it's mapped to, if any.