|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * virt/managing_vms/advanced_vm_management/virt-working-with-resource-quotas-for-vms.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: PROCEDURE |
| 6 | +[id="virt-creating-vm-quotas-web_{context}"] |
| 7 | += Creating virtual machine quotas using the web console |
| 8 | + |
| 9 | +[role="_abstract"] |
| 10 | +You can create Application Aware Quota (AAQ) quotas that limit virtual machine resource consumption by using the guided form in the {product-title} web console. The form is the recommended approach for simple virtualization quota use cases. |
| 11 | + |
| 12 | +.Prerequisites |
| 13 | + |
| 14 | +* You have cluster administrator privileges. |
| 15 | +* The Application Aware Quota operator is enabled in your cluster. See xref:virt-enabling-aaq-operator_{context}[Enabling the Application Aware Quota operator]. |
| 16 | +* The project where you want to create the quota exists. |
| 17 | +
|
| 18 | +.Procedure |
| 19 | + |
| 20 | +. In the {product-title} web console, click *Virtualization* -> *Quotas*. |
| 21 | + |
| 22 | +. Click *Create quota*. |
| 23 | + |
| 24 | +. In the dropdown menu, select *With form*. |
| 25 | ++ |
| 26 | +The create quota form is displayed. |
| 27 | + |
| 28 | +. Enter a name for your quota in the *Name* field. |
| 29 | ++ |
| 30 | +The name must be unique within the project. |
| 31 | + |
| 32 | +. Select the project where you want to apply this quota. |
| 33 | ++ |
| 34 | +By default, the current project is selected. You can click the dropdown to select a different project if needed. |
| 35 | ++ |
| 36 | +[NOTE] |
| 37 | +==== |
| 38 | +If a Kubernetes `ResourceQuota` already exists in the selected project, an alert is displayed with a link to view the existing ResourceQuota. You can still create the AAQ quota, but both quotas will apply to the project. |
| 39 | +==== |
| 40 | + |
| 41 | +. Configure CPU, memory, and VMI limits for the quota: |
| 42 | ++ |
| 43 | +The fields displayed vary based on the selected quota calculation method. For example: |
| 44 | ++ |
| 45 | +* For the `Virtual resources` or `Dedicated virtual resources` quota calculation method, the quotas exclude pod overhead: |
| 46 | +** Use the *vCPU allocation* field to set the maximum number of virtual CPUs permitted for all VMs in the project, excluding infrastructure overhead. |
| 47 | +** Use the *Virtual memory allocation* field to set the maximum memory capacity, in GiB, excluding infrastructure overhead. |
| 48 | +** Use the *VMI limits* field to set the maximum number of virtual machine instances. |
| 49 | +* For the `Virtual Machine Instance (VMI) pod usage` quota calculation method, the quotas include pod overhead: |
| 50 | +** Use the *CPU allocation* field to set the maximum number of CPU cores for pods that run VM workloads |
| 51 | +** Use the *Memory allocation* field to set the maximum memory capacity, in GiB, for pods that run VM workloads. |
| 52 | +** Use the *VMI limits* field to set the maximum number of virtual machine instances. |
| 53 | ++ |
| 54 | +[NOTE] |
| 55 | +==== |
| 56 | +Live migration overhead is excluded from the `Virtual Machine Instance (VMI) pod usage` quota calculation method. |
| 57 | +==== |
| 58 | + |
| 59 | +. Review the configuration and click *Create*. |
| 60 | ++ |
| 61 | +The quota is created and you are redirected to the quota details page. The new quota is now active and enforcing resource limits on virtual machines in the selected project. |
| 62 | + |
| 63 | +.Verification |
| 64 | + |
| 65 | +. In the {product-title} web console, click *Virtualization* -> *Quotas*. |
| 66 | + |
| 67 | +. In the quotas list, locate your newly created quota. |
| 68 | + |
| 69 | +. Verify that the quota name is displayed in the list with the correct project and resource limits configured. |
| 70 | + |
| 71 | +. Click the quota name to open its details page and confirm all settings are correct. |
0 commit comments