Horizon tenant list call should be cached
Bug #949491 reported by
Jake Dahn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Gabriel Hurley |
Bug Description
When I load any page, and look at the keystone log output, it shows that there are multiple calls being made to /tenants, to get a list of tenants which are authorized for the given token.
I think this is where the call is being made: https:/
We should probably add caching to this.
Changed in horizon: | |
assignee: | nobody → Mike Perez (thingee) |
Changed in horizon: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → essex-rc1 |
Changed in horizon: | |
status: | Confirmed → In Progress |
assignee: | Mike Perez (thingee) → Jake Dahn (jakedahn) |
summary: |
- Horizon tenant list call should be cached... + Horizon tenant list call should be cached |
Changed in horizon: | |
milestone: | none → folsom-1 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | folsom-1 → 2012.2 |
To post a comment you must log in.
I'm going to treat this as a request for caching rather than a bug report about the requests in the middleware, since there's already a ticket for that: https:/ /bugs.launchpad .net/horizon/ +bug/942074
FWIW, that only makes one request for the tokens (it used to make multiple calls in many cases), however if you're on a page like the syspanel tenants list, the launch instance dialog, the create user dialog, or any other place that makes a separate call to populate a tenant chooser dropdown, etc. then you will see multiple calls and this is correct behavior under the current assumptions in the dashboard.
I've been thinking a lot about the caching problem, though, and it's not simple. We need to cut down on making this tenants call so many times, however we also don't want to find ourselves stuck in a case where a newly-created tenant is inaccessible. This is going to be a tricky task and should be addressed in Folsom.