Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/ai-hypercomputer/docs/create/create-vm below:

Create an AI-optimized instance with A4 or A3 Ultra | AI Hypercomputer

Stay organized with collections Save and categorize content based on your preferences.

This document describes the steps to create standalone virtual machine (VM) instances that use A4 or A3 Ultra accelerator-optimized machine types. To learn more about the machine types, see A4 machine type and A3 Ultra machine type in the Compute Engine documentation.

To learn about other ways to create VMs or clusters, see the Overview page.

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

1. Choose a consumption option: the option that you pick determines how you want to get and use GPU resources.

To learn more, see Choose a consumption option.

2. Obtain capacity: to learn how to obtain capacity for your consumption option.

To learn more, see Capacity overview.

Select the tab for how you plan to use the samples on this page:

When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.

In the Google Cloud console, activate Cloud Shell.

Activate Cloud Shell

At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.

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.

For more information, see Authenticate for using REST in the Google Cloud authentication documentation.

To get the permissions that you need to create VMs, 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 VMs. To see the exact permissions that are required, expand the Required permissions section:

The following permissions are required to create VMs:

• compute.instances.create on the project
• To use a custom image to create the VM: compute.images.useReadOnly on the image
• To use a snapshot to create the VM: compute.snapshots.useReadOnly on the snapshot
• To use an instance template to create the VM: compute.instanceTemplates.useReadOnly on the instance template
• To assign a legacy network to the VM: compute.networks.use on the project
• To specify a static IP address for the VM: compute.addresses.use on the project
• To assign an external IP address to the VM when using a legacy network: compute.networks.useExternalIp on the project
• To specify a subnet for your VM: compute.subnetworks.use on the project or on the chosen subnet
• To assign an external IP address to the VM when using a VPC network: compute.subnetworks.useExternalIp on the project or on the chosen subnet
• To set VM instance metadata for the VM: compute.instances.setMetadata on the project
• To set tags for the VM: compute.instances.setTags on the VM
• To set labels for the VM: compute.instances.setLabels on the VM
• To set a service account for the VM to use: compute.instances.setServiceAccount on the VM
• To create a new disk for the VM: compute.disks.create on the project
• To attach an existing disk in read-only or read-write mode: compute.disks.use on the disk
• To attach an existing disk in read-only mode: compute.disks.useReadOnly on the disk

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

Creating an instance with A4 or A3 Ultra machine type includes the following steps:

1. Create VPC networks
2. Optional: Create a compact placement policy
3. Create an instance

For A4 or A3 Ultra machine type, you must create three VPC networks for the following network interfaces:

• 2 VPC networks for the gVNIC network interfaces (NIC). These are used for host to host communication.
• 1 VPC network with the RDMA network profile is required for the CX7 NICs. This network needs to have 8 subnets, one subnet for each CX7 NIC, and is used for GPU to GPU communication.

For more information about NIC arrangement, see Review network bandwidth and NIC arrangement.

Set up the networks either manually by following the instruction guides or automatically by using the provided script.

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

• To create the VPC networks for the gVNICs, see Create and manage Virtual Private Cloud networks.
• To create the VPC network with the RDMA network profile, see Create a Virtual Private Cloud network for RDMA NICs.

For these VPC networks, we recommend setting the maximum transmission unit (MTU) to a larger value. For A4 or A3 Ultra machine type, the recommended MTU is 8896 bytes. To review the recommended MTU settings for other GPU machine types, see MTU settings for GPU machine types.

To create the networks, follow these steps:

