Create a HPC MIG with H4D machine series

This document describes how to create a managed instance group (MIG) that uses a H4D machine type.

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 VMs in the group, MIGs offer high availability and scalability. To learn more about MIGs, see Managed instance groups.

To learn about HPC VM and HPC cluster creation options, see Overview of HPC cluster creation.

If you want to create a MIG but aren't using H4D machine types, or you don't need to create a dense deployment of instances, then see Basic scenarios for creating managed instance groups (MIGs).

Before you begin

Choose a consumption option: to create compute instances in bulk and enable enhanced cluster management capabilities, you can choose a Future Reservation in Calendar mode or Spot VMs.

If you choose to use Spot VMs, the VMs might not be compactly collocated. Also, Spot VMs can be preempted as needed and they are not eligible for managing host maintenance events for groups of VMs.
Obtain capacity: the process to obtain capacity differs for each consumption option.

To learn more, see Choose a consumption option and obtain capacity.
If you haven't already, set up authentication. Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:
Select the tab for how you plan to use the samples on this page:
Console

When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloud
1. Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:
  gcloud init
  If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
  
  Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
2. Set a default region and zone.
REST

To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.
For more information, see Authenticate for using REST in the Google Cloud authentication documentation.

Overview

Creating a MIG with the H4D machine type includes the following steps:

Create VPC networks
Optional: Create a workload policy
Create an instance template
Create a MIG

Limitations

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

If the instance template to use for the MIG specifies the flex-start provisioning model, then the following limitations apply:
- You can only add VMs to the MIG using resize requests.
- You can't apply a workload policy to the MIG.
- You must turn off repairs in the MIG.

If you create a regional MIG, then the MIG can only create VMs in the zone that contains your VPC network's profile.
You can't configure instance flexibility in the MIG.
If you apply a workload policy to a MIG, you cannot change the policy in the MIG when the group has VMs in it. To change the policy in a MIG that has VMs, you must first resize the MIG to zero.
You can't use an instance template that specifies a placement policy to create a MIG that uses a workload policy.

When you create MIG resize requests, the following limitations apply:
- In a regional MIG, you can use only the ANY_SINGLE_ZONE target distribution shape (Preview). Other distribution shapes aren't supported.
- 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 do the following:
  - You can't add a second instance template to initiate a canary update in the MIG.
  - 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.

Optional: Create VPC networks

When you create a compute instance, you can specify a VPC network and subnet. If you omit this configuration, the default network and subnet are used.

If you want to configure the H4D instances in the MIG to use Cloud RDMA, then complete the steps in this section; otherwise, you can skip this section and use the default network instead.

To use Cloud RDMA with H4D instances, you must have at least two networks configured, one for each type of network interface (NIC):

NIC type GVNIC: uses the gve driver for TCP/IP and Internet traffic for normal VM-VM and VM-Internet communication.
NIC type IRDMA: uses IDPF/iRDMA drivers for Cloud RDMA networking between instances.

Instances that use Cloud RDMA can have only one IRDMA interface. You can add up to eight additional GVNIC network interfaces for a total of 10 vNICs per instance.

To set up the Falcon VPC networks to use with your instances, you can either follow the documented instructions or use the provided script.

Instruction guides

To create the networks, you can use the following instructions:

To create the host networks for the GVNIC network interfaces, see Create and manage VPC networks.

If you are configuring only one GVNIC network interface, you can use the default VPC network and the auto subnet that's in the same region as the instance.
To create a network for the IRDMA network interface, see Create a VPC network with a Falcon VPC network profile. Use the default value for the maximum transmission unit (MTU) for a Falcon VPC network, which is 8896.

Script

You can create up to nine gVNIC network interfaces and one IRDMA network interface per instance. Each network interface must attach to a separate network. To create the networks, you can use the following script, which creates two networks for gVNIC and one network for IRDMA.

Optional: Before running the script, list the Falcon VPC network profiles to verify there is one available.
```
  gcloud compute network-profiles list
  
```

