Create shared future reservation requests

This document explains how to create shared future reservation requests.

If Google Cloud approves your shared future reservation request, then, at the start time specified in your request, Compute Engine automatically creates reservations that are shared across multiple projects. These auto-created shared reservations are consumed by matching VMs and existing reservations in the project that hosts the future reservation (owner project) and the projects the future reservation is shared with (consumer projects). For more information about how the auto-created shared reservations work and can be consumed, see Create shared reservations.

Before you begin

If you haven't already:
- Review the best practices for shared on-demand reservations.
- Review how future reservations work.
- To make sure that you have sufficient quota for the resources that you want to reserve, check your quota.
If you haven't already, set up authentication. Authentication is the process by which your identity is verified for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine as follows.

Select the tab for how you plan to use the samples on this page:
Console

When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloud
1. Install the Google Cloud CLI, then initialize it by running the following command:
```
gcloud init
```
  Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
2. Set a default region and zone.
REST

To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.

Required roles

To get the permissions that you need to create shared future reservation requests, ask your administrator to grant you the Compute Future Reservation User (roles/compute.futureReservationUser) IAM role on the project. For more information about granting roles, see Manage access.

This predefined role contains the permissions required to create shared future reservation requests. To see the exact permissions that are required, expand the Required permissions section:

Required permissions

The following permissions are required to create shared future reservation requests:

To create a future reservation request: compute.futureReservations.create on the project
To let Compute Engine auto-create reservations: compute.reservations.create on the project
To specify an instance template: compute.instanceTemplates.useReadOnly on the instance template

You might also be able to get these permissions with custom roles or other predefined roles.

Restrictions

In addition to the general restrictions for future reservations, creating shared future reservation requests has the following restrictions:

The project you use to create shared future reservation requests (the owner project) must be added to the allowlist for the Shared Reservations Owner Projects (compute.sharedReservationsOwnerProjects) organization policy constraint by an organization policy administrator. For more information, see Allow and restrict projects to create and modify shared reservations in the Compute Engine reservations documentation.
If you move a project that created a shared future reservation request to a different organization, the shared future reservation is deleted. The project is not automatically removed from the Shared Reservations Owner Projects (compute.sharedReservationsOwnerProjects) organizational policy constraint, but you can remove the project from this constraint if desired.
Each shared future reservation request can be shared with up to 100 consumer projects.
For each organization, you can create up to 100 shared future reservation requests for each unique combination of VM properties.

Create a shared future reservation request

This section explains how to create a shared future reservation request.

After you create a shared future reservation request, it can be canceled, deleted, or modified by the owner project only. However, the auto-created reservations can be consumed by the owner project and any consumer project the shared future reservation request is shared with.

Warning: After a future reservation request is submitted, approved by Google Cloud, and past its lock time, you can delete the future reservation and its auto-created reservations only after the end time of the future reservation's reservation period. Thus, before creating a future reservation request, make sure of the following:

Any existing reservations or future reservations in a project restrict the share settings of the future reservation requests you can create. To ensure that you can successfully create a future reservation request, and your request doesn't cause issues in other projects you share future reservations or reservations with, see Restrictions.
You must commit to pay for the reserved resources that Compute Engine provisions for the entire reservation period, regardless if the auto-created reservations are used or not. For more information, see Billing.

To consume an auto-created reservation for a future reservation, a VM must have properties that exactly match that reservation. To specify the properties of the VMs that you want to request to reserve by creating a future reservation request, select one of the following methods:

Recommended: Specify an instance template

This section explains how to use an existing instance template to define the properties of a shared future reservation request. By using an instance template, you can define the properties of a future reservation request and the VMs that can consume the auto-created reservations in the same place. However, because templates are project-specific, you can't use the same template to create VMs that can consume the auto-created reservations outside of the project that created the future reservation request. For the projects the future reservation is shared with, you must create similar templates in those projects or create VMs by specifying properties directly.
Specify properties directly

This section explains how to directly define the properties of a shared future reservation request. This method requires you to manually ensure that the properties of your VMs and the auto-created reservations match exactly—any mismatched properties prevent consumption.

An auto-created reservation for a future reservation can be automatically consumed by any VMs with matching properties. If you want to avoid a VM to consume any of these auto-created reservations, see how to create VMs without consuming reservations.

Specify an instance template

You can create a shared future reservation by specifying an existing instance template using the Google Cloud console, gcloud CLI, and REST.

Caution: Before using an instance template to create a future reservation request, make sure of the following:

An instance template contains project-specific settings, so you can only access and use an instance template within the same project. If you create a shared future reservation request by specifying an instance template, you must create similar templates to create VMs, or create VMs by specifying matching properties directly, to consume the auto-created reservations in each consumer project.
You must create your future reservation request in the same region and zone as the resources within the instance template. Any regional or zonal resources that are specified in an instance template—such as a machine type or a disk—restrict the use of the template to the locations where those resources are located. For example, if your instance template specifies an existing disk in the us-central1-a zone, then you must create your future reservation request in the same zone. Otherwise, creating the future reservation request fails.

To check if an existing template specifies any resources that bind the template to a specific region or zone, view the details of the template and look for references to regional or zonal resources inside of it.
After you create a future reservation request, you can't modify the future reservation request to override the template's VM properties or specify another template. Instead, you must create a new future reservation request with your desired updates.

Console

To create a shared future reservation request by specifying an instance template, follow these steps:

In the Google Cloud console, go to the Reservations page.

Go to Reservations
Click the Future reservations tab.
Click Create future reservation.

The Create a future reservation page opens.
In the Name field, enter a name for your future reservation request.
In the Prefix field, enter a name prefix. The name of each auto-created reservation from this future reservation request starts with this prefix.

To help you identify the auto-created reservations for this future reservation request, specifying an unique name prefix is recommended.
Optional: In the Description field, enter a description for your future reservation request.
In the Region field, select the region to reserve resources in.
In the Zone field, select the zone to reserve resources in.
In the Start time field, enter a start time for the reservation period. The start time can't be later than 1 year from the date and time at which you submit a future reservation request for review.

