Configure Per-Destination Quotas for Organizations

You can configure distinct quota limits for each deployment destination available to a user or organization. For example, for a single organization, you can set distinct resource quota limits for each destination. Or, you can set a cost quota for the Production destination, a resource quota for Staging and Development, and no quota limit for Lab.

Per-destination quotas can be useful for such scenarios as cloud-bursting: if an organization exceeds its quota on its private cloud destinations, then Commander can deploy to a public cloud destination instead. For more information, see Configure Placement Attributes.

• Per-destination quotas target a specific folder. VMs in subfolders under the targeted folder will not be restricted by quotas configured for the parent folder.
• Quotas cannot be configured for parent organizations.

Once you have configured a per-destination quota, Service Portal users can view their quota usage for each destination where they, or their organization, own VMs.

When configuring an organization, administrators can select the currency for all cost quotas for the organization. Admin Portal users will see quota information in the currency that was selected when the organization was configured.

Users in a Service Portal role with Manage Organization permission can manage this organization by adding and editing user's quotas for this organization. When managing quotas, they will see the currency selected for the organization. All Service Portal users will see Quota Usage on the Dashboard and quota warnings in their preferred currency.

Organization managers can configure quota limits for each member on each destination where quota is configured.

After you configure distinct quota limits for each deployment destination available to a user or organization, it is recommended that you set up a quota-based approval process. For more information, see Configure a Quota-Based Service Request Approval Process.

Set per-destination quotas for organizations

1. Click the Organizations tab.
2. On the Organizations tab, select the organization and click Edit to open the Configure Organization dialog.
3. Click Next until you get to the Quotas page.
4. On the Quotas page, select Destination Quota, and, when configuring cost quotas, select the currency to be used for cost quotas.

For each deployment destination already assigned to this organization, two pages appear in the wizard for each destination: one for Organization Quotas and one for Member Quotas.

If you want to create a new destination for this organization, click New Destination. For more information, see Configure Automated Deployment for Approved Service Requests.

5. On the Organization Quotas page, for each destination, from the Select Quota Type drop-down, select one of the following:
• No Quota Limit: No quota limits will be set for this organization on this destination. Continue to Set no quota limit for destinations.
• Resource Quota: This organization will have a resource quota limit on this destination. Continue to Set resource quota for destinations.
• Cost Quota: This organization will have a daily cost quota limit on this destination. Continue to Set cost quota for destinations.

6. Click Finish.

Quota details are displayed when you select the organization on the Organizations tab.

Set no quota limit for destinations

1. Click the Organizations tab.
2. On the Organizations page, select the organization and click Edit to open the Configure Organization dialog.
3. Click Next until you get to the Quotas page.
4. On the Quotas page, select No Quota Limit from the Select Quota Type drop-down list.
5. Configure quota settings for other destinations as required.
6. Click Finish.

   Quota details are displayed when you select the organization on the Organizations tab.

Set resource quota for destinations

1. Click the Organizations tab.
2. On the Organizations page, select the organization and click Edit to open the Configure Organization dialog.
3. Click Next until you get to the Quotas page.
4. On the Quotas page, select Resource Quota from the Select Quota Type drop-down list.

You can set an overall storage limit for an organization, per-tier storage limits, or both.

5. Enter values for CPUs, Memory and Storage as required.

   The organization's current resource usage is displayed to guide you in setting resource limits. Resource usage is based on all services in the location targeted by this deployment destination that are currently assigned to the organization.

   You can leave the organization's quota as Unlimited and still set member quotas.

6. To assign per-tier storage quota:
1. Enable Use Per Storage Tier Quotas.
2. In the Storage Tiers tab that appears next to the Resources tab, enter quota limits for storage tiers as required.

   You can exclude certain tiers from storage quota calculations (for example, if you use one tier for swap space).

7. To control how VM power state and disk format affect quota usage, click Advanced Configuration.
1. To exclude powered-off VMs from CPU and memory quota calculations, enable the option For stopped VMs, include only storage quota and exclude CPU and memory quota.
2. By default, if this option is enabled, members can't power on VMs when doing so would cause quota to be exceeded. To change this behavior, enable the option Allow organization members to power on VMs when quota is exceeded. In this case, members are warned that quota will be exceeded, but they can proceed with powering on the VM.
3. By default, quota usage for thin disks is calculated as actual (used) storage, rather than total provisioned size. To change this setting, enable Use total provisioned disk size for thin disks. Note that this setting affects both overall and per-tier storage quota.
8. On the Member Quotas page, optionally set quotas for organization members.

The default value of Max Quota indicates that all resources are available to any member until the maximum quota for the organization is reached.

You can't assign member quota to a directory services group. Member quotas can only be assigned to individual users (either local or directory services users).

1. Select one or more members and click Edit User Quota, then enter values for CPUs, Memory, and Storage as required.

   If you're editing quota for a single user, you can hover over the question mark  or warning icon  to view the member's current usage (based on all services currently assigned to the member).

2. Click Balance CPU, Balance Memory, or Balance Storage to balance the available quota among all organization members. Balancing the storage affects both overall and per-tier storage quota.

   When new members are added to the organization, they automatically have Max Quota. If you balanced the quota prior to adding more members, you must balance the quota again. Likewise, you must re-balance the quota if you remove members.

3. To remove a limit and specify that a user has Max Quota, clear the value and click OK.
4. If you enabled Use Per Storage Tier Quotas on the Organization Quotas page, in the Storage Tiers tab , enter quota limits for storage tiers as required.

   You can set an overall storage limit for a user, storage tier limits, or both. As with organizational quota, you can set per-tier storage quota limits for a member even if you don't set an overall storage quota for that member on the Resources tab.

5. Click OK.
9. Configure quota settings for other destinations as required.
10. Click Finish.

    Quota details are displayed when you select the organization on the Organizations tab.

Set cost quota for destinations

1. Click the Organizations tab.
2. On the Organizations page, select the organization and click Edit to open the Configure Organization dialog.
3. Click Next until you get to the Quotas page.
4. On the Quotas page, select Cost Quota, and select the currency to be used for cost quotas.
5. Enter a maximum daily cost limit.

   Once you have entered a value, the current daily cost for this organization's services in the location targeted by this deployment destination is displayed to guide you in setting limits.

   If the organization is over quota, warning messages are displayed. Admin Portal users will see quota warnings in the currency that was selected when the organization was configured. Service Portal users will see quota warnings in their preferred currency.

   You can leave the organization's quota as Unlimited and still set member quotas on the next page of the wizard.

6. By default, members can't power on VMs when doing so would cause quota to be exceeded. To change this behavior:
1. Click Advanced Configuration.
2. Enable the option Allow organization members to power on VMs when quota is exceeded. In this case, members are warned that quota will be exceeded, but they can proceed with powering on the VM.
3. Click OK.
7. On the Member Quotas page, optionally set quotas for organization members.

The default value of Max Quota indicates that all resources are available to any member until the maximum quota for the organization is reached.

You can't assign member quota to a directory services group. Member quotas can only be assigned to individual users (either local or directory services users).

1. Select a member and click Edit User Quota, then enter a maximum daily cost. Current daily cost is displayed (based on all services currently assigned to the organization).
2. Click Balance Cost to balance the available quota among all organization members.

When new members are added to the organization, they automatically have Max Quota. If you balanced the quota prior to adding more members, you must balance the quota again. Likewise, you must rebalance the quota if you remove members.

3. To remove a limit and specify that the user has Max Quota, clear the value and click OK.
8. Configure quota settings for other destinations as required.
9. Click Finish.

   Quota details are displayed when you select the organization on the Organizations tab.