To move sole-tenant VMs to a different node or node group, you can manuallyinitiate a live migration. You can also manually initiate a live migration tomove a multi-tenant VM into sole-tenancy. For information about how to move a VMout of sole-tenancy, seeMove a VM out of sole-tenancy.

Before you begin

• If you haven't already, set upauthentication. 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:

  gcloud

  1. Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:

     gcloudinit

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

  Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:

  gcloudinit

  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 runninggcloud components update.

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

API rate limits

Manual live migration requests are categorized in theQueriesAPI ratelimit.

Manually live migrate VMs into or within sole-tenancy

To manually live migrate VMs into or within sole-tenancy, use thegcloud CLI or REST.

If the destination of the VM is a node group, Compute Engine selectsthe node within the group that has both enough space for the VM and the leastamount of spare capacity.

You cannot perform live migration between projects while using sharedsole-tenant node groups.

Permissions required for this task

To perform this task, you must have the followingpermissions:

• compute.instances.update permissions on the VM.

gcloud compute instances updateVM_NAME \    ( --node=NODE \      --node-group=NODE_GROUP \      --node-affinity-file=NODE_AFFINITY_FILE )

PUT https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances/VM_NAME{  ...  "scheduling": {    "nodeAffinities": [      {        "key": "NODE_AFFINITY_LABEL_KEY",        "operator": "IN",        "values": [          "[NODE_AFFINITY_LABEL_VALUE]"        ]      }    ]  }  ...}

What's next

• Learn how to move a VM out of sole-tenancy