Allow irrelevant,self-defined specs in ComputeCapacityFilter
For backward compatibility, ComputeCapacityFilter treats extra spec
keys which contain no colons like 'x' the same as 'capabilities:x',
because hoststate doesn't contain attribute like x, this filter always
return False. So it causes conflict with
AggregateInstanceExtraSpecsFilter, and limits user to define extra spec
keys without colons.
This patch solves the conflict and keep it backward compatible.
This patch also joins two lines into one in method host_passes.
Reviewed: https:/ /review. openstack. org/317306 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=83b59ea6035 df173fb206167a4 911f512fe22e64
Committed: https:/
Submitter: Jenkins
Branch: master
commit 83b59ea6035df17 3fb206167a4911f 512fe22e64 yufei@99cloud. net>
Author: OctopusZhang <zhang.
Date: Tue May 17 08:05:19 2016 +0000
Allow irrelevant, self-defined specs in ComputeCapacity Filter
For backward compatibility, ComputeCapacity Filter treats extra spec stanceExtraSpec sFilter, and limits user to define extra spec
keys which contain no colons like 'x' the same as 'capabilities:x',
because hoststate doesn't contain attribute like x, this filter always
return False. So it causes conflict with
AggregateIn
keys without colons.
This patch solves the conflict and keep it backward compatible.
This patch also joins two lines into one in method host_passes.
Change-Id: Ia9e7c882bcee13 1e106e67dc46ed9 ce1224e4c67
Closes-Bug: #1582589