HP-UX Workload Manager User's Guide

Management of nested nPars / vPars / workload groups
Setting up the various configurations
Chapter 8278
Figure 8-1 Nested partitions to be managed (with Instant Capacity)
Assume you want to share cores, as indicated by the arrows in the figure,
among the:
• Virtual partitions within nPar1
• Virtual partitions within nPar2
• FSS and PSET-based workload groups within nPar3
• Three nPartitions
Instant Capacity (iCAP, formerly known as iCOD) is available on the
complex so WLM can migrate your rights to use the product across the
nPartitions to simulate CPU (core) movement. With Instant Capacity
present, you must have only one wlmpard managing the partitions. In
particular:
Step 1. Set up a wlmpard configuration on some system, say mysystem.
mysystem can be in the complex or on another system on your network.
In this file, say myfile, specify the utilitypri keyword to indicate the
range of SLO priorities that can cause WLM to activate Temporary
Instant Capacity (TiCAP) resources.
If you are not using Temporary Instant Capacity resources, you can omit
the utilitypri keyword.
vpar0
vpar1
vpar2
vpar0
vpar1
vpar2
FSS1
FSS2
PSET
nPar1 nPar2 nPar3