Releasing multiple connections between the volumes and compute nodes

Virtual Storage Platform One SDS Block Virtual Private Storage Administrator Guide
Version
1.15.x
Audience
anonymous
Part Number
MK-24VSP1SDS003-02

Releases the connections by removing all specified volumes and the path (volume path) of all specified compute nodes. Before you execute the operation, verify that no I/O operation is being performed between the intended compute node and the intended volume.

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.

  • 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: VpsStorage

  1. Verify the IDs of volumes.

    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

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

  3. Cancel allocation of the volumes to the compute nodes.

    Specify the IDs of the volumes and IDs of the compute node (for which you want to cancel allocation), and then 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: POST /v1/objects/volume-server-connections/actions/release/invoke

    CLI: volume_server_connection_release_connections

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

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

    After running the command, if you receive a response indicating "Succeeded" as the state, the job is completed.

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