When using the filter scheduler which is now the default,
we can no longer pass in extra-specs like: {minIOPS:500, ....},
because the capabilities filter will reject this because there is
no host reporting minIOPS:500 capabilities.
We now need to scope the keys (ie qos:minIOPS:500....), but
that unfortunately requires a fix to the SolidFire driver.
This change add a check for the ':' in the key, and parses
on it if it's there.
Also fixes backend_name and uses VERSION var instead of
generating string in stats reporting.
Reviewed: https:/ /review. openstack. org/26571 github. com/openstack/ cinder/ commit/ 0e3ea4e85dab00b 7cecd5596f6daa6 5cc4d710b5
Committed: http://
Submitter: Jenkins
Branch: master
commit 0e3ea4e85dab00b 7cecd5596f6daa6 5cc4d710b5
Author: John Griffith <email address hidden>
Date: Tue Apr 9 23:07:52 2013 -0600
Add parsing to extra-specs key check
When using the filter scheduler which is now the default,
we can no longer pass in extra-specs like: {minIOPS:500, ....},
because the capabilities filter will reject this because there is
no host reporting minIOPS:500 capabilities.
We now need to scope the keys (ie qos:minIOPS: 500.... ), but
that unfortunately requires a fix to the SolidFire driver.
This change add a check for the ':' in the key, and parses
on it if it's there.
Also fixes backend_name and uses VERSION var instead of
generating string in stats reporting.
Fixes bug: 1167141
Change-Id: Ie7fd7d231af78c b18a13f44a4379b 44d3c3385df