HP Insight Global Workload Manager 6.2 User Guide HP Part Number: T8672-90019 Published: October 2010 Edition: 1.
© Copyright 2004, 2010 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents 1 Overview.........................................................................................................................7 gWLM Overview....................................................................................................................................7 Benefits of using gWLM.........................................................................................................................7 Comparison of PRM, WLM, and gWLM features............................
Securing gWLM communications........................................................................................................31 Securing database communications......................................................................................................31 Securing Postgres communications.................................................................................................31 Securing Oracle communications..............................................................................
Workloads in gWLM do not follow associated Serviceguard packages.........................................58 Host name aliases are not supported..............................................................................................59 Making a configuration change to a large SRD is slow...................................................................59 Events for gWLM CPU migration can affect HP SIM CMS performance.......................................59 Deleting workloads takes a long time.........
1 Overview This document presents an overview of the techniques and tools available for using HP Insight Global Workload Manager software for Integrity (or gWLM.) It exposes you to the essentials and allows you to quickly start using gWLM. This document is intended to be used by Virtual Server Environment (VSE) system administrators, VSE application administrators, and other technical professionals involved with data center operations, administration, and planning.
• • • Integration with HP-UX Security Containment Integration with netgroup user lists Integration with HP System Management Homepage (SMH) Concepts and terms for using gWLM Here are some concepts and terms to know when using gWLM: Workload The collection of processes executing within a single compartment.
Shared Resource Domain (SRD) A collection of compartments that can share system resources. The compartments can be nPars, vPars, virtual machines, psets, or fss groups. For example, a server containing nPars can be an SRD—as long as the requirements in “The gWLM management model” (page 10) are met. Also, a server or an npar divided into vPars can be an SRD for its vPar compartments. Similarly, a server or an npar divided into virtual machines can be an SRD for its virtual machine compartments.
Undeploy Disable gWLM’s management of resources in a specified SRD. If an SRD is in managed mode, undeploying stops the migration of system resources among workloads in the SRD. If the SRD is in advisory mode, gWLM no longer provides information on what requests would have been made. The gWLM management model gWLM enables utility computing across a data center by providing resource-sharing policies that you centrally create and monitor.
For more information on these system divisions, visit: • HP Virtual Server Environment website: http://www.hp.com/go/vse • The “Technical Documentation website for HP Virtual Server Environment (VSE)” website: http://www.hp.com/go/insightdynamics/docs • The “Global Workload Manager” topic and the glossary in the online help for gWLM, available in gWLM’s graphical interface in HP SIM. gWLM manages resources based on the following model: 1. You define an SRD by: a.
Table 1-1 Default weights by policy type Policy type Default weight Fixed N/A (You cannot deploy an SRD where all the workloads with fixed policies are not satisfied.) Utilization 1 OwnBorrow Equal to its owned value Custom 1 NOTE: To ensure CPU resource allocations behave as expected for OwnBorrow policies, the sum of the CPU resources owned cannot exceed the number of cores in the SRD.
1. Decide which system will be your central management server (CMS), then install the VSE Management Software CMS on that system. This system must also have HP SIM installed and running. 2. Initialize the CMS by running the vseinitconfig command. For more information, see vseinitconfig(1M). 3. 4. Decide which systems will be your managed nodes, then install the gWLM agent software on those systems. (The agent software is free, but it is functional only for a limited time.
Table 1-2 Where to find additional information (continued) To... See... Learn how to update metrics when using custom policies. gwlmsend(1M) Learn how to manually place processes in workloads based on psets or fss groups. gwlmplace(1M) Learn about using gWLM with HP Serviceguard. The HP Insight Dynamics - VSE documentation website at Learn more about nPars, vPars, virtual machines, and psets. • HP Insight Dynamics - VSE documentation website: http://www.hp.com/go/insightdynamics/docs http://www.
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.
Choosing a policy type How do you decide which policy type to use? Table 2-1 answers this question for several common use cases. The section following the table helps you decide between using an OwnBorrow policy or a utilization policy. Table 2-1 Choosing a policy type If... Use the following type of policy... You want gWLM to allocate a constant amount of CPU resources to a workload. Fixed You have your own metric by which you want gWLM to Custom manage a workload.
Combining the different policy types Each workload in an SRD must have a policy. Starting with gWLM A.02.00.00.07, you can use any combination of the policy types within an SRD. Seeing how gWLM will perform without affecting the system gWLM provides an advisory mode that allows you to see how gWLM will approximately respond to a given SRD configuration—without putting gWLM in charge of your system’s resources. Using this mode, you can safely gain a better understanding of how gWLM works.
NOTE: You must be logged in as root on the systems where you run the mxstart, gwlmcmsd, and gwlmagent commands mentioned below. In HP SIM, you must be logged in as root or have authorizations for “All Tools” or “VSE All Tools.” 1. 2.
NOTE: You must be logged in as root on the systems where you run the mxstart, gwlmcmsd, and gwlmagent commands mentioned below. In HP SIM, you must be logged in as root or have authorizations for “All Tools” or “VSE All Tools.” 1. Start the gWLM agent daemons on vpar1 and vpar2: # vpar1> /opt/gwlm/bin/gwlmagent # vpar2> /opt/gwlm/bin/gwlmagent Alternatively, you can start the agents through HP SIM, as discussed in the VSE Management Software Installation and Update Guide. 2.
Common uses for gWLM gWLM is a powerful tool that allows you to manage your systems in numerous ways. The following sections explain some of the more common tasks that gWLM can do for you. Fixing the amount of CPU resources a workload gets gWLM allows you to give a workload a fixed amount of CPU resources. This fixed amount is in the form of a set amount of CPU resources given to an npar, a vpar, a virtual machine, a pset, or an fss group.
Resizing a workload’s npar, vpar, 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.
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 due to the nature of these compartments.) Managed mode, however, allows gWLM to automatically adjust the resource allocations for your defined workloads.
where hostname represents the hostname of the CMS. 3. From the HP SIM menu bar, select: Tools→Virtualization Manager... and then click the Shared Resource Domain tab. 4. From the VSE Management menu bar, select: Policy→Create gWLM Policy... 5. 6. Edit the settings, selecting a policy type and specifying the required values and optional values as desired. Click OK. Editing a policy A policy instructs gWLM how to manage a workload’s resources.
2. Connect to HP SIM by pointing your web browser to: http://hostname:280 where hostname represents the hostname of the CMS. 3. From the HP SIM menu bar, select: Tools→Virtualization Manager... and then click the Shared Resource Domain tab. 4. 5. 6. 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. From the VSE Management menu bar, select: Policy→Change Associated gWLM Policy... 7. 8.
1. 2. Ensure HP SIM, 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 21). Connect to HP SIM 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.
Quick Link Option In the previous procedure, instead of selecting an SRD and using the VSE Management menu bar, you can find the Details table for the SRD and click the Undeploy SRD link.
3 Monitoring workloads and gWLM This chapter describes how to monitor workloads and gWLM. Monitoring workloads There are several methods for monitoring workloads, as described below. High-Level view To see a high-level view of the performance of your SRDs and workloads: 1. From the HP SIM menu bar, select: Tools→Virtualization Manager... 2. Click the Shared Resource Domain tab. Graphical reports gWLM provides graphs showing either real-time or historical data through HP SIM.
Monitoring gWLM from the command line There are several command-line tools for monitoring gWLM. These commands are added to the path during installation. On HP-UX systems, the commands are in /opt/gwlm/bin/. On Microsoft Windows systems, the commands are in C:\Program Files\HP\Virtual Server Environment\bin\gwlm\ by default. However, a different path might have been selected at installation.
Table 3-1 gWLM log files (continued) Log for Location gWLM interface in HP Systems Insight Manager HP-UX: /var/opt/gwlm/gwlm.log.0 gwlm command HP-UX: /var/opt/gwlm/gwlmcommand.log.0 Windows: C:\Program Files\HP\Virtual Server Environment\logs\gwlm.log.0 Windows: C:\Program Files\HP\Virtual Server Environment\logs\gwlmcommand.log.0 NOTE: On systems running Windows, log files are in C:\Program Files\HP\Virtual Server Environment\logs\ by default.
Viewing HP Systems Insight Manager events gWLM allows you to configure a number of events you can monitor through HP SIM. Set these events in HP SIM as follows: 1. From the HP SIM menu bar, select: Tools→Virtualization Manager... 2. 3. Click the Shared Resource Domain tab. From the VSE Management menu bar, select: Tools→Global Workload Manager→Events… After configuring these events, you can monitor them through the various Events items in the left pane of HP SIM.
4 Security This chapter highlights several security items you should be aware of. General security topics The following items are a few general topics on security: • • • HP provides the HP-UX Bastille product, available from http://software.hp.com at no charge, for enhancing system security. You can secure gWLM’s communications as explained in the following section. HP SIM allows you to create user roles with different levels of privileges. For more information, see the HP SIM documentation.
3. Set the following properties as desired: • oracle.net.encryption_types_client • oracle.net.crypto_checksum_types_client For more information on these properties, read their associated comments in the gwlmcms.properties file. 4. 5. 6. Ensure the Oracle listener and port being used by HP SIM is configured to accept secure communication for the encryption and checksum types specified in the previous step. The Oracle database administrator can use netmgr to configure settings on the Oracle server.
5 Additional configuration and administration tasks This chapter covers various configuration and administration tasks. Manually adjusting CPU resources When an SRD is created, it has a certain number of cores. gWLM manages the SRD using the same number of cores. If the SRD—or a policy used in the SRD—is configured to use Temporary Instant Capacity (TiCAP), gWLM can automatically activate that additional capacity to meet policies.
• • • Creation or deletion of a pset using psrset on a system where gWLM is managing pset compartments. Performing online cell operations using parolrad. Enabling and disabling Hyper-Threading. To make use of these additional resources using the gWLM command-line interface: 1. 2. 3. 4. Undeploy the SRD containing the systems that you want to adjust. Make your adjustments. Re-create and re-deploy the SRD.
For more information, see vseinitconfig(1M).
# When you set the level, you will see messages only from that level and # the levels that are more severe. So, the SEVERE level produces the fewest # messages, while the FINEST level includes messages from all seven levels. # com.hp.gwlm.util.Log.logLevel = INFO # # Specify the size (in MB) and number of files to use # for logging. For a single file of unlimited size, set # logFileSize to negative one (logFileSize=-1). # Otherwise, total log file size is # logFileSize * logNFiles # com.hp.gwlm.util.Log.
# The number of minutes of real-time data used to aggregate into a # historical data point. The default is to aggregate the data into # 5-minute averages. # com.hp.gwlm.node.cachesize = 20 com.hp.gwlm.node.samples = 5 # # Support for real-time graphing properties. # # viewport: # The size of the displayed real-time graph (in minutes). # # refresh: # The refresh rate of the real-time graphs and tables (in seconds). # com.hp.gwlm.ui.monitor.viewport = 20 com.hp.gwlm.ui.monitor.
# # You must restart gwlmagent for changes made to this file to # take effect. # # # Set FileHandler /var/opt/gwlm/gwlmagent.log.0 log level. # Valid levels, from most severe to least, are: # SEVERE # WARNING # INFO # CONFIG # FINE # FINER # FINEST # When you set the level, you will see messages only from that level and # the levels that are more severe. So, the SEVERE level produces the fewest # messages, while the FINEST level includes messages from all seven levels. # com.hp.gwlm.util.Log.
Communications ports gWLM uses the following ports for communications: Managed nodes: 9617 CMS: 9618 If you need to change these ports, add the following lines: com.hp.gwlm.cms.port = portX com.hp.gwlm.node.port = portY to both properties files: • gwlmcms.properties On HP-UX, this file is in /etc/opt/gwlm/conf/. On Windows, it is in C:\ Program Files\HP\Virtual Server Environment\conf\. (The given Windows path is the default; however, a different path might have been selected at installation.
######################################################################## # (C) Copyright 2004-2008 Hewlett-Packard Development Company, L.P. # # gWLM Configuration File # # $Revision: 1.1 $ # $Date: 2008/12/02 20:17:18 $ ######################################################################## # Set GWLM_CMS_START to 1 to have the init process start the gWLM CMS # daemon. (HP recommends setting this variable to 1 only when used in a # secure operating environment.
NOTE: If a vpar is borrowing cores from other vPars when it loses contact with its SRD, those borrowed cores might be separated from the SRD. If the vpar might be down for an extended time, check that the SRD has reformed without that vpar and that it has enough cores to meet its commitments. If not, try using vparmodify to reclaim some of the cores. (With the vpar down, you will not be able to modify it locally, and only some versions of HP-UX Virtual Partitions allow you to easily modify a remote vpar.
3. If the problem persists, check the files /var/opt/gwlm/gwlmagent.log.0 and /var/ opt/gwlm/gwlmcmsd.log.0 for additional diagnostic messages. “SRD Communication Issue” and “SRD Reformed with Partial Set of Nodes” events NOTE: Reforming with a partial set of nodes requires a minimum of three managed nodes in the SRD. NOTE: “SRD Communication Issue” events are not enabled by default.
NOTE: If the gWLM CMS and agent disagree about whether an SRD is deployed or undeployed, you can use the --force option with the gwlm deploy or gwlm undeploy commands.
Nesting partitions gWLM allows you to form SRDs consisting of various compartment types. This ability provides flexibility in dividing your complex. For example, you can divide your complex as shown in Figure 5-1. The complex has four nPars, two of which are divided into vPars. One npar is hosting virtual machines, and the fourth npar is not divided. gWLM allows you to create an SRD containing the two virtual machine guests, the two vPars from npar 2, the two vPars from npar 3, and npar 4.
Changing the gWLM resource allocation interval The frequency of gWLM’s changes in the CPU resource allocations is an attribute of the SRDs. Once you create an SRD, you can change how often gWLM adjusts the CPU resource allocations of the workloads in that SRD using either of the methods discussed in the following sections.
those processes are. If the processes are on only two cores, the utilization is 50% (2/4). With the processes distributed across all four cores though, each process can consume an entire core, resulting in a utilization of 100%. When fss groups are being used, gWLM disables Hyper-Threading for the default pset, where fss groups are created, to optimize workload performance. When an SRD is undeployed, gwlmagent restores the lcpu_attr tunable to the value it had when the system booted.
1. For each host in the management LAN that you want to manage in an SRD: a. Edit the /etc/opt/gwlm/conf/gwlmagent.properties file to include the following property: com.hp.gwlm.security.virtualLocalHostName=hostnameOnLAN For example, with the host mgmtA, its property would be: com.hp.gwlm.security.virtualLocalHostName=mgmtA b. Restart gwlmagent on the host: # /opt/gwlm/bin/gwlmagent --restart 2. The CMS must also be in the management LAN.
• • A corporate LAN/WAN via one network interface card and IP address A second, private internal network and private IP address for communicating with a certain other set of hosts (such as cluster members) Global Workload Manager attempts to detect and report network configuration issues that can cause undesirable behavior, but in some cases this detection occurs in a context that can be reported only into a log file.
c. Verify that /etc/hosts has the same name configured for the address. Note that the first name should be the fully qualified domain name, and any aliases are listed afterward. [mysystem#3] > grep 15.11.100.17 /etc/hosts 15.11.100.17 mysystem.mydomain.com mysystem d. Verify that the reverse lookup of the IP address returns the same fully qualified domain name as configured in /etc/hosts. [mysystem#4] > nslookup 15.11.100.17 Trying DNS Name: mysystem.mydomain.com Address: 15.11.100.
6 Support and other resources This chapter contains support information and the available resources for the HP Insight Global Workload Manager software for Integrity.
NOTE: HP cannot provide product support through these email addresses. To obtain product support, see “Contacting HP” (page 51). For a forum with other gWLM users, visit the IT Resource Center’s forum for HP-UX Workload/Resource Management: http://forums.itrc.hp.com/cm/CategoryHome/1,,213,00.html New and changed information in this edition The following additions and changes have been made for this edition: • A limitation has been added to: — Appendix B Global Workload Manager 6.
Command Command name or qualified command phrase. user input Commands and other text that you type. computer output Text displayed by the computer. Enter The name of a keyboard key. Note that Return and Enter both refer to the same key. A sequence such as Ctrl+A indicates that you must hold down the key labeled Ctrl while pressing the A key. variable The name of an environment variable, for example PATH or errno.
A Compatibility with agents The gWLM A.6.2.0.* CMS runs on HP-UX 11i v1 (B.11.11), HP-UX 11i v2 (B.11.23), HP-UX 11i v3 (B.11.31), and Microsoft Windows systems. It works with the following versions of the agents: • gWLM A.03.00.00.05: HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3 • gWLM A.03.00.01.05: HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3 • gWLM A.04.00.07: HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3 • gWLM A.04.01.00.*: HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3 • gWLM A.6.0.0.
B Global Workload Manager A.6.2.0.* Known issues This appendix contains the limitations and known issues for the Global Workload Manager (gWLM) A.6.2.0.* release. Limitations The following are limitations for Global Workload Manager. HP Integrity Superdome 2 support HP Global Workload Manager (gWLM) supports fss, psets, and HP Integrity Virtual Machines on HP Integrity Superdome 2. It does not support nPars and vPars. Online migration of CPU is also not supported.
• You have specified hosts in different complexes and the complexes are not managed in the same GiCAP group. • You have specified hosts in different nPartitions in a complex when there are no iCAP usage rights to share between the nPartitions. • The cimserver (or a provider) on one or more hosts is not functioning properly and consequently complex or partition IDs are not discovered properly. If you receive this message: • Inspect the /var/opt/gwlm/gwlmagent.log.
nPartition). You can use a gWLM conditional policy to change the resource allocation depending on which packages are present. This enables you to control the resource allocation of the enclosing operating system instance and still monitor the workload via Virtualization Manager. Host name aliases are not supported Host name aliases are not supported by gWLM. Only canonical DNS host names (fully qualified domain names) are supported.
Only workloads with managed siblings can be added to SRDs with nested partitions Using the gWLM command-line interface, you cannot add a workload to an SRD that has nested partitions unless a sibling of that workload is already managed in that SRD. Workaround This is not an issue when you use the gWLM interface in HP SIM.
the placement rules, which are explained in the online help topic "pset / fss group tips" in the section "Precedence of placement techniques." If you use the psrset command to place processes in psets, gWLM is likely to move the processes to the default pset. Workaround To maintain the placement of a process, use gWLM's application records or user records when creating or editing your workload definitions in gWLM. If using records is not practical, use the gwlmplace command.
Documentation or minor issues The following are minor issues for Global Workload Manager. Cell-Local processors and iCAP environment Using cell-local processors with virtual partitions inside an nPartition that uses (iCAP) leads to failure of the icod_modify command. Workaround Do not assign CPUs using cell specifications. Consider assigning CPUs to the virtual partitions using a hardware path. Alternatively, to use cell-local processors, update to vPars A.04.04 on HP-UX 11i v2 (B.11.23) or to vPars A.05.
For HP-UX 11i v1, use version B.11.11.01.03.01.01 or later. For HP-UX 11i v2 on HP 9000 servers, use version B.11.23.01.03.01.01 or later. For HP-UX 11i v2 on HP Integrity servers, use version B.11.23.01.04 or later. You can find the nPartition Provider at the following locations: • The quarterly AR CD starting May 2005 • The Software Depot website: http://software.hp.
Workaround Undeploy the SRD using the --force option with the gwlm undeploy command, and restart gwlmagent on the managed node. SRD deployment times out and displays a blank screen If you attempt to deploy an SRD, but: • gWLM times out and displays a blank screen • There are events from each managed node similar to the following event: gWLM Agent MySystem.MyDomain.com Information Unable to manage the following hosts: Associated Exception Unable to manage the following hosts: MySystem.MyDomain.
Starting management of monitored workloads with pset compartments If you attempt to manage a set of monitored workloads by applying a policy and managing them with pset compartments, you might get the following error when attempting to complete the Workload & Policies step of the Manage Systems & Workloads Wizard: The value '0' specified for 'Total Size' must be a positive integer value.
Missing historical data (gWLM CMS daemon/service restarted) You might have blank sections of a historic report for a workload, or you might see the following error message when displaying historic data for a workload: There is no gWLM historical data for the workload MyWorkload.wkld. The workload has never been managed by gWLM, or the historical data has been removed.
Index multiple NICs, 47 policy types, 15 properties, 35 related information, 52 reports, 27 security, 31 set up, 21 startup behavior, 39 support, 51 tabs and menus, 17 wizard, 17 A advisory mode, 17 advisory mode to managed mode change, 22 automatic restart gWLM managed nodes in SRD, 40 C communication ports, 39 compartment, 8 compatibility with agents, 55 conditional policy, 15 configuration, 21 contacting HP, 51 CPU resources manual adjustment, 33 custom policy, 15 D H hardware partition, 10 hosts on
SRD add comparment or GiCAP group member, 24 automatic restart of gWLM managed nodes, 40 communication issue, 42 manually clearing, 42 node failed to rejoin SRD, 41 stop managing, 25 startup behavior, 39 support, 51 T tabs and menus, 17 typographic conventions, 52 U unable to create new native thread, 49 undeploy, 10 utilization policy, 15 V virtual partition, 10 W wizard, 17 workload, 8 disk space requirement, 34 monitoring, 27 stop managing, 24 68 Index
