Previous Topic: QuotasNext Topic: Quota Warn and Burst Levels


Quotas Overview

This section contains the following topics:

Quota Warn and Burst Levels

Operations Subject to Quotas

You can define a quota to restrict the resource allocations during the operation of a specific application or appliance class for specific users or groups on a single grid.

For example, you could limit the amount of CPU allocated during the provisioning of an application, then apply that limit to a specific customer.

Quotas allow you to:

You must be a Grid Administrator to create or modify quotas. Grid users can only view and list quota entries. By default, users and groups have no resource limits defined and do not have any restrictions.

You define a quota to restrict usage on the following resources:

Only Grid Administrators can create or modify quotas. Other users can only view and list quota entries.

The Grid Administrator can only assign one quota to a user or group, but a quota can contain zero or more resource limits. Also, quotas are restricted by the actual resources available on the grid. For example, if you set a CPU quota of 40, there may only be 20 total CPUs available on the grid. In this situation, defining a CPU quota of 40 would mean that this principal and its children can never use more than 40 CPUs (plus a burst, if a burst is also defined).

Note that the system only limits allocations of CA AppLogic® resources. Limits are enforced at the time these allocations are made, for example, when an application is started, or when a volume is created (Operations Subject to Quotas contains a complete list). Resource allocations within appliances (CPU, memory, disk space, and bandwidth usage) are not affected by quotas.

Note: Quotas apply only to objects that have an owner. Grid Administrators can create objects with no owner.