Make sure to specify a recommended value for the start time to ensure that you have sufficient time before your future reservation enters its lock time.
In the End time field, enter an end time for the reservation period. The reservation period must last at least 24 hours.

In the Duration summary section, you can see the length of the reservation period. To increase the likelihood that Google Cloud approves your future reservation request after submitting it for review, make sure to specify a recommended value for the reservation period.
In the Share type section, do the following:
1. To specify a shared future reservation request, click Shared.
2. Click Add projects, and then select the projects from the current project's organization that you want to share the future reservation request with.
  
  You can select up to 100 projects. Don't select the current project. By default, it is already allowed to consume the auto-created reservations for this future reservation request.
In the Number of VM instances field, enter the total count of VMs that you want reserved for the period, VM configuration, and project(s) specified in this future reservation request.

When calculating the amount of new reservations to create for an approved future reservation request shortly before the start time, Compute Engine subtracts any existing reservations that match the request from this total. For more information, see how Compute Engine counts and provisions reserved resources.

Caution: Make sure that you have sufficient quota for the resources that you're requesting to reserve. Otherwise, Google Cloud declines your future reservation request.
In the Machine configuration section, do the following:
1. To specify the properties of your VMs using an existing instance template, select Use instance template.
2. In the Instance template field, select the instance template of your choice. If you select a regional instance template, you can only reserve resources within the region where the instance template is located.
In the Auto-generated reservations auto-delete time section, do one of the following:
- To enable Compute Engine to automatically delete the auto-created reservations for your future reservation request, do the following:
  
  Caution: If the auto-delete option is enabled, all the auto-created reservations are deleted at the specified deletion time regardless if they're fully consumed or not.
  1. Click the Enable auto-delete toggle to the on position (default).
  2. Optional: In the Auto-delete time field, enter a new date and time when to delete the auto-created reservations. The date and time must be after the end time of the reservation period. If you leave this field empty, the auto-created reservations are deleted within 2 hours after the end time of the reservation period.
- Otherwise, click the Enable auto-delete toggle to the off position.
Do one of the following:
- To create a future reservation request and submit it for review to Google Cloud, click Submit.
  
  Caution: Make sure a future reservation request is ready for review before submitting it. After it is submitted, you can't revert back to drafting.
- To create a drafting future reservation request, click Save draft.
- To exit without saving, click Cancel.

The Reservations page opens. Creating the future reservation request can take up to a minute to complete.

gcloud

To create a shared future reservation request by specifying an instance template, use the gcloud beta compute future-reservations create command with the --source-instance-template flag.

gcloud beta compute future-reservations create FUTURE_RESERVATION_NAME \
    --auto-delete-auto-created-reservations \
    --description="DESCRIPTION" \
    --name-prefix=NAME_PREFIX \
    --planning-status=PLANNING_STATUS \
    --project=PROJECT_ID \
    --share-setting=projects \
    --share-with=CONSUMER_PROJECT_IDS \
    --source-instance-template=projects/PROJECT_ID/LOCATION/instanceTemplates/INSTANCE_TEMPLATE_NAME \
    --start-time=START_TIME \
    --end-time=END_TIME \
    --total-count=TOTAL_COUNT \
    --zone=ZONE

Replace the following:

FUTURE_RESERVATION_NAME: the name of the future reservation request to create.

DESCRIPTION: Optional. A description for the future reservation request.

NAME_PREFIX: the name prefix of the future reservation request. The name of each auto-created reservation for this future reservation request starts with the name prefix. To help you identify the auto-created reservations for this future reservation request, specifying an unique name prefix is recommended.
PLANNING_STATUS: Optional. The planning status of the future reservation request, which must be one of the following:
- To create the draft of a future reservation request, specify DRAFT.
- To create the future reservation request and submit it for approval to Google Cloud, specify SUBMITTED.
  
  Caution: After a future reservation request is submitted for review, you can't change its planning status back to DRAFT.
If you omit the --planning-status flag, its value is set to DRAFT.
PROJECT_ID: the ID of the project where you want to reserve resources and where the instance template is located.

CONSUMER_PROJECT_IDS: a comma-separated list of the project IDs of projects that this future reservation request can be shared with. For example, specify project-1,project-2. You can specify up to 100 projects. These projects must be in the same organization as the project where the future reservation request is created (the owner project). Don't specify the owner project. By default, it is already allowed to consume the auto-created reservations for this future reservation request.

LOCATION: the location of the instance template. Specify one of the following values:
- For a global instance template: global.
- For a regional instance template: regions/REGION. Replace REGION with the region where the instance template is located. If you specify a regional instance template, you can only reserve VMs within the region where the instance template is located.
INSTANCE_TEMPLATE_NAME: the name of an existing instance template. If you specify an instance template, you can't override its properties when creating the future reservation request. Otherwise, you encounter errors.

START_TIME: the start time of the reservation period formatted as an RFC 3339 timestamp, which must be as follows:
```
YYYY-MM-DDTHH:MM:SSOFFSET
```
Replace the following:
- YYYY-MM-DD: a data formatted as a 4-digit year, 2-digit month, and a 2-digit day of the month, separated by hyphens (-).
- HH:MM:SS: a time formatted as a 2-digit hour using a 24-hour time, 2-digit minutes, and 2-digit seconds, separated by colons (:).
- OFFSET: the time zone formatted as an offset of Coordinated Universal Time (UTC). For example, to use the Pacific Standard Time (PST), specify -08:00. Alternatively, to use no offset, specify Z.
The start time can't be later than 1 year from the date and time at which you submit a future reservation request for review. To have sufficient time to optionally cancel, delete, or modify a future reservation request after it's approved or before it enters its lock time, make sure to specify a recommended value for the start time.
END_TIME: the end time of the reservation period formatted as an RFC 3339 timestamp. The reservation period must last at least 24 hours. Alternatively, you can replace the --end-time flag with the --duration=END_DURATION flag where END_DURATION is the duration of the reservation period in seconds. For example, specify 1209600 for 1,209,600 seconds (14 days).

