Page MenuHomePhabricator

openstack-browser and horizon: Security group and floating IP quota information being pulled from Nova instead of Neutron for eqiad1-r
Closed, ResolvedPublic

Related Objects

StatusSubtypeAssignedTask
OpenNone
ResolvedMajavah
Resolvedaborrero
ResolvedAndrew
ResolvedAndrew
Resolveddcaro
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedCmjohnson
Resolvedayounsi
Resolvedaborrero
ResolvedCmjohnson
ResolvedJclark-ctr
OpenCmjohnson
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
Opendcaro
Resolvedaborrero
Opendcaro
Resolveddcaro
Opendcaro
Opendcaro
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedAndrew
ResolvedBstorm
Resolvedaborrero
Resolvedaborrero
Resolvedaborrero
OpenNone
Resolvedaborrero

Event Timeline

This turns out to be hard due to https://bugs.launchpad.net/neutron/+bug/1671448

I'm pretty surprised by that bug -- I guess that means that no Horizon user has ever seen their own network quota usage, even in the latest version...

Krenair renamed this task from openstack-browser: Security group and floating IP quota information being pulled from Nova instead of Neutron for eqiad1-r to openstack-browser and horizon: Security group and floating IP quota information being pulled from Nova instead of Neutron for eqiad1-r.Dec 10 2018, 9:41 PM
Krenair added a project: Horizon.

I am continually surprised at the types of things we end up needing to go to OpenStack upstream with.

@Andrew I see we do have floating IP and security group quota information visible in horizon. I wonder how the policy rules are set up for that..

@Andrew I see we do have floating IP and security group quota information visible in horizon. I wonder how the policy rules are set up for that..

This has been bothering me for a while! I believe this is because the api requires a token scoped in project A the quotas for project A, and we're trying to view the quotas for all projects with a single token.