HEX
Server: Apache/2.4.65 (Ubuntu)
System: Linux ielts-store-v2 6.8.0-1036-gcp #38~22.04.1-Ubuntu SMP Thu Aug 14 01:19:18 UTC 2025 x86_64
User: root (0)
PHP: 7.2.34-54+ubuntu20.04.1+deb.sury.org+1
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //snap/google-cloud-cli/current/help/man/man1/gcloud_beta_compute_future-reservations_update.1
.TH "GCLOUD_BETA_COMPUTE_FUTURE\-RESERVATIONS_UPDATE" 1



.SH "NAME"
.HP
gcloud beta compute future\-reservations update \- update Compute Engine future reservations



.SH "SYNOPSIS"
.HP
\f5gcloud beta compute future\-reservations update\fR \fIFUTURE_RESERVATION\fR [\fB\-\-[no\-]auto\-delete\-auto\-created\-reservations\fR] [\fB\-\-deployment\-type\fR=\fIDEPLOYMENT_TYPE\fR] [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-[no\-]enable\-emergent\-maintenance\fR] [\fB\-\-planning\-status\fR=\fIPLANNING_STATUS\fR] [\fB\-\-[no\-]require\-specific\-reservation\fR] [\fB\-\-reservation\-name\fR=\fIRESERVATION_NAME\fR] [\fB\-\-scheduling\-type\fR=\fISCHEDULING_TYPE\fR] [\fB\-\-total\-count\fR=\fITOTAL_COUNT\fR] [\fB\-\-zone\fR=\fIZONE\fR] [\fB\-\-auto\-created\-reservations\-delete\-time\fR=\fIAUTO_CREATED_RESERVATIONS_DELETE_TIME\fR\ |\ \fB\-\-auto\-created\-reservations\-duration\fR=\fIAUTO_CREATED_RESERVATIONS_DURATION\fR] [\fB\-\-clear\-name\-prefix\fR\ |\ \fB\-\-name\-prefix\fR=\fINAME_PREFIX\fR] [\fB\-\-clear\-share\-settings\fR\ |\ \fB\-\-share\-setting\fR=\fISHARE_SETTING\fR\ \fB\-\-share\-with\fR=\fIPROJECT\fR,[\fIPROJECT\fR,...]] [\fB\-\-commitment\-name\fR=\fICOMMITMENT_NAME\fR\ \fB\-\-commitment\-plan\fR=\fICOMMITMENT_PLAN\fR\ \fB\-\-previous\-commitment\-terms\fR=\fIPREVIOUS_COMMITMENT_TERMS\fR] [\fB\-\-machine\-type\fR=\fIMACHINE_TYPE\fR\ \fB\-\-min\-cpu\-platform\fR=\fIMIN_CPU_PLATFORM\fR\ \fB\-\-accelerator\fR=[\fIcount\fR=\fICOUNT\fR],[\fItype\fR=\fITYPE\fR]\ |\ \fB\-\-clear\-accelerator\fR\ \fB\-\-clear\-local\-ssd\fR\ |\ \fB\-\-local\-ssd\fR=[\fIcount\fR=\fICOUNT\fR],[\fIinterface\fR=\fIINTERFACE\fR],[\fIsize\fR=\fISIZE\fR]] [\fB\-\-start\-time\fR=\fISTART_TIME\fR\ \fB\-\-duration\fR=\fIDURATION\fR\ |\ \fB\-\-end\-time\fR=\fIEND_TIME\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(BETA)\fR Update Compute Engine future reservations.



.SH "EXAMPLES"

To update total count, start and end time of a Compute Engine future reservation
in \f5\fIus\-central1\-a\fR\fR, run:

.RS 2m
$ gcloud beta compute future\-reservations update \e
  my\-future\-reservation \-\-total\-count=1000 \e
  \-\-start\-time=2021\-11\-10T07:00:00Z \e
  \-\-end\-time=2021\-12\-10T07:00:00Z \-\-zone=us\-central1\-a
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIFUTURE_RESERVATION\fR

Name of the future reservation to update.


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-[no\-]auto\-delete\-auto\-created\-reservations\fR

If specified, the auto\-created reservations for a future reservation are
deleted at the end time (default) or at a specified delete time. Use
\fB\-\-auto\-delete\-auto\-created\-reservations\fR to enable and
\fB\-\-no\-auto\-delete\-auto\-created\-reservations\fR to disable.

.TP 2m
\fB\-\-deployment\-type\fR=\fIDEPLOYMENT_TYPE\fR

The deployment type for the reserved capacity. \fIDEPLOYMENT_TYPE\fR must be one
of:

.RS 2m
.TP 2m
\fBDENSE\fR
DENSE mode is for densely deployed reservation blocks.
.TP 2m
\fBFLEXIBLE\fR
FLEXIBLE mode is for highly flexible, logical reservation blocks.
.RE
.sp


.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

An optional description of the future reservation to create.

.TP 2m
\fB\-\-[no\-]enable\-emergent\-maintenance\fR

Emergent maintenance flag for the reservation, which enrolls all the underlying
vms, hosts and SB infrastructure to receive emergent maintenance notifications
in advance. Use \fB\-\-enable\-emergent\-maintenance\fR to enable and
\fB\-\-no\-enable\-emergent\-maintenance\fR to disable.

.TP 2m
\fB\-\-planning\-status\fR=\fIPLANNING_STATUS\fR

The planning status of the future reservation. The default value is DRAFT. While
in DRAFT, any changes to the future reservation's properties will be allowed. If
set to SUBMITTED, the future reservation will submit and its procurementStatus
will change to PENDING_APPROVAL. Once the future reservation is pending
approval, changes to the future reservation's properties will not be allowed.
\fIPLANNING_STATUS\fR must be one of:

.RS 2m
.TP 2m
\fBDRAFT\fR
Default planning status value.
.TP 2m
\fBSUBMITTED\fR
Planning status value to immediately submit the future reservation.
.RE
.sp


.TP 2m
\fB\-\-[no\-]require\-specific\-reservation\fR

Indicate whether the auto\-created reservations can be consumed by VMs with "any
reservation" defined. If enabled, then only VMs that target the auto\-created
reservation by name using \f5\-\-reservation\-affinity=specific\fR can consume
from this reservation. Auto\-created reservations delivered with this flag
enabled will inherit the name of the future reservation. Use
\fB\-\-require\-specific\-reservation\fR to enable and
\fB\-\-no\-require\-specific\-reservation\fR to disable.

.TP 2m
\fB\-\-reservation\-name\fR=\fIRESERVATION_NAME\fR

Name of reservations where the capacity is provisioned at the time of delivery
of future reservations. If the reservation with the given name does not exist
already, it is created automatically at the time of Approval with INACTIVE state
till specified start\-time. Either provide the reservation_name or a
name_prefix.

.TP 2m
\fB\-\-scheduling\-type\fR=\fISCHEDULING_TYPE\fR

Maintenance for the reserved capacity. \fISCHEDULING_TYPE\fR must be one of:

.RS 2m
.TP 2m
\fBGROUPED\fR
In GROUPED mode, maintenance on all reserved instances is synchronized.
.TP 2m
\fBINDEPENDENT\fR
In INDEPENDENT mode, maintenance is not synchronized for this reservation, and
each instance has its own maintenance window.
.RE
.sp


.TP 2m
\fB\-\-total\-count\fR=\fITOTAL_COUNT\fR

The total number of instances for which capacity assurance is requested at a
future time period.

.TP 2m
\fB\-\-zone\fR=\fIZONE\fR

Zone of the future reservation to update. If not specified and the
\f5\fIcompute/zone\fR\fR property isn't set, you might be prompted to select a
zone (interactive mode only).

To avoid prompting when this flag is omitted, you can set the
\f5\fIcompute/zone\fR\fR property:

.RS 2m
$ gcloud config set compute/zone ZONE
.RE

A list of zones can be fetched by running:

.RS 2m
$ gcloud compute zones list
.RE

To unset the property, run:

.RS 2m
$ gcloud config unset compute/zone
.RE

Alternatively, the zone can be stored in the environment variable
\f5\fICLOUDSDK_COMPUTE_ZONE\fR\fR.

.TP 2m

Manage the auto\-delete time properties.

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-auto\-created\-reservations\-delete\-time\fR=\fIAUTO_CREATED_RESERVATIONS_DELETE_TIME\fR

Automatically deletes an auto\-created reservations at a specific time. The
specified time must be an RFC3339 timestamp, which must be formatted as
"YYYY\-MM\-DDTHH:MM:SSZ" where YYYY = year, MM = month, DD = day, HH = hours, MM
= minutes, SS = seconds, and Z = time zone in Coordinated Universal Time (UTC).
For example, specify 2021\-11\-20T07:00:00Z.

.TP 2m
\fB\-\-auto\-created\-reservations\-duration\fR=\fIAUTO_CREATED_RESERVATIONS_DURATION\fR

Automatically deletes an auto\-created reservations after a specified number of
days, hours, minutes, or seconds. For example, specify 30m for 30 minutes, or
1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 seconds. For more information, see
$ gcloud topic datetimes.

.RE
.sp
.TP 2m

Manage the name\-prefix of a future reservation.

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-clear\-name\-prefix\fR

Clears the name prefix for the system generated reservations.

.TP 2m
\fB\-\-name\-prefix\fR=\fINAME_PREFIX\fR

A name prefix for the auto\-created reservations when capacity is delivered at
the start time. Each auto\-created reservation name starts with the name prefix.

.RE
.sp
.TP 2m

Manage the properties of a shared future reservation.

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-clear\-share\-settings\fR

Clear share settings on future reservation. This will result in non\-shared
future reservation.

.TP 2m

Manage the share settings of a future reservation.


.RS 2m
.TP 2m
\fB\-\-share\-setting\fR=\fISHARE_SETTING\fR

Specify if this future reservation is shared, and if so, the type of sharing. If
you omit this flag, this value is local by default. \fISHARE_SETTING\fR must be
one of: \fBlocal\fR, \fBprojects\fR.

.TP 2m
\fB\-\-share\-with\fR=\fIPROJECT\fR,[\fIPROJECT\fR,...]

If this future reservation is shared, provide a comma\-separated list of
projects that this future reservation is shared with. The list must contain
project IDs or project numbers.

.RE
.RE
.sp
.TP 2m

Manage the commitment info properties


.RS 2m
.TP 2m
\fB\-\-commitment\-name\fR=\fICOMMITMENT_NAME\fR

Name of commitment covering the delivered reservation at the time of delivery of
future reservations. If not specified, it takes the name of the future
reservation.

.TP 2m
\fB\-\-commitment\-plan\fR=\fICOMMITMENT_PLAN\fR

The plan for this commitment to be created, which determines duration and
discount rate. The currently supported plans are TWELVE_MONTH (1 year), and
THIRTY_SIX_MONTH (3 years). \fICOMMITMENT_PLAN\fR must be one of:
\fBTWELVE_MONTH\fR, \fBTHIRTY_SIX_MONTH\fR.

.TP 2m
\fB\-\-previous\-commitment\-terms\fR=\fIPREVIOUS_COMMITMENT_TERMS\fR

Applicable only if future reservation will deliver to an existing reservation
with a ramp plan. When set to EXTEND, all associated parent Committed Used
Discount's end\-date/term will be extended to the end\-time of this future
reservation. Default is to extend previous commitment's time to the end_time of
the reservation. \fIPREVIOUS_COMMITMENT_TERMS\fR must be (only one value is
supported): \fBEXTEND\fR.

.RE
.sp
.TP 2m

Manage the specific SKU reservation properties.


.RS 2m
.TP 2m
\fB\-\-machine\-type\fR=\fIMACHINE_TYPE\fR

The type of machine (name only) that has a fixed number of vCPUs and a fixed
amount of memory. You can also specify a custom machine type by using the
pattern \f5custom\-number_of_CPUs\-amount_of_memory\fR\-for example,
\f5custom\-32\-29440\fR.

.TP 2m
\fB\-\-min\-cpu\-platform\fR=\fIMIN_CPU_PLATFORM\fR

Optional minimum CPU platform of the reservation to create.

.TP 2m

Manage the accelerators of a future reservation.

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-accelerator\fR=[\fIcount\fR=\fICOUNT\fR],[\fItype\fR=\fITYPE\fR]

Manage the configuration of the type and number of accelerator cards attached.
.RS 2m
.TP 2m
\fBcount\fR
The number of accelerators to attach to each instance in the reservation.
.TP 2m
\fBtype\fR
The specific type (e.g. \f5nvidia\-tesla\-k80\fR for nVidia Tesla K80) of
accelerator to attach to instances in the reservation. Use \f5gcloud compute
accelerator\-types list\fR to learn about all available accelerator types.

.RE
.sp
.TP 2m
\fB\-\-clear\-accelerator\fR

Remove all accelerators from the future reservation.

.RE
.sp
.TP 2m

Manage the local ssd of a future reservation.

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-clear\-local\-ssd\fR

Remove all local ssd information on the future reservation.

.TP 2m
\fB\-\-local\-ssd\fR=[\fIcount\fR=\fICOUNT\fR],[\fIinterface\fR=\fIINTERFACE\fR],[\fIsize\fR=\fISIZE\fR]

Manage the size and the interface of local SSD to use. See
https://cloud.google.com/compute/docs/disks/local\-ssd for more information.
.RS 2m
.TP 2m
\fBinterface\fR
The kind of disk interface exposed to the VM for this SSD. Valid values are
\f5scsi\fR and \f5nvme\fR. SCSI is the default and is supported by more guest
operating systems. NVME may provide higher performance.
.TP 2m
\fBsize\fR
The size of the local SSD in base\-2 GB.
.TP 2m
\fBcount\fR
The number of local SSD to use per VM. If you don't specify this argument, then
the default value is 1.

.RE
.RE
.RE
.sp
.TP 2m

Manage the time specific properties for requesting future capacity


.RS 2m
.TP 2m
\fB\-\-start\-time\fR=\fISTART_TIME\fR

Start time of the Future Reservation. The start time must be an RFC3339 valid
string formatted by date, time, and timezone or "YYYY\-MM\-DDTHH:MM:SSZ"; where
YYYY = year, MM = month, DD = day, HH = hours, MM = minutes, SS = seconds, and Z
= timezone (i.e. 2021\-11\-20T07:00:00Z).

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-duration\fR=\fIDURATION\fR

Alternate way of specifying time in the number of seconds to terminate capacity
request relative to the start time of a request.

.TP 2m
\fB\-\-end\-time\fR=\fIEND_TIME\fR

End time of the Future Reservation. The end time must be an RFC3339 valid string
formatted by date, time, and timezone or "YYYY\-MM\-DDTHH:MM:SSZ"; where YYYY =
year, MM = month, DD = day, HH = hours, MM = minutes, SS = seconds, and Z =
timezone (i.e. 2021\-11\-20T07:00:00Z).


.RE
.RE
.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

This command is currently in beta and might change without notice. These
variants are also available:

.RS 2m
$ gcloud compute future\-reservations update
.RE

.RS 2m
$ gcloud alpha compute future\-reservations update
.RE