Quotas
Each project is assigned a quota which defines how much resources that a project can use. When resource consuming operations such as virtual machine creation are performed, the request is validated against the maximum quota permitted for the current project (as set by the environment variables or Horizon dashboard).
For shared projects, you can request additional resources via change project quota.
The project quota can be checked using:
$ openstack quota show 841615a3-ece9-4622-9fa0-fdc178ed34f8
+----------------------+--------------------------------------+
| Field | Value |
+----------------------+--------------------------------------+
| cores | 20 |
| fixed-ips | -1 |
| floating_ips | 0 |
| gigabytes | 100 |
| gigabytes_standard | -1 |
| injected-file-size | 10240 |
| injected-files | 5 |
| injected-path-size | 255 |
| instances | 10 |
| key-pairs | 100 |
| project | 841615a3-ece9-4622-9fa0-fdc178ed34f8 |
| properties | 128 |
| ram | 40960 |
| security_group_rules | 0 |
| security_groups | 0 |
| snapshots | 10 |
| snapshots_standard | -1 |
| volumes | 10 |
| volumes_standard | -1 |
+----------------------+--------------------------------------+
| Quota Name | Description |
|---|---|
| cores | Number of instance cores (VCPUs) allowed per project. |
| fixed-ips | Number of fixed IP addresses allowed per project. This number must be equal to or greater than the number of allowed instances. A value of -1 means unlimited |
| floating_ips | Number of floating IP addresses allowed per project. A value of -1 means unlimited. See Restrictions for the current status of floating IPs in the CERN cloud |
| gigabytes | Total space in volume storage |
| gigabytes_type | Total space in the volume storage class type such as standard |
| injected-file-size | Number of content bytes allowed per injected file. |
| injected-path-size | Number of bytes allowed per injected file path. |
| injected-files | Number of injected files allowed per project. |
| instances | Number of virtual machines allowed per project. |
| key-pairs | Number of key pairs allowed per user. |
| ram | Total megabytes of instance ram allowed per project. |
| security-groups | Number of security groups per project. |
| security-group-rules | Number of rules per security group. |
| snapshots | Total number of volume snapshots allowed per project |
| snapshots_type | Snapshots allowed for the volume storage class type |
| volumes | Total volumes allowed for the project |
| volumes_type | Volumes allowed for the volume storage class type |
Projects with virtual resources only (excludings special resources like GPUs)
The bulk of projects will contain only virtual resources. To give maximum flexibility to the users on the mixture of flavors, the global quota is set as described above.
Projects with physical resources only
For projects which only contain physical resources, the procedure can be simplified. In that case, the project will get access to a specific hardware flavor, and project meta data is added, indicating the number of instances of that flavor the project is allowed to have. The CPU, memory and disk quota of the project will have to match what is required to instantiate the given resources. Since the user will have full access to the machine list, the quota are set in an automatic maner, matching the number and kind of instances described by the project meta data.
Projects with mixed physical and virtual resources
There are cases of projects with mixed resources. For physical resources, we set the number of instances per physical flavor in the project meta data, as above. However, the quota is handled as in the pure VM project case, via a quota request as mentioned above. It is up to the user to correctly calculate what he needs, and respect the number of instances as specified in the project meta data for physical resources.
Projects with access to special resources
These are projects which have access to special flavors, providing e.g. GPU resources. These GPU VMs are treated like physical resources, that is, the project meta data will indicate how many resources of the special flavor the project is allowed to have.