HP Integrity Essentials Global Workload Manager: Workload Management for HP Integrity Virtual Machines

14
has deactivated one iCAP core in each vPar in nPartition2 (where there is less demand for CPU
resources) and activated the equivalent iCAP resources (two cores) in nPartition1. The result is that the
virtual machine workloads now have two additional cores to share their loads so that each virtual
machine has all the processing power of a whole core to itself. You do not incur a charge for these
extra (activated) cores. (The virtual machine workload sizes depicted in Figure 4B have changed
slightly from the sizes in Figure 4A.) The vPars in nPartition2, whose workloads continue to be light,
can easily meet their demands with one less core each. When the demands on the virtual machines
return to normal again, gWLM can automatically deactivate the extra Instant Capacity cores on
nPartition1 and shift usage rights back to nPartition2 as needed.
Figure 4B - Same Complex with Redistribution of iCAP Resources to Meet Demands
How You Enable gWLM to Use Instant Capacity: HP Instant Capacity must be installed on
each nPartition. For more information, see the latest Instant Capacity User’s Guide by going to the
following location and selecting “Network and Systems Management” and then “Utility Pricing
Solutions”:
http://docs.hp.com
For information on enabling gWLM to take advantage of Instant Capacity resources, see the “Getting
the Most Out of gWLM” topic in online help, especially the section “Setting Up npars to Maximize
Resource Sharing (npar requirements).” Set up an OwnBorrow policy for each nPartition to make
sure its number of owned CPU resources is the number you want the partition to have whenever
needed.
Scenario 3: Taking Advantage of Temporary Instant Capacity Resources
This scenario shows how you can use gWLM to activate (and deactivate) any number of TiCAP cores
to temporarily meet peak demands where needed. Assuming the original circumstances depicted in
Figure 4A (with the overloaded virtual machines in nPartition1), if you have TiCAP rights, you can
configure the SRD to support Temporary Instant Capacity. Then, when virtual machine workloads
increase and CPU utilization reaches a certain point, gWLM can activate as many TiCAP resources as
are needed until the demands on the virtual machine workloads diminish to a specified level or the
prepaid amount of temporary capacity units expires. Additional cores can be activated for nPartition2