To increase the likelihood that Google Cloud approves a future reservation request after you submit it for review, make sure to specify one of the recommended values for your reservation period.

Important: Make sure that your reservation period doesn't overlap with the reservation period of another existing future reservation request with matching VM properties and zone, and that was created in or is shared with your current project. Otherwise, creating the future reservation request fails.
TOTAL_COUNT: the total number of VMs that you want reserved for the period, VM configuration, and project(s) specified in this future reservation request.

When calculating the number of reservations to create for an approved future reservation, Compute Engine first checks for existing reservations. If there are existing reservations that match the approved future reservation, the number of existing reservations is subtracted from the requested total number of reservations in the request to determine the number of new reservations that Compute Engine creates. For more information, see how Compute Engine counts and provisions reserved resources.

Caution: Make sure that you have sufficient quota for the resources that you're requesting to reserve. Otherwise, Google Cloud declines your future reservation request.
ZONE: the zone to reserve resources in.

When you specify the --auto-delete-auto-created-reservations flag, Compute Engine automatically deletes the auto-created reservations for your future reservation request. By default, the deletion time is within 2 hours after the end time of the reservation period. Optionally, you can change this by doing one of the following:

To delete the auto-created reservations after the end time of the reservation period, select one of the following methods:

Caution: If you enable the auto-delete option, all the auto-created reservations are deleted at the specified deletion time regardless if they're fully consumed or not.
- To delete the auto-created reservations at a specific time after the end time of the reservation period, specify the --auto-delete-auto-created-reservations and --auto-created-reservations-delete-time flags.
```
gcloud beta compute future-reservations create example-future-reservation \
    --auto-delete-auto-created-reservations \
    --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME \
    ...
```
  Replace AUTO_CREATED_RESERVATIONS_DELETE_TIME with a date and time formatted as an RFC 3339 timestamp.
- To delete the auto-created reservations after a specific duration after the end time of the reservation period, specify the --auto-delete-auto-created-reservations and --auto-created-reservations-duration flags.
```
gcloud beta compute future-reservations create example-future-reservation \
    --auto-delete-auto-created-reservations \
    --auto-created-reservations-duration=DURATION_BEFORE_DELETE \
    ...
```
  Replace DURATION_BEFORE_DELETE with a duration in days, hours, minutes or seconds. For example, specify 30m for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 seconds.
To disable Compute Engine from automatically deleting the auto-created reservations, specify the --no-auto-delete-auto-created-reservations flag. You must disable the auto-delete option if you want to attach your auto-created reservation to a commitment.
```
gcloud beta compute future-reservations create example-future-reservation \
    --no-auto-delete-auto-created-reservations \
    ...
```

For example, the following command creates a draft future reservation request using the example-template global instance template for 80 VMs. The future reservation request is shared with project-1 and project-2. The reservation period starts at midnight on November 10, 2023 UTC, and ends at midnight on December 10, 2023 UTC. The auto-created reservations for the future reservation get created in zone us-central1-a, have a name that starts with fr-02-reservation, and are automatically deleted at midnight on December 13, 2023 UTC.

gcloud beta compute future-reservations create fr-02 \
    --auto-delete-auto-created-reservations \
    --auto-created-reservations-delete-time=2023-12-13T00:00:00Z \
    --name-prefix=fr-02-reservation \
    --planning-status=DRAFT \
    --project=example-project \
    --share-setting=projects \
    --share-with=project-1,project-2 \
    --source-instance-template=projects/example-project/global/instanceTemplates/example-template \
    --start-time=2023-11-10T00:00:00Z \
    --end-time=2023-12-10T00:00:00Z \
    --total-count=80 \
    --zone=us-central1-a

REST

To create a shared future reservation request by specifying an instance template, make a POST request to the beta.futureReservations.insert method.

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/zones/ZONE/futureReservations

{
  "autoDeleteAutoCreatedReservations": "AUTO_DELETE_AUTO_CREATED_RESERVATIONS",
  "description": "DESCRIPTION",
  "name": "FUTURE_RESERVATION_NAME",
  "namePrefix": "NAME_PREFIX",
  "planningStatus": "PLANNING_STATUS",
  "shareSettings": {
    "projects": [
      "CONSUMER_PROJECT_ID_1",
      "CONSUMER_PROJECT_ID_2"
    ],
    "shareType": "SPECIFIC_PROJECTS"
  },
  "specificSkuProperties": { 
    "sourceInstanceTemplate": "projects/PROJECT_ID/LOCATION/instanceTemplates/INSTANCE_TEMPLATE_NAME",
    "totalCount": "TOTAL_COUNT"
  },
  "timeWindow": {
    "startTime": "START_TIME",
    "endTime": "END_TIME"
  }
}

Replace the following:

PROJECT_ID: the ID of the project where you want to reserve resources and where the instance template is located.
ZONE: the zone where you want to reserve resources.
AUTO_DELETE_AUTO_CREATED_RESERVATIONS: if you set this field to true, Compute Engine automatically deletes the auto-created reservations for this future reservation request regardless if they're fully consumed or not. Set this field to false if you want to attach your auto-created reservation to a commitment.

By default, the deletion time is within 2 hours after the end time of the reservation period. To change this, do one of the following:
- To delete the auto-created reservations after a specific time after the end of your reservation period, set the autoDeleteAutoCreatedReservations to true and specify the autoCreatedReservationsDeleteTime field.
```
POST https://compute.googleapis.com/compute/beta/projects/example-project/zones/us-central1-a/futureReservations

{
  "autoDeleteAutoCreatedReservations": "true",
  "autoCreatedReservationsDeleteTime": "DELETE_TIME",
  ...
}
```
  Replace DELETE_TIME with a date and time when Compute Engine deletes the auto-created reservations. The date and time must be formatted as an RFC 3339 timestamp, which must be as follows:
