Resource order controls for template-based cloud catalog items

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Resource Order Controls for Template-Based Cloud Catalog Items

    Resource order controls enable quota checks for template-based catalog items, allowing you to manage resource provisioning effectively. With these controls, you can set limits for users and groups, triggering notifications or approval workflows when quota limits are exceeded. This feature is available starting with the Washington DC release.

    Show full answer Show less

    Key Features

    • Calculate quota and capacity for template-based catalog items.
    • Set limits for stack quota during provisioning for cloud users.
    • Create policies that trigger actions when quota limits are exceeded.
    • Show user and user group quotas in the Cloud User portal.

    How Resource Order Controls Work

    Resource order controls only apply when a quota is exceeded. The first time a user exceeds their quota, provisioning continues, but subsequent attempts to exceed the limit will trigger the Resource Order Control policy. If no quota is mapped to a catalog, quota calculations will not be performed.

    The stack count quota counts active stacks provisioned by users and does not require mapping to quota definitions. Default quota limits must be specified to enable this feature.

    Resource Order Control Policy

    The default Resource Order Control policy is in Draft state and can be customized or published. The 'on Resource Limits exceeded' policy action determines whether to initiate an approval workflow, a notification, or both when limits are exceeded.

    Note: Users cannot provision catalog items if their quota is exceeded without the policy being published, as existing behavior prevents further provisioning.

    Next Steps

    • Set up resource order controls.
    • Create quota definitions and policies mapped to cloud-template based catalog items.
    • Use policy rules and actions to trigger notifications or approval workflows when quotas are exceeded.

    Use resource order controls to perform quota checks for template-based catalog items using quota definitions and policies. Quota limits enable you to control provisioning or ordering resources for users and groups. Configure policy actions to trigger notifications, an approval workflow, or both.

    Resource Order Controls

    Resource order controls enable you to control the quota limit of resources provisioned through template-based catalogs. Quota checks for cloud template-based catalog items are available beginning with the Washington DC release.

    You can now map quota limits to template-based catalogs and trigger notifications or an approval workflow when the resource limit or quota definitions you specify for a user or user group is exceeded. For more information, see Resource Quota.

    Use resource controls to perform the following actions:
    • Calculate quota and capacity for template-based catalog items.
    • Set limits for stack quota during provisioning for the cloud user.
    • Create a policy to be triggered when a quota limit is exceeded.
    • Add a policy notification and request for approval when a quota limit is exceeded.
    • Show user and user group quotas for template-based catalogs in the Cloud User portal.

    How resource order controls work

    Resource order control applies only when the quota has exceeded. If the quota exceeds during catalog provisioning for the first time after resource order controls are configured, the cloud resources continue to be provisioned. However, if the cloud user tries to provision a resource that breaches the configured quota limits again, the Resource order limit exceeded policy action set up for the Resource Order Control policy is triggered.
    Note:
    If quota is not mapped to a template-based catalog, quota calculations for that catalog are not performed, even if users exceed their quota limits.

    For example, say you specify a quota limit of 20 GB for a storage volume for a cloud user and the user provisions a 40 GB storage volume. The first time, the storage volume is provisioned even though it exceeds the quota limit. However, provisioning will fail the next time the user attempts to provision a cloud resource over 20 GB.

    Stack count quota

    The stack count quota introduces a default base system quota for template-based cloud catalog items. The Stack count quota counts all active stacks (identified by the Stack CI class) provisioned by users and user groups. The stack count quota applies to all template-based cloud resources and you do not need to map catalog items to quota definitions. Once the stack quota is enabled, whenever a user from the group mapped to the stack quota provisions a cloud resource, the quota is calculated. When users from the mapped group try to provision resources beyond the limit defined in the quota definition for stacks, the Resource Order Control policy and on Resource Limit exceeded policy action is triggered.
    Note:
    The base system stack count quota does not have predefined default quotas to preserve stacks that might have been created prior to upgrading to Washington DC. You must specify default quota limits for users and user groups to enable the Stack count quota.

    Resource Order Control Policy

    The Resource Order Control policy is a base system policy that is in the Draft state by default. You can customize the default policy to meet your requirements and publish it, or create a new policy and define quotas, rules and actions to enable resource order controls. The 'on Resource Limits exceeded' policy action triggers the Resource Order Control policy when any resource exceeds the defined quota limit. You can determine whether to initiate an approval workflow, a notification, or a combination of both when the resource limit exceeded policy is triggered. For more information, see Create an action for an 'on Resource Limit exceeded' policy.
    Note:
    You cannot provision catalog items once the user or user group quota is exceeded without the policy being published because the existing quota behavior disables further provisioning and does not process the request further.

    Next Steps