Project resource quota administration
You can manage project resource quotas to prevent any single tenant from consuming excessive compute, networking, or storage resources, ensuring fair usage and overall system stability.
Each project is allocated resources, and project users are granted access to consume these resources. This enables multiple projects to use a single cloud without interfering with each other’s permissions and resources.
A set of resource quotas are pre-configured when a new project is created. The quotas include the amount of VCPUs, instances, RAM, and floating IPs that can be assigned to projects.
View user quotas for a project Copy linkLink copied!
View the resource quotas assigned to a project to check current limits. Comparing quota values against actual usage helps you troubleshoot why users cannot create resources and determine when to adjust specific allowances.
Procedure Copy linkLink copied!
$ openstack quota show [PROJECT-ID]
For example:
$ openstack quota show f0ba064c24ca4176ac55a45635ca561f
+-----------------------+-------+
| Resource | Limit |
+-----------------------+-------+
| cores | 20 |
| instances | 10 |
| ram | 51200 |
| volumes | 10 |
| snapshots | 10 |
| gigabytes | 1000 |
| backups | 10 |
| volumes___DEFAULT__ | -1 |
| gigabytes___DEFAULT__ | -1 |
| snapshots___DEFAULT__ | -1 |
| groups | 10 |
| trunk | -1 |
| networks | 100 |
| ports | 500 |
| rbac_policies | 10 |
| routers | 10 |
| subnets | 100 |
| subnet_pools | -1 |
| fixed-ips | -1 |
| injected-file-size | 10240 |
| injected-path-size | 255 |
| injected-files | 5 |
| key-pairs | 100 |
| properties | 128 |
| server-groups | 10 |
| server-group-members | 10 |
| floating-ips | 50 |
| secgroup-rules | 100 |
| secgroups | 10 |
| backup-gigabytes | 1000 |
| per-volume-gigabytes | -1 |
+-----------------------+-------+