TrustedFilter issue with ComputeCapabilitiesFilter and AggregateInstanceExtraSpecsFilter
Bug #1039386 reported by
Mark McLoughlin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Joe Gordon |
Bug Description
It appears impossible to use TrustedFilter while ComputeCapabili
The issue is that if you set trusted_
I guess there are a few ways to fix this - (a) have the other filters ignore trusted_host explicitly or (b) always set trusted_
Changed in nova: | |
assignee: | Don Dugger (n0ano) → Donald Dugger (n0ano-ddd) |
status: | Triaged → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
status: | Fix Committed → In Progress |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
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 ComputeCapabili tiesFilter, `*' 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.