Comment 2 for bug 1366859

I'm all for using the ImagePropertiesFilter but we should deal with this in a manner that doesn't break existing installations (particularly TripleO) if possible. Given existing DB data formats and such I was already considering and hacking on option #2 (Stop canonicalizing the data in the 'cpu_arch' extra specs field (but *still* canonicalize supported_instances)) so if we agree this is doable then I think that might be the best solution.

The hack to the ComputeCapabilitiesFilter seems really dirty given it is a generic extra_specs filter already... so it is also my least favorite.