HP Global Workload Manager 7.0 User Guide

Stop managing a workload
When you stop managing a workload:
gWLM stops managing resources for the workload
The workload’s definition is removed from the SRD, although it remains available for placing
in another SRD
NOTE: When gWLM stops managing npar-based or vpar-based workloads, it leaves the nPars
or vPars with the number of cores they had in the last allocation interval. For this reason, in Step
3 below, you associate fixed policies with the workloads based on these types of compartments.
You must stop a virtual machine before you stop managing it with gWLM. When gWLM stops
managing a virtual machine, it sets the entitlement of the running virtual machine to its minimum.
For psets and fss groups, gWLM removes the pset or fss group and moves the processes from that
compartment to the default compartment.
To stop managing workloads in an SRD:
1. Ensure in System Insight Manager, the gWLM CMS daemon or service (gwlmcmsd), and all
the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up
gWLM (initial setup steps)” (page 18).
2. Connect to System Insight Manager by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
3. Associate fixed policies with all workloads that you want to unmanage that are based on
nPars or vPars.
For information on setting the associated policy, refer to “Changing which policy is associated
with a workload” (page 21).
4. Wait an allocation interval for gWLM to set CPU resource allocations based on the fixed
policies.
5. Click the Shared Resource Domain tab.
6. Select the workload you want to stop managing in the workload table.
7. From the HP Matrix OE visualization menu bar, select:
PolicyRemove Associated gWLM Policy...
8. Associate policies.
Evaluate and change, if needed, the remaining workloads and their associated policies to
ensure they are appropriate, given that a workload has been removed.
9. Click OK.
Stop managing an SRD
To stop gWLM from managing an SRD and its workloads, returning resource allocation to HP-UX:
NOTE: In System Insight Manager, you must be logged in as root or have authorizations for
All Tools or “Matrix OE All tools.
1. Ensure in System Insight Manager, the gWLM CMS daemon or service (gwlmcmsd), and all
the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up
gWLM (initial setup steps)” (page 18).
2. Connect to System Insight Manager by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
22 Configuring gWLM to manage workloads