Using Dynamic Resource Management

Starting with the Logical Domains 1.3 software, you can use policies to determine how to automatically perform DR activities. At this time, you can only create policies to govern the dynamic resource management of virtual CPUs.

---

Caution - The following issues affect CPU dynamic resource management (DRM): When PM is in elastic mode, DRM cannot be enabled. Any change from performance mode to elastic mode is delayed while DRM is enabled. Ensure that you disable CPU DRM prior to performing a domain migration operation. DRM policies do not apply to domains that are configured with the whole-core constraint.

---

A resource management policy specifies under what conditions virtual CPUs can be automatically added to and removed from a logical domain. A policy is managed by using the ldm add-policy, ldm set-policy, and ldm remove-policy commands:

ldm add-policy [enable=yes|no] [priority=value] [attack=value] [decay=value]
  [elastic-margin=value] [sample-rate=value] [tod-begin=hh:mm[:ss]]
  [tod-end=hh:mm[:ss]] [util-lower=percent] [util-upper=percent] [vcpu-min=value]
  [vcpu-max=value] name=policy-name ldom...
ldm set-policy [enable=[yes|no]] [priority=[value]] [attack=[value]] [decay=[value]]
  [elastic-margin=[value]] [sample-rate=[value]] [tod-begin=[hh:mm:ss]]
  [tod-end=[hh:mm:ss]] [util-lower=[percent]] [util-upper=[percent]] [vcpu-min=[value]]
  [vcpu-max=[value]] name=policy-name ldom...
ldm remove-policy [name=]policy-name... ldom

For information about these commands and about creating resource management policies, see the ldm(1M) man page.

A policy is in effect during the times specified by the tod-begin and tod-end properties. The policy uses the value of the priority property to determine which policy to use if more than one policy is in effect simultaneously.

The policy uses the util-high and util-low property values to specify the high and low thresholds for CPU utilization. If the utilization exceeds the value of util-high, virtual CPUs are added to the domain until the number is between the vcpu-min and vcpu-max values. If the utilization drops below the util-low value, virtual CPUs are removed from the domain until the number is between the vcpu-min and vcpu-max values. If vcpu-min is reached, no more virtual CPUs can be dynamically removed. If the vcpu-max is reached, no more virtual CPUs can be dynamically added.

Example 10-4 Adding Resource Management Policies

For example, after observing the typical utilization of your systems over several weeks, you might set up policies to optimize resource usage. The highest usage is daily from 9:00 a.m. to 6:00 p.m. Pacific, and the low usage is daily from 6:00 p.m. to 9:00 a.m. Pacific.

Based on this system utilization observation, you decide to create the following high and low policies based on overall system utilization:

• High: Daily from 9:00 a.m. to 6:00 p.m. Pacific

• Low: Daily from 6:00 p.m. to 9:00 a.m. Pacific

The following ldm add-policy command creates the high-usage policy to be used during the high utilization period on the ldom1 domain.

The following high-usage policy does the following:

• Specifies that the beginning and ending times are 9:00 a.m. and 6:00 p.m. by setting the tod-begin and tod-end properties, respectively.

• Specifies that the lower and upper limits at which to perform policy analysis are 25 percent and 75 percent by setting the util-lower and util-upper properties, respectively.

• Specifies that the minimum and maximum number of virtual CPUs is 2 and 16 by setting the vcpu-min and vcpu-max properties, respectively.

• Specifies that the maximum number of virtual CPUs to be added during any one resource control cycle is 1 by setting the attack property.

• Specifies that the maximum number of virtual CPUs to be removed during any one resource control cycle is 1 by setting the decay property.

• Specifies that the priority of this policy is 1 by setting the priority property. A priority of 1 means that this policy will be enforced even if another policy can take effect.

• Specifies that the name of the policy file is high-usage by setting the name property.

• Uses the default values for those properties that are not specified, such as enable and sample-rate. See the ldm(1M) man page.

# ldm add-policy tod-begin=09:00 tod-end=18:00 util-lower=25 util-upper=75 \ vcpu-min=2 vcpu-max=16 attack=1 decay=1 priority=1 name=high-usage ldom1

The following ldm add-policy command creates the med-usage policy to be used during the low utilization period on the ldom1 domain.

The following med-usage policy does the following:

• Specifies that the beginning and ending times are 6:00 p.m. and 9:00 a.m. by setting the tod-begin and tod-end properties, respectively.

• Specifies that the lower and upper limits at which to perform policy analysis are 10 percent and 50 percent by setting the util-lower and util-upper properties, respectively.

• Specifies that the minimum and maximum number of virtual CPUs is 2 and 16 by setting the vcpu-min and vcpu-max properties, respectively.

• Specifies that the maximum number of virtual CPUs to be added during any one resource control cycle is 1 by setting the attack property.

• Specifies that the maximum number of virtual CPUs to be removed during any one resource control cycle is 1 by setting the decay property.

• Specifies that the priority of this policy is 1 by setting the priority property. A priority of 1 means that this policy will be enforced even if another policy can take effect.

• Specifies that the name of the policy file is high-usage by setting the name property.

• Uses the default values for those properties that are not specified, such as enable and sample-rate. See the ldm(1M) man page.

# ldm add-policy tod-begin=18:00 tod-end=09:00 util-lower=10 util-upper=50 \ vcpu-min=2 vcpu-max=16 attack=1 decay=1 priority=1 name=med-usage ldom1