Create an AI-optimized MIG with A3 Edge machine type

General GPUs

This document describes how to create a managed instance group (MIG) that uses an A3 Edge accelerator-optimized machine type. To learn more about the machine type, see A3 Edge in the Compute Engine documentation.

Creating a MIG lets you manage multiple virtual machines (VMs) as a single entity. Each VM in a MIG is based on an instance template. By automatically managing the health and size of the instance group, MIGs provide high availability and scalability. To learn more about MIGs, see Managed instance groups.

To learn about VM and cluster creation options, see VM and cluster creation overview page.

Limitations

When you create a MIG with A3 Edge VMs, consider the limitations for both the machine type and the MIG.

Limitations for A3 Edge VMs

Depending on the machine series that the VMs in your MIG use, the following limitations apply:

You don't receive sustained use discounts and flexible committed use discounts for instances that use an A3 Edge machine type.
You can only use an A3 Edge machine type in certain regions and zones.
You can't use regional Persistent Disk on an instance that uses an A3 Edge machine type.
The A3 Edge machine type is only available on the Sapphire Rapids CPU platform.
Machine type changes aren't supported for A3 Edge machine type. To switch to or from this machine type, you must create a new instance.
You can't run Windows operating systems on an A3 Edge machine type.
A3 Edge machine types don't support sole-tenancy.

Limitations for the MIG

When you create a MIG with A3 Edge VMs, the following limitations apply:

You must turn off repairs in the MIG, as described in this document.

You can't configure instance flexibility in the MIG.

Limitations for MIG resize requests

For MIG resize requests, the following limitations apply:

In regional MIGs, you can use only the ANY_SINGLE_ZONE target distribution shape.
You can only set the standby pool mode of the MIG to manual (default).
You can't set autoscaling.
If the MIG contains accepted resize requests, then you can't change the target size of the MIG.
You can't delete or abandon the managed instances in a CREATING status that the MIG creates for a resize request. To delete those managed instances, you must cancel the resize request.

For more information, see all the limitations for resize requests.

Before you begin

Before creating a MIG, if you haven't already done so, complete the following steps:

Choose a consumption option: your choice of consumption option determines how you get and use GPU resources. To learn more, see Choose a consumption option.
Obtain capacity: the process to obtain capacity differs for each consumption option. To learn about the process to obtain capacity for your chosen consumption option, see Capacity overview.

Required roles

To get the permissions that you need to create a MIG, ask your administrator to grant you the Compute Instance Admin (v1) (roles/compute.instanceAdmin.v1) IAM role on the project. For more information about granting roles, see Manage access to projects, folders, and organizations.

This predefined role contains the permissions required to create a MIG. To see the exact permissions that are required, expand the Required permissions section:

Required permissions

The following permissions are required to create a MIG:

To create a MIG: compute.instanceGroupManagers.create on the project

You might also be able to get these permissions with custom roles or other predefined roles.

Overview

Creating a MIG with the A3 Edge machine type includes the following steps:

Create VPC networks
Optional: Create a compact placement policy
Create an instance template
Create a MIG
Install GPU drivers

For each MIG, you must choose if you want to use a compact placement policy, use resize requests, or neither. For more information about when to use each option, see Limitations for the MIG in this document.

Create VPC networks

To enable efficient communication for your GPU VMs, you need to create a management network and one or more data networks. The management network is used for external access, for example SSH, and for most general network communication. The data networks are used for high-performance communication between the GPUs on different VMs, for example, for Remote Direct Memory Access (RDMA) traffic.

For these VPC networks, we recommend setting the maximum transmission unit (MTU) to a larger value. Higher MTU values increase the packet size and reduce the packet-header overhead, which increases payload data throughput. For more information about how to create VPC networks, see Create and verify a jumbo frame MTU network.

Create management network, subnet, and firewall rule

Complete the following steps to set up the management network:

Create the management network by using the networks create command:

gcloud compute networks create NETWORK_NAME_PREFIX-mgmt-net \
    --project=PROJECT_ID \
    --subnet-mode=custom \
    --mtu=8244

Create the management subnet by using the networks subnets create command:

gcloud compute networks subnets create NETWORK_NAME_PREFIX-mgmt-sub \
    --project=PROJECT_ID \
    --network=NETWORK_NAME_PREFIX-mgmt-net \
    --region=REGION \
    --range=192.168.0.0/24

Create firewall rules by using the firewall-rules create command.

Create a firewall rule for the management network.

gcloud compute firewall-rules create NETWORK_NAME_PREFIX-mgmt-internal \
    --project=PROJECT_ID \
    --network=NETWORK_NAME_PREFIX-mgmt-net \
    --action=ALLOW \
    --rules=tcp:0-65535,udp:0-65535,icmp \
    --source-ranges=192.168.0.0/16

Create the tcp:22 firewall rule to limit which source IP addresses can connect to your VM by using SSH.

gcloud compute firewall-rules create NETWORK_NAME_PREFIX-mgmt-external-ssh \
    --project=PROJECT_ID \
    --network=NETWORK_NAME_PREFIX-mgmt-net \
    --action=ALLOW \
    --rules=tcp:22 \
    --source-ranges=SSH_SOURCE_IP_RANGE

Create the icmp firewall rule that can be used to check for data transmission issues in the network.

