HP-UX Workload Manager User's Guide

Configuring WLM
Defining the PRM components (optional)
Chapter 5 149
Defining the PRM components (optional)
Use a prm structure to define Process Resource Manager, or PRM,
components—excluding the CPU allocations. The CPU allocations are
controlled by WLM, as determined by the entries in the slo structures.
NOTE If you plan on managing only virtual partitions or nPartitions—with no
FSS groups or PSETs inside them, you need not specify a prm structure.
You can go immediately to the section, “Defining SLOs” on page 186.
Likewise, if you plan to run WLM on an HP Integrity Virtual Machines
Host, you can go immediately to the section just indicated. To run WLM
on an Integrity VM Host, WLM must use a strictly host-based
configuration (a configuration for moving cores across nPartitions or
activating Instant Capacity or Pay per use cores). WLM runs inside an
Integrity VM (guest) but will not support Pay per use, vPar, and Instant
Capacity integration. However, an Integrity VM will take advantage of
cores added to the VM host by Pay per use (PPU), Instant Capacity
(iCAP), and Temporary Instant Capacity (TiCAP).
WLM replaces any existing PRM configuration on the system with the
PRM items specified in the prm structure. For example, if a system was
using PRM before starting the WLM daemon, any PRM groups,
application records, user records, and Unix group records defined in
PRM must be defined in this structure as well, or they will not be in force
when WLM takes control of the system.
Defining a prm structure consists of the following tasks:
• Specifying workload groups (optional)
• Assigning users and user access to workload groups (optional)
• Assigning Unix groups to workload groups (optional)
• Assigning applications to workload groups (optional)
• Assigning secure compartments to workload groups (optional)
• Specifying process maps to define your own criteria for workload
separation (optional)
• Specifying disk bandwidth shares (optional)