Copy the following code and run it in a Linux shell window.

  #!/bin/bash
  # Set the number of GVNIC interfaces to create. You can create up to 9.
  NUM_GVNIC=NUMBER_OF_GVNIC

  # Create regular VPC networks and subnets for the GVNIC interfaces
    for N in $(seq 0 $(($NUM_GVNIC - 1))); do
      gcloud compute networks create GVNIC_NAME_PREFIX-net-$N \
          --subnet-mode=custom

      gcloud compute networks subnets create GVNIC_NAME_PREFIX-sub-$N \
          --network=GVNIC_NAME_PREFIX-net-$N \
          --region=REGION \
          --range=10.$N.0.0/16

      gcloud compute firewall-rules create GVNIC_NAME_PREFIX-internal-$N \
          --network=GVNIC_NAME_PREFIX-net-$N \
          --action=ALLOW \
          --rules=tcp:0-65535,udp:0-65535,icmp \
          --source-ranges=10.0.0.0/8
  done

  # Create SSH firewall rules
  gcloud compute firewall-rules create GVNIC_NAME_PREFIX-ssh \
      --network=GVNIC_NAME_PREFIX-net-0 \
      --action=ALLOW \
      --rules=tcp:22 \
      --source-ranges=IP_RANGE

  # Optional: Create a firewall rule for the external IP address for the
  #  first GVNIC network interface
  gcloud compute firewall-rules create GVNIC_NAME_PREFIX-allow-ping-net-0 \
      --network=GVNIC_NAME_PREFIX-net-0 \
      --action=ALLOW \
      --rules=icmp \
      --source-ranges=IP_RANGE

  # Create a Falcon VPC network for the Cloud RDMA network interface
  gcloud compute networks create RDMA_NAME_PREFIX-irdma \
      --network-profile=ZONE-vpc-falcon \
      --subnet-mode custom

  # Create a subnet in the Falcon VPC network
  gcloud compute networks subnets create RDMA_NAME_PREFIX-irdma-sub \
      --network=RDMA_NAME_PREFIX-irdma \
      --region=REGION \
      --range=10.2.0.0/16  # offset to avoid overlap with GVNIC subnet ranges

Replace the following:

NUMBER_OF_GVNIC: the number of GVNIC interfaces to create. Specify a number from 1 to 9.
GVNIC_NAME_PREFIX: the name prefix to use for the regular VPC network and subnet that uses a GVNIC NIC type.
REGION: the region where you want to create the networks. This must correspond to the zone specified for the --network-profile flag, when creating the Falcon VPC network. For example, if you specify the zone as europe-west4-b, then your region is europe-west4.
IP_RANGE: the range of IP addresses outside of the VPC network to use for the SSH firewall rules. As a best practice, specify the specific IP address ranges that you need to allow access from, rather than all IPv4 or IPv6 sources. Don't use 0.0.0.0/0 or ::/0 as a source range because this allows traffic from all IPv4 or IPv6 sources, including sources outside of Google Cloud.
RDMA_NAME_PREFIX: the name prefix to use for the VPC network and subnet that uses the IRDMA NIC type.
ZONE: the zone where you want to create the networks and compute instances. Use either us-central1-a or europe-west4-b.

Optional: To verify that the VPC network resources are created successfully, check the network settings in the Google Cloud console:
1. In the Google Cloud console, go to the VPC networks page.
  Go to VPC networks
2. Search the list for the networks that you created in the previous step.
3. To view the subnets, firewall rules, and other network settings, click the name of the network.

Optional: Create a workload policy

If you want Compute Engine to place VM instances in a single block or adjacent blocks, then specify instance placement by creating a workload policy. However if you want Compute Engine to place your instances on a specific block, then skip this step and provide the name of the block in the reservation affinity when you create the instance template.

If you already have a workload policy, you can reuse it. When you apply a workload policy to your MIG, Compute Engine makes best-effort attempts to create instances that are as close to each other as possible. If your application is latency-sensitive and you want the instances to be closer together (maximum compactness), then specify the maxTopologyDistance field when creating a workload policy.

You cannot update a workload policy after you create it. To make changes in a workload policy, you must create a new one.

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

gcloud

To create a workload policy, use the gcloud compute resource-policies create workload-policy command.

For a best-effort placement of VMs, specify only the --type=high-throughput flag in the command:

gcloud compute resource-policies create workload-policy WORKLOAD_POLICY_NAME \
    --type=high-throughput \
    --region=REGION

For strict colocation of VMs, specify the --max-topology-distance flag in the command:

