imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-19 07:15:23 +00:00
Code Activity

gcloud: Wed Mar 8 10:34:05 UTC 2023

Browse source
This commit is contained in:
Automated 2023-03-08 10:34:05 +00:00
parent bdaa0b3cfc
commit 29661f002c
111 changed files with 1800 additions and 704 deletions
Download patch file Download diff file Expand all files Collapse all files

7
gcloud/alpha/compute/instances/bulk/create
View file

@ -22,6 +22,7 @@ SYNOPSIS
[--labels=[KEY=VALUE,...]]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]]
[--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT]
[--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE]
[--maintenance-interval=MAINTENANCE_INTERVAL]
[--max-count-per-zone=[ZONE=MAX_COUNT_PER_ZONE,...]]
@ -456,6 +457,12 @@ OPTIONAL FLAGS
partitions. You can specify a maximum of 24 local SSDs for a
maximum of 9TB attached to an instance.
--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT
Specifies the maximum amount of time a Local Ssd Vm should wait while
recovery of the Local Ssd state is attempted. Its value should be in
between 0 and 168 hours with hour granularity and the default value
being 1 hour.
--location-policy=[ZONE=POLICY,...]
Policy for which zones to include or exclude during bulk instance
creation within a region. Policy is defined as a list of key-value

10
gcloud/alpha/compute/instances/create
View file

@ -29,7 +29,9 @@ SYNOPSIS
[--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]]
[--local-nvdimm=[size=SIZE]]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE]
[interface=INTERFACE],[size=SIZE]]
[--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT]
[--machine-type=MACHINE_TYPE]
[--maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION]
[--maintenance-interval=MAINTENANCE_INTERVAL]
[--max-run-duration=MAX_RUN_DURATION]
@ -589,6 +591,12 @@ FLAGS
partitions. You can specify a maximum of 24 local SSDs for a
maximum of 9TB attached to an instance.
--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT
Specifies the maximum amount of time a Local Ssd Vm should wait while
recovery of the Local Ssd state is attempted. Its value should be in
between 0 and 168 hours with hour granularity and the default value
being 1 hour.
--machine-type=MACHINE_TYPE
Specifies the machine type used for the instances. To get a list of
available machine types, run 'gcloud compute machine-types list'. If

11
gcloud/alpha/compute/instances/create-with-container
View file

@ -36,8 +36,9 @@ SYNOPSIS
[--ipv6-prefix-length=IPV6_PREFIX_LENGTH] [--labels=[KEY=VALUE,...]]
[--local-nvdimm=[size=SIZE]]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE]
[--metadata=KEY=VALUE,[KEY=VALUE,...]]
[interface=INTERFACE],[size=SIZE]]
[--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT]
[--machine-type=MACHINE_TYPE] [--metadata=KEY=VALUE,[KEY=VALUE,...]]
[--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]]
[--min-cpu-platform=PLATFORM] [--network=NETWORK]
[--network-interface=[PROPERTY=VALUE,...]]
@ -515,6 +516,12 @@ FLAGS
partitions. You can specify a maximum of 24 local SSDs for a
maximum of 9TB attached to an instance.
--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT
Specifies the maximum amount of time a Local Ssd Vm should wait while
recovery of the Local Ssd state is attempted. Its value should be in
between 0 and 168 hours with hour granularity and the default value
being 1 hour.
--machine-type=MACHINE_TYPE
Specifies the machine type used for the instances. To get a list of
available machine types, run 'gcloud compute machine-types list'. If

6
gcloud/alpha/compute/instances/ops-agents/policies/create
View file

@ -229,8 +229,10 @@ REQUIRED FLAGS
debian 11
debian 10
debian 9
rhel 9.*
rhel 8.*
rhel 7.*
rocky 9.*
rocky 8.*
sles 12.*
sles 15.*
@ -249,8 +251,8 @@ REQUIRED FLAGS
short-name
Short name of the OS.
Required. Allowed values: centos, debian, rhel, sles, sles_sap,
ubuntu.
Required. Allowed values: centos, debian, rhel, rocky, sles,
sles_sap, ubuntu.
To inspect the exact OS short name of an instance, run:

6
gcloud/alpha/compute/instances/ops-agents/policies/update
View file