1. Use this script to create the network.

   For these VPC networks, we recommend setting the maximum transmission unit (MTU) to a larger value. For A4 or A3 Ultra machine type, the recommended MTU is 8896 bytes. To review the recommended MTU settings for other GPU machine types, see MTU settings for GPU machine types.

       #!/bin/bash
   
       # Create standard VPCs (network and subnets) for the gVNICs
       for N in $(seq 0 1); do
         gcloud compute networks create GVNIC_NAME_PREFIX-net-$N \
           --subnet-mode=custom \
           --mtu=8896
   
         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
   
       # Assumes that an external IP is only created for vNIC 0
       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
   
       # List and make sure network profiles exist in the machine type's zone
       gcloud compute network-profiles list --filter "location.name=ZONE"
   
       # Create network for CX-7
       gcloud compute networks create RDMA_NAME_PREFIX-mrdma \
         --network-profile=ZONE-vpc-roce \
         --subnet-mode custom \
         --mtu=8896
   
       # Create subnets
       for N in $(seq 0 7); do
         gcloud compute networks subnets create RDMA_NAME_PREFIX-mrdma-sub-$N \
           --network=RDMA_NAME_PREFIX-mrdma \
           --region=REGION \
           --range=10.$((N+2)).0.0/16 # offset to avoid overlap with gVNICs
       done
       

   Replace the following:

   • GVNIC_NAME_PREFIX: the custom name prefix to use for the standard VPC networks and subnets for the gVNICs.
   • RDMA_NAME_PREFIX: the custom name prefix to use for the VPC network and subnets with the RDMA network profile for the CX7 NICs.
   • ZONE: specify a zone in which the machine type that you want to use is available, such as us-central1-a. For information about regions, see GPU availability by regions and zones.
   • REGION: the region where you want to create the subnets. This region must correspond to the zone specified. For example, if your zone is us-central1-a, then your region is us-central1.
   • IP_RANGE: the IP range to use for the SSH firewall rules.
2. 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.

Tip: If you want your VMs to be placed in a single or adjacent blocks, specify VM placement by creating a placement policy. However if you want your VMs to be on a specific block, skip this step and provide the name of the block in the reservation affinity when you create the instance.

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 you want the VMs to be closer together (maximum compactness), then specify the maxDistance field (Preview) when creating 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:

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. The value must be 3 to place VMs in the adjacent blocks, or 2 to place VMs in the same block. For information about the maximum number of VMs supported for each maxDistance per machine series, see About compact placement policies in the Compute Engine documentation.
• REGION: the region where you want to create the compact placement policy. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU regions and zones.

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. The value must be 3 to place VMs in the adjacent blocks, or 2 to place VMs in the same block. For information about the maximum number of VMs supported for each maxDistance per machine series, see About compact placement policies in the Compute Engine documentation.
• REGION: the region where you want to create the compact placement policy. Specify a region in which the machine type that you want to use is available. For information about regions, see GPU regions and zones.

To create an A4 or A3 Ultra VM, use one of the following methods. If you choose to use a compact placement policy, you must use Google Cloud CLI or REST to create the VM.

1. In the Google Cloud console, go to the Create an instance page.

   Go to Create an instance

2. Specify a Name for your VM. See Resource naming convention.

3. Select the Region and Zone where you want to reserve capacity. See the list of available GPU regions and zones.

4. Click the GPUs tab, and then complete the following steps:

   1. In the GPU type list, select your GPU type.
      • For A4 VMs, select NVIDIA B200 180GB
      • For A3 Ultra VMs, select NVIDIA H200 141GB
   2. In the Number of GPUs list, select 8.

5. In the navigation menu, click OS and storage, and then complete the following steps:

   1. Click Change. The Boot disk configuration pane opens.
   2. On the Public images tab, select a recommended image. For a list of recommended images, see Operating systems.
   3. To confirm your boot disk options, click Select.

6. Configure the service account and access scopes as follows. Workloads running on the instance use the attached service account to authorize requests to other Google Cloud services.

   1. In the navigation menu, click Security.
   2. In the Service account list, select a service account to use.
   3. For Access scopes, select the Allow full access to all Cloud APIs option. This is the recommended best practice, as it lets you manage access by adding or removing IAM roles from the service account. For more information, see Attaching a service account to an instance.

7. To create a multi-NIC VM, complete the following steps. Otherwise, to create a single-NIC VM, skip these steps.

   1. In the navigation menu, click Networking.

   2. In the Network interfaces section, complete the following steps:

      1. Delete the default network interface. To delete the interface, click delete Delete.
      2. Click Add a network interface. Use this option to add the gVNIC and RDMA networks that you created in the previous section. When you add the networks, remember the following:
         • Specify your host networks in the Network and Subnetwork lists, and set the Network interface card list to gVNIC.
         • Specify your GPU networks in the Network and Sub-network lists, and set the Network interface card list to MRDMA for these networks.

8. In the navigation menu, click Advanced. Then, complete the following steps for the provisioning model that you want to use.

   Reservation-bound

   1. Click Choose a reservation. This action opens a pane with a list of available reservations within your selected zone. From the reservation list, complete the following steps:

      1. Select the reservation that you want to use for the VM. You can also select a specific block within the reservation.
      2. Click Choose.
   Spot
   1. In the Provisioning model section, select Spot from the VM provisioning model list.

   2. Optional: To select the termination action that happens when Compute Engine preempts the VM, complete the following steps:

      1. Expand the VM provisioning model advanced settings section.
      2. In the On VM termination list, select one of the following options:
         • To stop the VM during preemption, select Stop (default).
         • To delete the VM during preemption, select Delete.

