Skip to main content

Overview

Quotas enforce per-project resource ceilings to prevent any single tenant from exhausting cluster capacity. Xloud Compute applies quotas to instances, vCPUs, RAM, key pairs, and server groups. You can view and adjust quotas per project without affecting currently running workloads.
Administrator Access Required — This operation requires the admin role. Contact your Xloud administrator if you do not have sufficient permissions.
Prerequisites
  • Admin credentials sourced from admin-openrc.sh
  • openstack CLI installed and configured
  • The target project ID or name

Default Quota Values

The following defaults apply to all new projects unless explicitly overridden.
ResourceDefault LimitDescription
instances10Total running instances per project
cores20Total vCPUs allocated across all instances
ram51,200 MBTotal RAM allocated across all instances
key_pairs100SSH key pairs per user
server_groups10Server groups per project
server_group_members10Maximum instances per server group
injected_files5Files injectable at instance boot
Xloud Compute supports over-commitment — the default vCPU and RAM allocation ratios allow the sum of allocated resources to exceed physical capacity. In production, set explicit quotas that account for over-commitment ratios configured on each host. The default vCPU ratio is 16:1 and RAM ratio is 1.5:1. See Compute Hosts for details on over-commitment configuration.

View and Update Quotas

View cluster-wide defaults

Navigate to Admin → Compute → Defaults to view the global quota defaults applied to new projects.

Open project-level quota management

Navigate to Admin → Identity → Projects. Locate the target project in the list and click its name to open the project detail.

Modify project quotas

Select Modify Quotas from the Actions menu. Adjust the quota values for the resources you want to change:
FieldRecommended Approach
InstancesSet based on the project’s expected VM count plus a 20% buffer
vCPUsMatch the instance limit multiplied by the average flavor vCPU count
RAMMatch the instance limit multiplied by the average flavor RAM in MB
Click Save to apply the changes.
Changes apply immediately. Running instances are not affected by reduced quotas — only new allocations are blocked once the new limit is reached.

Monitoring Quota Usage

Track active quota consumption before raising limits to avoid enabling runaway resource use.
Show current usage versus the project quota:
Show quota usage for a project
openstack quota show --compute <project-id>
List all instances consuming quota in a project:
List instances in a project
openstack server list --project <project-id> --all-projects --long
View aggregate usage across all projects (admin only):
Show cluster-wide hypervisor statistics
openstack hypervisor stats show
Before increasing quotas, verify that the cluster has sufficient physical capacity to support the new limits. Use openstack hypervisor stats show to check aggregate free vCPUs and RAM across all hosts.

Next Steps

Compute Hosts

Monitor physical resource availability before adjusting project quotas.

Flavor Management

Define instance sizes that projects can deploy within their quota limits.

Admin Guide

Return to the Compute Administration Guide index.