Using HP Integrity Essentials Global Workload Manager 3.0.1 with Global Instant Capacity 8.02.01

Introduction

HP Integrity Essentials Global Workload Manager (gWLM) automatically allocates resources among

multiple workloads (based on policies you define) to increase server utilization while meeting service

levels for high-priority applications. gWLM is a component of the Virtual Server Environment (VSE).

Another HP offering, HP Instant Capacity (iCAP) enables you to purchase processor cores at a

fraction of their regular price. These cores are installed in your server; they are inactive but ready for

use. Then, when your needs change and the reserve capacity is needed, you have two options:

• Purchase permanent activation on a per-core basis for the remainder of the regular price

• Temporarily activate CPU resources through previously purchased Temporary Instant Capacity

(TiCAP)

For additional information on these options, see the HP Instant Capacity User’s Guide.

HP Global Workload Manager makes use of iCAP software to manage CPU resources across

nPartitions within an HP cell-based system. Using the iCAP software to satisfy usage right restrictions

and/or to use Temporary Instant Capacity, gWLM controls in which nPartitions CPU resources are

activated (based on where it detects an increased or higher priority need) and de-activated (based on

lower priority or need).

HP Instant Capacity software also provides a feature called Global Instant Capacity (GiCAP) through

which bookkeeping of usage rights for Instant Capacity components is maintained jointly over multiple

cell-based complexes through an entity known as a GiCAP group. (For more information, see the HP

Instant Capacity User’s Guide.) With this feature, your ability to share iCAP usage rights among the

partitions of a single complex is effectively extended to partitions of multiple complexes that are

members of the same GiCAP group.

gWLM performs resource management within a shared resource domain (SRD). Each SRD identifies a

set of operating system instances among which the resources can be shared. gWLM 3.0.1

management is currently restricted to SRDs created from operating system instances executing on the

nPartitions (hard partitions) or soft partitions of a single complex. As a result, gWLM is unaware of the

association between partitions of multiple complexes provided by GiCAP groups. However, you can

use gWLM 3.0.1 to manage individual complexes, even when some of those complexes are members

of a GiCAP group.

This white paper describes the considerations that apply when combining gWLM and GiCAP. These

considerations apply only when the following two conditions are met:

• A complex is a member of a GiCAP group

• Some or all of the complex's partitions are part of a gWLM SRD that is configured to use iCAP

gWLM / GiCAP Versions Used in this Paper

This white paper applies specifically to gWLM 3.0.1 and its interoperation with the GiCAP feature of

iCAP 8.02.01 and newer. HP does not recommend or support using gWLM with the GiCAP feature

of iCAP versions previous to 8.02.01.

Configuration of gWLM and GiCAP

You configure gWLM to manage partitions of a complex in the same manner as always, regardless of

whether the complex is included in a GiCAP group. In fact, gWLM provides no indication that a

complex is a member of a GiCAP group.

In addition, gWLM calculates a recommended resource allocation interval that does not consider

whether the nPartitions included in the SRD are members of a GiCAP group. However, as discussed