gcloud compute firewall-rules create NETWORK_NAME_PREFIX-mgmt-external-ping \
    --project=PROJECT_ID \
    --network=NETWORK_NAME_PREFIX-mgmt-net \
    --action=ALLOW \
    --rules=icmp \
    --source-ranges=0.0.0.0/0

Replace the following:

NETWORK_NAME_PREFIX: the name prefix to use for the VPC networks and subnets.
PROJECT_ID : your project ID.
REGION: the region where you want to create the networks.
SSH_SOURCE_IP_RANGE: IP range in CIDR format. This specifies which source IP addresses can connect to your VM by using SSH.

Create data networks, subnets, and firewall rule

A3 Edge requires four data networks. Use the following command to create four data networks, each with subnets and firewall rules.

for N in $(seq 1 4); do
gcloud compute networks create NETWORK_NAME_PREFIX-data-net-$N \
    --project=PROJECT_ID \
    --subnet-mode=custom \
    --mtu=8244

gcloud compute networks subnets create NETWORK_NAME_PREFIX-data-sub-$N \
    --project=PROJECT_ID \
    --network=NETWORK_NAME_PREFIX-data-net-$N \
    --region=REGION \
    --range=192.168.$N.0/24

gcloud compute firewall-rules create NETWORK_NAME_PREFIX-data-internal-$N \
    --project=PROJECT_ID \
    --network=NETWORK_NAME_PREFIX-data-net-$N \
    --action=ALLOW \
    --rules=tcp:0-65535,udp:0-65535,icmp \
    --source-ranges=192.168.0.0/16
done

Optional: Create a compact placement policy

You can specify VM placement by creating a compact placement policy. When you apply a compact placement policy to your VMs, Compute Engine makes best-effort attempts to create VMs that are as close to each other as possible. If your application is latency-sensitive and requires maximum compactness, then specify the maxDistance field (Preview) when you create a compact placement policy. A lower maxDistance value ensures closer VM placement, but it also increases the chance that some VMs won't be created.

To create a compact placement policy, select one of the following options:

gcloud

To create a compact placement policy, use the gcloud beta compute resource-policies create group-placement command:

gcloud beta compute resource-policies create group-placement POLICY_NAME \
    --collocation=collocated \
    --max-distance=MAX_DISTANCE \
    --region=REGION

Replace the following:

POLICY_NAME: the name of the compact placement policy.
MAX_DISTANCE: the maximum distance configuration for your VMs, which can either be specified (Preview, recommended) or unspecified (remove the --max-distance flag). Based on what your machine type supports, you can specify one of the following values:
- To place VMs in the same sub-block: 1
- To place VMs in the same block: 2
- To place VMs in adjacent blocks: 3
Ensure that the maximum distance configuration supports the machine series and number of VMs that you plan to create. For more information, see About compact placement policies in the Compute Engine documentation.
REGION: the region where you want to create the compact placement policy. Specify the region that contains the zone where you plan to create instances, and verify that the machine type that you want to use is available in that region. For information about regions, see GPU availability by regions and zones.

REST

To create a compact placement policy, make a POST request to the beta resourcePolicies.insert method. In the request body, include the collocation field set to COLLOCATED, and the maxDistance field.

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/resourcePolicies
  {
    "name": "POLICY_NAME",
    "groupPlacementPolicy": {
      "collocation": "COLLOCATED",
      "maxDistance": MAX_DISTANCE
    }
  }

Replace the following:

PROJECT_ID: your project ID.
POLICY_NAME: the name of the compact placement policy.
MAX_DISTANCE: the maximum distance configuration for your VMs, which can either be specified (Preview, recommended) or unspecified (remove the maxDistance field). Based on what your machine type supports, you can specify one of the following values:
- To place VMs in the same sub-block: 1
- To place VMs in the same block: 2
- To place VMs in adjacent blocks: 3
Ensure that the maximum distance configuration supports the machine series and number of VMs that you plan to create. For more information, see About compact placement policies in the Compute Engine documentation.
REGION: the region where you want to create the compact placement policy. Specify the region that contains the zone where you plan to create instances, and verify that the machine type that you want to use is available in that region. For information about regions, see GPU availability by regions and zones.

Create an instance template

Specify the VM properties for a MIG by creating an instance template.

To create an instance template, select one of the following options:

The following commands also set the access scope for your instances. To simplify permissions management, Google recommends that you set the access scope on an instance to cloud-platform access and then use IAM roles to define what services the instance can access. For more information, see Scopes best practice.

To create an instance template for A3 Edge VMs, you must specify four additional network interfaces for GPUDirect-TCPX traffic. If you haven't already, you must create four VPC networks as described in Create VPC networks.

gcloud

To create a regional instance template, use the gcloud compute instance-templates create command.

The parameters that you need to specify depend on the consumption option that you are using for this deployment. Select the tab that corresponds to your consumption option.

Reservation

Before you run the command, review all of the following steps to determine whether to include additional flags.

gcloud compute instance-templates create INSTANCE_TEMPLATE_NAME \
    --machine-type=MACHINE_TYPE \
    --image-family=IMAGE_FAMILY \
    --image-project=IMAGE_PROJECT \
    --instance-template-region=REGION \
    --boot-disk-type=DISK_TYPE \
    --boot-disk-size=DISK_SIZE \
    --scopes=cloud-platform \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-0,subnet=GVNIC_NAME_PREFIX-sub-0 \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-1,subnet=GVNIC_NAME_PREFIX-sub-1,no-address 
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-2,subnet=GVNIC_NAME_PREFIX-sub-2,no-address \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-3,subnet=GVNIC_NAME_PREFIX-sub-3,no-address \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-4,subnet=GVNIC_NAME_PREFIX-sub-4,no-address \
    --reservation-affinity=specific \
    --reservation=RESERVATION \
    --provisioning-model=RESERVATION_BOUND \
    --instance-termination-action=DELETE \
    --maintenance-policy=TERMINATE \
    --restart-on-failure

