Canceling allocation of volumes to compute nodes

Virtual Storage Platform One SDS Block Storage Administrator Guide

Version
1.17.x
Audience
anonymous
Part Number
MK-24VSP1SDS002-04

Disconnects by removing the path (volume path) between the volume and the compute node. Before you run the command, verify that no I/O operation is being performed between the intended compute node and the intended volume.

When you are using Universal Replicator, note the following:

  • Volume paths between a volume whose universalReplicatorAttribute is "P-VOL" or "S-VOL" and a compute node can be removed by deleting the Universal Replicator pair.
CAUTION:
  • When compute nodes are clustered and the volumes recognized by the compute nodes are online, set the intended volume offline and then cancel allocation of the volume.

  • For FC* or iSCSI connection, before you delete path information from a compute node, verify whether the volumes that can be accessed from the compute node are in SCSI-2 Reserve status or SCSI-3 Persistent Reserve status. If the volumes are in either status, release them from the status, and then delete path information.

    * Only the bare metal model is supported.

  • When you change the path information of a compute node, perform a rescan of the storage on that compute node. If the path information already deleted remains on the compute node, it might cause malfunction.

  • Required role: Storage

  • When removing volume paths belonging to a VPS: Scope of the VPS

  1. When removing volume paths that belong to a VPS, verify the VPS ID.

    If you want to specify a VPS by its name in the CLI, verify the VPS name.

    REST API: GET /v1/objects/virtual-private-storages

    CLI: vps_list

  2. Verify the ID of the intended volume.

    If you use the CLI to specify a volume by name, check the name of the volume.

    REST API: GET /v1/objects/volumes

    CLI: volume_list

  3. Verify the ID of the intended compute node.

    If you use the CLI to specify a compute node by nickname, check the nickname of the compute node.

    REST API: GET /v1/objects/servers

    CLI: server_list

  4. Obtain a list of information about allocation of volumes to compute nodes.

    Run one of the following commands with the volume ID and compute node ID specified in the query parameter.

    If you use the CLI, you can specify a name instead of the ID of the volume, but a nickname instead of the ID of the compute node.

    REST API: GET /v1/objects/volume-server-connections

    CLI: volume_server_connection_list

  5. Cancel allocation of the volume to the compute node.

    Specify the ID of the intended volume and ID of the intended compute node, and run either of the following commands.

    If you use the CLI, you can specify a name instead of the ID of the volume, but a nickname instead of the ID of the compute node.

    REST API: DELETE /v1/objects/volume-server-connections/<volumeId>,<serverId>

    CLI: volume_server_connection_delete

    Verify the job ID which is displayed after the command is run.

  6. 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 job is completed.

  7. Obtain a list of information about allocation of volumes to compute nodes and verify that the intended allocation is canceled.

    REST API: GET /v1/objects/volume-server-connections

    CLI: volume_server_connection_list

  8. (Bare metal) Back up the configuration information.

    Perform this step by referring to Backing up the configuration information (Bare metal).

    If you continue operations with other procedures, you must back up the configuration information after you have completed all operations.