gcloud compute resource-policies create workload-policy WORKLOAD_POLICY_NAME \
    --type=high-throughput \
    --max-topology-distance=TOPOLOGY_DISTANCE \
    --region=REGION

Replace the following:

WORKLOAD_POLICY_NAME: the name of the workload policy.
REGION: the region where you want to create the workload policy. Specify a region in which you want to create the MIG and the machine type that you want to use is available. For information about regions and zones, see Available regions and zones.

REST

To create a workload policy, make a POST request to the resourcePolicies.insert method.

For a best-effort placement of VMs, specify only the type field in the request as follows:

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/resourcePolicies
  {
    "name": "WORKLOAD_POLICY_NAME"
    "workloadPolicy": {
      "type": "HIGH_THROUGHPUT"
    }
  }

For strict colocation of VMs, specify the maxTopologyDistance field in the request as follows:

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/resourcePolicies
  {
    "name": "WORKLOAD_POLICY_NAME"
    "workloadPolicy": {
      "type": "HIGH_THROUGHPUT",
      "maxTopologyDistance": "TOPOLOGY_DISTANCE"
    }
  }

Replace the following:

PROJECT_ID: your project ID
REGION: the region where you want to create the workload policy. Specify a region in which you want to create the MIG and the machine type that you want to use is available. For information about regions and zones, see Available regions and zones.
WORKLOAD_POLICY_NAME: the name of the workload policy.

Create an instance template

To specify the instance and consumption properties for each instance in the MIG, create an instance template by using one of the following methods.

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.

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 and provisioning model.

Flex-start

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

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=hyperdisk-balanced \
    --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, \
      stack-type=STACK_TYPE, \
      address=EXTERNAL_IPV4_ADDRESS \
--network-interface=nic-type=GVNIC, \
      network=GVNIC_NAME_PREFIX-net-1, \
      subnet=GVNIC_NAME_PREFIX-sub-1,no-address \
--network-interface=nic-type=IRDMA, \
      network=RDMA_NAME_PREFIX-irdma, \
      subnet=RDMA_NAME_PREFIX-irdma-sub, \
      stack-type=IPV4_ONLY,no-address \
    
    --reservation-affinity=none \
    --instance-termination-action=DELETE \
    --max-run-duration=RUN_DURATION \
    --maintenance-policy=TERMINATE \
    --provisioning-model=FLEX_START

Replace the following:

INSTANCE_TEMPLATE_NAME: the name of the instance template.
MACHINE_TYPE: the H4D machine type to use for the instance.
IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Supported operating systems.
IMAGE_PROJECT: the project ID of the 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.
DISK_SIZE: the size of the boot disk in GiB.
GVNIC_NAME_PREFIX: the name prefix that you used when creating the standard VPC networks and subnets for the gVNIC interfaces.

If you are using the default network, include only a single --network-interface field with the nic-type field set to GVNIC. Also, omit the network and subnetwork settings for this network interface.
STACK_TYPE: Optional: the stack type to use for the gVNIC interface. Specify either IPV4_ONLY or IPV4_IPV6. If you don't specify a value, IPV4_ONLY is used by default.
EXTERNAL_IPV4_ADDRESS: Optional: a static external IPv4 address to use with the gVNIC network interface. You must have previously reserved an external IPv4 address. Do one of the following:
- Specify a valid IPv4 address from the subnet.
- Use the flag no-address if you don't want the network interface to have an external IP address.
- Specify address='' if you want the network interface to receive an ephemeral external IP address.
To specify an external IPv6 address for the GVNIC network interface, use the flag --external-ipv6-address instead.
RDMA_NAME_PREFIX: the name prefix that you used when creating the VPC network and subnet for the IRDMA network interface.

If you are not using Cloud RDMA with your H4D instances, omit the --network-interface field for the IRDMA interface.
RUN_DURATION: the duration you want the requested instances 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.

Reservation-bound

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

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=hyperdisk-balanced \
    --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, \
      stack-type=STACK_TYPE, \
      address=EXTERNAL_IPV4_ADDRESS \
--network-interface=nic-type=GVNIC, \
      network=GVNIC_NAME_PREFIX-net-1, \
      subnet=GVNIC_NAME_PREFIX-sub-1,no-address \