Complete the following steps:

Replace the following:
- INSTANCE_TEMPLATE_NAME: the name of the instance template.
- MACHINE_TYPE: the machine type to use for the A3 Edge instance. For more information, see GPU machine types in the Compute Engine documentation.
- IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of all supported operating systems, see Supported operating systems. For the A3 Edge machine series, we strongly recommend that you use the cos-121-lts or later Container-Optimized OS image and disable automatic updates.
- IMAGE_PROJECT: the project ID of the OS image. For example, use cos-cloud for the cos-121-lts or later Container-Optimized OS image.
- REGION: the region where you want to create the instance template. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU availability by regions and zones.
- DISK_TYPE: the type of the boot disk. For this machine series, we recommend that you use hyperdisk-balanced. For more information about the supported disk types for your machine type, see GPU machines in accelerator-optimized machine family in the Compute Engine documentation.
- DISK_SIZE: the size of the boot disk in GB. For more information, see either Google Cloud Hyperdisk size limits or Persistent Disk size limits based on the type of disk.
- GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- RESERVATION: either the reservation name or a specific block within a reservation. To get the reservation name or the available blocks, see View reserved capacity. Based on your requirement for instance placement, choose one of the following:
  - To create instances across blocks or on a single block:
```
projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME
```
    Additionally, for a single block, apply a compact placement policy that specifies a block collocation (maxDistance=2) . Compute Engine then applies the policy to the reservation and creates instances on the same block.
  - To create instances on a specific block:
```
projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME/reservationBlocks/RESERVATION_BLOCK_NAME
```
  Tip: If the reservation exists in the current project, then you can omit projects/RESERVATION_OWNER_PROJECT_ID/reservations/ from the RESERVATION value.
Optional: If you chose to use a compact placement policy, then add the following flag to the command:
```
--resource-policies=POLICY_NAME
```
Replace the following:
- POLICY_NAME: the name of the compact placement policy.
Run the command.

Flex-start

Before you run the command, review all of the following steps to determine whether to include additional flags.

gcloud compute instance-templates create INSTANCE_TEMPLATE_NAME \
    --machine-type=MACHINE_TYPE \
    --image-family=IMAGE_FAMILY \
    --image-project=IMAGE_PROJECT \
    --instance-template-region=REGION \
    --boot-disk-type=DISK_TYPE \
    --boot-disk-size=DISK_SIZE \
    --scopes=cloud-platform \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-0,subnet=GVNIC_NAME_PREFIX-sub-0 \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-1,subnet=GVNIC_NAME_PREFIX-sub-1,no-address 
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-2,subnet=GVNIC_NAME_PREFIX-sub-2,no-address \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-3,subnet=GVNIC_NAME_PREFIX-sub-3,no-address \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-4,subnet=GVNIC_NAME_PREFIX-sub-4,no-address \
    --reservation-affinity=none \
    --instance-termination-action=DELETE \
    --max-run-duration=RUN_DURATION \
    --maintenance-policy=TERMINATE \
    --provisioning-model=FLEX_START

Complete the following steps:

Replace the following:
- INSTANCE_TEMPLATE_NAME: the name of the instance template.
- MACHINE_TYPE: the machine type to use for the A3 Edge instance. For more information, see GPU machine types in the Compute Engine documentation.
- IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of all supported operating systems, see Supported operating systems. For the A3 Edge machine series, we strongly recommend that you use the cos-121-lts or later Container-Optimized OS image and disable automatic updates.
- IMAGE_PROJECT: the project ID of the OS image. For example, use cos-cloud for the cos-121-lts or later Container-Optimized OS image.
- REGION: the region where you want to create the instance template. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU availability by regions and zones.
- DISK_TYPE: the type of the boot disk. For this machine series, we recommend that you use hyperdisk-balanced. For more information about the supported disk types for your machine type, see GPU machines in accelerator-optimized machine family in the Compute Engine documentation.
- DISK_SIZE: the size of the boot disk in GB. For more information, see either Google Cloud Hyperdisk size limits or Persistent Disk size limits based on the type of disk.
- GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- RUN_DURATION: the duration you want the requested VMs to run. You must format the value as the number of days, hours, minutes, or seconds followed by d, h, m, and s respectively. For example, specify 30m for 30 minutes or 1d2h3m4s for one day, two hours, three minutes, and four seconds. The value must be between 10 minutes and seven days.
Run the command.

Spot

Before you run the command, review all of the following steps to determine whether to include additional flags.

gcloud compute instance-templates create INSTANCE_TEMPLATE_NAME \
    --machine-type=MACHINE_TYPE \
    --image-family=IMAGE_FAMILY \
    --image-project=IMAGE_PROJECT \
    --instance-template-region=REGION \
    --boot-disk-type=DISK_TYPE \
    --boot-disk-size=DISK_SIZE \
    --scopes=cloud-platform \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-0,subnet=GVNIC_NAME_PREFIX-sub-0 \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-1,subnet=GVNIC_NAME_PREFIX-sub-1,no-address 
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-2,subnet=GVNIC_NAME_PREFIX-sub-2,no-address \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-3,subnet=GVNIC_NAME_PREFIX-sub-3,no-address \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-4,subnet=GVNIC_NAME_PREFIX-sub-4,no-address \
    --provisioning-model=SPOT \
    --instance-termination-action=TERMINATION_ACTION \
    --maintenance-policy=TERMINATE \
    --no-restart-on-failure

