To prevent system capacities from being exhausted without notification, you can set up quotas. Quotas are operational limits. For example, the number of gigabytes allowed for each project can be controlled so that cloud resources are optimized. Quotas can be enforced at both the project and the project-user level.
Typically, you change quotas when a project needs more than ten volumes or 1 TB on a compute node.
Using the Dashboard, you can view default Compute and Block Storage quotas for new projects, as well as update quotas for existing projects.
Using the command-line interface, you can manage quotas for the OpenStack Compute service, the OpenStack Block Storage service, and the OpenStack Networking service (see OpenStack Administrator Guide). Additionally, you can update Compute service quotas for project users.
The following table describes the Compute and Block Storage service quotas:
|Quota Name||Defines the number of||Service|
|Gigabytes||Volume gigabytes allowed for each project.||Block Storage|
|Instances||Instances allowed for each project.||Compute|
|Injected Files||Injected files allowed for each project.||Compute|
|Injected File Content Bytes||Content bytes allowed for each injected file.||Compute|
|Keypairs||Number of keypairs.||Compute|
|Metadata Items||Metadata items allowed for each instance.||Compute|
|RAM (MB)||RAM megabytes allowed for each instance.||Compute|
|Security Groups||Security groups allowed for each project.||Compute|
|Security Group Rules||Security group rules allowed for each project.||Compute|
|Snapshots||Volume snapshots allowed for each project.||Block Storage|
|VCPUs||Instance cores allowed for each project.||Compute|
|Volumes||Volumes allowed for each project.||Block Storage|
You can sort the table by clicking on either the Quota Name or Limit column headers.
The dashboard does not show all possible project quotas. To view and update the quotas for a service, use its command-line client. See OpenStack Administrator Guide.