Reserved Hardware

Reserved hardware gives you the ability to reserve specific servers for a committed period of time. Unlike hourly on-demand, once you reserve hardware, you will have access to that specific hardware for the duration of the reservation. For additional information, it is suggested to reach out to your specific account manager. If you do not yet have one, please email [email protected]

Deploy via Portal

Once you have reserved hardware assigned to your project, you can go to the deploy page and there you will see a section where you can provision your reserved servers as shown here:

deploy via portal 1

When hardware is reserved to your account, the next prompt will allow allow to choose which hardware device, and OS

deploy via portal 2

Moving Reservations between Projects

Moving hardware reservations between projects within the same organization can be done from the customer portal under Organization Settings > Reserved Hardware:

moving a reservation 1

From here, you can also copy your hardware reservation full ID by hovering on each reservation ID.

Click Manage:

moving a reservation 2

Click Assign to new Project & choose your specific project name:

moving a reservation 3

API Endpoints

There is also API endpoints to interact with these hardware reservations.

To get a list of all hardware reservations:

curl -X GET -H 'X-Auth-Token: token' ''

By using some jq magic we are able to clean out up the json output to a readable printout:

  "id": "2e0e16b8-8824-44b8-bbcd-9d209adedc5d",
  "provisionable": false

  "id": "32ffabf2-26e4-4664-9277-2fc035756bb6",
  "provisionable": true

  "id": "202f186b-b773-499c-bh59-35676d4261a5",
  "provisionable": true

To create a device using a specific hardware reservation, there is a new JSON parameter hardware_reservation_id, e.g.

POST<id>/devices -d '{"hardware_reservation_id":"uuid"}'

An example of provisioning reserved hardware in EWR:

curl -X POST \
-H "Content-Type: application/json" \
-H "X-Auth-Token: token" \
"" \
-d '{
  "hostname": "ewr-reserved",
  "operating_system": "ubuntu_16_04_image"

An example of provisioning next available reserved hardware:

  "hardware_reservation_id": "next-available",
  "plan": "baremetal_1",
  "facility": "abc1",
  "operating_system": "coreos_stable",
  "tags": ["database", "primary"],
  "locked": true

Was it helpful?