Complete the following steps:

Replace the following:
- INSTANCE_TEMPLATE_NAME: the name of the instance template.
- MACHINE_TYPE: the machine type to use for the A3 Edge instance. For more information, see GPU machine types in the Compute Engine documentation.
- IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of all supported operating systems, see Supported operating systems. For the A3 Edge machine series, we strongly recommend that you use the cos-121-lts or later Container-Optimized OS image and disable automatic updates.
- IMAGE_PROJECT: the project ID of the OS image. For example, use cos-cloud for the cos-121-lts or later Container-Optimized OS image.
- REGION: the region where you want to create the instance template. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU availability by regions and zones.
- DISK_TYPE: the type of the boot disk. For this machine series, we recommend that you use hyperdisk-balanced. For more information about the supported disk types for your machine type, see GPU machines in accelerator-optimized machine family in the Compute Engine documentation.
- DISK_SIZE: the size of the boot disk in GB. For more information, see either Google Cloud Hyperdisk size limits or Persistent Disk size limits based on the type of disk.
- GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- TERMINATION_ACTION: the action to take when Compute Engine preempts the instance, either STOP (default) or DELETE.
  
  Important: Make sure your application can handle preemption. For example, handle preemption by specifying a shutdown script during instance creation. Learn how to handle preemption with a shutdown script.
Optional: If you chose to use a compact placement policy, then add the following flag to the command:
```
--resource-policies=POLICY_NAME
```
Replace the following:
- POLICY_NAME: the name of the compact placement policy.
Run the command.

REST

To create a regional instance template, make a POST request to the regionInstanceTemplates.insert method.

The parameters that you need to specify depend on the consumption option that you are using for this deployment. Select the tab that corresponds to your consumption option.

Reservation

Before you submit the request, review all of the following steps to determine whether to include additional fields.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
  "name": "INSTANCE_TEMPLATE_NAME",
  "properties": {
    "machineType": "MACHINE_TYPE",
    "disks": [
      {
        "boot": true,
        "initializeParams": {
          "diskSizeGb": "DISK_SIZE",
          "diskType": "DISK_TYPE",
          "sourceImage": "projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
        },
        "mode": "READ_WRITE",
        "type": "PERSISTENT"
      }
    ],
    "serviceAccounts": [
      {
        "email": "default",
        "scopes": [
          "https://www.googleapis.com/auth/cloud-platform"
        ]
      }
    ],
    "networkInterfaces": [
      {
        "accessConfigs": [
          {
            "name": "external-nat",
            "type": "ONE_TO_ONE_NAT"
          }
        ],
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-0",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-0"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-1",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-1"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-2",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-2"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-3",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-3"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-4",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-4"
      }
    ],
    "reservationAffinity": {
        "consumeReservationType": "SPECIFIC_RESERVATION",
        "key": "compute.googleapis.com/reservation-name",
        "values": [
          "RESERVATION"
        ]
      },
    "scheduling": {
        "provisioningModel": "RESERVATION_BOUND",
        "instanceTerminationAction": "DELETE",
        "onHostMaintenance": "TERMINATE",
        "automaticRestart": true
      }
  }
}

Complete the following steps:

Replace the following:
- INSTANCE_TEMPLATE_NAME: the name of the instance template.
- MACHINE_TYPE: the machine type to use for the A3 Edge instance. For more information, see GPU machine types in the Compute Engine documentation.
- IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of all supported operating systems, see Supported operating systems. For the A3 Edge machine series, we strongly recommend that you use the cos-121-lts or later Container-Optimized OS image and disable automatic updates.
- IMAGE_PROJECT: the project ID of the OS image. For example, use cos-cloud for the cos-121-lts or later Container-Optimized OS image.
- REGION: the region where you want to create the instance template. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU availability by regions and zones.
- DISK_SIZE: the size of the boot disk in GB. For more information, see either Google Cloud Hyperdisk size limits or Persistent Disk size limits based on the type of disk.
- DISK_TYPE: the type of the boot disk. For this machine series, we recommend that you use hyperdisk-balanced. For more information about the supported disk types for your machine type, see GPU machines in accelerator-optimized machine family in the Compute Engine documentation.
- NETWORK_PROJECT_ID: the project ID of the network.
- GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- REGION: the region of the subnetwork.
- RESERVATION: either the reservation name or a specific block within a reservation. To get the reservation name or the available blocks, see View reserved capacity. Based on your requirement for instance placement, choose one of the following:
  - To create instances across blocks or on a single block:
```
projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME
```
    Additionally, for a single block, apply a compact placement policy that specifies a block collocation (maxDistance=2) . Compute Engine then applies the policy to the reservation and creates instances on the same block.
  - To create instances on a specific block:
```
projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME/reservationBlocks/RESERVATION_BLOCK_NAME
```
  Tip: If the reservation exists in the current project, then you can omit projects/RESERVATION_OWNER_PROJECT_ID/reservations/ from the RESERVATION value.
