VNX manage volume does not support id-type of 'source-id' and 'source-name'

[Peter Wang]

VNX Cinder driver added support of cinder volume manage/unmanage previously.

VNX currently only supports 'id' as the id-type, while with release of new version python-cinderclient, 'source-id' and 'source-name' are preferred id-type when using cinder manage.

VNX Cinder driver should support source-id and source-name and obsolete the self-defined 'id'

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/178969

[OpenStack Infra (hudson-openstack)]

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

commit 01467f62413be38bfde7a7efed8b4d3fb01c7af8
Author: peter_wang <email address hidden>
Date: Thu May 28 20:38:56 2015 -0400

    Add 'source-id' and 'source-name' support in VNX driver

    Currently, VNX driver only supports 'id' as the id-type in manage/unmanage volume.
    With release of new version python-cinderclient, 'source-id' and 'source-name' are
    preferred id-type when using cinder manage.

    This fix is to add 'source-id' and 'source-name' support
    and obsolete the self-defined 'id' support.

    Change-Id: Ia0619123ff56e44da98c4f12c554474c8fe6093c
    closes-bug: 1450280