```
YYYY-MM-DDTHH:MM:SSOFFSET
```
  Replace the following:
  - YYYY-MM-DD: a data formatted as a 4-digit year, 2-digit month, and a 2-digit day of the month, separated by hyphens (-).
  - HH:MM:SS: a time formatted as a 2-digit hour using a 24-hour time, 2-digit minutes, and 2-digit seconds, separated by colons (:).
  - OFFSET: the time zone formatted as an offset of the Coordinated Universal Time (UTC) time zone. For example, to use the Pacific Standard Time (PST) time zone, specify -08:00. Alternatively, to use no offset, specify Z.
- To delete the auto-created reservations after a specific duration from the start time of the reservation period, set the autoDeleteAutoCreatedReservations to true and specify the autoCreatedReservationsDuration field.
```
POST https://compute.googleapis.com/compute/beta/projects/example-project/zones/us-central1-a/futureReservations

{
  "autoDeleteAutoCreatedReservations": "true",
  "autoCreatedReservationsDuration": {
    "seconds": "DURATION_BEFORE_DELETE"
  },
  ...
}
```
  Replace DURATION_BEFORE_DELETE with a duration in seconds. For example, specify 604800 for 604,800 seconds (7 days).
DESCRIPTION: Optional. A description for the future reservation request.
FUTURE_RESERVATION_NAME: the name of the future reservation request to create.
NAME_PREFIX: the name prefix of the future reservation request. The name of each auto-created reservation for this future reservation request starts with the name prefix. To help you identify the auto-created reservations for this future reservation request, specifying an unique name prefix is recommended.

CONSUMER_PROJECT_ID_1 and CONSUMER_PROJECT_ID_2: the project IDs of projects that this future reservation request can be shared with. You can specify up to 100 projects. These projects must be in the same organization as the project where the future reservation request is created (the owner project). Don't specify the owner project. By default, it is already allowed to consume the auto-created reservations for this future reservation request.

PLANNING_STATUS: Optional. The planning status of the future reservation request, which must be one of the following:
- To create the draft of a future reservation request, specify DRAFT.
- To create the future reservation request and submit it for approval to Google Cloud, specify SUBMITTED.
  
  Caution: After a future reservation request is submitted for review, you can't change its planning status back to DRAFT.
If you omit the planningStatus field, its value is set to DRAFT.

LOCATION: the location of the instance template. Specify one of the following values:
- For a global instance template: global.
- For a regional instance template: regions/REGION. Replace REGION with the region where the instance template is located. If you specify a regional instance template, you can only reserve VMs within the region where the instance template is located.
INSTANCE_TEMPLATE_NAME: the name of an existing instance template. If you specify an instance template, you can't override its properties when creating the future reservation request. Otherwise, you encounter errors.

TOTAL_COUNT: the total number of VMs that you want reserved for the period, VM configuration, and project(s) specified in this future reservation request.

When calculating the number of reservations to create for an approved future reservation, Compute Engine first checks for existing reservations. If there are existing reservations that match the approved future reservation, the number of existing reservations is subtracted from the requested total number of reservations in the request to determine the number of new reservations that Compute Engine creates. For more information, see how Compute Engine counts and provisions reserved resources.

Caution: Make sure that you have sufficient quota for the resources that you're requesting to reserve. Otherwise, Google Cloud declines your future reservation request.
START_TIME: the start time of the reservation period formatted as an RFC 3339 timestamp. The start time can't be later than 1 year from the date and time at which you submit a future reservation request for review. Additionally, make sure to specify a recommended value for the start time to ensure that you have sufficient time before a future reservation enters its lock time.
END_TIME: the end time of the reservation period formatted as an RFC 3339 timestamp. The reservation period must last at least 24 hours. Alternatively, you can replace the endTime field with the duration field to specify a specific duration from the start time of the reservation period:
```
"duration": {
  "seconds": "END_DURATION"
}
```
Replace END_DURATION with a duration in seconds. For example, specify 1209600 for 1,209,600 seconds (14 days).

To increase the likelihood that Google Cloud approves a future reservation request after you submit it for review, make sure to specify one of the recommended values for your reservation period.

Important: Make sure that your reservation period doesn't overlap with the reservation period of another existing future reservation request with matching VM properties and zone, and that was created in or is shared with your current project. Otherwise, creating the future reservation request fails.

POST https://compute.googleapis.com/compute/beta/projects/example-project/zones/us-central1-a/futureReservations

{
  "autoDeleteAutoCreatedReservations": "true",
  "autoCreatedReservationsDeleteTime": "2023-12-13T00:00:00Z",
  "name": "fr-02",
  "namePrefix": "fr-02-reservation",
  "specificSkuProperties": { 
    "sourceInstanceTemplate": "projects/example-project/global/instanceTemplates/example-template",
    "totalCount": "80"
  },
  "planningStatus": "DRAFT",
  "shareSettings": {
    "projects": [
      "project-1",
      "project-2"
    ],
    "shareType": "SPECIFIC_PROJECTS"
  },
  "timeWindow": {
    "startTime": "2023-11-10T00:00:00Z",
    "endTime": "2023-12-10T00:00:00Z"
  }
}

Specify VM properties directly

You can create a shared future reservation request by specifying properties directly using the Google Cloud console, gcloud CLI, and REST.

Console

To create a shared future reservation request by specifying properties directly, follow these steps:

In the Google Cloud console, go to the Reservations page.

Go to Reservations
Click the Future reservations tab.
Click Create future reservation.

The Create a future reservation page opens.
In the Name field, enter a name for your future reservation request.
In the Prefix field, enter a name prefix. The name of each auto-created reservation from this future reservation request starts with this prefix.

To help you identify the auto-created reservations for this future reservation request, specifying an unique name prefix is recommended.
Optional: In the Description field, enter a description for your future reservation request.
In the Region field, select the region to reserve resources in.
In the Zone field, select the zone to reserve resources in.
In the Start time field, enter a start time for the reservation period. The start time can't be later than 1 year from the date and time at which you submit a future reservation request for review.

Make sure to specify a recommended value for the start time to ensure that you have sufficient time before your future reservation enters its lock time.
In the End time field, enter an end time for the reservation period. The reservation period must last at least 24 hours.