Optional: If you chose to use a compact placement policy, then add the following instanceProperties subfield to the request body:
```
    "resourcePolicies": [
      "projects/PROJECT_ID/regions/REGION/resourcePolicies/POLICY_NAME"
    ]
```
Replace the following:
- PROJECT_ID: the project ID of the compact placement policy.
- REGION: the region of the compact placement policy.
- POLICY_NAME: the name of the compact placement policy.
Submit the request.

Flex-start

Before you submit the request, review all of the following steps to determine whether to include additional fields.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
  "name": "INSTANCE_TEMPLATE_NAME",
  "properties": {
    "machineType": "MACHINE_TYPE",
    "disks": [
      {
        "boot": true,
        "initializeParams": {
          "diskSizeGb": "DISK_SIZE",
          "diskType": "DISK_TYPE",
          "sourceImage": "projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
        },
        "mode": "READ_WRITE",
        "type": "PERSISTENT"
      }
    ],
    "serviceAccounts": [
      {
        "email": "default",
        "scopes": [
          "https://www.googleapis.com/auth/cloud-platform"
        ]
      }
    ],
    "networkInterfaces": [
      {
        "accessConfigs": [
          {
            "name": "external-nat",
            "type": "ONE_TO_ONE_NAT"
          }
        ],
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-0",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-0"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-1",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-1"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-2",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-2"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-3",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-3"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-4",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-4"
      }
    ],
    "reservationAffinity": {
        "consumeReservationType": "NO_RESERVATION"
      },
    "scheduling": {
        "instanceTerminationAction": "DELETE",
        "maxRunDuration": {
          "seconds": RUN_DURATION
        },
        "onHostMaintenance": "TERMINATE",
        "provisioningModel": "FLEX_START"
      }

  }
}

Complete the following steps:

Replace the following:
- INSTANCE_TEMPLATE_NAME: the name of the instance template.
- MACHINE_TYPE: the machine type to use for the A3 Edge instance. For more information, see GPU machine types in the Compute Engine documentation.
- IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of all supported operating systems, see Supported operating systems. For the A3 Edge machine series, we strongly recommend that you use the cos-121-lts or later Container-Optimized OS image and disable automatic updates.
- IMAGE_PROJECT: the project ID of the OS image. For example, use cos-cloud for the cos-121-lts or later Container-Optimized OS image.
- REGION: the region where you want to create the instance template. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU availability by regions and zones.
- DISK_SIZE: the size of the boot disk in GB. For more information, see either Google Cloud Hyperdisk size limits or Persistent Disk size limits based on the type of disk.
- DISK_TYPE: the type of the boot disk. For this machine series, we recommend that you use hyperdisk-balanced. For more information about the supported disk types for your machine type, see GPU machines in accelerator-optimized machine family in the Compute Engine documentation.
- NETWORK_PROJECT_ID: the project ID of the network.
- GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- REGION: the region of the subnetwork.
- RUN_DURATION: the duration, in seconds, you want the requested VMs to run. The value must be between 600, which is 600 seconds (10 minutes), and 604800, which is 604,800 seconds (seven days).
Submit the request.

Spot

Before you submit the request, review all of the following steps to determine whether to include additional fields.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
  "name": "INSTANCE_TEMPLATE_NAME",
  "properties": {
    "machineType": "MACHINE_TYPE",
    "disks": [
      {
        "boot": true,
        "initializeParams": {
          "diskSizeGb": "DISK_SIZE",
          "diskType": "DISK_TYPE",
          "sourceImage": "projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
        },
        "mode": "READ_WRITE",
        "type": "PERSISTENT"
      }
    ],
    "serviceAccounts": [
      {
        "email": "default",
        "scopes": [
          "https://www.googleapis.com/auth/cloud-platform"
        ]
      }
    ],
    "networkInterfaces": [
      {
        "accessConfigs": [
          {
            "name": "external-nat",
            "type": "ONE_TO_ONE_NAT"
          }
        ],
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-0",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-0"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-1",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-1"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-2",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-2"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-3",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-3"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-4",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-4"
      }
    ],
    "scheduling":
    {
      "provisioningModel": "SPOT",
      "instanceTerminationAction": "TERMINATION_ACTION",
      "onHostMaintenance": "TERMINATE",
      "automaticRestart": false
    }
  }
}

Complete the following steps:

Replace the following:
- INSTANCE_TEMPLATE_NAME: the name of the instance template.
- MACHINE_TYPE: the machine type to use for the A3 Edge instance. For more information, see GPU machine types in the Compute Engine documentation.
- IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of all supported operating systems, see Supported operating systems. For the A3 Edge machine series, we strongly recommend that you use the cos-121-lts or later Container-Optimized OS image and disable automatic updates.
- IMAGE_PROJECT: the project ID of the OS image. For example, use cos-cloud for the cos-121-lts or later Container-Optimized OS image.
- REGION: the region where you want to create the instance template. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU availability by regions and zones.
- DISK_SIZE: the size of the boot disk in GB. For more information, see either Google Cloud Hyperdisk size limits or Persistent Disk size limits based on the type of disk.
- DISK_TYPE: the type of the boot disk. For this machine series, we recommend that you use hyperdisk-balanced. For more information about the supported disk types for your machine type, see GPU machines in accelerator-optimized machine family in the Compute Engine documentation.
- NETWORK_PROJECT_ID: the project ID of the network.
- GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- REGION: the region of the subnetwork.
- TERMINATION_ACTION: the action to take when Compute Engine preempts the instance, either STOP (default) or DELETE.
  
  Important: Make sure your application can handle preemption. For example, handle preemption by specifying a shutdown script during instance creation. Learn how to handle preemption with a shutdown script.
