Global Workload Manager (gWLM) Installation Guide and Release Notes This document provides information for those intending to install and use the Global Workload Manager (gWLM) agent for OpenVMS. It contains the following sections: 1. gWLM Preliminaries 1.1 Prerequisites 1.2 Installation requirements 1.3 Terminology and workload definitions 1.4 File locations and interfaces available 2. Installation and Operation 2.1 Installation procedure 2.2 Starting and Stopping the gWLM 2.3 Compatibilities 3. Issues and Workarounds 4. Related Documentation 1 gWLM Preliminaries The following sections contain information you need prior to installing the gWLM. 1.1 Prerequisites You need to install the gWLM agent for OpenVMS on all of the systems whose workloads you want to manage. To set up and monitor the gWLM, you use the gWLM Central Management Server (CMS). Therefore, to complete your installation you also need the following: o HP Systems Insight Manager V4.2 o HP Global Workload Manager CMS (Central Management Server) A.01.01.x Versions of these products for HP-UX and Linux are available as free downloads from the following web site: http://h20293.www2.hp.com/portal/swdepot/displayProductsList.do?category=ISS o TCP/IP is required. You can use either of the following versions: HP TCP/IP Services for OpenVMS I64 5.5 or higher 1 HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 4 or higher o UTC time Ensure that UTC time is correctly set up on the managed systems. Failure to do so might result in errors in time stamp values reported in the user interface. 1.2 Installation Requirements This is the first version of the gWLM agent for OpenVMS. The installation requirements are in the following sections. Versions of OpenVMS You can install the gWLM on the versions of OpenVMS shown in the following table. Required patches, if any, are also listed. ___________________________________________________________ OpenVMS Version Platform Required Patches ___________________________________________________________ Version 7.3-2 Alpha VMS732_UPDATE V4.0 VMS732_PTHREAD V3.0 VMS732_SYS V7.0 Version 8.2 Alpha None Version_8.2-1 I64 None ___________________________________________________________ Disk Space Post-installation space used on the system disk is approximately the following: o I64: 320000 blocks (155 MB) o Alpha: 110000 blocks (53 MB) 1.3 Terminology and Definitions The following sections explain gWLM terms and provide workload definitions. 2 1.3.1 Terminology The gWLM manages several types of virtual compartments. In the user interface (UI) and in related gWLM documents, these types are referred to in terms that are familiar to HPUX users. Explanations of these terms for OpenVMS users are in the following table. ___________________________________________________________ Term Explanation ___________________________________________________________ npar Hard partitions are not managed by this version of the agent. vpar OpenVMS soft partition. Selecting this compartment type allows gWLM to reassign processors between the soft partitions of a hard partition. This functionality is currently only available on OpenVMS Alpha. pset A processor set (pset) is a subset of the processors available to a single OS instance. gWLM on OpenVMS uses process and processor capabilities to implement psets. fss The equivalent of HPUX fair-share scheduler (fss) is the OpenVMS class scheduler. Selecting this compartment type causes gWLM to manage CPU resources using the class scheduler. ___________________________________________________________ Online help contains a useful glossary, which you can access through the gWLM home page in the HP SIM. (Click the large '?' at the top right.) 1.3.2 Workload Definitions Guidelines for composing application workload definitions are in the following list. o When you compose an application workload definition using application path names, UNIX-style path names are preferred; for example: /sys$common/java$142/bin/java$java.exe /sys$system/vms*.exe /RED$DKA0/SYS0/SYSCOMMON/JAVA$142/BIN/JAVA$JAVA.EXE 3 o The usual wildcard characters, "%" and "*", are allowed. "Application Alternate Names" are not necessary on OpenVMS; do not specify them. o You can use OpenVMS-style path names for individual, non-wildcarded executables; for example: RED$DKA0:[SYS0.SYSCOMMON.JAVA$142.BIN]JAVA$JAVA.EXE SYS$SYSTEM:VMSHELP.EXE SYS$COMMON:[SYSEXE]VMSHELP.EXE o If you use a Version 1.1.1, 1.1.2, or 2.0 gWLM CMS, in addition, the path name must start with a "/" character; for example: /RED$DKA0:[SYS0.SYSCOMMON.JAVA$142.BIN]JAVA$JAVA.EXE /SYS$SYSTEM:VMSHELP.EXE /SYS$COMMON:[SYSEXE]VMSHELP.EXE 1.4 File Locations and Interfaces Available The gWLM agent installs on OpenVMS in the following directory: sys$sysroot:[gwlm] UNIX pathnames referenced in the UI and elsewhere are mapped as follows: ___________________________________________________________ UNIX Pathname OpenVMS Pathname ___________________________________________________________ /etc/opt/gwlm sys$sysroot:[gwlm] /var/opt/gwlm sys$sysroot:[gwlm.log] ___________________________________________________________ Available Interfaces You can perform most operations using either HP Systems Insight Manager or the 'gwlm' command on the gWLM Central Management Server (CMS). The following agent commands are available on a system on which the OpenVMS agent is installed: o gwlmsslconfig o gwlmimportkey 4 o gwlmexportkey o gwlmplace o gwlmsend These commands are implemented as foreign commands. Before you can use them, you must first execute the following command line: $ @sys$sysroot:[gwlm.bin]gwlm$env get_commands You can obtain interactive help for these commands by entering the following command: $ help gWLM To use agent commands, you must have read and write access to the files in the following directory: sys$sysroot:[gwlm] 2 gWLM Installation and Operation The following sections tell how to install the gWLM agent and stop the gWLM, what compatibilities the gWLM has with other products, and what issues and workarounds the gWLM has. 2.1 Installation Procedure Before installing the gWLM, you must install a PAK that is appropriate to your hardware platform. To install the gWLM agent, enter the following command: $ product install gwlm/source= Likewise, you can remove the gWLM with the following command: $ product remove gwlm 5 2.2 Starting and Stopping gWLM You can start the gWLM agent by invoking a command procedure by entering the following command: $ @sys$startup:gwlm$startup You can stop the gWLM agent by invoking a command procedure by entering the following command: $ @sys$startup:gwlm$shutdown 2.3 Compatibility with Other System Management Methods The gWLM agent makes use of the following OpenVMS technologies: o Class scheduler o Process and processor capabilities o Processor assignment among soft partitions ________________________ Note ________________________ If other software is attempting resource management with any of these technologies, the gWLM might not be able to place all the system processes in the workloads you define using the gWLM user interface. ______________________________________________________ 3 Known Issues and Workarounds The following issues are in addition to those documented in the main product release notes. 3.0.1 Host Name Configuration Differences in host name configuration between the CMS and managed hosts might lead to an error during the discovery phase. An example of an error message is the following: "The IP address 16.32.16.151 resolves to two different fully qualified domain names. The fully qualified domain name on the managed node is wbem6; the CMS has the managed node's fully qualified domain name as wbem6.zko.dec.com. Please correct and retry. Please re-enter the systems." 6 The following example deals with the problem on the managed node by providing the managed node with a fully qualified domain name definition. TCPIP> show host wbem6 LOCAL database Host address Host name 16.32.16.151 wbem6, WBEM6 TCPIP> set nohost "wbem6" TCPIP> set host "wbem6.zko.dec.com"/address=16.32.16.151/alias=("wbem6",wbem6) TCPIP> show host wbem6 LOCAL database Host address Host name 16.32.16.151 wbem6, WBEM6 TCPIP> set nohost "wbem6" TCPIP> set host "wbem6.zko.dec.com"/address=16.32.16.151/alias=("wbem6",wbem6) TCPIP> show host wbem6 LOCAL database Host address Host name 16.32.16.151 wbem6.zko.dec.com, wbem6, WBEM6 3.0.2 Class Scheduler and I/O-Intensive Applications Current versions of the OpenVMS class scheduler treat I/O- intensive applications rather harshly. This is evident in irregularly high CPU usage being reported to gWLM, which causes rapid CPU quota depletion and results in poor throughput. You can lessen this problem by setting the system parameter IOTA to 0. HP plans to release a patch kit for the OpenVMS SYS facility in the near future. 3.0.3 Identification of Hardware Complex ID OpenVMS Versions 7.3-2, 8.2 and V8.2-1 identify the hardware complex ID using the $getsyi item code SERIAL_ NUMBER. In cases where this result is not consistent with other environments in the complex, you can specify the gWLM agent value to be used with the logical name GWLM$COMPLEX_ ID. 7 3.0.4 Identification of Host Hard Partition ID OpenVMS Versions 7.3-2, 8.2, and V8.2-1 are unable to identify the host hard partition ID, so the gWLM agent uses a default value. In cases where this result is required to be consistent with other environments in the complex, you can specify the value to be used with the logical name GWLM$HARD_PARTITION_ID. 3.0.5 Stalls in Process Identification Thread A problem with the $getjpi system service on OpenVMS I64 systems results in occasional stalls in the thread responsible for process identification. As a result, it might occasionally take longer than expected for gWLM to assume control of new processes. To correct this problem, install patch VMS821I_SYS-V0100 when it becomes available. (You need to be running OpenVMS Version 8.2-1 first.) 3.0.6 Patch Required for gWLM to Start The gWLM agent process does not start on an OpenVMS Alpha Version 7.3-2 system unless patch kit VMS732_PTHREAD V3.0 or later is installed. 3.0.7 Failure When Managing Vpars If the value of the system parameter MULTITHREAD is less than the number of processors in the hard partition, the gWLM agent might fail following a change in the number of active processors. The agent process will then exhibit one or more CPU-bound kernel threads and be unresponsive to requests from the user interface. To avoid this problem, set the value of MULTITHREAD to the number of processors in the hard partition. In the near future, HP plans to release a patch kit for the PTHREAD facility to address this problem. 4 Related Documentation Additional gWLM documents are available from the following web sites: o HP gWLM Version A.01.01.x Release and Installation Notes for HP-UX 11i v1, HP-UX 11i v2 Update 2, and Linux http://docs.hp.com/en/T2762-90004/index.html 8 o Getting Started with gWLM: Version A.01.01.x http://docs.hp.com/en/T2762-90005/index.html o gWLM: Reference and Additional Topics: Version A.01.01.x http://docs.hp.com/en/T2762-90006/index.html 9