In folsom, I can use the command below to check the quota usage information of a tenant, but in grizzly, I found the command not work. #nova-manage project quota $Tenant_ID

Does the command to check quota usage have been changed? If so, what's the new command? If not, is this a openstack grizzly bug?

In Folsom:

nova-manage project quota 2d571f433da343b8aa832efae1783180

Quota Limit In Use Reserved metadata_items 128 0 0
injected_file_content_bytes 10240 0 0
volumes 10 0 0
gigabytes 1000 0 0
ram 51200 20480 -16384
floating_ips 10 0 0
security_group_rules 20 0 0
instances 10 6 -4
key_pairs 100 0 0
injected_files 5 0 0
cores 20 10 -8
fixed_ips 10 6 0
injected_file_path_bytes 255 0 0
security_groups 50 0 0

But in Grizzly:

nova-manage project quota 1d833ef4105443968d5c97fc87efadd6

None is not a valid quota key. Valid options are: metadata_items, injected_file_content_bytes, ram, floating_ips, security_group_rules, instances, key_pairs, injected_files, cores, fixed_ips, injected_file_path_bytes, security_groups.

nova-manage project quota -h

usage: nova-manage project quota [-h] [--project <project name="">] [--key <key>] [--value <value>] [action_args [action_args ...]]

positional arguments: action_args

optional arguments: -h, --help show this help message and exit --project <project name=""> Project name --key <key> Key --value <value> Value

nova-manage project quota --project admin

None is not a valid quota key. Valid options are: metadata_items, injected_file_content_bytes, ram, floating_ips, security_group_rules, instances, key_pairs, injected_files, cores, fixed_ips, injected_file_path_bytes, security_groups.