Optional: If you chose to use a compact placement policy, then add the following instanceProperties subfield to the request body:
```
    "resourcePolicies": [
      "projects/PROJECT_ID/regions/REGION/resourcePolicies/POLICY_NAME"
    ]
```
Replace the following:
- PROJECT_ID: the project ID of the compact placement policy.
- REGION: the region of the compact placement policy.
- POLICY_NAME: the name of the compact placement policy.
Submit the request.

After you create the instance template, you can view it to see its ID and review its instance properties.

Create a MIG

After you complete all the previous steps, create a MIG based on your scenario as follows:

Scenario	Method to create a MIG and VMs in it	Example
You have multiple or parallel jobs that can start with any number of VMs.	Create a MIG and use the target size to specify the number of VMs that you want in the group. See Create a MIG with a target size.	ML inference jobs
You have a job that requires distribution across an exact number of VMs.	Create a MIG without any VMs in it, and then create a resize request in the MIG. The resize request helps you to obtain VMs all at once. See Create a MIG and a resize request.	Distributed ML training and fine-tuning jobs

Create a MIG with a target size

If you can start your job without creating all of the VMs at once, then create a MIG with a target size. The target size determines the number of VMs in the MIG. When you specify a target size, the MIG starts creating VMs based on current resource availability. If any resources are temporarily unavailable, then the MIG continuously attempts to create VMs to meet the target size.

To create a MIG with a target size, select one of the following options:

gcloud

To create a MIG with a specified target size, use the instance-groups managed create command.

Important: If the instance template specifies Flex-start VMs, then you must also turn off repairs by adding the --default-action-on-vm-failure=do-nothing flag to the command.

Create a zonal or regional MIG as follows:

To create a zonal MIG, use the following command:

gcloud compute instance-groups managed create MIG_NAME \
  --template=INSTANCE_TEMPLATE_URL \
  --size=TARGET_SIZE \
  --zone=ZONE

To create a regional MIG, use the following command:

gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=TARGET_SIZE \
    --region=REGION

Replace the following:

MIG_NAME: the name of the MIG.
INSTANCE_TEMPLATE_URL: the URL of the instance template that you want to use to create instances in the MIG. The URL can contain either the ID or name of the instance template. Specify one of the following values:
- For a regional instance template: projects/PROJECT_ID/regions/REGION/instanceTemplates/INSTANCE_TEMPLATE_ID
- For a global instance template: INSTANCE_TEMPLATE_ID
TARGET_SIZE: the number of instances that you want in the MIG.
ZONE: the zone in which you want to create the MIG.
REGION: the region in which you want to create the MIG. For a regional MIG, instead of a region, you can specify the zones in that region by using the --zones flag.

REST

To create a MIG with a specified target size, make a POST request.

Important: If the instance template specifies Flex-start VMs, then you must also turn off repairs by adding the "defaultActionOnFailure": "DO_NOTHING" field to the request.

Create a zonal or regional MIG as follows:

To create a zonal MIG, make a POST request to the instanceGroupManagers.insert method.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers
{
  "versions": [
    {
      "instanceTemplate": "INSTANCE_TEMPLATE_URL"
    }
  ],
  "name": "MIG_NAME",
  "targetSize": TARGET_SIZE
}

To create a regional MIG, make a POST request to the regionInstanceGroupManagers.insert method.

  POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers
  {
    "name": "MIG_NAME",
    "instanceTemplate": "INSTANCE_TEMPLATE_URL",
    "targetSize": TARGET_SIZE
  }

Replace the following:

PROJECT_ID: the project ID.
ZONE: the zone in which you want to create the MIG.
REGION: the region in which you want to create the MIG.
INSTANCE_TEMPLATE_URL: the URL of the instance template that you want to use to create instances in the MIG. The URL can contain either the ID or name of the instance template. Specify one of the following values:
- For a regional instance template: projects/PROJECT_ID/regions/REGION/instanceTemplates/INSTANCE_TEMPLATE_ID
- For a global instance template: INSTANCE_TEMPLATE_ID
MIG_NAME: the name of the MIG.
TARGET_SIZE: the number of instances that you want in the MIG.

Create a MIG and a resize request

If you require multiple VMs all at once to start a job, then create a MIG, and create a resize request in the MIG as described in this section.

To create a resize request in a MIG, select one of the following options:

gcloud

The parameters that you need to specify depend on the consumption option that you are using for this deployment. Select the tab that corresponds to your consumption option's provisioning model.

Reservation

Create a zonal or regional MIG and a resize request as follows:

To create a zonal MIG and a resize request in it, do the following:
1. Create a zonal MIG using the instance-groups managed create command as follows.
```
gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --zone=ZONE
```
2. Create a resize request in the zonal MIG using the instance-groups managed resize-requests create command as follows. This command specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
gcloud compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --resize-by=COUNT \
    --zone=ZONE
```
To create a regional MIG and a resize request in it, do the following:
1. Create a regional MIG using the instance-groups managed create command as follows.
```
gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --zones=ZONE \
    --target-distribution-shape=any-single-zone \
    --instance-redistribution-type=none
  
