HP UX 11i Workload Management (gWLM/WLM) Software manual Configuring gWLM to manage workloads

Page 14

2 Configuring gWLM to manage workloads

This chapter describes the various aspects of configuring gWLM to effectively manage the resources for your workloads.

Policy types

You can define several types of policies to instruct gWLM how to manage the resources for your workloads. These types are:

Fixed

Allocates a fixed (constant) amount of CPU resources to a workload’s

 

compartment.

 

gWLM satisfies these policies before attempting to satisfy any other type of

 

policies.

Utilization

Attempts to keep a workload’s CPU utilization close to a target percentage by

 

requesting more CPU resources when the workload is using too much of its

 

current CPU resource allocation or by requesting fewer resources when the

 

workload is using too little of its allocation. For example, assume a workload

 

has a utilization policy with a target of 80% and an allocation of 5 cores. If

 

the workload is consuming 4.5 cores, its utilization percentage is 4.5/5, or

 

90%. gWLM would attempt to allocate additional CPU resources to the

 

workload’s compartment to meet the target. An allocation of 6 cores would

 

result in a utilization percentage of 4.5/6, or 75%, meeting the target.

 

With a utilization policy, you specify the minimum and maximum CPU resource

 

requests. Workloads with this type of policy are always allocated at least the

 

minimum request. Utilization policies allow you to prioritize workloads.

OwnBorrow

Allows you to set the following values:

 

• Amount of CPU resources, in cores, a workload’s compartment owns.

 

• Minimum amount of CPU resources, in cores, a workload’s compartment

 

must have (after lending resources to other workloads).

 

• Maximum amount of CPU resources, in cores, a workload’s compartment

 

can have (after borrowing resources from other workloads).

 

The compartment of a workload with an OwnBorrow policy is allocated the

 

owned CPU resources when needed. The minimum and maximum sizes allow

 

you to specify how much the workload can lend (when resources are not needed)

 

or borrow (when additional resources are needed and available). If a

 

compartment has lent out cores and that compartment’s workload becomes

 

busy, the compartment re-acquires those lent-out cores.

Custom

Available for advanced users. For information on custom policies, refer to the

 

online help or gwlmxml(4).

Conditional

Specifies the existing policy to use when a time-based condition, a file-based

 

condition, or a Serviceguard condition is met.

14 Configuring gWLM to manage workloads

