Parser for filter_func and goodness_func can't handle ":" characters

Bug #1800224 reported by Matt Smith
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
In Progress
Undecided
Matt Smith

Bug Description

When writing a filter_function in cinder.conf any capabilities key that contains a ":" character can't be used in the filter because the parser can't handle this character.

Example Valid:

filter_function = "extra.some_non_prefixed_key >= 10"

Example Invalid:

filter_function = "extra.PREFIX:some_prefixed_key >= 10"

The parser does not support index notation for dictionaries, so this is not valid either:

filter_function = "extra['PREFIX:some_prefixed_key'] >= 10" even though it is valid Python

This means any vendor prefixed extra_spec is precluded from being used in a filter_function or goodness_function. This eliminates many possibilities for selection among several backends of the same vendor.

Matt Smith (mss-4)
tags: added: filter
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.