Moving a VM to a different folder

Use the move REST API method for the Instance resource or the InstanceService/Move gRPC API call.

Example

Below is an example of a Bash script for Linux.

To use it, get authenticated with the API and install cURL.

You can move a VM without stopping it.

1. Create a script file:

   sudo touch <file_name>
   

2. Open the file to write the script to:

   sudo nano <file_name>
   

3. Place the script in the file:

   #!/bin/bash
   
   # Creating variables
   
   export IAM_TOKEN=`yc iam create-token`
   
   instanceId='<VM_ID>'
   bootDiskId='<VM_boot_disk_ID>'
   destinationFolderId='<folder_ID>'
   
   # Moving a VM
   
   curl \
     --request POST \
     --header "Authorization: Bearer ${IAM_TOKEN}" \
     --data '{ "destinationFolderId": "'"${destinationFolderId}"'" }' \
     "https://compute.api.cloud.yandex.net/compute/v1/instances/{${instanceId}}:move"
   
   # Moving a boot disk
   
   curl \
     --request POST \
     --header "Authorization: Bearer ${IAM_TOKEN}" \
     --data '{ "destinationFolderId": "'"${destinationFolderId}"'" }' \
     "https://compute.api.cloud.yandex.net/compute/v1/disks/{${bootDiskId}}:move"
   

   Where:

   • IAM_TOKEN: IAM token for API authentication.
   • instanceId: ID of the VM to move.
   • bootDiskId: ID of the boot disk of the VM to move.
   • destinationFolderId: ID of the folder to move the VM to.

4. Make the file executable:

   chmod +x <file_name>
   

5. Run the script:

   ./<file_name>
   

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder through the --folder-name or --folder-id parameter.

1. See the description of the CLI command for updating a subnet:

   yc compute instance update-network-interface --help
   

2. Stop the VM:

   yc compute instance stop fhm0b28lgfp4********
   

3. Get a list of VM network interfaces by specifying the VM ID:

   yc compute instance get fhm0b28lgfp4********
   

   Result:

   ...
   network_interfaces:
     - index: "0"
       mac_address: d0:0d:24:**:**:**
       subnet_id: e2lpp96bvvgp********
       primary_v4_address:
         address: 192.168.2.23
     - index: "1"
       mac_address: d0:1d:24:**:**:**
       subnet_id: e2lrucutusnd********
       primary_v4_address:
         address: 192.168.1.32
     - index: "2"
       mac_address: d0:2d:24:**:**:**
       subnet_id: e2lv9c6aek1d********
       primary_v4_address:
         address: 192.168.4.26
   ...
   

   Save the index field value, i.e., the number of the network interface you want to connect to a different subnet.

4. Run this command:

   yc compute instance update-network-interface fhm0b28lgfp4******** \
     --subnet-id e2lfibapq818******** \
     --ipv4-address auto \
     --network-interface-index 0 \
     --security-group-id enpi8m85mj14********
   

   Where:

   • --subnet-id: Subnet in the destination folder.
   • --ipv4-address: Internal IP address of the VM network interface in the subnet in the destination folder. Set to auto to enable automatic internal address assignment.
   • --network-interface-index: VM network interface number you saved earlier.
   • --security-group-id: ID of the security group to assign to the VM network interface.

   Result:

   done (9s)
   id: fhm0b28lgfp4********
   folder_id: b1gd73mbrli7********
   created_at: "2023-11-16T06:09:46Z"
   name: oslogigor1
   zone_id: ru-central1-a
   platform_id: standard-v3
   resources:
     memory: "2147483648"
     cores: "2"
     core_fraction: "100"
   status: STOPPED
   metadata_options:
     gce_http_endpoint: ENABLED
     aws_v1_http_endpoint: ENABLED
     gce_http_token: ENABLED
     aws_v1_http_token: DISABLED
   boot_disk:
     mode: READ_WRITE
     device_name: epdophaf2gh9********
     auto_delete: true
     disk_id: epdophaf2gh9********
   network_interfaces:
     - index: "0"
       mac_address: d0:0d:24:**:**:**
       subnet_id: e2lfibapq818********
       primary_v4_address:
         address: 10.129.0.22
       security_group_ids:
         - enpi8m85mj14********
     - index: "1"
       mac_address: d0:1d:24:**:**:**
       subnet_id: e2lrucutusnd********
       primary_v4_address:
         address: 192.168.1.32
     - index: "2"
       mac_address: d0:2d:24:**:**:**
       subnet_id: e2lv9c6aek1d********
       primary_v4_address:
         address: 192.168.4.26
   gpu_settings: {}
   fqdn: relocated-vm.ru-central1.internal
   scheduling_policy: {}
   network_settings:
   type: STANDARD
   placement_policy: {}
   

   If a VM has multiple network interfaces, update the subnet for each one.

5. Run the VM:

   yc compute instance start fhm0b28lgfp4********
   

Use the updateNetworkInterface REST API method for the Instance resource or the InstanceService/UpdateNetworkInterface gRPC API call.