Removing initiator nodes

Virtual Storage Platform One SDS Cloud GCP Data Migration
Version
1.19.x
Audience
anonymous
Part Number
MK-24VSP1SDS033-03
ft:lastEdition
2026-04-07

  • Required role: Service and Storage

Note on the procedure

  • Run Terraform in an environment that can support the execution.

  1. Remove the initiator node.

    Run either of the following commands with the ID of the initiator node to be removed specified.

    REST API: DELETE/v1/objects/storage-nodes/<id>

    CLI: storage_node_delete

  2. Verify the state of the job.

    Run either of the following commands with the job ID specified.

    REST API: GET /v1/objects/jobs/<jobId>

    CLI: job_show

    If the job state is "Succeeded", the initiator node removal is complete.

    If the job state is not "Succeeded", see Troubleshooting.

    Note:

    Until initiator node removal completes, it might not be possible to perform other operations.

  3. Obtain a list of storage nodes, and then verify that the ID of the removed storage node is not included in the list.

    REST API: GET /v1/objects/storage-nodes

    CLI: storage_node_list

  4. Delete the VM instance of the initiator node.
    1. See Exporting configuration files (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration to obtain configuration files from VSP One SDS Block for deleting storage nodes not included in the configuration.

      When exporting configuration files, specify "RemoveInitiatorNode" for the exportFileType parameter by using a REST API.

    2. See Deploying VM configuration files in the Terraform working directory (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration to unzip the configuration file, and then deploy the obtained files.
      CAUTION:

      • Make sure you do not edit the unzipped configuration files unless instructed to do so by the manual. If you edit these files, a problem such as storage cluster blockage might occur.

      • When you specify "RemoveInitiatorNode" for the exportFileType parameter for configuration file export, use the REST API because CLI commands are unavailable.

    3. Verify the impact of deploying configuration files for deleting storage nodes not included in the configuration.

      Run the following command.

      terraform plan

      When you run the command, the message Terraform will perform the following actions appears, followed by the contents of resource changes.

      Verify that the following resource changes are performed.

      Resource

      Resource manipulation

      Resource name

      Confirmation details

      google_compute_instance.initiator_instance[ ]

      delete

      <clusterName>-initiatornode

      One resource is deleted.

      google_compute_instance.instance[ ]

      update in-place

      <clusterName>-snXX

      If a change is made in the following item, there is no problem.

      • metadata
      • deletion_protection
    4. If there is no problem as a result of confirmation by using the terraform plan command, delete the initiator node resource.

      Run the following command.

      terraform apply

      When [Enter a value:] is displayed after running the command, enter [yes].

      If [Apply complete!] is output after running the command, there is no problem.

      Note:

      You do not need to release termination protection because termination protection is not enabled for an initiator node.