The filter scheduler late in the Grizzly release cycle changed some of the behavior when creating a volume based on a type with extra-specs. Currently users would have to use the Simple Scheduler in order for them to work correctly.
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 this keys and fail to schedule deployment of the volume because no suitable back-end reports those capabilities.
To fix this all we need to do is scope the custom keys (ie: hp3par:cpg=TEST_CPG, hp3par:provisioning=full,....), unfortunately this requires an additional check in the driver to parse the key.
Fix proposed to branch: master /review. openstack. org/34273
Review: https:/