Quota commands need more clear help and output

[Eugene Nikanorov]

Quota-related commands need more clear description and output.
Currently there are a few examples of misleading behavior such as:

(neutron) quota-delete
Deleted quota: be2a31a3b4204c448be24a51e4512b3b

quota-list shows empty list, quota-update shows existing quotas

[Matt Dietz (cerberus)]

Assuming this is abandoned since it's been assigned for a year and a half. I'm claiming it

[Matt Dietz (cerberus)]

This seems more broken than I originally thought. Listing quotas doesn't work at all unless I actually have some associated with my tenant. If I enter even a SINGLE record, suddenly all the quotas will appear, including the defaults defined by configuration values. Meanwhile, a delete will delete ALL quotas for the calling tenant in the database. That's not a typo. Additionally, delete doesn't even seem to take an argument in neutronclient. It just passes the calling tenant_id as /quotas/<tenant>

How did this *ever* pass review?

[Matt Dietz (cerberus)]

Actually, it looks like the delete problem is because of the plugin I have in use, but in any case the base driver prevents deletions, which neutronclient itself doesn't seem to understand. Raising a 403 in response to a delete implies something *could* be done if the user only had the right parameters, which doesn't seem useful. To be honest, as implemented, I don't see how quota-delete could ever be useful to someone.

[Matt Dietz (cerberus)]

Last correction, it looks like the base implementation also deletes all quotas for the tenant. I still see how that's useful, however.

[Matt Dietz (cerberus)]

Digging a little deeper, it seems all of this behavior is entirely deliberate. See https://bugs.launchpad.net/neutron/+bug/1204956 for more details. While I disagree with the utility, yelling at myself about it in a bug report isn't going to solve it, so I'm going to close this.