1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 23:08:48 +00:00

gcloud: Wed Oct 9 09:55:07 UTC 2024

This commit is contained in:
Automated 2024-10-09 09:55:07 +00:00
parent 489be55d99
commit 4ffb04ab9e
211 changed files with 7635 additions and 1232 deletions

View file

@ -170,18 +170,20 @@ REQUIRED FLAGS
OPTIONAL FLAGS
--deployment-type=DEPLOYMENT_TYPE
Indicates if the reservation allocation strategy is static or dynamic.
DENSE refers to a fixed size and topology, with deployment expressed in
terms of blocks. FLEXIBLE indicates a non-static distribution of
capacity that can change over time. Deployment is not expressed in
blocks. DEPLOYMENT_TYPE must be one of: DENSE, FLEXIBLE.
The deployment type for the reserved capacity. DEPLOYMENT_TYPE must be
one of:
DENSE
DENSE mode is for densely deployed reservation blocks.
FLEXIBLE
FLEXIBLE mode is for highly flexible, logical reservation blocks.
--description=DESCRIPTION
An optional description of the future reservation to create.
--[no-]enable-opportunistic-maintenance
Indicates if this group of VMs have opportunistic maintenance enabled.
Applicable only to dense coordinated maintenance. Use
Enable or disable opportunistic maintenance. If enabled, maintenance is
performed on unused reservations whenever possible. Use
--enable-opportunistic-maintenance to enable and
--no-enable-opportunistic-maintenance to disable.
@ -226,9 +228,14 @@ OPTIONAL FLAGS
the reservation_name or a name_prefix.
--scheduling-type=SCHEDULING_TYPE
Indicates the maintenance type for this group of VMs. This will be set
on the reservation via FR, and will be inherited for reservation
blocks. SCHEDULING_TYPE must be one of: GROUPED, INDEPENDENT.
Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of:
GROUPED
In GROUPED mode, maintenance on all reserved instances
issynchronized.
INDEPENDENT
In INDEPENDENT mode, maintenance is not synchronized for this
reservation, and each instance has its own maintenance window.
--zone=ZONE
Zone of the future reservation to create. If not specified and the

View file

@ -52,18 +52,20 @@ FLAGS
--no-auto-delete-auto-created-reservations to disable.
--deployment-type=DEPLOYMENT_TYPE
Indicates if the reservation allocation strategy is static or dynamic.
DENSE refers to a fixed size and topology, with deployment expressed in
terms of blocks. FLEXIBLE indicates a non-static distribution of
capacity that can change over time. Deployment is not expressed in
blocks. DEPLOYMENT_TYPE must be one of: DENSE, FLEXIBLE.
The deployment type for the reserved capacity. DEPLOYMENT_TYPE must be
one of:
DENSE
DENSE mode is for densely deployed reservation blocks.
FLEXIBLE
FLEXIBLE mode is for highly flexible, logical reservation blocks.
--description=DESCRIPTION
An optional description of the future reservation to create.
--[no-]enable-opportunistic-maintenance
Indicates if this group of VMs have opportunistic maintenance enabled.
Applicable only to dense coordinated maintenance. Use
Enable or disable opportunistic maintenance. If enabled, maintenance is
performed on unused reservations whenever possible. Use
--enable-opportunistic-maintenance to enable and
--no-enable-opportunistic-maintenance to disable.
@ -103,9 +105,14 @@ FLAGS
the reservation_name or a name_prefix.
--scheduling-type=SCHEDULING_TYPE
Indicates the maintenance type for this group of VMs. This will be set
on the reservation via FR, and will be inherited for reservation
blocks. SCHEDULING_TYPE must be one of: GROUPED, INDEPENDENT.
Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of:
GROUPED
In GROUPED mode, maintenance on all reserved instances
issynchronized.
INDEPENDENT
In INDEPENDENT mode, maintenance is not synchronized for this
reservation, and each instance has its own maintenance window.
--total-count=TOTAL_COUNT
The total number of instances for which capacity assurance is requested