Allowing user to transform volumes between Thin and Thick/Generic provisioning and migrate a volume to a different pool using Volume Mirror

[mainline-automation]

SUMMARY

Updated to allow changing of a volume between Thin and Thick/Generic provisioning. This also allows a user to migrate a volume between pools in an IO Group using Volume Mirroring.

Additionally, when a user attempts to resize a hyperswap volume in the manage mirror module, the error message used the word "shrinked", which isn't proper english. I edited the message for clarity and flow.

Fixes #32

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

ibm_svc_manage_mirrored_volume.py

ADDITIONAL INFORMATION

The GUI and the CLI of Storage Virtualize allow a user to convert a volume between Thick and Thin provisioning. On the back end, of the GUI this uses Volume Mirroring. If you use the capability in the GUI, you never see anything happen. In the CLI this is done by setting the -autodelete flag in the command.
This capability does not exist in the current version of the ibm_svc_manage_mirrored_volume.py module, however. The module requires that the volumes be in different pools and does not allow for -autodelete. As a result, the mirrored volume module only really works if your intent is to maintain the mirrored volumes for some sort of availability purpose (hyperswap or standard).
My change introduces a new "state" parameter option. "transform".
An unmirrored volume with "transform" set as the desired state can create a new vdisk copy within the same pool. The new vdisk can be set to be thin/thick as needed. It will also allow migration of the volume to a different pool, including a DRP, or back from a DRP (if performance isn't working out, for example). When the synchronization is complete, the original copy of the volume will be deleted automatically, leaving only the new form of the volume in whichever pool was required.

original bugfix/grammar fix:
before: "Size of a HyperSwap Volume cannot be shrinked"
after: "A HyperSwap Volume cannot be reduced in size"

Transform:
before: "Volume [test] already exists, no modifications done"
     It also would not have set autodelete if you created a vdisk in a different pool and would have left a volume mirror in place.
after: localhost Volume [test] is being transformed. The original copy will be deleted after synchronization