Defining and creating quotas
What are quotas? Within OpenStack, you can set quotas on a tenant/project or user level in order to restrict the resource consumption allowed. The Compute service (Nova) manages the quota values and also enforces them. As a cloud operator, this is another important feature OpenStack offers. Quotas allow you to control the cloud's overall system capacity. You may ask, why not just set up one default quota and let every project use it? We will step through why this approach may or may not work based on the particular use case. It is also worth mentioning that the Block Storage service (Cinder) also has the capability of setting quotas.
Since we now know that you can set quotas, let's review what resources can be restricted and what the default values are. The following table describes the type of quotas that can be set:
|
Quota Name |
Defines the number of |
|
Instances |
Instances allowed in each project |
|
Cores |
Instance cores allowed in each project |
|
RAM (MB) |
RAM... |
