I think specifying roles is a matter of different not quota-related
work, which is better done in the scope of a blueprint.
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1368010
Title:
Specific roles should be allowed to view or configure quota
Status in OpenStack Neutron (virtual network service):
Opinion
Bug description:
Currently in Neutron, only admins are allowed to view or configure
tenant quota:
http://docs.openstack.org/user-guide-admin/content/cli_set_quotas.html
"Only users with the admin role can change a quota value."
And it's hard coded in
https://github.com/openstack/neutron/blob/master/neutron/extensions/quotasv2.py
to check admin context.
We should allow specifying roles in policy.json to view or configure
quota for more flexible configuration.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1368010/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
