These contents are for storage operations with Configuration Manager (CM) REST API. The REST API is for managing Hitachi storage arrays.
|Setup||Register Storage Array||Register storage array to Configuration Manager REST. This is needed to manage storage by REST API.|
|Unregister Storage Array||Unregister storage array from Configuration Manager REST|
Create new volumes and get list of volumes
Unallocate specified volumes by followgins.
|Delete LUN Path||Delete luns from specified host groups|
|Delete Volumes||Delete specified volumes|
|Delete Host Groups||Delete host groups from specified ports|
|Utilitiy||Find LUN Path||Find LUN path information for specified ldevs|
|Get Host Group Detail Information||Get detail information for specified host groups. This includes information about how many luns are in host group, and hostport wwns under the host groups.|
The download file includes following contents (service templates) for storage operations with Configuration Manager (CM) REST API.
How to use
- Download file and unzip, then import service templates
- Configure Web Service Connections to access CM REST Server. That is, add new entry of connection settings for CM REST Server. The service templates utilizes the information of connection settings (e.g. credential, endpoint) to call CM REST API. (CM REST neeeds to be instlaled in your environment)
- Create services from the service templates. For Configuration Manager REST Settings, specify name of connection settings which you sepcified at the previous step.
- Submit Service Request (Note: Detail of each properties of services, see service detail help and description for \each property)
The editor has also code assistant feature, and you can find which api can be called and what type of parameters you need to specify.
One you get/create primitive component (e.g. delete lun path, delete volume). You can combine them to achieve more complex use cases by using Service Builder. Following is flow of "Unallocate Volumes" service, and this uses multiple service templates inside it. Finding lun path for specified volumes, deleting them, deleting volumes (optional), getting number of luns in host group, deleting host group if there are no luns (optional).
Of course, you can implement all logic in single script in the plugin.