HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide

where hostname represents the hostname of the CMS.

3. From the System Insight Manager menu bar, select:

Tools→HP Matrix OE visualization...

and then click the Shared Resource Domain tab.

4. Select the shared resource domain containing the workload for which you want to change

the policy.

5. Select the workload for which you want to change the policy.

6. From the HP Matrix OE visualization menu bar, select:

Policy→Change Associated gWLM Policy...

7. From the Policy dropdown in the table row for the workload, select the new policy to associate,

or apply, to the workload.

8. Click OK.

Adding a new compartment or GiCAP group member to an SRD

If you:

• Have added an npar, a vpar, a VSP, or a virtual machine to your system and want to add it

to an SRD,

• Have added a Global Instant Capacity (GiCAP) group member and want to add it to an SRD,

• Want to create psets or fss groups in a host already in an SRD

You can use the gWLM wizard to accomplish those tasks. To start the wizard, select from the

System Insight Manager menu bar:

Tools→HP Matrix OE visualization...

and then click the Shared Resource Domain tab. From the HP Matrix OE visualization menu bar,

select:

Create→Shared Resource Domain

Step 1 in the wizard allows you to add nPars, vPars, VSPs, and GiCAP group members. Step 3

allows you to create psets or fss groups, as well as manage existing virtual machines.

NOTE: When you are managing nodes in a GiCAP group, if all partitions of a GiCAP group

are not added to an SRD, a warning message is logged. To view the warning message in the GUI,

on the CMS click Optimize→Global Workload Manager (gWLM)→Events and select the check box

for Warning Message Logged. You can select the required severity level.

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:

24 Configuring gWLM to manage workloads