In the Duration summary section, you can see the length of the reservation period. To increase the likelihood that Google Cloud approves your future reservation request after submitting it for review, make sure to specify a recommended value for the reservation period.
In the Share type section, do the following:
1. To specify a shared future reservation request, click Shared.
2. Click Add projects, and then select the projects from the current project's organization that you want to share the future reservation request with.
  
  You can select up to 100 projects. Don't select the current project. By default, it is already allowed to consume the auto-created reservations for this future reservation request.
In the Number of VM instances field, enter the total count of VMs that you want reserved for the period, VM configuration, and project(s) specified in this future reservation request.

When calculating the amount of new reservations to create for an approved future reservation request shortly before the start time, Compute Engine subtracts any existing reservations that match the request from this total. For more information, see how Compute Engine counts and provisions reserved resources.

Caution: Make sure that you have sufficient quota for the resources that you're requesting to reserve. Otherwise, Google Cloud declines your future reservation request.
In the Machine configuration section, do the following:
1. Select Specify machine type (default).
2. Select one of the following options:
  - For common workloads, click the General purpose tab (default).
  - For performance-intensive workloads, click the Compute optimized tab.
  - For high memory-to-vCPUs ratios workloads, click the Memory optimized tab.
  - For workloads that use Graphics processing units (GPUs), click the GPUs tab.
3. Do one of the following:
  - If you specified General purpose, Compute optimized, or Memory optimized in the previous step, do the following:
    1. In the Series list, select a machine series.
    2. In the Machine type list, select a machine type.
    3. Optional: To further customize the machine for the VMs you're requesting to reserve, expand Advanced configurations and follow the prompts.
  - If you specified GPUs in the previous step, do the following:
    1. In the GPU type menu, select a type of GPU.
    2. In the Number of GPUs menu, select the number of GPUs.
    3. Optional: If the GPU type allows it and you want to use the reserved resources to run graphics-intensive workloads, select the Enable Virtual Workstation (NVIDIA GRID) checkbox.
    4. In the Machine type list, select a machine type.
    5. In the CPU platform list, select a CPU platform for the VMs you're requesting to reserve.
4. Optional: If the machine type allows it and you want to add local SSDs, do the following:
  1. In the Number of disks field, select the number of disks for your local SSDs.
  2. In the Interface type section, select one of the following interfaces:
    - SCSI (default)
    - NVMe
In the Auto-generated reservations auto-delete time section, do one of the following:
- To enable Compute Engine to automatically delete the auto-created reservations for your future reservation request, do the following:
  
  Caution: If the auto-delete option is enabled, all the auto-created reservations are deleted at the specified deletion time regardless if they're fully consumed or not.
  1. Click the Enable auto-delete toggle to the on position (default).
  2. Optional: In the Auto-delete time field, enter a new date and time when to delete the auto-created reservations. The date and time must be after the end time of the reservation period. If you leave this field empty, the auto-created reservations are deleted within 2 hours after the end time of the reservation period.
- Otherwise, click the Enable auto-delete toggle to the off position.
Do one of the following:
- To create a future reservation request and submit it for review to Google Cloud, click Submit.
  
  Caution: Make sure a future reservation request is ready for review before submitting it. After it is submitted, you can't revert back to drafting.
- To create a drafting future reservation request, click Save draft.
- To exit without saving, click Cancel.

The Reservations page opens. Creating the future reservation request can take up to a minute to complete.

gcloud

To create a shared future reservation request by specifying properties directly, use the gcloud beta compute future-reservations create command.

gcloud beta compute future-reservations create FUTURE_RESERVATION_NAME \
    --accelerator=count=NUMBER_OF_ACCELERATORS,type=ACCELERATOR_TYPE \
    --auto-delete-auto-created-reservations \
    --description="DESCRIPTION" \
    --local-ssd=size=375,interface=INTERFACE_1 \
    --local-ssd=size=375,interface=INTERFACE_2 \
    --machine-type=MACHINE_TYPE \
    --min-cpu-platform=MIN_CPU_PLATFORM \
    --name-prefix=NAME_PREFIX \
    --planning-status=PLANNING_STATUS \
    --project=PROJECT_ID \
    --share-setting=projects \
    --share-with=CONSUMER_PROJECT_IDS \
    --start-time=START_TIME \
    --end-time=END_TIME \
    --total-count=TOTAL_COUNT \
    --zone=ZONE

Replace the following:

FUTURE_RESERVATION_NAME: the name of the future reservation request to create.

Optional: To add graphics processing units (GPUs) to each reserved VM, specify the following:
- NUMBER_OF_ACCELERATORS: the number of GPUs to add per reserved VM.
- ACCELERATOR_TYPE: the type of GPU to add to the reserved VMs.
Make sure that the machine type you specify in the future reservation request supports the types of GPUs you specify and that the GPU is available in the zone where you want to reserve resources. Otherwise, you encounter errors.

DESCRIPTION: Optional. A description for the future reservation request.

INTERFACE_1 and INTERFACE_2: Optional. The type of interface you want the local SSDs for each VM to use. The value must be one of the following:
- If your boot disk image has optimized NVMe drivers, specify nvme.
- Otherwise, specify scsi.
Each local SSD is 375 GB. Repeat the --local-ssd flag for each local SSD that you want to add. You can specify a maximum of 24 local SSDs.
MACHINE_TYPE: a machine type to use for each VM. Specify one of the following values:
- For a predefined machine type: MACHINE_FAMILY-standard-CPUS.
- For a custom machine type: MACHINE_FAMILY-custom-CPUS-MEMORY. Before specifying a custom machine type, review the limitations for VMs with custom machine types.
Replace the following:
- MACHINE_FAMILY: the machine family.
- CPUS: the number of vCPUs.
- MEMORY: the total memory for a reserved VM. Memory must be a multiple of 256 MB and must be supplied in MB.
For example, to specify an N2 custom machine type with 4 vCPUs and 5 GB of memory, which is 5,120 MB, specify n2-custom-4-5120.
MINIMUM_CPU_PLATFORM: Optional. The minimum CPU platform to use for each VM. If you omit the --min-cpu-platform flag, its value is set to the zone's default CPU platform.