```
2. Create a resize request in the regional MIG using the instance-groups managed resize-requests create command as follows. This command specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
gcloud compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --resize-by=COUNT \
    --region=REGION
```

Flex-start

Create a zonal or regional MIG and a resize request as follows:

To create a zonal MIG and a resize request in it, do the following:
1. Create a zonal MIG using the instance-groups managed create command as follows.
```
gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --default-action-on-vm-failure=do-nothing \
    --zone=ZONE
```
2. Create a resize request in the zonal MIG using the instance-groups managed resize-requests create command as follows. This command specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
gcloud compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --resize-by=COUNT \
    --zone=ZONE
```

To create a regional MIG and a resize request in it, do the following:

Create a regional MIG using the instance-groups managed create command as follows.

gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --default-action-on-vm-failure=do-nothing \

    --region=REGION \
    --target-distribution-shape=any-single-zone \
    --instance-redistribution-type=none

Create a resize request in the regional MIG using the instance-groups managed resize-requests create command as follows. This command specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
gcloud compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --resize-by=COUNT \
    --region=REGION
```

Spot

Create a zonal or regional MIG and a resize request as follows:

To create a zonal MIG and a resize request in it, do the following:
1. Create a zonal MIG using the instance-groups managed create command as follows.
```
gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --zone=ZONE
```
2. Create a resize request in the zonal MIG using the instance-groups managed resize-requests create command as follows. This command specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
gcloud compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --resize-by=COUNT \
    --zone=ZONE
```
To create a regional MIG and a resize request in it, do the following:
1. Create a regional MIG using the instance-groups managed create command as follows.
```
gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --zones=ZONE \
    --target-distribution-shape=any-single-zone \
    --instance-redistribution-type=none
  
```
2. Create a resize request in the regional MIG using the instance-groups managed resize-requests create command as follows. This command specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
gcloud compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --resize-by=COUNT \
    --region=REGION
```

Replace the following:

MIG_NAME: the name of the MIG.
INSTANCE_TEMPLATE_URL: the URL of the instance template that you want to use to create instances in the MIG. The URL can contain either the ID or name of the instance template. Specify one of the following values:
- For a regional instance template: projects/PROJECT_ID/regions/REGION/instanceTemplates/INSTANCE_TEMPLATE_ID
- For a global instance template: INSTANCE_TEMPLATE_ID
ZONE: the zone in which you want to create the MIG. For a regional MIG also, you must specify a zone. This zone must be the zone that contains the profile for your VPC network and must be a zone where the machine type is available. For more information, see Limitations.
RESIZE_REQUEST_NAME: the name of the resize request, which must be unique within the specified MIG. Otherwise, creating the resize request fails.
COUNT: the number of instances to add to the MIG all at once.
REGION: the region in which you want to create the MIG.

Create a resize request by specifying a list of VM names

If your workload requires specific VM names, then specify a list of names to create the VMs. The number of names that you specify determines the number of VMs that the MIG creates all at once.

To create a resize request with specific VM names in a MIG, use the beta gcloud compute instance-groups managed resize-requests create command with the --instances flag:

In a zonal MIG, run the following command:

gcloud beta compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --instances=INSTANCE_NAMES \
    --zone=ZONE

In a regional MIG, run the following command:

gcloud beta compute instance-groups managed resize-requests create MIG_NAME \
    --resize-request=RESIZE_REQUEST_NAME \
    --instances=INSTANCE_NAMES \
    --region=REGION

Replace INSTANCE_NAMES with a comma-separated list of names for the VMs. For example, instance-1,instance-2,instance-3.

REST

The parameters that you need to specify depend on the consumption option that you are using for this deployment. Select the tab that corresponds to your consumption option's provisioning model.

Reservation

Create a zonal or regional MIG and a resize request as follows:

To create a zonal MIG and a resize request in it, do the following:
1. Create a zonal MIG by making a POST request to the instanceGroupManagers.insert method as follows.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers
{
  "versions": [
    {
      "instanceTemplate": "INSTANCE_TEMPLATE_URL"
    }
  ],
  "name": "MIG_NAME",
  "targetSize": 0
}
```
2. Create a resize request in the zonal MIG by making a POST request to the instanceGroupManagerResizeRequests.insert method as follows. This request specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}
```

To create a regional MIG and a resize request in it, do the following:

Create a regional MIG by making a POST request to the regionInstanceGroupManagers.insert method as follows.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers
{
  "versions": [
    {
      "instanceTemplate": "INSTANCE_TEMPLATE_URL"
    }
  ],
  "name": "MIG_NAME",
  "targetSize": 0,
  "distributionPolicy": {
    "targetShape": "ANY_SINGLE_ZONE",
    "zones": [
      {
        "zone": "projects/PROJECT_ID/zones/ZONE"
      }
    ]
  },
  "updatePolicy": {
    "instanceRedistributionType": "NONE"
  }
}

Create a resize request in the regional MIG by making a POST request to the regionInstanceGroupManagerResizeRequests.insert method as follows. This request specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}
```

Flex-start

Create a zonal or regional MIG and a resize request as follows:

To create a zonal MIG and a resize request in it, do the following:

Create a zonal MIG by making a POST request to the instanceGroupManagers.insert method as follows.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers
{
  "versions": [
    {
      "instanceTemplate": "INSTANCE_TEMPLATE_URL"
    }
  ],
  "name": "MIG_NAME",
  "targetSize": 0,
  "instanceLifecyclePolicy": {
    "defaultActionOnFailure": "DO_NOTHING"
  }
}

Create a resize request in the zonal MIG by making a POST request to the instanceGroupManagerResizeRequests.insert method as follows. This request specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}
```

