quota-show should default to current user

[Phil Day]

quota-show accepts (for admin use) tenant and user parameters to show the quotas values for a specific tenant or a specific user within an tenant. By default it should show the quotas for the current tenant and user.

However if tenant is not specified user defaults to None - which then shows the tenant level quotas. If the user has their own quotas within the tenant this is quiet confusing, since they won't be able to use all of the tenant level quotas shown, and also potentially leaks information that they may not be entitled to see (the tenant level quotas)

When no tenant is specified the used should be set to the current user, so that only their specific quota values are shown (which will be the same as the tenant ones when there are no user specific quotas)

[Neetu Jain (nutshi)]

i think there are a lot of bugs around quota-show

to start with i think the input validation of tenant needs to be fixed

novaclient/v2/shell.py

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/265971

[Neetu Jain (nutshi)]

fix proposed in https://review.openstack.org/#/c/265971/

[Neetu Jain (nutshi)]

once i find out how to validate tenant-name ( basically how to find the corresponding tenant-id based on tenant name ) I would like to add that validation too to solve issues like
https://bugs.launchpad.net/python-novaclient/+bug/1103601

https://bugs.launchpad.net/python-novaclient/+bug/1531611

[Neetu Jain (nutshi)]

Few points from the discussion

1) If no user is specified then should we default to current user ..is that right? If so then by default "quota-show" will display user level quotas not tenant level

2) For tenant-level quotas dispplay do we have a flag like --only ? of user=None or any other better choice?

3) is there a way to map tenant-name to tenand-id without a keystone call ?

any inputs ?

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/265971
Reason: This review is > 6 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.