Skip to main content

​
Overview

Quotas prevent individual projects from consuming excessive object storage capacity. Quotas are enforced at the account level (project-wide) or container level. When a quota is exceeded, the storage service returns 413 Request Entity Too Large.
Administrator Access Required — This operation requires the admin role. Contact your Xloud administrator if you do not have sufficient permissions.

​
Account-Level Quotas

Account quotas limit the total storage consumed by a project across all containers.
Set account-level quota (100 GB)
openstack object store account set \
  --property X-Account-Meta-Quota-Bytes=107374182400
View current account usage vs quota
openstack object store account show \
  -c x-account-bytes-used \
  -c x-account-meta-quota-bytes

​
Container-Level Quotas

Container quotas limit storage within a specific container.
Set container byte quota (10 GB)
openstack container set \
  --property X-Container-Meta-Quota-Bytes=10737418240 \
  app-uploads

​
Quota Reference

Quota TypeHeaderScopeEnforcement
Account byte limitX-Account-Meta-Quota-BytesAll containers in accountReturns 413 on exceed
Container byte limitX-Container-Meta-Quota-BytesSingle containerReturns 413 on exceed
Container object countX-Container-Meta-Quota-CountSingle containerReturns 413 on exceed

​
Common Quota Sizes

SizeBytes
10 GB10737418240
50 GB53687091200
100 GB107374182400
500 GB536870912000
1 TB1099511627776

​
Next Steps

Security

Apply access controls and TLS hardening alongside quotas

Monitoring

Track capacity usage across nodes and accounts

Storage Policies

Design storage tiers to optimize cost and capacity

Admin Troubleshooting

Diagnose quota enforcement and 413 errors