Common Configuration Tasks

This section discusses various configuration tasks:

Setting up gWLM (Initial Setup Steps)

Several of the configuration tasks require the same initial set-up steps. (Each task requiring these steps indicates that the steps are needed.) These steps are given below.




	NOTE: You must be logged in as root on the systems where you run the `mxstart`, `gwlmcmsd`, and `gwlmagent` commands mentioned below.

Configure your CMS as indicated in the VSE Management Software Installation and Update Guide if you have not already done so
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 SIM, as discussed in the VSE Management Software Installation and Update Guide.

Changing from Advisory Mode to Managed Mode

Advisory mode allows you to see what CPU resource requests gWLM would make for a workload—without actually affecting resource allocation. (Advisory mode is not available for SRDs containing virtual machines, psets, or fss groups.) Managed mode, however, allows gWLM to automatically adjust the resource allocations for your defined workloads.

To change from one mode to the other:




	NOTE: In SIM, you must be logged in as root or have authorizations for “All Tools,” “VSE All Tools,” or “gWLM All Tools.”If you are changing from managed mode to advisory mode and you do not plan to change back soon, be aware that gWLM leaves the npar and vpar and pset compartments with the number of cores they had in the last allocation interval. Set the compartments to your desired sizes before changing to advisory mode by associating fixed policies with all the compartments and waiting for an allocation interval to pass.

Ensure SIM, the gWLM CMS daemon (gwlmcmsd) and all the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up gWLM (Initial Setup Steps)”
Connect to SIM by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
Select from the SIM menu bar:
ToolsVSE Management
and then click the Shared Resource Domain tab
Select the SRD for which to change the mode
Select from the VSE Management menu bar:
ModifyShared Resource Domain
Change to the desired mode
Select the [OK] button

Creating a New Policy

A policy instructs gWLM how to manage a workload’s resources. You can create a policy when managing a workload or create a policy separately. To create a policy separately:




	NOTE: In SIM, you must be logged in as root or have authorizations for “All Tools,” “VSE All Tools,” or “gWLM All Tools.”

Ensure SIM, the gWLM CMS daemon (gwlmcmsd) and all the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up gWLM (Initial Setup Steps)”
Connect to SIM by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
Select from the SIM menu bar:
ToolsVSE Management
and then click the Shared Resource Domain tab
Select from the VSE Management menu bar
PolicyCreate gWLM Policy...
Edit the settings, selecting a policy type and specifying the required values and optional values as desired
Select the [OK] button

Editing a Policy

A policy instructs gWLM how to manage a workload’s resources.




	NOTE: You can edit the policies provided with gWLM; however, there is currently no way to restore these policies to their original definitions.

To edit a policy:




	NOTE: In SIM, you must be logged in as root or have authorizations for “All Tools,” “VSE All Tools,” or “gWLM All Tools.”

Ensure SIM, the gWLM CMS daemon (gwlmcmsd) and all the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up gWLM (Initial Setup Steps)”
Connect to SIM by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
Select from the SIM menu bar:
ToolsVSE Management
Select from the VSE Management menu bar:
PolicyEdit gWLM Policies...
Select the policy to edit
Select the [Edit] button
Edit the settings
Select the [OK] button
NOTE: All workloads associated with this policy will automatically use the updated policy.

Changing Which Policy is Associated with a Workload

To change the policy affecting how gWLM allocates resources to a workload:




	NOTE: In SIM, you must be logged in as root or have authorizations for “All Tools,” “VSE All Tools,” or “gWLM All Tools.”

Ensure SIM, the gWLM CMS daemon (gwlmcmsd) and all the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up gWLM (Initial Setup Steps)”
Connect to SIM by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
Select from the SIM menu bar:
ToolsVSE Management
and then click the Shared Resource Domain tab
Select the shared resource domain containing the workload for which you want to change the policy
Select the workload for which you want to change the policy
Select from the VSE Management menu bar:
PolicyChange Associated gWLM Policy...
Select the new policy to associate, or apply, to the workload from the options menu in the table row for the workload
Select the [OK] button

Adding a New Npar, Vpar, Virtual Machine, Pset, or FSS Group to an SRD

If you:

Have added an npar, a vpar, or a virtual machine to your system and want to add it to an SRD, or
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 SIM menu bar:

ToolsVSE Management

and then click the Shared Resource Domain tab and then from the VSE Management menu bar:

CreateShared Resource Domain

Step 1 in the wizard allows you to add npars and vpars. Step 3 allows you to create psets or fss groups, as well as manage existing virtual machines.

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:

Ensure SIM, the gWLM CMS daemon (gwlmcmsd) and all the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up gWLM (Initial Setup Steps)”
Connect to SIM by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
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”
Wait an allocation interval for gWLM to set CPU resource allocations based on the fixed policies.
Select the Shared Resource Domain tab
Select the workload you want to stop managing in the workload table
Select from the VSE Management menu bar:
PolicyRemove Associated gWLM Policy...
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
Select the [OK] button

Stop Managing an SRD

To stop gWLM from managing an SRD and its workloads, returning resource allocation to HP-UX:




	NOTE: In SIM, you must be logged in as root or have authorizations for “All Tools,” “VSE All Tools,” or “gWLM All Tools.”

Ensure SIM, the gWLM CMS daemon (gwlmcmsd) and all the gWLM agents (gwlmagent) are still running, as explained in the section “Setting up gWLM (Initial Setup Steps)”
Connect to SIM by pointing your web browser to:
http://hostname:280
where hostname represents the hostname of the CMS.
Associate fixed policies with all npars or vpars that were in the SRD
When gWLM stops managing an SRD, it leaves compartments based on npars or vpars as they were in the last allocation interval. Associating fixed policies allows you to set the sizes exactly to what you want. (For virtual machines, gWLM sets the entitlements of the running virtual machines to their minimums. psets and fss groups are removed in this situation, with their processes going to the default pset or default fss group.)
For information on setting the associated policy, refer to “Changing Which Policy is Associated with a Workload”
Select the Shared Resource Domain tab
Find the Details table for the SRD you want to stop managing (undeploy)
Select the “Undeploy SRD” link in the SRD's Details table