gcloud beta compute resource-policies create group-placement - create a Compute Engine group placement resource policy

gcloud beta compute resource-policies create group-placementNAME[--availability-domain-count=AVAILABILITY_DOMAIN_COUNT][--collocation=COLLOCATION][--description=DESCRIPTION][--gpu-topology=GPU_TOPOLOGY][--max-distance=MAX_DISTANCE][--region=REGION][--vm-count=VM_COUNT][GCLOUD_WIDE_FLAG …]

NAME

Name of the resource policy to operate on.

--availability-domain-count=AVAILABILITY_DOMAIN_COUNT

Number of availability domain in the group placement policy.

--collocation=COLLOCATION

Collocation specifies whether to place VMs inside the sameavailability domain onthe same low-latency network.COLLOCATION must be oneof:

collocated

Low network latency between more VMs placed on the same availability domain.

unspecified-collocation

Unspecified network latency between VMs placed on the same availability domain.This is the default behavior.

--description=DESCRIPTION

An optional, textual description for the backend.

--gpu-topology=GPU_TOPOLOGY

Specifies the shape of the GPU slice, in slice based GPU families eg. A4X.

--max-distance=MAX_DISTANCE

Specifies the number of max logical switches between VMs.

--region=REGION

Region of the resource policy to operate on. If not specified, you might beprompted to select a region (interactive mode only).

To avoid prompting when this flag is omitted, you can set thecompute/region property:

gcloudconfigsetcompute/regionREGION

A list of regions can be fetched by running:

gcloudcomputeregionslist

To unset the property, run:

gcloudconfigunsetcompute/region

Alternatively, the region can be stored in the environment variableCLOUDSDK_COMPUTE_REGION.

--vm-count=VM_COUNT

Number of instances targeted by the group placement policy. Google does notrecommend that you use this flag unless you use a compact policy and you wantyour policy to work only if it contains this exact number of VMs.

Run$gcloud help for details.