--network-interface=nic-type=IRDMA, \
      network=RDMA_NAME_PREFIX-irdma, \
      subnet=RDMA_NAME_PREFIX-irdma-sub, \
      stack-type=IPV4_ONLY,no-address \
    --reservation-affinity=specific \
    --reservation=RESERVATION \
    --provisioning-model=RESERVATION_BOUND \
    --instance-termination-action=DELETE \
    --maintenance-policy=TERMINATE

Replace the following:

INSTANCE_TEMPLATE_NAME: the name of the instance template.
MACHINE_TYPE: the H4D machine type to use for the instance.
IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Supported operating systems.
IMAGE_PROJECT: the project ID of the 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.
DISK_SIZE: the size of the boot disk in GiB.
GVNIC_NAME_PREFIX: the name prefix that you used when creating the standard VPC networks and subnets for the gVNIC interfaces.

If you are using the default network, include only a single --network-interface field with the nic-type field set to GVNIC. Also, omit the network and subnetwork settings for this network interface.
STACK_TYPE: Optional: the stack type to use for the gVNIC interface. Specify either IPV4_ONLY or IPV4_IPV6. If you don't specify a value, IPV4_ONLY is used by default.
EXTERNAL_IPV4_ADDRESS: Optional: a static external IPv4 address to use with the gVNIC network interface. You must have previously reserved an external IPv4 address. Do one of the following:
- Specify a valid IPv4 address from the subnet.
- Use the flag no-address if you don't want the network interface to have an external IP address.
- Specify address='' if you want the network interface to receive an ephemeral external IP address.
To specify an external IPv6 address for the GVNIC network interface, use the flag --external-ipv6-address instead.
RDMA_NAME_PREFIX: the name prefix that you used when creating the VPC network and subnet for the IRDMA network interface.

If you are not using Cloud RDMA with your H4D instances, omit the --network-interface field for the IRDMA interface.
RESERVATION: the name of the reservation that you want to use.
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, create the MIG by applying a workload policy that specifies a block collocation (maxTopologyDistance=BLOCK) . 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.

Spot

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

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=hyperdisk-balanced \
    --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, \
      stack-type=STACK_TYPE, \
      address=EXTERNAL_IPV4_ADDRESS \
--network-interface=nic-type=GVNIC, \
      network=GVNIC_NAME_PREFIX-net-1, \
      subnet=GVNIC_NAME_PREFIX-sub-1,no-address \
--network-interface=nic-type=IRDMA, \
      network=RDMA_NAME_PREFIX-irdma, \
      subnet=RDMA_NAME_PREFIX-irdma-sub, \
      stack-type=IPV4_ONLY,no-address \
    --provisioning-model=SPOT \
    --instance-termination-action=TERMINATION_ACTION

Replace the following:

INSTANCE_TEMPLATE_NAME: the name of the instance template.
MACHINE_TYPE: the H4D machine type to use for the instance.
IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Supported operating systems.
IMAGE_PROJECT: the project ID of the 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.
DISK_SIZE: the size of the boot disk in GiB.
GVNIC_NAME_PREFIX: the name prefix that you used when creating the standard VPC networks and subnets for the gVNIC interfaces.

If you are using the default network, include only a single --network-interface field with the nic-type field set to GVNIC. Also, omit the network and subnetwork settings for this network interface.
STACK_TYPE: Optional: the stack type to use for the gVNIC interface. Specify either IPV4_ONLY or IPV4_IPV6. If you don't specify a value, IPV4_ONLY is used by default.
EXTERNAL_IPV4_ADDRESS: Optional: a static external IPv4 address to use with the gVNIC network interface. You must have previously reserved an external IPv4 address. Do one of the following:
- Specify a valid IPv4 address from the subnet.
- Use the flag no-address if you don't want the network interface to have an external IP address.
- Specify address='' if you want the network interface to receive an ephemeral external IP address.
To specify an external IPv6 address for the GVNIC network interface, use the flag --external-ipv6-address instead.
RDMA_NAME_PREFIX: the name prefix that you used when creating the VPC network and subnet for the IRDMA network interface.

If you are not using Cloud RDMA with your H4D instances, omit the --network-interface field for the IRDMA interface.
TERMINATION_ACTION: whether Compute Engine stops (STOP) or deletes (DELETE) the Spot VMs on preemption.

