Documentation Index
Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Quotas enforce per-project resource limits to prevent over-consumption and ensure fair resource distribution across tenants. Xloud Compute tracks quotas for instances, vCPUs, RAM, server groups, key pairs, and other compute resources.Prerequisites
- Administrator access for modifying quotas
- Users can view their own project quota usage in the instance create wizard
Default Compute Quotas
| Resource | Default Limit | Description |
|---|---|---|
| Instances | 10 | Maximum number of instances per project |
| Cores | 20 | Maximum vCPUs across all instances |
| RAM | 51200 MB | Maximum RAM across all instances |
| Key Pairs | 100 | Maximum SSH key pairs per user |
| Server Groups | 10 | Maximum server groups per project |
| Server Group Members | 10 | Maximum instances per server group |
View Quota Usage
- Dashboard
- CLI
Quota usage is displayed in real-time during instance creation. The
Instance Create wizard (Step 4: Confirm Config) shows a footer badge with
current usage for: Instances, CPU, Memory, Volumes, Volume Capacity, and
Server Group Members.If any quota would be exceeded, the badge turns red and the submit button
is disabled.
The Dashboard does not provide a dedicated quota management page. Quota
modifications are performed via the CLI or through
XDeploy configuration.
Modify Quotas
- XDeploy
- CLI
Next Steps
Launch an Instance
See quota enforcement in action during instance creation
Flavors
Manage flavor sizes that consume quota
Compute Hosts
Monitor cluster-wide resource availability
Storage Quotas
Manage block storage volume and capacity quotas