Console

1. In the Google Cloud console, go to theReservations page.

   Go to Reservations

2. Click theFuture reservations tab.

3. In theName column, click the name of the future reservation requestthat you want to modify.

   The details page of the selected future reservation request opens.

4. If you want to modify the auto-delete option, description, or nameprefix of an approved future reservation, then do one or more of thefollowing:

   • To modify the auto-delete option, in theAuto-created reservations auto-delete time row, clickeditEdit, and then do thefollowing:

     1. Specify if you want to enable, disable, or modify theauto-delete option by doing one of the following:

        • To enable the auto-delete option or change the time whenCompute Engine automatically deletes theauto-created reservations, do the following:

          1. Click theEnable auto-delete toggle to the onposition.

          2. Optional: ForAuto-delete time, enter a new date andtime when to delete the auto-created reservations. Thedate and time must be after the end time of thereservation period. If you leave this field empty, thenthe auto-created reservations are deleted within twohours after the reservation period's end time.

        • Otherwise, click theEnable auto-delete toggle to theoff position.

     2. ClickSubmit.

   • To modify the name prefix, in thePrefix row, clickeditEdit, and then do thefollowing:

     1. ForPrefix, enter a new name prefix.

     2. ClickSubmit.

   • To modify the description, in theDescription row, clickeditEdit, and then do thefollowing:

     1. ForDescription, enter a new description.

     2. ClickSubmit.

5. ClickeditEdit oreditEdit draft.

   The page to edit the selected future reservation request opens.

6. To modify a future reservation request and submit it toGoogle Cloud for review, or save the draft request, do one or moreof the following:

   • ForPrefix, enter a new name prefix for the auto-createdreservations provisioned for this future reservation request.

   • ForDescription, enter a new description.

   • Modify theStart time orEnd time for your futurereservation request. Make sure of the following:

     • The start time can't be later than one year from the date andtime at which you submit a future reservation request forreview.

     • Specify arecommended value for the start timeto help ensure that you have sufficient time before your futurereservation enters its lock time.

     • Specify arecommended minimum reservation periodto increase the likelihood that Google Cloud approves yourrequest after submitting it for review.

   • In theShare type section, you can select eitherLocal orShared. If you selectShared, you can add or remove projectsto share the future reservation request with. You can include up to100 projects.

   • ForNumber of VM instances, enter the total count of VMs thatyou want reserved.

     Caution: If you want to increase the number of VMs to reserve, thenverify that you have sufficient quota for the additional resourcesthat you're requesting to reserve. Otherwise, Google Clouddeclines your modification request.

   • If you're modifying a future reservation that wasn't created throughan instance template, then, in theMachine configurationsection, you can change the following:

     • The machine series and machine type used in the reserved VMs.

     • The GPUs to attach to the reserved VMs.

     • The Local SSD disks and the disk interface type of the reservedVMs.

   • In theAuto-generated reservations auto-delete section, you canenable or disable the automatic deletion of auto-createdreservations for your future reservation request.

7. Depending on the procurement status of the future reservation requestthat you're modifying, do one of the following:

   • If you're modifying a draft future reservation request, then do oneof the following:

     • To save your changes, clickSave draft.

     • To submit the draft future reservation request toGoogle Cloud for review, clickSubmit.

   • Otherwise, clickSubmit.

If you submit a modification request, then theReservations page opens.Otherwise, the details page of the future reservation opens.

gcloud

To modify a future reservation request, use thegcloud compute future-reservations update command.

gcloud compute future-reservations updateFUTURE_RESERVATION_NAME \    --accelerator=count=NUMBER_OF_ACCELERATORS,type=ACCELERATOR_TYPE \    --description="DESCRIPTION" \    --local-ssd=size=375,interface=INTERFACE \    --machine-type=MACHINE_TYPE \    --min-cpu-platform=MIN_CPU_PLATFORM \    --name-prefix=NAME_PREFIX \    --planning-status=PLANNING_STATUS \    --share-setting=SHARE_SETTING \    --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 futurereservation request.

• PLANNING_STATUS: the planning status of the futurereservation request. Specify one of the following values:

  • To modify a draft future reservation request without submitting itfor review:DRAFT.

  • To submit the future reservation request for review:SUBMITTED.

• ZONE: the zone where the future reservation requestis located.

Replace one or more of the following placeholders, or remove them along withtheir corresponding flags:

