HP UX 11i Workload Management (gWLM/WLM) Software manual Common configuration tasks

Page 21

Resizing a workload’s npar, vpar, VSP, virtual machine, pset, or fss group as needed

To ensure a workload gets the CPU resources it needs—while also allowing resource sharing when possible—gWLM provides OwnBorrow policies.

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 resources—when it needs it. However, you can configure the workload to:

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 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 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

Image 21
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Support and other resources Additional configuration and administration tasksIndex Comparison of PRM, WLM, and gWLM features Benefits of using gWLMOverview GWLM OverviewScheduler fss group. gWLM manages a workload by Concepts and terms for using gWLMWould make for a workload-without actually affecting SRD GWLM management modelHow gWLM allocates CPU resources Assumptions Available interfacesFinding more gWLM information Where to find additional informationLearn about other gWLM commands Policy types Configuring gWLM to manage workloadsPolicy types Choosing a policy type Choosing a policy typeSeeing how gWLM will perform without affecting the system Using the wizardGetting started with gWLM Combining the different policy types # /opt/gwlm/bin/gwlmagent Seeing gWLM in action# perl -e ’print $$\nwhile 1 ’ & 1 Fixing the amount of CPU resources a workload gets Common uses for gWLMSetting up gWLM initial setup steps Common configuration tasksCreating a new policy Changing from advisory mode to managed modeChanging which policy is associated with a workload Editing a policyStop managing a workload Adding a new compartment or GiCAP group member to an SRDStop managing an SRD Quick Link Option Monitoring workloads and gWLM Viewing gWLM reports in monitor-Only modeMonitoring workloads High-Level viewMessage logs Monitoring gWLM from the command lineHP-UX /var/opt/gwlm/gwlmcommand.log.0 Monitoring gWLM with GlancePlus Viewing HP Systems Insight Manager eventsGeneral security topics SecuritySecuring gWLM communications Securing database communicationsSecurity Manually adjusting CPU resources Additional configuration and administration tasksSetting aside space for historical data Manually adjusting memory resourcesSetting database recovery model Setting cache size for historical configuration dataCreating a database maintenance plan Tips for backup and restoreCMS properties Setting gWLM propertiesSetting gWLM properties Agent properties # Severe # Warning # Info # Config # Fine # Finer # Finest Communications ports Controlling gWLM’s startup behavior# /opt/gwlm/bin/gwlmagent --enablestartonboot Related events How the automatic restart worksNode Failed to Rejoin SRD on Start-up event Manually clearing an SRD# gwlm undeploy --srd=SRD--force Nested partitions Nesting partitionsChanging the interval on the command line Using gWLM with Hyper-ThreadingChanging the gWLM resource allocation interval Changing the interval in HP System Insight ManagerShows a possible scenario Using gWLM with hosts on multiple LANsMultiple network interface cards Creating Golden ImagesGet the IP address configured for the host using nslookup Incorrectly configured host name or IP addressEnabling or disabling dumping core for gWLM Unable to create new native threadCore dump file is available in root directory Subscription service How to contact HPSupport and other resources Information to collect before contacting HPHP authorized resellers Related informationTypographic conventions User input Documentation feedback Compatibility with agents Limitations Global Workload Manager known issuesCompatibility with PRM and WLM Unable to build a single shared resource domainMaking a configuration change to a large SRD is slow Rare incompatibility with virtual partitionsHost name aliases are not supported Integrity VM prevents discovery of psets and fss groups Deleting workloads takes a long timeInformation error during shutdown Process placement using psrset is ignoredCustom metrics lost on redeploy Major issues Remove old configuration data from the gWLM database Documentation or minor issuesCMS is slow to respond Cell-local processors and iCAP environmentError during discovery of compartments Combining psets and virtual partitionsModifying Java while gWLM is running Missing or unexpected historical data system clocks differ Sample missing at start or end of gwlmreport outputOnly one SRD is allowed to be deployed SRD deployment times out and displays a blank screen Processes moved to default pset or default fss groupApplication hangs in fss group Scripts not placed in correct workloadsConfiguration of agent and CMS not synchronized Changes in sizes in DiscoveryUnable to remove workload from nested partitions SRD Negative current size for Nonvm Missing historical data gWLM CMS daemon/service restartedUnmanaging a VM or vPar that is on leaves SRD undeployed SRD IndexIndex