Comment 4 for bug 1842061

Ideally AggregateInstanceExtraSpecsFilter should check only scoped specs in aggregate metadata.
e.g.

flavor spec {"key1": "value1}" and {"aggregate_instance_extra_specs:key1":"value1"}, both are filtered to must have {"key1": "value1"} in either of host aggregate. This should be limited to only scoped spec.

Is it bug in filter or its expected behavior ?