@ -266,8 +266,10 @@ FLAGS
debian 11
debian 10
debian 9
rhel 9.*
rhel 8.*
rhel 7.*
rocky 9.*
rocky 8.*
sles 12.*
sles 15.*
@ -286,8 +288,8 @@ FLAGS
short-name
Short name of the OS.
Required. Allowed values: centos, debian, rhel, sles, sles_sap,
ubuntu.
Required. Allowed values: centos, debian, rhel, rocky, sles,
sles_sap, ubuntu.
To inspect the exact OS short name of an instance, run:

59
gcloud/alpha/compute/instances/set-scheduling
View file

@ -6,13 +6,16 @@ SYNOPSIS
gcloud alpha compute instances set-scheduling INSTANCE_NAME
[--clear-min-node-cpu]
[--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS]
[--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT]
[--min-node-cpu=MIN_NODE_CPU] [--[no-]preemptible]
[--provisioning-model=PROVISIONING_MODEL] [--[no-]restart-on-failure]
[--zone=ZONE]
[--clear-instance-termination-action
| --instance-termination-action=INSTANCE_TERMINATION_ACTION]
[--clear-max-run-duration | --max-run-duration=MAX_RUN_DURATION]
[--clear-node-affinities | --node=NODE
| --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP]
[--clear-termination-time | --termination-time=TERMINATION_TIME]
[--maintenance-policy=MAINTENANCE_POLICY
| --on-host-maintenance=MAINTENANCE_POLICY] [GCLOUD_WIDE_FLAG ...]
@ -44,6 +47,12 @@ FLAGS
with 30 second increments, with a range of 90 to 330 seconds. If unset,
the default behavior of the host error recovery is used.
--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT
Specifies the maximum amount of time a Local Ssd Vm should wait while
recovery of the Local Ssd state is attempted. Its value should be in
between 0 and 168 hours with hour granularity and the default value
being 1 hour.
--min-node-cpu=MIN_NODE_CPU
Minimum number of virtual CPUs this instance will consume when running
on a sole-tenant node.
@ -123,6 +132,33 @@ FLAGS
Default. Stop the VM without preserving memory. The VM can be
restarted later.
Max Run Duration
At most one of these can be specified:
--clear-max-run-duration
Removes the max-run-duration field from the scheduling options.
--max-run-duration=MAX_RUN_DURATION
Limits how long this VM instance can run, specified as a duration
relative to the VM instance's most-recent start time. Format the
duration, MAX_RUN_DURATION, as the number of days, hours, minutes,
and seconds followed by d, h, m, and s respectively. For example,
specify 30m for a duration of 30 minutes or specify 1d2h3m4s for a
duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Alternatively,
to specify a timestamp, use --termination-time instead.
If neither --max-run-duration nor --termination-time is specified
(default), the VM instance runs until prompted by a user action or
system event. If either is specified, the VM instance is scheduled to
be automatically terminated using the action specified by
--instance-termination-action. For --max-run-duration, the VM
instance is automatically terminated when the VM's current runtime
reaches MAX_RUN_DURATION. Note: Anytime the VM instance is stopped or
suspended, --max-run-duration and (unless the VM uses
--provisioning-model=SPOT) --instance-termination-action are
automatically removed from the VM.
Sole Tenancy.
At most one of these can be specified:
@ -159,6 +195,29 @@ FLAGS
--node-group=NODE_GROUP
The name of the node group to schedule this instance on.
Termination Time
At most one of these can be specified:
--clear-termination-time
Removes the termination-time field from the scheduling options.
--termination-time=TERMINATION_TIME
Limits how long this VM instance can run, specified as a time. Format
the time, TERMINATION_TIME, as a RFC 3339 timestamp. For more
information, see https://tools.ietf.org/html/rfc3339. Alternatively,
to specify a duration, use --max-run-duration instead.
If neither --termination-time nor --max-run-duration is specified
(default), the VM instance runs until prompted by a user action or
system event. If either is specified, the VM instance is scheduled to
be automatically terminated using the action specified by
--instance-termination-action. For --termination-time, the VM
instance is automatically terminated at the specified timestamp.
Note: Anytime the VM instance is stopped or suspended,
--termination-time and (unless the VM uses --provisioning-model=SPOT)
--instance-termination-action are automatically removed from the VM.
Maintenance Behavior.
At most one of these can be specified: