Resizing partitions automatically with HP-UX Workload Manager

d. Start the WLM daemon, wlmd, on each partition:

# /opt/wlm/bin/wlmd –a /tmp/par_usage_goal.wlm

4. Set up the WLM global arbiter in the “primary host” partition as described in “Configuring

automatic partition resizing” (on page 23).

Configuring HP-UX Workload Manager to isolate the workloads within

the partition

If you must isolate your workloads within a partition, you can place them in WLM workload groups.

These groups then share the cores allocated to the partition they are in. WLM enables you to base

workload groups on pSets or FSS groups. (pSets enable you to allocate whole cores to your workload

groups. With FSS groups, each group gets a portion of each core in the partition, which can be less

than one core or several whole cores.) Note that you cannot use WLM to isolate virtual machines into

separate workload groups.

To configure WLM to move processors among partitions while isolating the partition’s workloads:

1. Set up your partitions as you would normally:

For virtual partitions versions prior to v4.x (starting with v4.x, vPars no longer have the concept of

bound/unbound CPUs):

a. Ensure the system has enough floating (unbound) CPUs so that WLM can reassign the CPUs as

needed.

b. Ensure that each virtual partition has enough fixed CPUs to handle the I/O required for that

virtual partition.

For nPartitions, install and configure Instant Capacity software on each nPartition. WLM uses

Instant Capacity to simulate movement of cores among nPartitions. Consequently, Instant Capacity

must be installed and properly configured on each nPartition.

2. Install WLM A.03.02 on each partition (for installation instructions, see the WLM release notes

available at http://docs.hp.com/hpux/netsys/index.html#HP-UX%20Workload%20Manager).

3. Set up WLM in each partition. Use the configuration wizard to create a minimal configuration for

managing resources of the isolated workloads in the partition ():

NOTE

Usage of the WLM wizard requires Java™ Runtime Environment

version 1.4.2 or later. (Starting with WLM A.03.04, Java 1.5 or later

is required.) For PRM-based configurations, PRM C.03.00 or later is

required (to take advantage of the latest updates to WLM, use the latest

version of PRM available).

a. Set your DISPLAY environment variable.

b. Start the configuration wizard: # /opt/wlm/bin/wlmcw

c. Create a workload group for each application you want isolated.

The following steps show how to create a usage goal, which allocates CPU resources to a

workload group as it is needed. For information on creating time-based CPU allocation, see the

white paper, “Getting started with HP-UX Workload Manager,” available at:

http://www.hp.com/products1/unix/operating/docs/wlm.gettingstarted.pdf