NAME_PREFIX: the name prefix of the future reservation request. The name of each auto-created reservation for this future reservation request starts with the name prefix. To help you identify the auto-created reservations for this future reservation request, specifying an unique name prefix is recommended.
PLANNING_STATUS: Optional. The planning status of the future reservation request, which must be one of the following:
- To create the draft of a future reservation request, specify DRAFT.
- To create the future reservation request and submit it for approval to Google Cloud, specify SUBMITTED.
  
  Caution: After a future reservation request is submitted for review, you can't change its planning status back to DRAFT.
If you omit the --planning-status flag, its value is set to DRAFT.
PROJECT_ID: the ID of the project where you want to reserve resources.

CONSUMER_PROJECT_IDS: a comma-separated list of the project IDs of projects that this future reservation request can be shared with. For example, specify project-1,project-2. You can specify up to 100 projects. These projects must be in the same organization as the project where the future reservation request is created (the owner project). Don't specify the owner project. By default, it is already allowed to consume the auto-created reservations for this future reservation request.

START_TIME: the start time of the reservation period formatted as an RFC 3339 timestamp, which must be as follows:
```
YYYY-MM-DDTHH:MM:SSOFFSET
```
Replace the following:
- YYYY-MM-DD: a data formatted as a 4-digit year, 2-digit month, and a 2-digit day of the month, separated by hyphens (-).
- HH:MM:SS: a time formatted as a 2-digit hour using a 24-hour time, 2-digit minutes, and 2-digit seconds, separated by colons (:).
- OFFSET: the time zone formatted as an offset of Coordinated Universal Time (UTC). For example, to use the Pacific Standard Time (PST), specify -08:00. Alternatively, to use no offset, specify Z.
The start time can't be later than 1 year from the date and time at which you submit a future reservation request for review. To have sufficient time to optionally cancel, delete, or modify a future reservation request after it's approved or before it enters its lock time, make sure to specify a recommended value for the start time.
END_TIME: the end time of the reservation period formatted as an RFC 3339 timestamp. The reservation period must last at least 24 hours. Alternatively, you can replace the --end-time flag with the --duration=END_DURATION flag where END_DURATION is the duration of the reservation period in seconds. For example, specify 1209600 for 1,209,600 seconds (14 days).

To increase the likelihood that Google Cloud approves a future reservation request after you submit it for review, make sure to specify one of the recommended values for your reservation period.

Important: Make sure that your reservation period doesn't overlap with the reservation period of another existing future reservation request with matching VM properties and zone, and that was created in or is shared with your current project. Otherwise, creating the future reservation request fails.
TOTAL_COUNT: the total number of VMs that you want reserved for the period, VM configuration, and project(s) specified in this future reservation request.

When calculating the number of reservations to create for an approved future reservation, Compute Engine first checks for existing reservations. If there are existing reservations that match the approved future reservation, the number of existing reservations is subtracted from the requested total number of reservations in the request to determine the number of new reservations that Compute Engine creates. For more information, see how Compute Engine counts and provisions reserved resources.

Caution: Make sure that you have sufficient quota for the resources that you're requesting to reserve. Otherwise, Google Cloud declines your future reservation request.
ZONE: the zone to reserve resources in.

To delete the auto-created reservations after the end time of the reservation period, select one of the following methods:

Caution: If you enable the auto-delete option, all the auto-created reservations are deleted at the specified deletion time regardless if they're fully consumed or not.
- To delete the auto-created reservations at a specific time after the end time of the reservation period, specify the --auto-delete-auto-created-reservations and --auto-created-reservations-delete-time flags.
```
gcloud beta compute future-reservations create example-future-reservation \
    --auto-delete-auto-created-reservations \
    --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME \
    ...
```
  Replace AUTO_CREATED_RESERVATIONS_DELETE_TIME with a date and time formatted as an RFC 3339 timestamp.
- To delete the auto-created reservations after a specific duration after the end time of the reservation period, specify the --auto-delete-auto-created-reservations and --auto-created-reservations-duration flags.
```
gcloud beta compute future-reservations create example-future-reservation \
    --auto-delete-auto-created-reservations \
    --auto-created-reservations-duration=DURATION_BEFORE_DELETE \
    ...
```
  Replace DURATION_BEFORE_DELETE with a duration in days, hours, minutes or seconds. For example, specify 30m for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 seconds.
To disable Compute Engine from automatically deleting the auto-created reservations, specify the --no-auto-delete-auto-created-reservations flag. You must disable the auto-delete option if you want to attach your auto-created reservation to a commitment.
```
gcloud beta compute future-reservations create example-future-reservation \
    --no-auto-delete-auto-created-reservations \
    ...
```

For example, the following command creates a draft future reservation request for 80 VMs. The future reservation request is shared with project-1 and project-2. The reservation period starts at midnight on November 10, 2023 UTC, and ends at midnight on December 10, 2023 UTC. The reserved VMs specify an n2-standard-4 machine type, a skylake minimum CPU platform, and 1 local SSD with the scsi interface and 375 GB each. The auto-created reservations for the future reservation get created in zone us-central1-a, have a name that starts with fr-02-reservation, and are automatically deleted at midnight on December 13, 2023 UTC.

gcloud beta compute future-reservations create fr-02 \
    --auto-delete-auto-created-reservations \
    --auto-created-reservations-delete-time=2023-12-13T00:00:00Z \
    --local-ssd=size=375,interface=scsi \
    --machine-type=n2-standard-4 \
    --min-cpu-platform=skylake \
    --name-prefix=fr-02-reservation \
    --planning-status=DRAFT \
    --project=example-project \
    --share-setting=projects \
    --share-with=project-1,project-2 \
    --start-time=2023-11-10T00:00:00Z \
    --end-time=2023-12-10T00:00:00Z \
    --total-count=80 \
    --zone=us-central1-a

REST

To create a shared future reservation request by specifying properties directly, make a POST request to the beta.futureReservations.insert method.

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/zones/ZONE/futureReservations

