Andrew Robles

What’s NEW with Hitachi Integration with VMware vRealize Orchestrator/VMware vRealize Automation since v1.0

Blog Post created by Andrew Robles Employee on Nov 13, 2015

This blog highlights some of the new features that are included for version 1.2 of our Adapter, for vRealize Orchestrator(vRO).For more information and an introduction on how to configure vRO, please visit:


Discovering Hitachi Storage Connector for VMware vRealize Orchestrator  and Configuring vRO.


What’s new?


Version 1.1 included several new features such as support for VSP GX00, HUS iSCSI support, and vRealize Automation 6.2 integration. During the 1.1 release, we’ve also released a compute connector. Notably, one of our Compute workflow's has the capability to get server HBA ports. This allows you to automate operation process and quickly retrieve the WWPN/WWNN without logging in the OS/Hypervisor on the server. This is an ideal method if the customers has hundreds of servers. This can also seamlessly integrated with our storage connector (vRO). Currently both our Storage and Compute currently has over 200 workflows:




For our latest Storage release, there are few new features I’d like to highlight:


Storage Profiles

In 1.2, user will be given choice to store storage configuration details including dynamic pool and parity group information using storage profile workflows. This profile will help to register storage array without in need of entering storage details again and again to run the workflows. Just choose the profile workflows and register the array.


Before creating a profile, the admin has to enter in specific information about the storage array. Once completed, you can use this profile in the future.
Sp captuer2.JPGSP capture1.JPG



Smart Provisioning ESXi Datastore


This workflow is created for end users to provision a datastore in a multi-store environment. Before doing so, the user must have their arrays registered as well as having vCenter registered with vRO. This Smart workflow will identify thestorage (which is connected to an ESXi server) and identify the least capacity available and next create a LUN with a specified size. The workflow will then identify the host group and present that LUN to the host group. Lastly, that LUN is created and a datastore is provisioned to 1 ESXi server.

In this release we eliminated the details that the user was required to manually enter in a whole list of attriubutes (subsystem, serial number, user ID, password, horcminst, port, and host group).


In v1.2 this is the first thing the user will see. The number of fields is reduced down to 3:

workflow input.jpg



Here is an example of a Smart Provisioning workflow schema:

Smart Provisioning a LUN to ESXi host-cluster.jpg


Steps involved for this operation:


  1. Get register storage arrays
  2. Gets selected ESXi or cluster host WWNs
  3. Get associated host for WWNs
  4. Finds host group on registered storage array
  5. Identifies least capacity available storage across all storage systems
  6. Then creates LU in dynamic pool
  7. Present LU to the ESXi host or cluster
  8. Once presented, datastore is created on ESXi Host or cluster


The datastore then can be used for VM provisioning.


Self Service VM Recovery

The third major addition is HDS vRO's Self Service VM Recovery workflow (note: Hitachi Virtual Infrastructure Integrator (V2I) data protection software required).


In this scenario the VM environment is being protected by Hitachi V2I which is creating storage based VM backups at a predefined schedule for every VM in the environment. This provides space efficient backups of these VMs plus allowing for quick and granular recover options. Assume an application administrator that is being served by one of these VMs encounters a corruption or accidental deletion of data that requires a level of VM data recoverability. Rather than go through the usual helpdesk service desk, they can simply go to their vRealize Automation portal  were this Self Service VM recovery workflow would be made available via import of HDS Connector workflows. The app admin selects which snapshot point in time they would like to retrieve data from and the workflow will initiate an operation to mount that point in time disks directly into their server. They can now simply drag and drop data from their X and Y drive to their C and D drive to get back their important data.


This workflow can also be used with vRealize Automation (vRA) to create a service catalog item that an end user can access to submit a recovery request. See example below. This reduces administration cost because the user can now request/perform this task directly without constantly contacting IT. This new Self Service recovery workflow is exposed to vRA. This will present a catalog to the end-user can go in and select which service they want to use. 




Base workflow for self-recovery:

Self service VM Recovery.jpg


Hitachi Storage Connector for VMware vRealize Orchestrator supports both HDS block and unified platforms. This is a no charge adapter and can be downloaded from or VMware Solution Exchange.


If you need more information, reach out to me or pop a request at , fill in “vRealize Orchestrator” within the subject lines.

To learn more about other management packs for VMware environments, please visit