Comment 1 for bug 1039386

I don't really like b or c, having the scheduler implicitly set an attribute that it doesn't know about (and will probably be an incorrect value) just doesn't seem right.

I would prefer a and I'll create a patch for it but I do have a more radical idea I'd like to propose. How about we add a new colum to the `extra_specs' table that can be used to specify the scope of the entry? We put entries in this colum like `trust' to indicate that the row is only used by the trusted filter, `compute' for the ComputeCapabilitiesFilter, `*' to indicate the row is global and used by all. I suggest this because I know there are other usages of the `extra_specs' that people are considering so I'm afraid there will be other conflicts that come up.