HP-UX Workload Manager User's Guide

Integration with other products
Integrating with nPartitions (nPars)
Appendix D 407
Integrating with nPartitions (nPars)
You can run WLM within and across nPartitions. For systems with
partitions using Instant Capacity cores, WLM provides a global arbiter,
wlmpard, that can take input from the WLM instances on the individual
partitions. The global arbiter then “moves” cores across partitions, if
needed, to better achieve the SLOs specified in the WLM configuration
files that are active in the partitions. (This movement is achieved by
deactivating a core in one nPar, then activating a core in another nPar.
The way WLM manages cores depends on the software enabled on the
complex (such as Instant Capacity, Pay per use, and Virtual Partitions.)
For more information, see wlmpard(1M) and wlmparconf(4). (Instant
Capacity was formerly known as iCOD.)
For more information on configuring this integration, including the
nesting of virtual partitions within nPartitions, see Chapter 7,
“Managing SLOs across partitions,” on page 255.
Integrating with virtual partitions
You can run WLM within and across virtual partitions. For systems with
partitions, WLM provides a global arbiter, wlmpard, that can take input
from the WLM instances on the individual partitions. The global arbiter
then moves cores between partitions, if needed, to better achieve the
SLOs specified in the WLM configuration files that are active in the
partitions.
For more information on configuring this integration, including the
nesting of virtual partitions within nPartitions, see Chapter 7,
“Managing SLOs across partitions,” on page 255.