HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide Abstract This document presents an overview of the techniques and tools available for using Global Workload Manager servers (or gWLM). It exposes you to the essentials and allows you to quickly get started with gWLM. This document is intended to be used by HP Matrix Operating Environment system administrators, application administrators, and other technical professionals involved with data center operations, administration, and planning.
© Copyright 2004, 2014 Hewlett-Packard Development Company, L.P. 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.
Contents 1 Overview..................................................................................................6 gWLM Overview......................................................................................................................6 Benefits of using gWLM.............................................................................................................6 Comparison of PRM, WLM, and gWLM features..........................................................................
5 Additional configuration and administration tasks.........................................33 Manually adjusting CPU resources............................................................................................33 Manually adjusting memory resources.......................................................................................34 Setting aside space for historical data.......................................................................................
Compatibility with PRM and WLM.......................................................................................57 Rare incompatibility with virtual partitions.............................................................................58 Workloads in gWLM do not follow associated Serviceguard packages.....................................58 Host name aliases are not supported....................................................................................
1 Overview This chapter provides an overview of gWLM, including benefits, key concepts and terms, and the gWLM management model. gWLM Overview gWLM allows you to centrally define resource-sharing policies that you can use across multiple HP servers. Using these policies can increase system utilization and facilitate controlled sharing of system resources. In addition, gWLM provides both real-time and historical monitoring of the resource allocation.
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. The compartment can be an nPartition (npar), a virtual partition (vPar), a Virtualization Services Platform (VSP), a virtual machine provided by HP Integrity Virtual Machines (hpvm), a processor set (pset), or a Fair Share Scheduler (fss) group. gWLM manages a workload by adjusting the system resource allocations for its compartment.
Mode Two modes are available: advisory and managed. 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. Use this mode when creating and fine-tuning your policies.
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 Matrix Operating Environment website: http://www.hp.com/go/matrixoe/integrity • The “Technical Documentation website for HP Matrix Operating Environment” website: Enterprise Information Library • The “Global Workload Manager” topic and the glossary in the online help for gWLM, available in gWLM’s graphical interface in System Insight Manager. gWLM manages resources based on the following model: 1. You define an SRD by: a.
Table 1 Default weights by policy type (continued) Policy type Default weight (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.
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. For unlimited use, purchase the agent license to use, or LTU.) On each managed node, start the gWLM agent daemon gwlmagent.
Table 2 Where to find additional information (continued) To... See... Learn about using gWLM with HP Serviceguard. The HP Matrix Operating Environment documentation website at Enterprise Information Library Learn more about nPars, vPars, virtual machines, • HP Integrity Virtual Machines website: and psets. www.hp.com/go/hpux-vpars-docs • HP Matrix Operating Environment documentation website: Enterprise Information Library • The HP Matrix Operating Environment for HP-UX product website: http://www.hp.
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.
gWLM provides conditional policies that can detect the following HP Serviceguard conditions: • SgReducedClusterCapacity: Detects whether any cluster members are missing from the HP Serviceguard cluster associated with the host of the workload. • SgNonPrimaryPackagePresent: Detects whether any HP Serviceguard package that is active on the host of the workload does not have the host configured as its primary node.
Choosing a policy type How do you decide which policy type to use? Table 3 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 3 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 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 System Insight Manager, you must be logged in as root or have authorizations for “All Tools” or “Matrix OE 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 System Insight Manager, you must be logged in as root or have authorizations for “All Tools” or “Matrix OE All tools.” 1.
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 VSP, a virtual machine, a pset, or an fss group.
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.
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 System Insight Manager menu bar, select: Tools→HP Matrix OE visualization... and then click the Shared Resource Domain tab. 4. From the HP Matrix OE visualization 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.
where hostname represents the hostname of the CMS. 3. From the System Insight Manager menu bar, select: Tools→HP Matrix OE visualization... 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 HP Matrix OE visualization menu bar, select: Policy→Change Associated gWLM Policy... 7. 8.
1. 2. Ensure in System Insight Manager, 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 System Insight Manager 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.
NOTE: When gWLM manages a VSP, it sets the OLSTARPOLICY policy parameter of the VSP to GUEST. The status of the OLSTARPOLICY policy parameter does not change even after the SRD is undeployed. Quick Link Option In the previous procedure, instead of selecting an SRD and using the HP Matrix OE visualization 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 System Insight Manager menu bar, select: Tools→HP Matrix OE visualization... 2. Click the Shared Resource Domain tab.
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 4 gWLM log files (continued) Log for Location Windows: C:\Program Files\HP\Virtual Server Environment\logs\gwlm.log.0 gwlm command HP-UX: /var/opt/gwlm/gwlmcommand.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. However, a different path might have been selected at installation. The name of the current log always ends in .log.0.
Viewing HP Systems Insight Manager events gWLM allows you to configure a number of events you can monitor through System Insight Manager. Set these events in System Insight Manager as follows: 1. From the System Insight Manager menu bar, select: Tools→HP Matrix OE visualization... 2. 3. Click the Shared Resource Domain tab.
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. • System Insight Manager allows you to create user roles with different levels of privileges.
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 System Insight Manager is configured to accept secure communication for the encryption and checksum types specified in the previous step.
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.
gWLM cannot take advantage—even temporarily—of resources added by: • Adjustments to entitlements for virtual machines. • Changes to a virtual machine's number of virtual CPUs while gWLM is managing the virtual machine. • 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.
Setting cache size for historical configuration data The gWLM CMS daemon or service (gwlmcmsd) maintains a cache of historical configuration data of workloads. If there are huge number of workloads on the CMS, to avoid the gwlmcmsd running out of heap space, reduce the size of the cache by setting the com.hp.gwlm.cms.cachesize property to a lower value. The com.hp.gwlm.cms.cachesize is part of the gwlmcms.properties file. The gwlmcms.
If you are using Transact-SQL to create the maintenance plan, use the following SQL statements: USE gwlm GO ALTER INDEX ALL ON gwlm_config_wkld REBUILD GO Setting gWLM properties gWLM provides two properties files that allow you to control various gWLM behaviors. One file is for the CMS daemon or service, and the other is for use on all the managed nodes. Read the files for information on the behaviors they control. CMS properties The CMS properties are in /etc/opt/gwlm/conf/gwlmcms.
# 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.logFileSize = 20 com.hp.gwlm.util.Log.logNFiles = 3 # # Support for automatic database statistics gathering. These properties # control how often row-level statistics are gathered from the database in # order to optimize performance. # # com.hp.gwlm.cms.db.analyze.
# # 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.refresh = 15 # # Support for securing Oracle communication. # # com.hp.gwlm.jdbc.oracle.secure: # Whether communication with Oracle server is secure or not. Possible # values are 'on' and 'off'. Default is off. # # oracle.net.
gwlmagent.properties on Windows. (The given Windows path is the default; however, a different path might have been selected at installation.) NOTE: You must restart the gwlmagent daemon on each managed node where you have modified the properties file for the changes to the file to take effect. The gwlmagent.properties file is shown below. # # # # # # # # # # # # # # # (C) Copyright 2004-2007 Hewlett-Packard Development Company, L.P. $Date: 2008/12/02 20:17:18 $ $Revision: 1.
# each managed nPartition where you want to take advantage of iCAP. Also, # each nPartition must meet the requirements outlined in the online help # topic "Getting the most out of gWLM" as well as in the section "USING # nPars AS COMPARTMENTS IN AN SRD" in the gwlmxml(4) man page on HP-UX or # the gwlmxml(5) man page on Linux. # com.hp.gwlm.platform.icap.manageWithIcap = on # # Set the minimum number of Temporary Instant Capacity (TiCAP) minutes # that must be available for TiCAP activation.
On HP-UX, you can control whether the gWLM CMS daemon (gwlmcmsd) and its agent daemons on the managed nodes (gwlmagent) start at boot by: • Manually setting variables in the /etc/rc.config.d/gwlmCtl file. (The /sbin/init.d/ gwlmcmsd and /sbin/init.d/gwlmagt scripts use these variables.) • Using the --enable_start_on_boot and --disable_start_on_boot options to gwlmcmsd and gwlmagent.
2. (Optional) Edit the property com.hp.gwlm.node.HA.minimumTimeout in the file /etc/opt/gwlm/conf/gwlmagent.properties to set the minimum number of seconds that must pass before a managed node considers itself separated from its SRD. Set this property to ensure that minor network problems do not cause a managed node to prematurely consider itself separated. gWLM uses this value only if it is larger than 10 multiplied by gWLM’s allocation interval.
For information on enabling and viewing these events, refer to Optimize→Global Workload Manager→Events. You can then view these events using the Event Lists item in the left pane of System Insight Manager. The following sections explain how to handle some of the events. “Node Failed to Rejoin SRD on Start-up” event If you see the event “Node Failed to Rejoin SRD on Start-up”: 1. Restart the gwlmagent on each managed node in the affected SRD: # /opt/gwlm/bin/gwlmagent --restart 2. 3.
1. Delete the deployed.config file on each managed node: # rm -f /etc/opt/gwlm/deployed.config 2. Force an undeploy of the SRD (named SRD below) to ensure the CMS and the managed nodes agree on the SRD’s state. Run the following command on the CMS: # gwlm undeploy --srd=SRD --force 3.
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 2. The complex has five nPars, two of which are divided into vPars. One npar is hosting virtual machines, fourth npar is not divided, and the fifth nPar is hosting vPars.
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.
processes, each consuming an entire logical CPU, the reported utilization depends on where 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.
Figure 3 shows a management LAN in which the hosts are known as mgmtA, mgmtB, mgmtC, and mgmtD. With this management LAN, gWLM can manage the hosts in a single SRD. Complete the following procedure to set up gWLM to manage such hosts in an SRD: 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.
This issue is most often a concern when a host is connected to both of the following items: • 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
[mysystem#2] > nslookup mysystem Trying DNS Name: mysystem.mydomain.com Address: 15.11.100.17 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.
6 Support and other resources This chapter contains support information and the available resources for the HP Global Workload Manager (gWLM) servers.
Registering for software technical support and update service Insight Management includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources for assistance in resolving software implementation or operations problems. The service also provides access to software updates and reference manuals in electronic form as they are made available from HP.
Key The name of a keyboard key. Return and Enter both refer to the same key. Term A term or phrase that is defined in the body text of the document, not in a glossary. User input Indicates commands and text that you type exactly as shown. Replaceable The name of a placeholder that you replace with an actual value. [] In command syntax statements, these characters enclose optional content. {} In command syntax statements, these characters enclose required content.
7 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com ). Include the document title and part number, version number, or the URL when submitting your feedback.
A Compatibility with agents The gWLM CMS runs on 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.*: HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3 • gWLM A.6.2.
B Global Workload Manager known issues This appendix contains the limitations and known issues for the Global Workload Manager. Limitations The following are limitations for Global Workload Manager. Incorrect workload name for NONVM workload gWLM supports managing VSPs that has both vPars and HPVMs configured. When you create a NONVM workload for a VSP which has both vPar and HPVM guests configured, it is added as part of an SRD. Sometimes, the NONVM workload name is found to be incorrect.
• A change in the browser locale setting is reflected in: ◦ VSEMgmt software at the start of the next user-interface action ◦ System Insight Manager at the next logon • The properties files for gwlmagent and gwlmcmsd are parsed as English, regardless of the locale setting. So, be careful of using commas where English would use periods.
# /opt/wlm/bin/wlmd -k Rare incompatibility with virtual partitions Depending on workload characteristics, gWLM can migrate CPU resources rapidly. This frequent migration can potentially, although very rarely, produce a race condition, causing the virtual partition to crash. It can also produce a panic, resulting in one or more of the following messages: No Chosen CPU on the cell-cannot proceed with NB PDC. or PDC_PAT_EVENT_SET_MODE(2) call returned error Workaround Upgrading to vPars A.03.
result in a high enough number of events that the performance of the System Insight Manager CMS is adversely affected. Workaround The following options are available as workarounds: Option 1 For systems managed by gWLM that are running HP-UX 11i v3, install the patches PHCO_36126 and PHSS_36078. (These patches are included in the September 2007 Operating Environment Update Release.) A fix to EMS hardware monitors is available with the September 2007 Operating Environment Update Release.
configuration, if the SRD is undeployed before upgrading the agents, the re-deployment of the SRD will fail with an error message. If the SRD was left deployed while the agents were upgraded, the agents will not be able to restore SRD operations. Also, System Insight Manager events will be generated to report the validation failure. Workaround There are two workarounds: • Update to vPars A.04.00 or later. • Update your configurations so that psets are not nested in virtual partitions.
iCAP compliance warning gWLM might give the following warning: Warning: gwlmagent cimserver error, icapd down, or icap out of compliance. First restart cimserver. Make sure icapd is running. If this error happens again, consult gwlmagent man page for steps to return to compliance. Workaround Verify that no partition changes (parmodify) are pending. If partition changes are pending, please restart the system. Then, either consult iCAP documentation or contact HP to return the iCAP system back to compliance.
Engine marks the database as RESOURCE PENDING. In either case, user action is required to recover from the issue. Workaround HP recommends a regular database backup which will help to recover easily from such a scenario. Choose from the following options that best suits the situation after consulting the database vendor's guidelines. • Back up the log. • Free disk space so that the log can automatically grow. • Move the log file to a disk drive with sufficient space.
gwlm history --purge=30 2. Automatically remove the old configuration data from the gWLM database. To remove data automatically, the following properties must be set in the gwlmcms.properties file : com.hp.gwlm.cms.db.history.keep Valid values: 0 : Do not remove any historical data (default). 1 - 10000 : The number of days for which history will be retained. Any historical data older than the specified number of days will be removed from the database.
Combining psets and virtual partitions When using psets on virtual partitions, assigning CPUs to virtual partitions by either path or cell specification can result in processes losing their processor set affiliations when CPUs are removed. Workaround Two workarounds are available: • Do not assign CPUs to virtual partitions by either path or cell specification.
Missing or unexpected historical data (system clocks differ) You might have no historical data available for graphing, even though you are certain an SRD was deployed for the time period in question. A related issue occurs when you select a time period where you expect high system activity, but the graph shows limited activity. Similarly, you might expect very little activity for a time period, but the graph shows lots of activity.
Application hangs in fss group On HP-UX 11i v2 (B.11.23), an application inside an fss group might hang when running in a single-processor virtual partition, nPartition, or system. Workaround Install patch PHKL_33052. Scripts not placed in correct workloads With compartments based on psets or fss groups, gWLM allows you to place scripts in the compartments using application records with alternate names. This works only if the shell or interpreter being used is listed in the file /etc/shells.
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 security, 31 set up, 21 startup behavior, 40 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, 41 C communication ports, 40 compartment, 7 compatibility with agents, 55 conditional policy, 14 configuration, 21 CPU resources manual adjustment, 33 custom policy, 14 H D K database backup and restore, 35 deploy, 8 known issues, 56 F memory resources manual adjustment, 34 message logs, 28 messages inc
node failed to rejoin SRD, 43 stop managing, 25 startup behavior, 40 support, 51 T tabs and menus, 17 typographic conventions, 52 U unable to create new native thread, 50 undeploy, 9 utilization policy, 14 V virtual partition, 9 Virtualization Services Platform, 7 VSP, 7 W wizard, 17 workload, 7 disk space requirement, 34 monitoring, 27 stop managing, 24 70 Index