9. To create and start the VM, click Create.

To create the VM, use the gcloud compute instances 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's provisioning model.

Before running the command, optionally add the flag for a compact placement policy.

gcloud compute instances create VM_NAME  \
    --machine-type=MACHINE_TYPE \
    --image-family=IMAGE_FAMILY \
    --image-project=IMAGE_PROJECT \
    --zone=ZONE \
    --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 \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-1,subnet=GVNIC_NAME_PREFIX-sub-1,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-0,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-1,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-2,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-3,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-4,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-5,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-6,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-7,no-address \
    --reservation-affinity=specific \
    --reservation=RESERVATION \
    --provisioning-model=RESERVATION_BOUND \
    --instance-termination-action=TERMINATION_ACTION \
    --maintenance-policy=TERMINATE

Complete the following steps:

1. Replace the following:

   • VM_NAME: the name of the VM.
   • MACHINE_TYPE: the machine type to use for the VM. Specify either an A4 or A3 Ultra machine type. For more information, see GPU machine types.
   • IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Operating system details.
   • IMAGE_PROJECT: the project ID of the OS image.
   • ZONE: the zone in which the machine type that you want to use is available. If you want to specify a compact placement policy, then you must use a zone in the same region as the compact placement policy. For information about regions, see GPU regions and zones.
   • DISK_SIZE: the size of the boot disk in GB.
   • GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNICs.
   • RDMA_NAME_PREFIX: the name prefix that you specified when creating the VPC networks and subnets that use RDMA 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 the instance on any block:

       projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME

       Additionally, to create multiple instances in the same block, apply the same compact placement policy that specifies a block collocation (maxDistance=2) when creating each instance. Compute Engine then applies the policy to the reservation and creates instances on the same block.

     • To create the instance 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.

   • TERMINATION_ACTION: whether Compute Engine stops (STOP) or deletes (DELETE) the VM at the end of the reservation period.

2. 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.
3. Run the command.

Before running the command, optionally add the flag for a compact placement policy.

gcloud compute instances create VM_NAME  \
    --machine-type=MACHINE_TYPE \
    --image-family=IMAGE_FAMILY \
    --image-project=IMAGE_PROJECT \
    --zone=ZONE \
    --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 \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-1,subnet=GVNIC_NAME_PREFIX-sub-1,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-0,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-1,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-2,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-3,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-4,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-5,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-6,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-7,no-address \
    --provisioning-model=SPOT \
    --instance-termination-action=TERMINATION_ACTION

Complete the following steps:

1. Replace the following:

   • VM_NAME: the name of the VM.
   • MACHINE_TYPE: the machine type to use for the VM. Specify either an A4 or A3 Ultra machine type. For more information, see GPU machine types.
   • IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Operating system details.
   • IMAGE_PROJECT: the project ID of the OS image.
   • ZONE: the zone in which the machine type that you want to use is available. If you want to specify a compact placement policy, then you must use a zone in the same region as the compact placement policy. For information about regions, see GPU regions and zones.
   • DISK_SIZE: the size of the boot disk in GB.
   • GVNIC_NAME_PREFIX: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNICs.
   • RDMA_NAME_PREFIX: the name prefix that you specified when creating the VPC networks and subnets that use RDMA 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, we recommend that you handle preemption by specifying a shutdown script during instance creation. Learn how to handle preemption with a shutdown script.

2. 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.
3. Run the command.

To create the VM, make a POST request to the instances.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's provisioning model.