• To enable Compute Engine to automatically delete theauto-created reservations after the end time of the reservation period,do one of the following:

  • To delete the reservations within two hours after the end time(default), include the--auto-delete-auto-created-reservationsflag.

    gcloud compute future-reservations updateFUTURE_RESERVATION_NAME \--auto-delete-auto-created-reservations \    --planning-status=PLANNING_STATUS \    --zone=ZONE

  • To delete the auto-created reservations at a specific time after theend time of the reservation period, include the--auto-delete-auto-created-reservations and--auto-created-reservations-delete-time flags.

    gcloud compute future-reservations updateFUTURE_RESERVATION_NAME \--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME \--auto-delete-auto-created-reservations \    --planning-status=PLANNING_STATUS \    --zone=ZONE

    ReplaceAUTO_CREATED_RESERVATIONS_DELETE_TIMEwith a date and time formatted as anRFC 3339 timestamp.

  • To delete the auto-created reservations after a specific durationafter the end time of the reservation period, include the--auto-delete-auto-created-reservations and--auto-created-reservations-duration flags.

    gcloud compute future-reservations updateFUTURE_RESERVATION_NAME \--auto-created-reservations-duration=DURATION_BEFORE_DELETE \--auto-delete-auto-created-reservations \    --planning-status=PLANNING_STATUS \    --zone=ZONE

    ReplaceDURATION_BEFORE_DELETE with a duration indays, hours, minutes, or seconds. For example, specify30m for 30minutes, or1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 seconds.

• To disable Compute Engine from automatically deleting theauto-created reservations provisioned for this future reservationrequest, include the--no-auto-delete-auto-created-reservations flag.

  gcloud compute future-reservations updateFUTURE_RESERVATION_NAME \--no-auto-delete-auto-created-reservations \    --planning-status=PLANNING_STATUS \    --zone=ZONE

• To add or remove GPUs attached to reserved N1 VMs, or update the GPUtype, do one of the following:

  • To change the number and type of GPUs, replace the following:

    • NUMBER_OF_ACCELERATORS: the number of GPUs toadd per reserved VM.

    • ACCELERATOR_TYPE: the type of GPU to add tothe reserved VMs. Verify thatthe GPU is available in the zonewhere the future reservation request is located. Otherwise,modifying the request fails.

  • To remove all GPUs attached to reserved N1 VMs, replace the--accelerator flag with the--clear-accelerator flag.

• DESCRIPTION: A new description for your futurereservation request.

• To add or remove Local SSD disks from your reserved VMs, or edit theLocal SSD disk interface type, do one of the following:

  • To add Local SSD disks or edit the disk interface type, replace theINTERFACE with one of the following values:

    • If your boot disk imagehas optimized NVMe drivers:nvme.

    • Otherwise:scsi.

    Include the--local-ssd flag for as many Local SSD disks that youwant to add. You can specify a maximum of 24 Local SSD disks.

  • To remove all Local SSD disks attached to the reserved VMs, removeall--local-ssd flags and include the--clear-local-ssd flag.

• MACHINE_TYPE: The new machine type to use for eachreserved VM. If you change the machine type, then also specify arecommended minimum reservation periodfor the new machine series. Otherwise, Google Cloud is likely toto decline your modification request.

• MINIMUM_CPU_PLATFORM: A new minimum CPU platform touse for each reserved VM.

• NAME_PREFIX: A new name prefix for the auto-createdreservations provisioned for your future reservation request.

• SHARE_SETTING: A new share type for your futurereservation request. Specify one of the following values:

  • For a single-project future reservation request:local. To avoiderrors, you must also replace the--share-with flag with the--clear-share-settings flag.

  • For a shared future reservation request:projects. To avoiderrors, you must also specify at least one consumer project in the--share-with flag.

• CONSUMER_PROJECT_IDS: A comma-separated list of IDsof projects that you want to share your future reservation requestwith—for example,project-1,project-2. You can specify up to 100consumer projects.

• START_TIME: The new start time of the reservationperiod formatted as anRFC 3339 timestamp. The starttime can't be later than one year from the date and time at which yousubmit the modification request for review. To have sufficient time tooptionally cancel, delete, or modify a future reservation after it'sapproved and before it enters its lock time, specify arecommended start time.

