Removing an instance from a placement group

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

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

1. View a list of VMs in the placement group:

   yc compute placement-group list-instances --name my-group
   

   Result:

   +----------------------+---------------------+-------------------+---------+-------------+-------------+
   |          ID          |        NAME         |      ZONE ID      | STATUS  | EXTERNAL IP | INTERNAL IP |
   +----------------------+---------------------+-------------------+---------+-------------+-------------+
   | epdep2kq6dt5******** | instance-in-group-1 |   ru-central1-a   | RUNNING |             | 10.129.0.5  |
   | epdlv1pp5401******** | instance-in-group-2 |   ru-central1-a   | RUNNING |             | 10.129.0.30 |
   +----------------------+---------------------+-------------------+---------+-------------+-------------+
   

2. Stop the VM instance you want to remove:

   yc compute instance stop instance-in-group-2
   

   Result:

   id: epdlv1pp5401********
   ...
   status: STOPPED
   

3. Remove the VM instance from the placement group. To do this, update the VM instance leaving placement-group-name blank:

   yc compute instance update --name instance-in-group-2 --placement-group-name=""
   

4. Check that the VM instance was removed from the placement group:

   yc compute placement-group list-instances --name my-group
   

   Result:

   +----------------------+---------------------+-------------------+---------+-------------+-------------+
   |          ID          |        NAME         |      ZONE ID      | STATUS  | EXTERNAL IP | INTERNAL IP |
   +----------------------+---------------------+-------------------+---------+-------------+-------------+
   | epdep2kq6dt5******** | instance-in-group-1 |   ru-central1-a   | RUNNING |             | 10.129.0.5  |
   +----------------------+---------------------+-------------------+---------+-------------+-------------+
   

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the documentation on the Terraform website or mirror website.

If you don't have Terraform, install it and configure the Yandex Cloud provider.

To remove a VM created with Terraform from a placement group:

1. Open the VM configuration file and delete the placement_group_id parameter.

   Here is a sample configuration file structure:

   ...
   resource "yandex_compute_instance" "vm-1" {
     name        = "my-vm"
     platform_id = "standard-v3"
     placement_policy {
       placement_group_id = "${yandex_compute_placement_group.group1.id}"
     }
   }
   
   resource "yandex_compute_placement_group" "group1" {
     name = "test-pg"
   }
   ...
   

2. In the command line, go to the directory with the Terraform configuration file.

3. Check the configuration using this command:

   terraform validate
   

   If the configuration is correct, you will get this message:

   Success! The configuration is valid.
   

4. Run this command:

   terraform plan
   

   The terminal will display a list of resources with parameters. No changes will be made at this step. If the configuration contains any errors, Terraform will point them out.

5. Apply the configuration changes:

   terraform apply
   

6. Confirm the changes: type yes into the terminal and press Enter.

   You can check the changes in the management console.

Use the update REST API method for the Instance resource or the InstanceService/Update gRPC API call.