VMware: Cannot identify volume backings in vCenter

[Vipin Balachandran]

Currently there is no easy way to identify Cinder volumes in vCenter.

HP reported this:

"HP Data Protector (backup and recovery enterprise) product has VADP (APIs provided by VMware) integration for backing up and restoring VMs in VMware. In that context, the shadow VM (cinder volumes) creation in vCenter due to OpenStack integration has become an issue for us to manage. Because of the Shadow VMs, VADP backups fail since the disk appears twice in the infrastructure. One belonging to instance VM as a folder path to the shadow VM, and the other as a disk to the shadow VM. We need to track these Shadow VMs by a interfaced mechanism, so that backups/restores work as expected."

[Vipin Balachandran (vbala)]

The fix:
https://review.openstack.org/#/c/194534/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/194534
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=cb98bb48f1af590ecdc0f5e064fdad31ef61eec8
Submitter: Jenkins
Branch: master

commit cb98bb48f1af590ecdc0f5e064fdad31ef61eec8
Author: Vipin Balachandran <email address hidden>
Date: Mon Jun 22 19:56:09 2015 +0530

    VMware: Add volume ID in vCenter's volume config

    HP data protector's backup of vCenter inventory is failing
    for 'in-use' Cinder volumes because the vmdk is attached
    to two VMs (Nova instance and the backing VM corresponding
    to Cinder volume). The solution is to skip the backing VM
    during data protector's backup.

    This patch adds key 'cinder.volume.id' with value set to
    volume UUID in volume's vCenter config file so that other
    vCenter solutions can uniquely identify Cinder volumes.

    Closes-Bug: #1484012
    Change-Id: I08a5f1a39def14f164ab3ca08a480310ce0b79ca

[Sunitha K (sunitha-kannan)]

Can this fix be back ported to Juno release of OpenStack?