Page 13 Page 15
Image 14
Page 13 Page 15
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Additional configuration and administration tasks Support and other resourcesIndex Overview Benefits of using gWLMComparison of PRM, WLM, and gWLM features GWLM OverviewConcepts and terms for using gWLM Scheduler fss group. gWLM manages a workload byWould make for a workload-without actually affecting GWLM management model SRDHow gWLM allocates CPU resources Available interfaces AssumptionsWhere to find additional information Finding more gWLM informationLearn about other gWLM commands Configuring gWLM to manage workloads Policy typesPolicy types Choosing a policy type Choosing a policy typeGetting started with gWLM Using the wizardSeeing how gWLM will perform without affecting the system Combining the different policy typesSeeing gWLM in action # /opt/gwlm/bin/gwlmagent# perl -e ’print $$\nwhile 1 ’ & 1 Common uses for gWLM Fixing the amount of CPU resources a workload getsCommon configuration tasks Setting up gWLM initial setup stepsChanging from advisory mode to managed mode Creating a new policyEditing a policy Changing which policy is associated with a workloadAdding a new compartment or GiCAP group member to an SRD Stop managing a workloadStop managing an SRD Quick Link Option Monitoring workloads Viewing gWLM reports in monitor-Only modeMonitoring workloads and gWLM High-Level viewMonitoring gWLM from the command line Message logsHP-UX /var/opt/gwlm/gwlmcommand.log.0 Viewing HP Systems Insight Manager events Monitoring gWLM with GlancePlusSecuring gWLM communications SecurityGeneral security topics Securing database communicationsSecurity Additional configuration and administration tasks Manually adjusting CPU resourcesManually adjusting memory resources Setting aside space for historical dataCreating a database maintenance plan Setting cache size for historical configuration dataSetting database recovery model Tips for backup and restoreSetting gWLM properties CMS propertiesSetting gWLM properties Agent properties # Severe # Warning # Info # Config # Fine # Finer # Finest Controlling gWLM’s startup behavior Communications ports# /opt/gwlm/bin/gwlmagent --enablestartonboot How the automatic restart works Related eventsManually clearing an SRD Node Failed to Rejoin SRD on Start-up event# gwlm undeploy --srd=SRD--force Nesting partitions Nested partitionsChanging the gWLM resource allocation interval Using gWLM with Hyper-ThreadingChanging the interval on the command line Changing the interval in HP System Insight ManagerUsing gWLM with hosts on multiple LANs Shows a possible scenarioCreating Golden Images Multiple network interface cardsIncorrectly configured host name or IP address Get the IP address configured for the host using nslookupUnable to create new native thread Enabling or disabling dumping core for gWLMCore dump file is available in root directory Support and other resources How to contact HPSubscription service Information to collect before contacting HPTypographic conventions HP authorized resellersRelated information User input Documentation feedback Compatibility with agents Global Workload Manager known issues LimitationsUnable to build a single shared resource domain Compatibility with PRM and WLMHost name aliases are not supported Making a configuration change to a large SRD is slowRare incompatibility with virtual partitions Deleting workloads takes a long time Integrity VM prevents discovery of psets and fss groupsCustom metrics lost on redeploy Information error during shutdownProcess placement using psrset is ignored Major issues Documentation or minor issues Remove old configuration data from the gWLM databaseCell-local processors and iCAP environment CMS is slow to respondModifying Java while gWLM is running Error during discovery of compartmentsCombining psets and virtual partitions Only one SRD is allowed to be deployed Missing or unexpected historical data system clocks differSample missing at start or end of gwlmreport output Application hangs in fss group Processes moved to default pset or default fss groupSRD deployment times out and displays a blank screen Scripts not placed in correct workloadsUnable to remove workload from nested partitions SRD Configuration of agent and CMS not synchronizedChanges in sizes in Discovery Missing historical data gWLM CMS daemon/service restarted Negative current size for NonvmUnmanaging a VM or vPar that is on leaves SRD undeployed Index SRDIndex

UX 11i Workload Management (gWLM/WLM) Software specifications

HP-UX 11i Workload Management (gWLM/WLM) software is an integral component of HP's premier UNIX operating system, designed to enhance system performance and resource management across diverse workloads. This advanced tool allows system administrators to monitor, control, and allocate resources effectively to achieve optimal performance, reliability, and service levels in enterprise environments.

One of the main features of gWLM/WLM is its ability to classify workloads and manage them according to specific policies set by the administrator. By using service level objectives (SLOs), administrators can define the performance criteria for various applications and workloads. gWLM continuously tracks these workloads, ensuring that they adhere to the defined SLOs, thus maintaining a high level of application performance.

The software employs resource pools, which segment resources such as CPU, memory, and I/O bandwidth among different workloads based on predefined priorities. This capability ensures that critical applications receive the resources they require, even during peak usage periods, thereby preventing resource starvation that could lead to system slowdowns or crashes.

Another significant characteristic of gWLM/WLM is its real-time monitoring and reporting capabilities. The software provides detailed insights into resource utilization, workload performance, and system health. Administrators can access this information through a user-friendly interface, allowing for informed decision-making and proactive management.

Integration with HP Serviceguard adds another layer of functionality, enabling high availability for critical applications. gWLM can orchestrate workload migration to ensure that service levels are maintained, even in the event of hardware failures or resource contention.

The technology behind gWLM/WLM is built on advanced algorithms that leverage historical data and predictive modeling to optimize resource allocation dynamically. This means that as workloads change, the system can automatically adjust resource distribution to meet performance targets without the need for constant manual intervention.

gWLM also supports integration with various enterprise management tools, enabling administrators to implement comprehensive monitoring and management strategies across the IT infrastructure. The scalability of gWLM allows organizations of all sizes to benefit from its robust workload management features, ensuring that they can adapt to changing demands in their operational environments.

In summary, HP-UX 11i Workload Management software offers a sophisticated solution for optimizing resource utilization, managing workloads effectively, and maintaining high performance in complex enterprise environments. Its comprehensive features and technologies make it an essential tool for any organization seeking to enhance their IT operations.
Top Page Image Contents