Using the IBM Storage Plug-in for VMware vCenter Orchestrator

Use the IBM® Storage Plug-in for VMware vCenter Orchestrator to include IBM Storage discovery and provisioning in your vCenter Orchestrator (vCO) automation workflows.

After the IBM Storage Plug-in is deployed (see GUI – Downloading and installing the plug-in package for vCO), the IBM storage objects become available in the vCO, as detailed in the table below.

Table 1. IBM storage objects and events in vCO
Object Attribute Return type
IBMStorage:Pool name String
poolId String
physicalSize long
logicalSize long
physicalFree long
logicalFree long
array String
domain Integer
getVolumes() List<IBMStorage:Volume>
addVolume(string name, integer size) IBMStorage:Volume
removeVolume(String id) void
IBMStorage:Volume name String
scsiIdentifier String
logicalCapacity long
physicalCapacity long
usedCapacity long
pool String
array String
extend(Integer newSize) void
map(String initiators) List<IBMStorage:MappingError>
unMap(String initiators) List<IBMStorage:MappingError>
IBMStorage: MappingError getHostName() String
getReason() String

The Orchestrator workflows, supported by the IBM storage objects are as follows:

  • Create a volume
  • Map a volume
  • Extend a volume
  • Unmap a volume
  • Delete a volume
Follow these guidelines for vCO workflows:
  • Volume creation: the allowed volume sizes are set in whole numbers. Any number after a decimal point is ignored by the vCO. For example, when the volume size is set to 1.6 GB, the 1 GB volume is created.
  • Volume extension: the allowed volume sizes are set in whole numbers. Any number after a decimal point is ignored by the vCO. For example, when the volume size is extended to 3.6 GB, the volume size is set to 3 GB.
  • Volume mapping is performed by passing initiators to the workflow. If a host definition at the storage array includes two initiators, only one of them is passed by the workflow, when it is run. Also, a volume must be mapped to all hosts using the same LUN.

The following figures display the IBM Storage workflows and elements in vCO.

Figure 1. vCenter Orchestrator – Create New Volume workflow – General tab
This image shows vCenter Orchestrator – Create New Volume workflow – General tab.
Figure 2. vCenter Orchestrator – Create New Volume workflow – Inputs tab
This image shows vCenter Orchestrator – Create New Volume workflow – Inputs tab.
Figure 3. vCenter Orchestrator – Create New Volume workflow – Parameter References tab
This image shows vCenter Orchestrator – Create New Volume workflow – Parameter References tab.
Figure 4. vCenter Orchestrator – Storage Arrays panel
This image shows vCenter Orchestrator – Storage Arrays panel.
The code sample below illustrates a script for finding a pool with the largest amount of logical free space.
var pools = Server.findAllForType("IBMStorage:Pool");
var largestLogicalFreePool = pools.reduce(function (p, v) {
    return ( p.logicalFree > v.logicalFree ? p : v );
});

For information about how to initiate workflows in vCenter Orchestrator, refer to the relevant VMware documentation.