Important: Make sure your application can handle preemption. For example, we recommend that you handle preemption by specifying a shutdown script during instance creation. Learn how to handle preemption with a shutdown script.

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 and provisioning model.

Flex-start

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

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
  "name":"INSTANCE_TEMPLATE_NAME",
  "properties":{
    "disks":[
      {
        "boot":true,
        "initializeParams":{
          "diskSizeGb":"DISK_SIZE",
          "diskType":"hyperdisk-balanced",
          "sourceImage":"projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
        },
        "mode":"READ_WRITE",
        "type":"PERSISTENT"
      }
    ],
    "machineType":"MACHINE_TYPE",
    
        "networkInterfaces": [
        {
          "network": "GVNIC_NAME_PREFIX-net-0",
          "subnetwork": "GVNIC_NAME_PREFIX-sub-0",
          "accessConfigs": [
            {
                "type": "ONE_TO_ONE_NAT",
                "name": "External IP",
                "natIP": "EXTERNAL_IPV4_ADDRESS"
            }
          ],
          "stackType": "IPV4_ONLY",
          "nicType": "GVNIC",
      },
      {
          "network": "GVNIC_NAME_PREFIX-net-1",
          "subnetwork": "GVNIC_NAME_PREFIX-sub-1",
          "stackType": "IPV4_ONLY",
          "nicType": "GVNIC",
      },
      {
          "network": "RDMA_NAME_PREFIX-irdma",
          "subnetwork": "RDMA_NAME_PREFIX-irdma-sub",
          "stackType": "IPV4_ONLY",
          "nicType": "IRDMA",
      }
    ],
,
    "reservationAffinity": {
        "consumeReservationType": "NO_RESERVATION"
      },
    "scheduling": {
        "instanceTerminationAction": "DELETE",
        "maxRunDuration": {
          "seconds": RUN_DURATION
        },
        "onHostMaintenance": "TERMINATE",
        "provisioningModel": "FLEX_START"
      }

  }
}

Replace the following:

INSTANCE_TEMPLATE_NAME: the name of the instance template.
MACHINE_TYPE: the machine type to use for the instance. Specify a H4D machine type. For more information, see H4D machine types.
IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Supported operating systems.
IMAGE_PROJECT: the project ID of the 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 Regions and zones.
DISK_SIZE: the size of the boot disk in GiB.
GVNIC_NAME_PREFIX: the name prefix that you used when creating the standard VPC networks and subnets for the gVNIC interfaces.

If you are using the default network, include only a single --network-interface field with the nic-type field set to GVNIC. Also, omit the network and subnetwork settings for this network interface.
EXTERNAL_IPV4_ADDRESS: Optional: a static external IPv4 address to use with the gVNIC network interface. You must have previously reserved an external IPv4 address.
To specify an external IPv6 address for the GVNIC network interface, use the flag --external-ipv6-address instead.
RDMA_NAME_PREFIX: the name prefix that you used when creating the VPC network and subnet for the IRDMA network interface.

If you are not using Cloud RDMA with your H4D instances, omit the --network-interface field for the IRDMA interface.
RUN_DURATION: the duration, in seconds, you want the requested instances to run. The value must be between 600, which is 600 seconds (10 minutes), and 604800, which is 604,800 seconds (seven days).

