10 docs tagged with "quota"

CMP manages quotas at account and project levels:

Global Resource Quota defines the default resource limits copied to every new customer account under a Cloud Provider setup. Customer-facing quota for CloudStack is managed entirely in CMP — not through CloudStack quota APIs.

CMP manages quotas at the application level. Each connected orchestrator also enforces its own limits. The two systems are not synced automatically — admins must keep orchestrator limits equal to or greater than CMP account and project quotas.

In StackConsole CMP, Web Hosting plans are commercial offerings that map directly to underlying WHM packages. This guide covers how to create CMP-compatible packages in WHM, understand critical naming constraints, and map packages to sellable plans and rate cards in CMP.

CMP manages quotas at account and project levels. Account-level quotas are the hard ceiling for a customer account. Project-level quotas let the account owner distribute that capacity across projects (teams or sub-users).

CMP customer projects map one-to-one to OpenStack projects. Quota can be enforced in CMP only, or synced so OpenStack project limits follow CMP.

CloudStack has its own quota management system at domain, account, and project levels. CMP also has a separate quota engine — and the two systems do not share state.

StackConsole CMP provides a multi-tier quota management system to enforce resource boundaries across cloud providers, tenant accounts, and individual customer projects.

Customers can review how much quota their account is using and sync usage when reported numbers do not match their live services.

When a customer reaches their account-level quota limit, they can submit a Quota Increase Request from the customer portal. A CMP admin reviews the request and approves or rejects it.