Quota Overview
StackConsole CMP provides a multi-tier quota management system to enforce resource boundaries across cloud providers, tenant accounts, and individual customer projects.
Quota enforcement ensures predictable resource consumption, prevents cluster exhaustion, and provides a structured workflow for customers requesting additional capacity.
Quota Hierarchy
Quota enforcement in CMP operates across three primary tiers:
Global Resource Quota (Default template configured per Cloud Provider setup)
↓ (copied on new customer registration)
Account-Level Quota (Hard ceiling per customer account)
↓ (distributed by account owner)
Project-Level Quota (Allocations across customer projects and sub-users)
| Tier | Configured By | Scope | Documentation |
|---|---|---|---|
| Global Quotas | CMP Admin | Default resource limits automatically copied to newly created accounts | Global Resource Quotas |
| Account Quotas | CMP Admin | Hard resource ceiling on compute, storage, and networking for a specific account | Account-Level Quotas |
| Project Quotas | Customer Account Owner | Capacity distribution across internal teams and projects (defaults to Unlimited up to account ceiling) | Project-Level Quotas |
| Quota Requests | Customer & CMP Admin | Self-service increase requests submitted from customer portal, approved/rejected in admin console | Quota Requests & Approvals |
| Orchestrator Sync | CMP Admin | Alignment between CMP application quotas and backend orchestrators (e.g. CloudStack, OpenStack) | Orchestrator-Side Quota Sync |
Core Principles
1. Application-Level Management
Customer-facing quota limits are managed and enforced directly within StackConsole CMP, rather than relying exclusively on orchestrator quota APIs.
2. Independent Ceilings After Creation
When a new customer is registered, CMP copies the current Global Resource Quota into the customer's account-level quota. Subsequent modifications to the global quota apply only to new accounts; existing accounts maintain their independent ceilings unless updated by an admin.
3. Account Ceiling Precedence
Project quotas allow account owners to divide their assigned resources among projects. However, project limits can never exceed the overall account ceiling. An "Unlimited" project quota simply allows that project to consume up to the account limit.
4. Orchestrator Sync Alignment
Because CMP quotas operate at the application level, backend orchestrator domains and accounts must have equal or higher resource limits to prevent orchestrator-side provisioning rejections. See Orchestrator-Side Quota Sync for details on avoiding quota mismatch issues.
Related Documentation
- Billing Overview — Rate cards, billing cycles, and payment modes
- Customer Billing Dashboard — Usage and resource reporting
- CloudStack Quota Management — CloudStack-specific quota settings
- OpenStack Quota Management — OpenStack-specific quota settings