Delete the initiator information of a compute node. Deleting information about an initiator also deletes the path information of all the related compute nodes.
-
Required role: VpsStorage
-
Verify the ID of the applicable 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
-
Verify the ID of the intended initiator.
If you use the CLI to specify an initiator by WWN, iSCSI name, or host NQN, verify the WWN, iSCSI name, or host NQN of the initiator.
Specify the ID of the applicable compute node and run either of the following commands.
If you use the CLI, you can specify a nickname instead of the compute node ID.
REST API: GET /v1/objects/servers/<id>/hbas
CLI: hba_list
-
Delete information about the intended initiator.
Specify the ID of the applicable compute node and ID of the intended initiator, and run either of the following commands.
If you use the CLI, you can specify nicknames instead of compute node IDs, and specify WWNs, iSCSI names, or host NQNs instead of initiator IDs.
REST API: DELETE /v1/objects/servers/<id>/hbas/<hbaId>
CLI: hba_delete
Verify the job ID which is displayed after the command is run.
-
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.
-
Obtain a list of information about initiators and verify that the information about the intended initiator is deleted.
Run either of the following commands with the compute node ID specified.
If you use the CLI, you can specify a nickname instead of the compute node ID.
REST API: GET /v1/objects/servers/<id>/hbas
CLI: hba_list