On Mon, 2015-12-07 at 18:21 -0600, Chris Friesen wrote: > Can someone explain why nova doesn't seem to be doing any validation in the > "nova quota-show" command? (At least in kilo/stable.) > > If I run: > nova --debug quota-show --tenant aprojectdoesnotexist --user nosuchuser > > the debug info shows: > > DEBUG (connectionpool:383) "GET > /v2/ceddf233621f4772a8b4f17de3d45e31/os-quota-sets/aprojectdoesnotexist?user_id=nosuchuser > > HTTP/1.1" 200 359 > > and it returns a reasonable-looking set of quota information. > > > > Shouldn't nova be complaining that the specified tenant/user don't actually > exist?
1. Nova doesn't know what tenants and users exist; that's something only Keystone knows. 2. There are defaults for quotas, which is how nova determines what quotas to apply to a tenant when there's no specific quota for that tenant in its database. That's why you're getting a reasonable-looking set of quota information. -- Kevin L. Mitchell <[email protected]> Rackspace __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