• END_TIME: The new end time of the reservation periodformatted as an RFC 3339 timestamp. To increase the likelihood thatGoogle Cloud approves your request after submission, specify arecommended minimum reservation period.To specify a duration instead of an end time, replace the--end-timeflag with the--duration=END_DURATION flag. ReplaceEND_DURATION with the duration of the reservationperiod in seconds. For example, specify1209600 for 1,209,600 seconds(14 days).

  Important: Verify that your reservation period doesn't overlap with thereservation period of another existing future reservation request withmatching VM properties and zone, and that was created in or is sharedwith your current project. Otherwise, modifying the future reservationrequest fails.

• TOTAL_COUNT: The new total number of VMs that youwant reserved for the period, VM configuration, and project(s) specifiedin your future reservation request. If you want to increase the totalcount, than verify that you have sufficient quota for the resources thatyou're reserving. Otherwise, Google Cloud declines yourmodification request.

For example, consider a draft shared future reservation request namedfr-03 and located in zoneus-central1-a. Suppose that you want to modifythis shared future reservation request by making the following changes:

• Convert the request into a single-project future reservation request.

• Disable the auto-delete option.

• Reserve 100 VMs.

• Submit the future reservation request to Google Cloud for review.

To modifyfr-03, run the following command:

gcloud compute future-reservations update fr-03 \    --clear-share-settings \    --no-auto-delete-auto-created-reservations \    --planning-status=SUBMITTED \    --share-setting=local \    --total-count=100 \    --zone=us-central1-a

REST

To modify a future reservation request, make aPATCH request to thefutureReservations.update method.

PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/futureReservations/FUTURE_RESERVATION_NAME?updateMask=UPDATE_FIELDS{  "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": "SHARE_TYPE"  },  "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": {    "endTime": "END_TIME",    "startTime": "START_TIME"  }}

Replace the following:

• PROJECT_ID: the ID of the project where the futurereservation request is located.

• ZONE: the zone where the future reservation requestis located.

• FUTURE_RESERVATION_NAME: the name of the futurereservation request.

• UPDATE_FIELDS: a comma-separated list of fields toupdate in the request body. You must encode each comma as%2C. If youspecify a field in theupdateMask query parameter and in the requestbody, then this updates the value of the field. Otherwise, if youspecify the field only in theupdateMask query parameter, then thisdeletes the field.

  For example, to update theautoDeleteAutoCreatedReservations,totalCount, andendTime fields in your future reservation request,specify the following:

  autoDeleteAutoCreatedReservations%2CspecificSkuProperties.totalCount%2CtimeWindow.endTime

• PLANNING_STATUS: the planning status of the futurereservation request. Specify one of the following values:

  • To modify a draft future reservation request without submitting itfor review:DRAFT.

  • To submit the modification request for review:SUBMITTED.

Replace one or more of the following placeholders, or remove them along withtheir corresponding fields:

• AUTO_DELETE_AUTO_CREATED_RESERVATIONS: If you setthis field totrue, then Compute Engine automatically deletesthe auto-created reservations provisioned for your future reservationrequest. By default, the deletion is within two hours after thereservation period's end time. To change this, do one of the following:

  • To delete the auto-created reservations at a specific time afterthe end time of your reservation period, set theautoDeleteAutoCreatedReservations totrue and specify theautoCreatedReservationsDeleteTime field.

    PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/futureReservations/FUTURE_RESERVATION_NAME?updateMask=autoDeleteAutoCreatedReservations%2CautoCreatedReservationsDeleteTime%2CplanningStatus{"autoDeleteAutoCreatedReservations": "true",  "autoCreatedReservationsDeleteTime": "DELETE_TIME",  "name": "FUTURE_RESERVATION_NAME",  "planningStatus": "PLANNING_STATUS"}

    ReplaceDELETE_TIME with a date and time whenCompute Engine deletes reservations. The date and time mustbe formatted as anRFC 3339 timestamp.

  • To delete the auto-created reservations after a specific durationfrom the start time of the reservation period, set theautoDeleteAutoCreatedReservations totrue and specify theautoCreatedReservationsDuration field.

    PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/futureReservations/FUTURE_RESERVATION_NAME?updateMask=autoDeleteAutoCreatedReservations%2CautoCreatedReservationsDuration%2CplanningStatus{"autoDeleteAutoCreatedReservations": "true",  "autoCreatedReservationsDuration": {    "seconds": "DURATION_BEFORE_DELETE"  },  "name": "FUTURE_RESERVATION_NAME",  "planningStatus": "PLANNING_STATUS"}

    ReplaceDURATION_BEFORE_DELETE with a duration inseconds. For example, specify604800 for 604,800 seconds (7 days).

