IBM Storwize driver: Retype the volume with correct empty QoS
* Currently for Storwzie driver, if the new type does not have QoS
configurations, the old QoS configurations remain in the volume after
retyping it. It should be retyped into a volume with empty QoS for the
Storwize driver.
* Refactor three dicts into one for better maintainance of the QoS keys
for Storwize driver.
DocImpact
Change-Id: I2b2801a4ef72ef02c11392ed00b56f5263a8a7e4
Closes-Bug: #1368595
(cherry picked from commit 26de1b1d829849665dae921b8be739194b84515d)
Reviewed: https:/ /review. openstack. org/126858 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=2601acaec8d 3c154f7638db0e7 dad307d0efcc48
Committed: https:/
Submitter: Jenkins
Branch: proposed/juno
commit 2601acaec8d3c15 4f7638db0e7dad3 07d0efcc48
Author: Vincent Hou <email address hidden>
Date: Fri Sep 12 16:10:02 2014 +0800
IBM Storwize driver: Retype the volume with correct empty QoS
* Currently for Storwzie driver, if the new type does not have QoS
configurations, the old QoS configurations remain in the volume after
retyping it. It should be retyped into a volume with empty QoS for the
Storwize driver.
* Refactor three dicts into one for better maintainance of the QoS keys
for Storwize driver.
DocImpact
Change-Id: I2b2801a4ef72ef 02c11392ed00b56 f5263a8a7e4 65dae921b8be739 194b84515d)
Closes-Bug: #1368595
(cherry picked from commit 26de1b1d8298496