Before submitting the request, optionally add the field for a compact placement policy to the request body.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances
{
  "machineType":"projects/PROJECT_ID/zones/ZONE/machineTypes/MACHINE_TYPE",
  "name":"VM_NAME",
  "disks":[
    {
      "boot":true,
      "initializeParams":{
        "diskSizeGb":"DISK_SIZE",
        "diskType":"hyperdisk-balanced",
        "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/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-0"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-1"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-2"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-3"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-4"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-5"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-6"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-7"
    }
  ],
  "reservationAffinity":{
    "consumeReservationType":"SPECIFIC_RESERVATION",
    "key":"compute.googleapis.com/reservation-name",
    "values":[
      "RESERVATION"
    ]
  },
"scheduling":{
    "provisioningModel":"RESERVATION_BOUND",
    "instanceTerminationAction":"TERMINATION_ACTION",
    "onHostMaintenance": "TERMINATE",
    "automaticRestart":true
  }
}

Complete the following steps:

1. Replace the following:

   • PROJECT_ID: the project ID of the project where you want to create the VM.
   • ZONE: the zone in which the machine type that you want to use is available. If you want to specify a compact placement policy, then you must use a zone in the same region as the compact placement policy. For information about regions, see GPU regions and zones.
   • MACHINE_TYPE: the machine type to use for the VM. Specify either an A4 or A3 Ultra machine type. For more information, see GPU machine types.
   • VM_NAME: the name of the VM.
   • DISK_SIZE: the size of the boot disk in GB.
   • IMAGE_PROJECT: the project ID of the OS image.
   • IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Operating system details.
   • 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 gVNICs.
   • REGION: the region of the subnetwork.
   • RDMA_NAME_PREFIX: the name prefix that you specified when creating the VPC networks and subnets that use RDMA 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 the instance on any block:

       projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME

       Additionally, to create multiple instances in the same block, apply the same compact placement policy that specifies a block collocation (maxDistance=2) when creating each instance. Compute Engine then applies the policy to the reservation and creates instances on the same block.

     • To create the instance 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.

   • TERMINATION_ACTION: whether Compute Engine stops (STOP) or deletes (DELETE) the VM at the end of the reservation period.

2. Optional: If you chose to use a compact placement policy, then add the following field 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.
3. Submit the request.

Before submitting the request, optionally add the field for a compact placement policy to the request body.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances
{
  "machineType":"projects/PROJECT_ID/zones/ZONE/machineTypes/MACHINE_TYPE",
  "name":"VM_NAME",
  "disks":[
    {
      "boot":true,
      "initializeParams":{
        "diskSizeGb":"DISK_SIZE",
        "diskType":"hyperdisk-balanced",
        "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/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-0"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-1"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-2"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-3"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-4"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-5"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-6"
    },
    {
      "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
      "nicType": "MRDMA",
      "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-7"
    }
  ],
  "scheduling":
  {
    "provisioningModel": "SPOT",
    "instanceTerminationAction": "TERMINATION_ACTION"
  }
}

Complete the following steps:

1. Replace the following:

   • PROJECT_ID: the project ID of the project where you want to create the VM.
   • ZONE: the zone in which the machine type that you want to use is available. If you want to specify a compact placement policy, then you must use a zone in the same region as the compact placement policy. For information about regions, see GPU regions and zones.
   • MACHINE_TYPE: the machine type to use for the VM. Specify either an A4 or A3 Ultra machine type. For more information, see GPU machine types.
   • VM_NAME: the name of the VM.
   • DISK_SIZE: the size of the boot disk in GB.
   • IMAGE_PROJECT: the project ID of the OS image.
   • IMAGE_FAMILY: the image family of the OS image that you want to use. For a list of supported operating systems, see Operating system details.
   • 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 gVNICs.
   • REGION: the region of the subnetwork.
   • RDMA_NAME_PREFIX: the name prefix that you specified when creating the VPC networks and subnets that use RDMA 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, we recommend that you handle preemption by specifying a shutdown script during instance creation. Learn how to handle preemption with a shutdown script.

2. Optional: If you chose to use a compact placement policy, then add the following field 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.
3. Submit the request.

• Verify reservation consumption
• View VMs topology
• Run workloads overview
• Troubleshoot reservation consumption

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-15 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-15 UTC."],[[["This guide provides instructions for creating individual A3 Ultra VMs on Hypercompute Cluster, which are subject to the Pre-GA Offerings Terms and may have limited support."],["Before creating VMs, you must have reserved capacity on Hypercompute Cluster, and you'll need to use the provided gcloud, console, or REST instructions."],["Creating A3 Ultra VMs requires specific permissions, such as the Compute Instance Admin (v1) role, or the proper permissions within custom or other predefined roles."],["A3 Ultra VMs use ten network interfaces and require the creation of three Virtual Private Cloud networks: two gVNIC networks and one RDMA network with eight subnetworks, all of which can be set up manually or with the provided script."],["When creating the VM using the gcloud or console, you need to specify the machine type, OS image, reservation, zone, and network interfaces, among other configurations."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4