-
Required role: Service and Storage
-
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
Note:You do not need to release resource protection because resource protection is not set for an initiator node.
-
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.
-
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
-
Delete the Azure Virtual Machines of the initiator node.
In the Azure portal, access the resource group page of VSP One SDS Block to select and delete resources of the VM, NIC, and disk of the removed initiator node.
Note:The resources of the initiator node VM, NIC, and disk created by VSP One SDS Block are each assigned a resource name in the format of "<clusterName>-InitiatorNode-<suffix>." Accordingly, you can identify each resource.
<clusterName> indicates the storage cluster name, and <suffix> indicates the resource type or resource number. Resources existing in configuration information of VSP One SDS Block are protected (to avoid inadvertent deletion).