HP-UX Workload Manager User's Guide

Managing SLOs across partitions
Setting up your WLM global arbiter configuration file
Chapter 7 273
Specifying the priority at which to use Temporary
Instant Capacity or Pay per use resources (optional)
While wlmpard has always managed migration of cores across partitions
for WLM, it also now provides management of Temporary Instant
Capacity (TiCAP) and Pay per use (PPU) resources for WLM. This
management is available on standalone systems, as well as across a
collection of partitions. With the utilitypri keyword, wlmpard
optimizes the Temporary Instant Capacity or Pay per use resources. It
determines the amount of resources needed to meet your workloads’
SLOs, then adjusts the total active cores to meet demand. Owned cores
are always kept active.
If you have Temporary Instant Capacity (v6 or later) or Pay per use (v4,
v7, or later) resources available on a system, WLM can help you optimize
the use of those resources—using them only as needed to meet the
service-level objectives for your workloads. To use wlmpard to optimize
the use of these resources, follow the steps given previously in the section
“Setting up cross-partition management” on page 260—with one
exception: Specify the utilitypri keyword in the global arbiter
configuration file. This keyword works with Temporary Instant Capacity
v6 or later and with PPU v4, v7, and later.
NOTE The utilitypri keyword allows WLM—when Temporary Instant
Capacity is available—to adjust the total of cores to meet demand. Also,
this keyword ensures WLM maintains compliance with your Temporary
Instant Capacity usage rights. When the prepaid amount of temporary
capacity days have expired, WLM no longer attempts to activate the
temporary resources. In addition, by default WLM will not activate
Temporary Instant Capacity when 15 or fewer processing days of
temporary capacity are available; in this case, you must purchase extra
capacity. You can change this default by setting the
utility_reserve_threshold, as described in “Specifying the reserve
threshold that determines when WLM stops activating temporary
capacity resources” on page 274. Before adding the capacity, be sure to
stop wlmpard (using the -k option). For more information on Temporary
Instant Capacity, see “Integrating with Temporary Instant Capacity
(TiCAP)/ Pay per use (PPU)” on page 410. For information about how to
stop wlmpard, see Appendix A, “WLM command reference,” on page 363.
This keyword has the syntax: