Resizing a workload’s npar, vpar, VSP, virtual machine, pset, or fss group as needed
To ensure a workload gets the CPU resources it
With such a policy, you indicate the amount of CPU resources a workload should own. The workload is then allocated this owned amount of CPU
•Lend CPU resources to other workloads when it is idle
•Borrow CPU resources from workloads that are idle Associate an OwnBorrow policy with a workload:
•When creating an SRD, as described in “Getting started with gWLM” (page 17)
•When adding a workload to an SRD, as described in “Adding a new compartment or GiCAP group member to an SRD” (page 24)
•By changing the policy associated with an existing workload, as described in “Changing which policy is associated with a workload” (page 23)
gWLM’s utilization policies also allow resizing.
Common configuration tasks
This section discusses various configuration tasks:
•“Changing from advisory mode to managed mode” (page 22)
•“Creating a new policy” (page 22)
•“Editing a policy” (page 23)
•“Changing which policy is associated with a workload” (page 23)
•“Adding a new compartment or GiCAP group member to an SRD” (page 24)
•“Stop managing a workload” (page 24)
•“Stop managing an SRD” (page 25)
Setting up gWLM (initial setup steps)
Several of the configuration tasks require the same initial
NOTE: You must be logged in as root on the systems where you run the gwlmagent command mentioned below.
1.Configure your CMS as indicated in the HP Matrix Operating Environment Software Installation and Update Guide, if you have not already done so.
2.On each managed node, start the gWLM agent (if it is not already running):
# /opt/gwlm/bin/gwlmagent
Alternatively, you can start the agents through System Insight Manager, as discussed in the HP Matrix Operating Environment Software Installation and Update Guide.
Common configuration tasks 21