To create a regional MIG and a resize request in it, do the following:

Create a regional MIG by making a POST request to the regionInstanceGroupManagers.insert method as follows.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers
{
  "versions": [
    {
      "instanceTemplate": "INSTANCE_TEMPLATE_URL"
    }
  ],
  "name": "MIG_NAME",
  "targetSize": 0,
  "distributionPolicy": {
    "targetShape": "ANY_SINGLE_ZONE",
    "zones": [
      {
        "zone": "projects/PROJECT_ID/zones/ZONE"
      }
    ]
  },
  "updatePolicy": {
    "instanceRedistributionType": "NONE"
  },
  "instanceLifecyclePolicy": {
    "defaultActionOnFailure": "DO_NOTHING"
  }
}

Create a resize request in the regional MIG by making a POST request to the regionInstanceGroupManagerResizeRequests.insert method as follows. This request specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}
```

Spot

Create a zonal or regional MIG and a resize request as follows:

To create a zonal MIG and a resize request in it, do the following:
1. Create a zonal MIG by making a POST request to the instanceGroupManagers.insert method as follows.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers
{
  "versions": [
    {
      "instanceTemplate": "INSTANCE_TEMPLATE_URL"
    }
  ],
  "name": "MIG_NAME",
  "targetSize": 0
}
```
2. Create a resize request in the zonal MIG by making a POST request to the instanceGroupManagerResizeRequests.insert method as follows. This request specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}
```

To create a regional MIG and a resize request in it, do the following:

Create a regional MIG by making a POST request to the regionInstanceGroupManagers.insert method as follows.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers
{
  "versions": [
    {
      "instanceTemplate": "INSTANCE_TEMPLATE_URL"
    }
  ],
  "name": "MIG_NAME",
  "targetSize": 0,
  "distributionPolicy": {
    "targetShape": "ANY_SINGLE_ZONE",
    "zones": [
      {
        "zone": "projects/PROJECT_ID/zones/ZONE"
      }
    ]
  },
  "updatePolicy": {
    "instanceRedistributionType": "NONE"
  }
}

Create a resize request in the regional MIG by making a POST request to the regionInstanceGroupManagerResizeRequests.insert method as follows. This request specifies the number of VMs that you want to create. If your workload requires specific VM names, then create a resize request by specifying a list of VM names.
```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}
```

Replace the following:

PROJECT_ID: the project ID.
ZONE: the zone in which you want to create the MIG. This zone must be the same as the zone that contains the profile for your VPC network and must be a zone where your chosen machine type is available. For more information, see Limitations.
REGION: the region in which you want to create the MIG. This region must be the same region that contains the profile for your VPC network and must contain a zone where your chosen machine type is available. For more information, see Limitations.
INSTANCE_TEMPLATE_URL: the URL of the instance template that you want to use to create instances in the MIG. The URL can contain either the ID or name of the instance template. Specify one of the following values:
- For a regional instance template: projects/PROJECT_ID/regions/REGION/instanceTemplates/INSTANCE_TEMPLATE_ID
- For a global instance template: INSTANCE_TEMPLATE_ID
MIG_NAME: the name of the MIG.
RESIZE_REQUEST_NAME: the name of the resize request, which must be unique within the specified MIG. Otherwise, creating the resize request fails.
COUNT: the number of instances to add to the MIG all at once

Create a resize request by specifying a list of VM names

If your workload requires specific VM names, then specify a list of names to create the VMs. The number of names that you specify determines the number of VMs that the MIG creates all at once.

To create a resize request with specific VM names in a MIG, use one of the following methods:

In a zonal MIG, send a POST request by using the beta.instanceGroupManagerResizeRequests.insert method:

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/MIG_NAME/resizeRequests

In a regional MIG, send a POST request by using the beta.regionInstanceGroupManagerResizeRequests.insert method:

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/instanceGroupManagers/MIG_NAME/resizeRequests

For example, to specify two VM names, include the following in the request body:

{
  "name": "RESIZE_REQUEST_NAME",
  "instances": [
    {
      "name": "INSTANCE_NAME_1"
    },
    {
      "name": "INSTANCE_NAME_2"
    }
  ]
}

Replace INSTANCE_NAME_1, INSTANCE_NAME_2 with the names for the VMs.

Create an AI-optimized MIG with A3 Edge machine type Stay organized with collections Save and categorize content based on your preferences.

Limitations

Limitations for A3 Edge VMs

Limitations for the MIG

Limitations for MIG resize requests

Before you begin

Required roles

Required permissions

Overview

Create VPC networks

Create management network, subnet, and firewall rule

Create data networks, subnets, and firewall rule

Optional: Create a compact placement policy

gcloud

REST

Create an instance template

gcloud

Reservation

Flex-start

Spot

REST

Reservation

Flex-start

Spot

Create a MIG

Create a MIG with a target size

gcloud

REST

Create a MIG and a resize request

gcloud

Reservation

Flex-start

Spot

Create a resize request by specifying a list of VM names

REST

Reservation

Flex-start

Spot

Create a resize request by specifying a list of VM names

What's next?

Create an AI-optimized MIG with A3 Edge machine type