• DESCRIPTION: A new description for the futurereservation request.

• NAME_PREFIX: A new name prefix for the auto-createdreservations provisioned for your future reservation request.

• CONSUMER_PROJECT_ID_1 andCONSUMER_PROJECT_ID_2: The IDs of projects that youwant to share your future reservation request with. The projects must bein the same organization as the owner project. You can specify up to 100consumer projects.

• SHARE_TYPE: A new share type for your futurereservation request. Do one of the following:

  • To specify a single-project future reservation request, do thefollowing:

    • SpecifyLOCAL.

    • Remove theshareSettings.projects field.

  • To specify a shared future reservation request, do the following:

    • SpecifySPECIFIC_PROJECTS.

    • Specify at least one consumer project in theshareSettings.projects field. The consumer projects must be inthe same organization as the owner project. You can specify upto 100 consumer projects.

• To change the number and type of GPUs to attach to your reserved N1 VMs,replace the following:

  • NUMBER_OF_ACCELERATORS: the number of GPUs to addper reserved VM.

  • ACCELERATOR_TYPE: the type of GPU to add to thereserved VMs. Verify thatthe GPU is available in the zonewhere the future reservation request is located. Otherwise,modifying the request fails.

• INTERFACE_1 andINTERFACE_2: The type of disk interface type for the Local SSD disks attached to each reserved VM. Specify one of the following values:

  • If your boot disk imagehas optimized NVMe drivers:NVME.

  • Otherwise:SCSI.

    You can specify a maximum of 24 Local SSD disks.

• MACHINE_TYPE: The new machine type to use for eachreserved VM. If you change the machine type, then also specify arecommended minimum reservation period.for the new machine series. Otherwise, Google Cloud is less likelyto approve your modification request.

• MINIMUM_CPU_PLATFORM: A new minimum CPU platform touse for each reserved VM.

• TOTAL_COUNT: The new total number of VMs that youwant reserved for the period, VM configuration, and project(s) specifiedin this future reservation request. If you want to increase the totalcount, than verify that you have sufficient quota for the resources thatyou're reserving. Otherwise, Google Cloud declines yourmodification request.

• START_TIME: The new start time of the reservationperiod formatted as anRFC 3339 timestamp. The starttime can't be later than one year from the date and time at which yousubmit the modification request for review. To have sufficient time tooptionally cancel, delete, or modify a future reservation after it'sapproved and before it enters its lock time, specify arecommended start time.

• END_TIME: The new end time of the reservation periodformatted as an RFC 3339 timestamp. To increase the likelihood thatGoogle Cloud approves your request after submission, specify aminimum reservation period.To specify a duration instead of an end time, replace theendTimefield with theduration field:

  PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/futureReservations/FUTURE_RESERVATION_NAME?updateMask=timeWindow.duration%2CplanningStatus{  "name": "FUTURE_RESERVATION_NAME",  "planningStatus": "PLANNING_STATUS",  "timeWindow": {"duration": {      "seconds": "END_DURATION"    }  }}

  ReplaceEND_DURATION with a duration in seconds. Forexample, specify1209600 for 1,209,600 seconds (14 days).

  Important: Verify that your reservation period doesn't overlap with thereservation period of another existing future reservation request withmatching VM properties and zone, and that was created in or is sharedwith your current project. Otherwise, modifying the future reservationrequest fails.

For example, consider a draft shared future reservation request namedfr-03 and located in zoneus-central1-a. Suppose that you want to modifythis shared future reservation request by making the following changes:

• Convert the request into a single-project future reservation request.

• Disable the auto-delete option.

• Reserve 100 VMs.

• Submit the future reservation request to Google Cloud for review.

To modifyfr-03, make aPATCH request as follows:

PATCH https://compute.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/futureReservations/fr-03?updateMask=autoDeleteAutoCreatedReservations%2CplanningStatus%2CshareSettings.shareType%2CspecificSkuProperties.totalCount{  "autoDeleteAutoCreatedReservations": false,  "name": "fr-03",  "planningStatus": "SUBMITTED",  "shareSettings": {    "shareType": "LOCAL"  },  "specificSkuProperties": {    "totalCount": "100"  }}