Skip to main content

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

Storage quotas limit the total volumes, snapshots, backups, and capacity that each project can consume. Quotas prevent runaway resource consumption in multi-tenant deployments and ensure fair capacity distribution. Default limits apply to all new projects; per-project overrides allow specific projects to receive higher or lower limits.
Administrator Access Required — This operation requires the admin role. Contact your Xloud administrator if you do not have sufficient permissions.
Prerequisites
  • Administrator credentials with the admin role
  • Project IDs for per-project quota adjustments

​
Default Quota Values

QuotaDefaultDescription
volumes10Maximum number of volumes per project
gigabytes1,000Maximum total volume capacity (GiB) per project
snapshots10Maximum number of snapshots per project
backups10Maximum number of backups per project
backup_gigabytes1,000Maximum backup storage capacity (GiB) per project
per_volume_gigabytes-1Maximum size of a single volume (-1 = unlimited)

​
View Quota Usage

View global defaults

Navigate to Storage > Volume Types (admin view). The Volume Quotas section shows the global default limits applied to all new projects.

View project-specific usage

Navigate to Identity > Projects (admin view). Select a project, then click Edit Quota to see the current limits and usage for that project.

​
Update Project Quotas

Navigate to Projects

Navigate to Identity > Projects (admin view) and select the target project.

Modify quotas

Click Edit Quota. Adjust the volume, gigabytes, snapshot, and backup limits as required. Click Confirm.
Reducing a quota below the project’s current usage does not reclaim resources. Existing volumes and snapshots are unaffected, but no new resources can be created until usage drops below the new limit.

Verify

Return to Edit Quota for the project and confirm the new limits are applied.
Quota updated — new limits take effect immediately for future operations.

​
Update Global Default Quotas

Global defaults apply to all new projects. Updating them does not affect projects that already have explicit quota overrides.
Set global default quotas
openstack quota set \
  --volumes 20 \
  --gigabytes 2000 \
  --snapshots 20 \
  --class default

​
Remove Per-Project Quota Override

To revert a project to the global defaults, delete its quota override:
Delete project quota override
openstack quota delete <project-id-or-name>
The project reverts to the global default values immediately.

​
Quota Planning Guidelines

To size quotas appropriately, estimate:
  1. Average volume size per instance (typically 50–200 GiB for boot + data)
  2. Number of instances expected in the project
  3. Snapshot overhead (typically 10–30% of volume data for active snapshots)
  4. Growth buffer (20–50% headroom)
Example: A project running 10 instances with 100 GiB average volumes, 20% snapshot overhead, and 30% growth buffer: (10 × 100) + (1000 × 0.20) + (1200 × 0.30) = 1000 + 200 + 360 = 1,560 GiB
Regularly audit quota usage to identify projects approaching their limits:
List all project quotas
openstack quota list --detail
Review projects approaching 80% of their gigabytes or volumes quota — either clean up unused resources or increase the quota proactively.

​
Next Steps

Volume Types & QoS

Control per-volume IOPS and throughput with QoS policies

Security Hardening

Restrict volume type access and enforce security policies

Admin Guide

Return to the Block Storage administration overview

Troubleshooting (Admin)

Diagnose and resolve service-level Block Storage issues