Reservation-bound

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

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
  "name":"INSTANCE_TEMPLATE_NAME",
  "properties":{
    "disks":[
      {
        "boot":true,
        "initializeParams":{
          "diskSizeGb":"DISK_SIZE",
          "diskType":"hyperdisk-balanced",
          "sourceImage":"projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
        },
        "mode":"READ_WRITE",
        "type":"PERSISTENT"
      }
    ],
    "machineType":"MACHINE_TYPE",
    
        "networkInterfaces": [
        {
          "network": "GVNIC_NAME_PREFIX-net-0",
          "subnetwork": "GVNIC_NAME_PREFIX-sub-0",
          "accessConfigs": [
            {
                "type": "ONE_TO_ONE_NAT",
                "name": "External IP",
                "natIP": "EXTERNAL_IPV4_ADDRESS"
            }
          ],
          "stackType": "IPV4_ONLY",
          "nicType": "GVNIC",
      },
      {
          "network": "GVNIC_NAME_PREFIX-net-1",
          "subnetwork": "GVNIC_NAME_PREFIX-sub-1",
          "stackType": "IPV4_ONLY",
          "nicType": "GVNIC",
      },
      {
          "network": "RDMA_NAME_PREFIX-irdma",
          "subnetwork": "RDMA_NAME_PREFIX-irdma-sub",
          "stackType": "IPV4_ONLY",
          "nicType": "IRDMA",
      }
    ],
,
    "reservationAffinity":{
        "consumeReservationType":"SPECIFIC_RESERVATION",
        "key":"compute.googleapis.com/reservation-name",
        "values":[
          "RESERVATION"
        ]
      },
    "scheduling":{
        "provisioningModel":"RESERVATION_BOUND",
        "instanceTerminationAction":"DELETE",
        "onHostMaintenance": "TERMINATE",
        "automaticRestart":true
      }
  }
}

Replace the following:

INSTANCE_TEMPLATE_NAME: the name of the instance template.
MACHINE_TYPE: the machine type to use for the instance. Specify a H4D machine type. For more information, see H4D machine types.
IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Supported operating systems.
IMAGE_PROJECT: the project ID of the 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 Regions and zones.
DISK_SIZE: the size of the boot disk in GiB.
GVNIC_NAME_PREFIX: the name prefix that you used when creating the standard VPC networks and subnets for the gVNIC interfaces.

If you are using the default network, include only a single --network-interface field with the nic-type field set to GVNIC. Also, omit the network and subnetwork settings for this network interface.
EXTERNAL_IPV4_ADDRESS: Optional: a static external IPv4 address to use with the gVNIC network interface. You must have previously reserved an external IPv4 address.
To specify an external IPv6 address for the GVNIC network interface, use the flag --external-ipv6-address instead.
RDMA_NAME_PREFIX: the name prefix that you used when creating the VPC network and subnet for the IRDMA network interface.

If you are not using Cloud RDMA with your H4D instances, omit the --network-interface field for the IRDMA interface.
RESERVATION: the name of the reservation that you want to use.
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, create the MIG by applying a workload policy that specifies a block collocation (maxTopologyDistance=BLOCK) . 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.

Spot

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

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
  "name":"INSTANCE_TEMPLATE_NAME",
  "properties":{
    "disks":[
      {
        "boot":true,
        "initializeParams":{
          "diskSizeGb":"DISK_SIZE",
          "diskType":"hyperdisk-balanced",
          "sourceImage":"projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
        },
        "mode":"READ_WRITE",
        "type":"PERSISTENT"
      }
    ],
    "machineType":"MACHINE_TYPE",
    
        "networkInterfaces": [
        {
          "network": "GVNIC_NAME_PREFIX-net-0",
          "subnetwork": "GVNIC_NAME_PREFIX-sub-0",
          "accessConfigs": [
            {
                "type": "ONE_TO_ONE_NAT",
                "name": "External IP",
                "natIP": "EXTERNAL_IPV4_ADDRESS"
            }
          ],
          "stackType": "IPV4_ONLY",
          "nicType": "GVNIC",
      },
      {
          "network": "GVNIC_NAME_PREFIX-net-1",
          "subnetwork": "GVNIC_NAME_PREFIX-sub-1",
          "stackType": "IPV4_ONLY",
          "nicType": "GVNIC",
      },
      {
          "network": "RDMA_NAME_PREFIX-irdma",
          "subnetwork": "RDMA_NAME_PREFIX-irdma-sub",
          "stackType": "IPV4_ONLY",
          "nicType": "IRDMA",
      }
    ],
,
    "scheduling":
    {
      "provisioningModel": "SPOT",
      "instanceTerminationAction": "TERMINATION_ACTION"
    }
  }
}

Replace the following:

INSTANCE_TEMPLATE_NAME: the name of the instance template.
MACHINE_TYPE: the machine type to use for the instance. Specify a H4D machine type. For more information, see H4D machine types.
IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Supported operating systems.
IMAGE_PROJECT: the project ID of the 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 Regions and zones.
DISK_SIZE: the size of the boot disk in GiB.
GVNIC_NAME_PREFIX: the name prefix that you used when creating the standard VPC networks and subnets for the gVNIC interfaces.

