Added extra-spec key scoping to the 3PAR drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Kurt Martin |
Bug Description
https:/
commit 78cb294b457d3ce
Author: Kurt Martin <email address hidden>
Date: Sun Dec 23 16:47:58 2012 -0800
Added extra-spec key scoping to the 3PAR drivers
The Filter scheduler uses the extra-specs data to determine capabilities
and back-end, and it also enforces strict checking. As a result previous
method of setting all the 3PAR settings(cpg, snap_cpg, persona, provisioning)
on the 3PAR volume using extra-specs on a volume type will not work with the
default scheduler. The filter scheduler will look at these keys and fail to
schedule deployment of the volume because no suitable back-end reports those
capabilities.
This fix will allow the custom keys (ie: hp3par:
hp3par:
additional checks in the common driver to parse the keys.
I'll update the 3PAR driver section of the OpenStack Block Storage Admin
Guide in a follow-up patch.
DocImpact
Fixes: bug 1194289
Change-Id: Id3fde3b3a185ee
Changed in openstack-manuals: | |
milestone: | none → havana |
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
description: | updated |
tags: | added: cinder |
Changed in openstack-manuals: | |
assignee: | nobody → Kurt Martin (kurt-f-martin) |
status: | Confirmed → Fix Committed |
Changed in openstack-manuals: | |
status: | Fix Committed → Fix Released |
This was fixed in the following review for the Havana release with this review: https:/ /review. openstack. org/#/c/ 34465/
The doc changes should *not* be backported to the Grizzly release.