Use optional key-value pair metadata to track OpenStack volume on the 3PAR storage array

[sivaramakrishna]

Currently, when a volume is created on the 3PAR, metadata is added onto “comment” section onto the 3PAR which can be modified by users directly from management console. Hence for any new driver related tasks, to avoid manipulation from user, the 3PAR driver should use optional key value pairs for adding metadata. Comments section would be mainly used for informational purposes. All metadata keys should start with a custom prefix for ease of use.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit dd9536ac6e6df0e1ae6754e580b99cfbfd05eb77
Author: Sivaramakrishna Garimella <email address hidden>
Date: Mon Dec 9 11:11:13 2013 +0530

    Add additional metadata as key-value pairs in 3PAR

    Track status of openstack volumes on 3PAR through
    additional metadata added as key-value pairs. During volume attach
    and detach, corresponding instance metadata is updated onto the
    cinder volumes.

    Change-Id: Iea8d2f26555e6be60001bf73755cae42446afec6
    Closes-Bug: #1258033