Modifying consumer properties

Modify your consumer properties, including user account and roles, execution user account, resources available for a consumer and its sub-consumers, and reclaim behavior.

Before you begin

You must have created at least one consumer before you can modify consumer properties.

You must either be a cluster administrator, consumer administrator, or have Consumer Modify permission for this branch to modify consumer properties.

About this task

You can modify any consumer at any level of your existing tree, but do not modify the built-in ManagementServices consumer. You may see different fields for different levels of consumers in your tree.

Procedure

  1. From the cluster management console Dashboard, select Resources > Consumers.
  2. Locate the consumer you want to modify in the tree and click it.

    A list of sub-consumers displays.

  3. Click the Consumer Properties tab.

    The Consumer Properties page displays.

  4. Modify the consumer properties. Note that the consumer name cannot be changed.
    1. Select the users and respective roles for this consumer.
    2. Specify the workload execution user account (the OS account under which workload runs).

      If you specify a Windows user account that has not already been configured, you must run egosh ego execpasswd before you can use the consumer.

    3. Specify the allowed execution user list or group list:
      • For the parent consumer, update the user list and group list with new values, or select or deselect Any user can be the OS execution user.
      • For child consumers, update the user list and group list with new values, or select or deselect Inherit the user list and group list from parent consumer.
      Note: For enhanced security and permission control, you can restrict a user from changing the allowed execution user list or group list for a consumer unless that consumer also has the privilege to edit the consumer’s parent consumer. To set this restriction, in the ego.conf file, set the EGO_RESTRICT_EXECUTION_USER_CHECK_PARENT_CONSUMER parameter to Y.
    4. Specify one or more resource groups to which this consumer should have access.

      If you do not specify at least one resource group, workload does not run for this consumer.

      Note: You can rank resource groups in order of preference, so that an application gets its planned share of resources first from the preferred resource group and then from the less preferred resource group. To enable this ranking, set the EGO_ENABLE_RG_PREFERENCE to Y in the ego.conf file. Then, set the preference level for each consumer from the cluster management console.
    5. Specify a reclaim grace period.

      The reclaim grace period is applied when a resource belonging to another consumer is now being reclaimed by its owner consumer. Setting the reclaim grace period high (compared to the average length of your workload) allows workload to finish before the resource is reclaimed. Setting the reclaim grace period to 0 kills all workload running and reclaims the resource almost immediately.

    6. (Optional) Select Rebalance when time intervals change.

      Select this option to rebalance or reset the ownership when a new time interval occurs with a change in ownership of resources. Similarly, when resources are reclaimed (or passed back to their original owners), you can evoke a rebalancing in accordance with the resource plan.

      Before EGO rebalances according to the resource plan, a consumer's grace period is honored to help ensure workload is completed before being killed.

    7. (Optional) Specify the configuration for an SNMP event to be triggered under Slot underallocation SNMP event.

      You must be a cluster administrator or consumer administrator to update this configuration. The consumer administrator can update only the consumer for which they have been assigned permission.

      To enable the Slot underallocation SNMP event, complete the following steps:
      1. Ensure that Send SNMP event when this consumer has unsatisfied demand, and the slot allocation is less than is selected.
      2. Specify the minimum number of slots to be allocated for the consumer. The minimum number of slots includes all slots that the consumer can get from all configured resource groups, such as ManagementHosts, ComputeHosts, and so on.
      3. Specify the period for which the minimum number of slots can stay under the configured minimum for the consumer.
      When the consumer has pending workload and the minimum number of slots allocated to the consumer is less than the defined setting for the specified period, an SNMP event is triggered.
  5. Click Apply.

    The Consumer Properties page updates and your changes are saved.