Openstack stores quota usage for tenants in the database in quota_usages table. Nova and cinder have by default their own separate databases and in each database you get a new quota_usages table.<\/p>\n
The structure of the quota_usages table is as follows<\/p>\n
+---------------+--------------+------+-----+---------+----------------+\n| Field | Type | Null | Key | Default | Extra |\n+---------------+--------------+------+-----+---------+----------------+\n| created_at | datetime | YES | | NULL | |\n| updated_at | datetime | YES | | NULL | |\n| deleted_at | datetime | YES | | NULL | |\n| id | int(11) | NO | PRI | NULL | auto_increment |\n| project_id | varchar(255) | YES | MUL | NULL | |\n| resource | varchar(255) | NO | | NULL | |\n| in_use | int(11) | NO | | NULL | |\n| reserved | int(11) | NO | | NULL | |\n| until_refresh | int(11) | YES | | NULL | |\n| deleted | int(11) | YES | | NULL | |\n| user_id | varchar(255) | YES | MUL | NULL | |\n+---------------+--------------+------+-----+---------+----------------+<\/pre>\n<\/p>\n
Remember that quotas are managed per project, so in this table project_id is your navigating key. Project IDs are used to identify projects. For a particular project, you can retrieve the project ID using<\/p>\n
openstack project list | grep $PROJECT_NAME<\/pre>\nThe other interesting fields in the quota_usages table are<\/p>\n
resource: for example in nova, it can be “instance, ram, cores, security_groups”<\/p>\n
in_use : This is the amount per resource that Openstack “thinks” that project is using<\/p>\n
Occasionally the in_use field is not updated properly and you might find yourself in a situation where openstack is reporting usage that doesn’t exist. You have two options at this point<\/p>\n
nova-manage project quota_usage_refresh --project PROJECT_ID --user USER_ID --key cores<\/pre>\n
Openstack stores quota usage for tenants in the database in quota_usages table. Nova and cinder have by default their own separate databases and in each database you get a new quota_usages table. The structure of the quota_usages table is as follows +—————+————–+——+—–+———+—————-+ | Field | Type | Null | Key | Default | Extra |