Overview
Quotas limit the number of networking resources a project can consume. Default quotas are set cluster-wide during deployment. You can override them per project to accommodate workloads that require higher limits or to restrict projects that should operate within a strict budget.Prerequisites
- Admin credentials sourced from
admin-openrc.sh - The target project ID or name
Default Quota Reference
| Resource | Default Limit | Notes |
|---|---|---|
| Networks | 10 | Per project |
| Subnets | 10 | Per project |
| Ports | 50 | Per project |
| Routers | 10 | Per project |
| Floating IPs | 50 | Per project |
| Security Groups | 10 | Per project |
| Security Group Rules | 100 | Per project |
View Current Quotas
- Dashboard
- CLI
Log in to the Xloud Dashboard (
https://connect.<your-domain>) as an administrator
and navigate to Admin → Identity → Projects. Select the project, then click
Modify Quotas. Scroll to the Network section to review and update networking
quotas.Update Quotas for a Project
- Dashboard
- CLI
Navigate to Admin → Identity → Projects, select the project, click
Modify Quotas, update the values in the Network section, and click Save.
Reset Quotas to Defaults
Reset project quotas to cluster defaults
View Quota Usage
Show quota usage for a project
--usage flag adds In Use and Reserved columns alongside the quota limit, making
it easy to identify projects approaching their limits.
Floating IP Pool Management
Floating IPs are allocated from the external network’s address pool. Monitor pool exhaustion at the cluster level:List all floating IPs across all projects
Count floating IPs by status
Next Steps
Quality of Service
Control bandwidth alongside quota management for fair resource sharing
Security Hardening
Harden network security policies across all projects
Provider Networks
Expand the external network pool to support more floating IP allocations
Admin Troubleshooting
Diagnose quota exhaustion and resource allocation failures