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

12
use more than half of a core for its operations, and that VM2 and VM3 each do not use more than
60% of each core. In addition, VM3 typically does not need the resources it owns. To make this
happen, you could set up the gWLM OwnBorrow policies shown in the table in Figure 3. These
policies would ensure that VM1 (and VM2) can get more resources when needed by borrowing from
VM3 and VM4; gWLM limits the resource allocation of the latter two less-critical workloads to make
sure resources are always available for the higher-priority workloads. If VM1 and VM2 both need
more resources, VM1 is ensured resources first (it has the highest priority, 1).
Figure 3 – Integrity VM Managed by gWLM
Scenario 2: Taking Advantage of Instant Capacity Resources
This scenario shows how you can use gWLM to activate (and deactivate) any number of iCAP cores
to “migrate” usage rights to where they are needed. In this scenario, a cell-based complex consists of
two hard partitions with a total of 14 cores. Of these cores, 10 have Instant Capacity usage rights
while 4 are expected as inactive. As shown in Figure 4, the first partition (nPartition1) includes an
Integrity VM Host that runs six lightly-loaded virtual machines sharing four cores. Two additional cores
are inactive iCAP resources. Assume each virtual machine owns 25% of the resources of one core.
For sake of simplicity, the virtual machines in this scenario each have one vCPU, and they are
associated with one core only. A later figure shows an Integrity VM configuration where several
virtual machines are associated with multiple cores (symmetric multiprocessing). The second partition
(nPartition2) has two virtual partitions, each owning three cores, with two additional inactive iCAP
cores. The nPartitions are monitored by the Partition Manager.