{
  "autoDeleteAutoCreatedReservations": "AUTO_DELETE_AUTO_CREATED_RESERVATIONS",
  "description": "DESCRIPTION",
  "name": "FUTURE_RESERVATION_NAME",
  "namePrefix": "NAME_PREFIX",
  "planningStatus": "PLANNING_STATUS",
  "shareSettings": {
    "projects": [
      "CONSUMER_PROJECT_ID_1",
      "CONSUMER_PROJECT_ID_2"
    ],
    "shareType": "SPECIFIC_PROJECTS"
  },
  "specificSkuProperties": { 
    "instanceProperties": {
      "guestAccelerators": [
        {
          "acceleratorCount": NUMBER_OF_ACCELERATORS,
          "acceleratorType": "ACCELERATOR_TYPE"
        }
      ],
      "localSsds": [
        {
          "diskSizeGb": "375",
          "interface": "INTERFACE_1"
        },
        {
          "diskSizeGb": "375",
          "interface": "INTERFACE_2"
        }
      ],
      "machineType": "MACHINE_TYPE",
      "minCpuPlatform": "MINIMUM_CPU_PLATFORM"
    },
    "totalCount": "TOTAL_COUNT"
  },
  "timeWindow": {
    "startTime": "START_TIME",
    "endTime": "END_TIME"
  }
}

Replace the following:

PROJECT_ID: the ID of the project where you want to reserve resources.
ZONE: the zone where you want to reserve resources.
AUTO_DELETE_AUTO_CREATED_RESERVATIONS: if you set this field to true, Compute Engine automatically deletes the auto-created reservations for this future reservation request regardless if they're fully consumed or not. Set this field to false if you want to attach your auto-created reservation to a commitment.

By default, the deletion time is within 2 hours after the end time of the reservation period. To change this, do one of the following:
- To delete the auto-created reservations after a specific time after the end of your reservation period, set the autoDeleteAutoCreatedReservations to true and specify the autoCreatedReservationsDeleteTime field.
```
POST https://compute.googleapis.com/compute/beta/projects/example-project/zones/us-central1-a/futureReservations

{
  "autoDeleteAutoCreatedReservations": "true",
  "autoCreatedReservationsDeleteTime": "DELETE_TIME",
  ...
}
```
  Replace DELETE_TIME with a date and time when Compute Engine deletes the auto-created reservations. The date and time must be formatted as an RFC 3339 timestamp, which must be as follows:
```
YYYY-MM-DDTHH:MM:SSOFFSET
```
  Replace the following:
  - YYYY-MM-DD: a data formatted as a 4-digit year, 2-digit month, and a 2-digit day of the month, separated by hyphens (-).
  - HH:MM:SS: a time formatted as a 2-digit hour using a 24-hour time, 2-digit minutes, and 2-digit seconds, separated by colons (:).
  - OFFSET: the time zone formatted as an offset of the Coordinated Universal Time (UTC) time zone. For example, to use the Pacific Standard Time (PST) time zone, specify -08:00. Alternatively, to use no offset, specify Z.
- To delete the auto-created reservations after a specific duration from the start time of the reservation period, set the autoDeleteAutoCreatedReservations to true and specify the autoCreatedReservationsDuration field.
```
POST https://compute.googleapis.com/compute/beta/projects/example-project/zones/us-central1-a/futureReservations

{
  "autoDeleteAutoCreatedReservations": "true",
  "autoCreatedReservationsDuration": {
    "seconds": "DURATION_BEFORE_DELETE"
  },
  ...
}
```
  Replace DURATION_BEFORE_DELETE with a duration in seconds. For example, specify 604800 for 604,800 seconds (7 days).
DESCRIPTION: Optional. A description for the future reservation request.
FUTURE_RESERVATION_NAME: the name of the future reservation request to create.
NAME_PREFIX: the name prefix of the future reservation request. The name of each auto-created reservation for this future reservation request starts with the name prefix. To help you identify the auto-created reservations for this future reservation request, specifying an unique name prefix is recommended.

CONSUMER_PROJECT_ID_1 and CONSUMER_PROJECT_ID_2: the project IDs of projects that this future reservation request can be shared with. You can specify up to 100 projects. These projects must be in the same organization as the project where the future reservation request is created (the owner project). Don't specify the owner project. By default, it is already allowed to consume the auto-created reservations for this future reservation request.

PLANNING_STATUS: Optional. The planning status of the future reservation request, which must be one of the following:
- To create the draft of a future reservation request, specify DRAFT.
- To create the future reservation request and submit it for approval to Google Cloud, specify SUBMITTED.
  
  Caution: After a future reservation request is submitted for review, you can't change its planning status back to DRAFT.
If you omit the planningStatus field, its value is set to DRAFT.

Optional: To add graphics processing units (GPUs) to each reserved VM, specify the following:
- NUMBER_OF_ACCELERATORS: the number of GPUs to add per reserved VM.
- ACCELERATOR_TYPE: the type of GPU to add to the reserved VMs.
Make sure that the machine type you specify in the future reservation request supports the types of GPUs you specify and that the GPU is available in the zone where you want to reserve resources. Otherwise, you encounter errors.
INTERFACE_1 and INTERFACE_2: Optional. The type of interface you want the local SSDs for each VM to use. The value must be one of the following:
- If your boot disk image has optimized NVMe drivers, specify NVME.
- Otherwise, specify SCSI.
Each local SSD is 375 GB. Repeat the --local-ssd flag for each local SSD that you want to add. You can specify a maximum of 24 local SSDs.
MACHINE_TYPE: a machine type to use for each VM. Specify one of the following values:
- For a predefined machine type: MACHINE_FAMILY-standard-CPUS.
- For a custom machine type: MACHINE_FAMILY-custom-CPUS-MEMORY. Before specifying a custom machine type, review the limitations for VMs with custom machine types.
Replace the following:
- MACHINE_FAMILY: the machine family.
- CPUS: the number of vCPUs.
- MEMORY: the total memory for a reserved VM. Memory must be a multiple of 256 MB and must be supplied in MB.
For example, to specify an N2 custom machine type with 4 vCPUs and 5 GB of memory, which is 5,120 MB, specify n2-custom-4-5120.
MINIMUM_CPU_PLATFORM: Optional. The minimum CPU platform to use for each VM. If you omit the --min-cpu-platform flag, its value is set to the zone's default CPU platform.