If you are using the default network, include only a single --network-interface field with the nic-type field set to GVNIC. Also, omit the network and subnetwork settings for this network interface.
EXTERNAL_IPV4_ADDRESS: Optional: a static external IPv4 address to use with the gVNIC network interface. You must have previously reserved an external IPv4 address.
To specify an external IPv6 address for the GVNIC network interface, use the flag --external-ipv6-address instead.
RDMA_NAME_PREFIX: the name prefix that you used when creating the VPC network and subnet for the IRDMA network interface.

If you are not using Cloud RDMA with your H4D instances, omit the --network-interface field for the IRDMA interface.
TERMINATION_ACTION: whether Compute Engine stops (STOP) or deletes (DELETE) the Spot VMs on preemption.

Important: Make sure your application can handle preemption. For example, we recommend that you handle preemption by specifying a shutdown script during instance creation. Learn how to handle preemption with a shutdown script.

After you create the instance template, you can view the template 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 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 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. The MIG starts creating VMs based on current resource availability. If any resource is temporarily unavailable, 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.

The commands to create a MIG use a workload policy to specify VM placement. If you don't want to use a workload policy, then remove the --workload-policy flag.

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 \
  --workload-policy=WORKLOAD_POLICY_URL \
  --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 \
    --workload-policy=WORKLOAD_POLICY_URL \
    --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 VMs 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 VMs that you want in the MIG.
WORKLOAD_POLICY_URL: Optional: the URL of the workload policy. For example, projects/example-project/regions/us-central1/resourcePolicies/example-workload-policy. If you don't want to use a workload policy, then you can remove the --workload-policy flag.
ZONE: the zone in which you want to create the MIG. If you use a workload policy, then specify a zone within the policy's region.
REGION: the region in which you want to create the MIG. If you use a workload policy, then specify the same region as that of the policy. 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.

The requests to create a MIG use a workload policy to specify VM placement. If you don't want to use a workload policy, then remove the resourcePolicies.workloadPolicy field.

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",
  "instanceTemplate": "INSTANCE_TEMPLATE_URL",
  "targetSize": "TARGET_SIZE",
  "resourcePolicies": {
    "workloadPolicy": WORKLOAD_POLICY_URL
  }
}

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
  {
    "versions": [
      {
        "instanceTemplate": "INSTANCE_TEMPLATE_URL"
      }
    ],
    "name": "MIG_NAME",
    "instanceTemplate": "INSTANCE_TEMPLATE_URL",
    "targetSize": "TARGET_SIZE",
    "resourcePolicies": {
      "workloadPolicy": WORKLOAD_POLICY_URL
    }
  }

Replace the following:

PROJECT_ID: the project ID.
ZONE: the zone in which you want to create the MIG. If you use a workload policy, then specify a zone within the policy's region.
REGION: the region in which you want to create the MIG. If you use a workload policy, then specify the same region as that of the policy.
INSTANCE_TEMPLATE_URL: the URL of the instance template that you want to use to create VMs 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 VMs that you want in the MIG.
WORKLOAD_POLICY_URL: Optional: the URL of the workload policy. For example, projects/example-project/regions/us-central1/resourcePolicies/example-workload-policy. If you don't want to use a workload policy, then you can remove the resourcePolicies.workloadPolicy field.

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.

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 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

Create a resize request in the zonal MIG using the instance-groups managed resize-requests create command as follows:

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 \
    --zones=ZONE \
    --target-distribution-shape=any-single-zone \
    --instance-redistribution-type=none

Create a resize request in the regional MIG using the beta instance-groups managed resize-requests create command as follows:

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

Reservation-bound

The commands to create a MIG use a workload policy to specify VM placement. If you don't want to use a workload policy, then remove the --workload-policy flag.

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 using the instance-groups managed create command as follows.

gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --workload-policy=WORKLOAD_POLICY_URL \
    --zone=ZONE

Create a resize request in the zonal MIG using the instance-groups managed resize-requests create command as follows:

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 \
    --workload-policy=WORKLOAD_POLICY_URL \
    --zones=ZONE \
    --target-distribution-shape=any-single-zone \
    --instance-redistribution-type=none