TOTAL_COUNT: the total number of VMs that you want reserved for the period, VM configuration, and project(s) specified in this future reservation request.

When calculating the number of reservations to create for an approved future reservation, Compute Engine first checks for existing reservations. If there are existing reservations that match the approved future reservation, the number of existing reservations is subtracted from the requested total number of reservations in the request to determine the number of new reservations that Compute Engine creates. For more information, see how Compute Engine counts and provisions reserved resources.

Caution: Make sure that you have sufficient quota for the resources that you're requesting to reserve. Otherwise, Google Cloud declines your future reservation request.
START_TIME: the start time of the reservation period formatted as an RFC 3339 timestamp. The start time can't be later than 1 year from the date and time at which you submit a future reservation request for review. Additionally, make sure to specify a recommended value for the start time to ensure that you have sufficient time before a future reservation enters its lock time.
END_TIME: the end time of the reservation period formatted as an RFC 3339 timestamp. The reservation period must last at least 24 hours. Alternatively, you can replace the endTime field with the duration field to specify a specific duration from the start time of the reservation period:
```
"duration": {
  "seconds": "END_DURATION"
}
```
Replace END_DURATION with a duration in seconds. For example, specify 1209600 for 1,209,600 seconds (14 days).

To increase the likelihood that Google Cloud approves a future reservation request after you submit it for review, make sure to specify one of the recommended values for your reservation period.

Important: Make sure that your reservation period doesn't overlap with the reservation period of another existing future reservation request with matching VM properties and zone, and that was created in or is shared with your current project. Otherwise, creating the future reservation request fails.

For example, the following command creates a draft future reservation request for 80 VMs. The future reservation request is shared with project-1 and project-2. The reservation period starts at midnight on November 10, 2023 UTC, and ends at midnight on December 10, 2023 UTC. The reserved VMs specify an n2-standard-4 machine type, a skylake minimum CPU platform, and 1 local SSD with the SCSI interface and 375 GB each. The auto-created reservations for the future reservation get created in zone us-central1-a, have a name that starts with fr-02-reservation, and are automatically deleted at midnight on December 13, 2023 UTC.

POST https://compute.googleapis.com/compute/beta/projects/example-project/zones/us-central1-a/futureReservations

{
  "autoDeleteAutoCreatedReservations": "true",
  "autoCreatedReservationsDeleteTime": "2023-12-13T00:00:00Z",
  "name": "fr-02",
  "namePrefix": "fr-02-reservation",
  "specificSkuProperties": { 
    "instanceProperties": {
      "localSsds": [
        {
          "diskSizeGb": "375",
          "interface": "SCSI"
        }
      ],
      "machineType": "n2-standard-4",
      "minCpuPlatform": "Skylake"
    },
    "totalCount": "80"
  },
  "planningStatus": "DRAFT",
  "shareSettings": {
    "projects": [
      "project-1",
      "project-2"
    ],
    "shareType": "SPECIFIC_PROJECTS"
  },
  "timeWindow": {
    "startTime": "2023-11-10T00:00:00Z",
    "endTime": "2023-12-10T00:00:00Z"
  }
}

Submit a draft future reservation request for review

You can submit a draft future reservation request to Google Cloud for review using the Google Cloud console, gcloud CLI, and REST. If you also want to modify one or more properties when submitting the draft future reservation request for review, see Modify a draft or declined future reservation request instead.

Console

To submit a draft future reservation request for review, follow these steps:

In the Google Cloud console, go to the Reservations page.

Go to Reservations
Click the Future reservations tab.
In the Name column, click the name of the a future reservation request with a procurement status of Drafting.

The Future reservations page with the details of the future reservation request opens.
Click Edit draft.

The details page of the draft future reservation request opens.
To submit the draft future reservation request for review to Google Cloud, click Submit.

The Reservation page opens. In the Status column of the future reservation request you've just submitted, the procurement status is set to Pending approval.

gcloud

To submit a draft future reservation request for review, use the gcloud beta compute future-reservations update command with the --planning-status flag set to SUBMITTED.

gcloud beta compute future-reservations update FUTURE_RESERVATION_NAME  \
    --planning-status=SUBMITTED \
    --project=PROJECT_ID \
    --zone=ZONE

Replace the following:

FUTURE_RESERVATION_NAME: the name of an existing draft future reservation request.
PROJECT_ID: the ID of the project where the future reservation request is located.
ZONE: the zone where the future reservation request is located.

REST

To submit a draft future reservation request for review, make a PATCH request to the beta.futureReservations.update method with the planningStatus field set to SUBMITTED.

PATCH https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/zones/ZONE/futureReservations/FUTURE_RESERVATION_NAME?updateMask=planningStatus

{
  "name": "FUTURE_RESERVATION_NAME",
  "planningStatus": "SUBMITTED"
}

Replace the following:

PROJECT_ID: the ID of the project where the future reservation request is located.
ZONE: the zone where the future reservation request is located.
FUTURE_RESERVATION_NAME: the name of an existing draft future reservation request.

After you submit a draft future reservation request for review, you can do the following:

To monitor the request's procurement status and see whether Google Cloud has approved or declined your request, then view the details of your future reservation request.
To stop Google Cloud from reviewing your request and prevent Compute Engine from provisioning the requested capacity, then cancel or delete your future reservation request.

Troubleshoot

If you run into errors when creating a future reservation request, see how to troubleshoot future reservation requests.

If you still encounter issues after troubleshooting, contact your Technical Account Manager or the Sales Team.

What's next

Learn how to view future reservation requests.
Learn how to modify, cancel, or delete future reservation requests.
After you reach the start time of your reservation period, learn how to consume the auto-created reservations.