Create a resize request in the regional MIG using the beta instance-groups managed resize-requests create command as follows:

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

Spot

The commands to create a MIG use a workload policy to specify VM placement. If you don't want to use a workload policy, then remove the --workload-policy flag.

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 using the instance-groups managed create command as follows.

gcloud compute instance-groups managed create MIG_NAME \
    --template=INSTANCE_TEMPLATE_URL \
    --size=0 \
    --workload-policy=WORKLOAD_POLICY_URL \
    --zone=ZONE

Create a resize request in the zonal MIG using the instance-groups managed resize-requests create command as follows:

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 \
    --workload-policy=WORKLOAD_POLICY_URL \
    --zones=ZONE \
    --target-distribution-shape=any-single-zone \
    --instance-redistribution-type=none

Create a resize request in the regional MIG using the beta instance-groups managed resize-requests create command as follows:

gcloud beta 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 VMs 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
WORKLOAD_POLICY_URL: Optional: the URL of the workload policy. For example, projects/example-project/regions/us-central1/resourcePolicies/example-workload-policy. If you don't want to use a workload policy, then you can remove the --workload-policy flag.
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 VMs to add to the MIG all at once.
REGION: the region in which the MIG is located.

If your workload requires specific VM names, then you can specify a list of names of VMs to create by using the beta instance-groups managed resize-requests create command. In the command, replace the --resize-request flag with the --instances flag.

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.

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:

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 beta.regionInstanceGroupManagerResizeRequests.insert method as follows:

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}

Reservation-bound

The requests to create a MIG use a workload policy to specify VM placement. If you don't want to use a workload policy, then remove the resourcePolicies.workloadPolicy field.

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,
  "resourcePolicies": {
    "workloadPolicy": WORKLOAD_POLICY_URL
  }
}

Create a resize request in the zonal MIG by making a POST request to the instanceGroupManagerResizeRequests.insert method as follows:

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"
  },
  "resourcePolicies": {
    "workloadPolicy": WORKLOAD_POLICY_URL
  }
}

Create a resize request in the regional MIG by making a POST request to the beta.regionInstanceGroupManagerResizeRequests.insert method as follows:

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/instanceGroupManagers/MIG_NAME/resizeRequests
{
  "name": "RESIZE_REQUEST_NAME",
  "resizeBy": COUNT
}

Spot

The requests to create a MIG use a workload policy to specify VM placement. If you don't want to use a workload policy, then remove the resourcePolicies.workloadPolicy field.

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,
  "resourcePolicies": {
    "workloadPolicy": WORKLOAD_POLICY_URL
  }
}

Create a resize request in the zonal MIG by making a POST request to the instanceGroupManagerResizeRequests.insert method as follows:

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"
  },
  "resourcePolicies": {
    "workloadPolicy": WORKLOAD_POLICY_URL
  }
}

Create a resize request in the regional MIG by making a POST request to the beta.regionInstanceGroupManagerResizeRequests.insert method as follows:

POST https://compute.googleapis.com/compute/beta/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. 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.
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 VMs 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.
WORKLOAD_POLICY_URL: Optional: the URL of the workload policy. For example, projects/example-project/regions/us-central1/resourcePolicies/example-workload-policy. If you don't want to use a workload policy, then you can remove the resourcePolicies.workloadPolicy field.
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 VMs to add to the MIG all at once

If your workload requires specific VM names, then you can specify a list of names of VMs to create. To do so, send a POST request to the beta.regionInstanceGroupManagerResizeRequests.insert method for a regional MIG, or the beta.instanceGroupManagerResizeRequests.insert method for a zonal MIG. In the request body, replace the resizeBy field with the instanceNames field.

Create a HPC MIG with H4D machine series

Before you begin

Console

gcloud

REST

Overview

Limitations

Optional: Create VPC networks

Instruction guides

Script

Optional: Create a workload policy

gcloud

REST

Create an instance template

gcloud

Flex-start

Reservation-bound

Spot

REST

Flex-start

Reservation-bound

Spot

Create a MIG

Create a MIG with target size

gcloud

REST

Create a MIG and a resize request

gcloud

Flex-start

Reservation-bound

Spot

REST

Flex-start

Reservation-bound

Spot

What's next?