wlm gwlm migration

8/6/2019 WLM gWLM Migration

1/32

Migrating from W LM to gWLM

Overview...... .......................... ........................... ........................... ........................... ..................... 2

Why migrate?.......................... ........................... ........................... ........................... ..................... 2

gWLM terms to know ......................... ........................... ........................... ........................... ............ 3

WLM-to-gWLM terminology comparison........ ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .. 4

Availability of W LM features in gWLM......................... ........................... .......................... ................. 4

Command comparison ....................... ........................... ........................... ........................... ............ 6

System requirements for gWLM ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... 6

Common gWLM tasks............................. ........................... ........................... .......................... ........ 6

Migrating W LM configurations .......................... ........................... .......................... .......................... 7

Migration example: FSS-based workloads with usage goals..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .. 8

The W LM configuration.......................................... ........................... .......................... ................. 8

Creating an equivalent gWLM configuration..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .... 8

The gWLM configuration file................. ........................... .......................... ........................... ...... 16

Migration example: FSS-based workloads with stretch goals. ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ... 18

The W LM configuration.......................................... ........................... .......................... ............... 18

Creating an equivalent gWLM configuration..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .. 19


Migration example: vPar-based workloads with usage goals..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .... 25

The WLM configurations........................... ........................... ........................... ........................... . 25

Creating an equivalent gWLM configuration..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .. 26


Integrating with Security Containment ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .... 31

Licensing and availability.................... ........................... ........................... ........................... .......... 32

For more information........................................ ........................... .......................... ........................ 32


2/32

2

Overview

HP Global W orkload Manager (gW LM) and HP-UX Workload Manager (WLM) provide the intelligen

control for the HP Virtual Server Environment. They enable automated, dynamic allocation of server

resources among applications according to defined policiesso resource utilization improves and

service levels are maintained. W hile gW LM and WLM are best suited for different types of Virtual

Server Environment deployments, they both provide the following capabilities:

Management of real-time resource allocation of many soft partitions (HP-UX virtual partitions, HPIntegrity virtual machines, or Secure Resource Partitions)

Shifting of Instant Capacity usage rights for cores between hard partitions (nPars) or servers based

on business priorities

Resizing within or across servers based on demand by activating or deactivating Temporary Instant

Capacity

Synchronization of resource management policies to re-allocate server resources in the case of a

failover

So how do they differ, and how are they positioned? As HPs strategic workload management

product, HP gW LM is ideal for both a large-scale deployment with multiple servers, as well as for

workloads on a single system or in a high-availabili ty environment. A typical example is a shared IT

deployment where a single IT department manages servers for multiple business units and manyapplications run on a large number of serverseach with several partitions. HP-UX Workload

Manager is designed to manage workloads on a single system or in a high-availability cluster. HP-UX

WLM is a suitable solution for a line-of-business (LOB) consolidation in which the LOB owns its servers

but relies on an IT team to manage them. W LM also gives you the ability to fine-tune policies to

support specialized resource management needs.

HP-UX WLM is intended for installations where it is already in use. HP gW LM should be considered

for new installations as well as installations where growth, in terms of scale or complexity, are

anticipated.

W hy migrate?

In addition to the positioning of gWLM discussed above, consider migrating to gWLM for benefits

including:

Simplified configuration, including a library of policies that are ready to use

Centralized management using HP SIM that provides policy administration and reporting features

that enable IT to easily set up, manage, and track resource usage

Integration with HP VSE products

Deeper integration with HP Integrity Virtual Machines

Automatic discovery of systems to manage

OwnBorrow policies (allow you to specify the amount of resources a workload owns, as well as

exactly how much the workload can borrow and lend, in essence combining base and stretch goals

into a single policy)


3/32

3

gW LM terms to know

Here are some terms to know when using gWLM:

Workload

The collection of processes that are within a single compartment. gW LM manages a workload by

adjusting the system resource allocations for its compartment.

CompartmentAn entity with its resource allocation being managed by gW LM. A compartment can be an

nPartition, a virtual partition, a virtual machine, a processor set (pset), or a Fair Share Scheduler

(fss) group.

Multiple compartments are grouped to form a shared resource domain, or SRD. The compartments

all share the resources within the SRD. Each compartment holds a workload and can be in only one

deployed SRD. gW LM manages each workload by adjusting the resource allocation for its

compartment.

Shared Resource Domain (SRD)

A collection of compartments that share system resources.

gW LM creates SRDs when you use the Manage Systems and W orkloads wizard.

Policy

A policy is a collection of settings that instruct gW LM how to manage a compartments resources

and thus the resources available to the workload within the compartment. For example, a policy

can indicate the amount of CPU resources a workload owns (and is allocated when needed), how

much of those resources the workload can lend to other workloads, and how much the workload

can borrow from other workloads.

A single policy can be associated, or applied, to multiple workloads.

Mode

gW LM offers two modes: advisory and managed. Advisory mode allows you to see what CPUresource requests gW LM would make for a compartmentwithout actually affecting resource

allocation. You can use this mode when creating and fine-tuning your policies. Once you are

comfortable with your policies, use managed mode to have gWLM automatically adjust the

resource allocations for your defined compartments. (Advisory mode is not available for SRDs

containing virtual machines, psets, or fss groups.)

You can only set the mode on the SRD level: All compartments within an SRD operate in the same

mode, either advisory or managed.

Deploy

Enable gW LM control of an SRD.

Deploying an SRD in managed mode enables gW LM control of resource allocation within the SRD.When deploying an SRD in advisory mode, gWLM simply reports what the allocation would be

without actually affecting resource allocations on a system.

Undeploy

Disable gW LMs management of resources in a specified SRD.

If an SRD is in managed mode, undeploying stops the migration of system resources among

compartments in the SRD. If the SRD is in advisory mode, gW LM no longer provides information on

what requests would have been made.


4/32

4

W LM-to-gW LM terminology comparison

The following table shows WLM terms and their corresponding gW LM terms.

WLM term gWLM term

Service-level objective Policy

Partition set Shared resource domain (SRD)

Passive mode Advisory mode (not available for HP Integrity Virtual

Machines, psets, or fss groups)

Availability of W LM features in gW LM

The table below lists various WLM features and then indicates whether the given feature is supported

by gWLM.

Comparisons are based on the functionality available in WLM A.03.03 and gWLM A.04.00.

Feature WLM A.03.03 support gWLM A.04.00 support

CPU resource management Yes Yes

Memory resource management Yes No

Disk bandwidth resource

management

YesNo

Workload types FSS groups, psets, virtual partitions,

nPartitions that use Instant Capacity

FSS groups, psets, virtual partitions,

nPartitions that use Instant Capacity,

HP Integrity Virtual Machines, simulated

psets on OpenVMS, OpenVMS soft

partitions, workloads based on the

OpenVMS class scheduler

SLO (policy) types Fixed, utilization-based, metric-based

(including shares-per-metric)

Fixed, utilization-based, metric-based

(including shares-per-metric custom

policies), OwnBorrow

Multiple SLOs (policies) per

workload (stretch goals)

Yes No

However, OwnBorrow policies

simulate a W LM base/ stretch goal

combination

Nested partitions Yes Yes

Time-based SLOs (policies) Yes(condition keyword) Yes

Conditional SLOs (policies) Yes(condition keyword) Yes (for Serviceguard events and

file-based conditions)

Process placement based on

binary name

Yes Yes


user name

Yes Yes


Unix group name

Yes Yes (with a user-defined process map)


process maps

Yes (procmaps keyword) Yes

Monitoring process placement by

workload with ps

Yes Yes


5/32

5

Feature WLM A.03.03 support gWLM A.04.00 support

Smoothing of metric data

available

Yes (cntl_smooth keyword) Yesi f WLM Toolki ts are installed

(/ opt/ wlm/ toolkits/ oracle/ bin/ smooth)

WLM Toolkits Yes Yeswith customizations

SAP integration paper: Using HP GlobalWorkload Manager with SAPavailablefrom http:/ / docs.hp.com/ en/ vse.html

Workload monitoring (on the

command line and in a GUI)

Yes Yes

Events/ alarms Event Monitoring Service (EMS) HP Systems Insight Manager (SIM)

Events

Data collector started when a

configuration is activated

Yes No

No standard mechanism for starting a

data collector; however, you can use

gwlmsend to supply data

Policy/ SLO storage SLO data is stored in configuration

files on each node; identical SLOs are

cut-and-paste copies of an original

Policies are stored in a centralized

database; the same policy can be

applied to multiple workloads without

being replicated

Can export or import in XML format

Data source integration (DSI)

support, providing workload data

to OpenView tools including

OVPM

Yes Yes

HP-UX Security Containment

integration

Yes No built-in integration; however, you

can integrate as explained in the section

Integrating with Security Containment

on page 31

Passive mode Yes Yes (Advisory mode)

Advisory mode is not available for HPIntegrity Virtual Machines, psets, or fss

groups


6/32

6

Command comparison

The following table lists all the WLM commands and their equivalent gW LM commands.

WLM A.03.03 command Equivalent gWLM A.04.00 command

wlmaudit gwlmreport

wlmd HP SIM interface; gwlm

wlmcw HP SIM interface

wlmgui HP SIM interface

wlmpard HP SIM interface; gwlm

wlmcomd Not needed

wlminfo gwlm monitor

wlmcert HP SIM interface; gwlmsslconfig

wlmsend/wlmrcvdc gwlmsend/ built-in standard out capture

glance_* No equivalent

sg_pkg_active (Serviceguard integration) Conditional policies use a built-in equivalent

prmrun/prmmove gwlmplace

The manpages for these commands are avai lable from the following websites:

WLM: http:/ / www.hp.com/ go/ wlm, in the Information library

gW LM: http:/ / docs.hp.com/ en/ vse.html

System requirements for gW LM

gW LM is a component of the Virtual Server Environment Management Software suite. For information

on system requirements for this suite, see the VSE Management Software Installation and UpdateGuideavailable from:

http:/ / docs.hp.com/ en/ vse.html

Common gWLM tasks

For information on how to accomplish common gWLM tasks, see the document HP Global WorkloadManager Version 4.0 Users Guideavailable from:

http:/ / docs.hp.com/ en/ vse.html

Examples of gW LM tasks discussed include:

Fixing the amount of CPU resources a workload gets Resizing a workloads compartment as needed, based on the workloads utilization


7/32

7

Migrating W LM configurations

The gWLM management model has a central management server, or CMS, and the managed

systems, or nodes. The CMS must have HP Systems Insight Manager (SIM) and gW LM installed,

while managed nodes need only gW LM agent software installed. To manage a system with gWLM,

you define a shared resource domain (SRD) to contain workloads on that system. You can use existing

workloads or create new ones. Each workload needs a policy to govern its resource allocation. You

can choose a policy from the collection of policies that come with gWLM or create new ones. You

can apply a single policy to multiple workloads. If you update a policy definition, that update isautomatically used to govern resource allocations for all workloads associated with the policy. The

gW LM interface in HP SIM provides a wizard to step you through the creation of SRDs, workloads,

and policies.

HP recommends using the gWLM interface in HP SIM to configure gW LM. However, you can also

configure gW LM using XML-based files. You create these files according to the syntax described in

the gwlmxml(4) manpage and then import and deploy them using the /opt/gwlm/bin/gwlm

command, described in the gwlm(1M) manpage.

To convert WLM configurations:

1. Determine whether the systems designated to be the CMS and managed nodes can support the

system requirements of HP SIM and gW LM (for the CMS) or just gWLM (for the managed nodes).Find alternate systems if needed. Install HP SIM and gW LM.

2. Determine the policies to use in place of the SLOs in your W LM configurations.

Both WLM and gW LM provide:

Fixed SLOs (policies)

Utilization SLOs (policies)

Metric-based SLOs (policies) (In gW LM, metric-based policies are available as custom policies.)

gW LM also provides an OwnBorrow policy type, which is based on utilization, that lets you

explicitly indicate how much of a resource a workload should own as well as how much it should

be allowed to borrow and lend.

gW LM comes with a library of polices (SLOs) for you to use. Check whether the provided policies

meet your needs. If not, create the appropriate policies.

3. Create your SRD using the gW LM Manage Systems and W orkloads wizard.

For each system to be managed by gWLM, use the wizard to enter the system name and define

the workloads and policies. The wizard produces an SRD and immediately begins managing the

workloads for the specified system.

To access the wizard in HP SIM:

a. Select

Tools > VSE Management

b. Click the Shared Resource Domain tab

c. Select the menu item

Create > Shared Resource Domain

Once you have an SRD deployed, you can monitor your workloads by selecting items in the Reports

menu. You can also monitor workloads on the command line using gwlm monitor. (In WLM, when

you are working with FSS-based workload groups or PSET-based workload groups, you have a

default group, PRM_SYS, for system processes. gW LM monitoring tools do not show PRM_SYS.

However, activity in PRM_SYS may still affect the resources available to the workloads you define.)


8/32

8

Migration example: FSS-based workloads with usage goals

WLM and gW LM both provide usage goals. However, in gW LM, the usage goal is known as a

utilization policy.

The WLM configuration

The example below splits an 8-core server into two FSS-based workload groups, each sized by CPU

utilization. Each group gets a minimum of one core and maximum of seven cores. Application records

place a few applications in the workload groups.

prm {groups = app_dev_grp : 2,

db_dev_grp : 3;

# place a custom binary and perl script into app_dev_grp,# shell script and oracle instance into g3apps = app_dev_grp : /opt/perl/bin/perl "myperlscript.pl",

app_dev_grp : /opt/myapp/bin/myapp,db_dev_grp : /bin/sh "myscript.sh",db_dev_grp :

/oracle/u01/app/oracle/product/10.2.0/db_dev_1/bin/oracle "ora*MYINST*";}

slo slo2 {pri = 1;goal = usage _CPU;mincpu = 100;maxcpu = 700;entity = PRM group app_dev_grp;

}

slo slo3 {pri = 1;goal = usage _CPU;mincpu = 100;maxcpu = 700;entity = PRM group db_dev_grp;

}

tune {absolute_cpu_units=1; # 100 units is 100% of 1 CPU, not the whole server

}

Creating an equivalent gW LM configuration

To create an equivalent gWLM configuration, follow the steps below in HP Systems Insight Manager.

(For information on installing, configuring, and accessing VSE Management Software, such as

gW LM, in HP Systems Insight Manager, see the VSE Management Software Installation and Update

Guide, available from http:/ / docs.hp.com/ en/ vse.html.)

In a WLM configuration, you can optionally specify the default user workload group OTHERS. In thegW LM configuration though, the workload must be specified. It takes a name of the form

hostname.OTHER. The steps below reflect this requirement. Although gW LM provides a number ofpolicies you can use, the procedure below creates a new policy to match the behavior of the SLOs in

the WLM configuration. While the WLM configuration explicitly uses absolute CPU units, gW LM uses

such units by default.


9/32

9

1. From the Shared Resource Domain tab, select Create followed by Shared Resource Domain to start

the Manage Systems and Workloads wizard.

2. Specify, using the table or the Additional Hosts field, the host that will be divided into fss-basedworkloads. Then select the Next button.


10/32

10

3. Set Mode to Managed and select the Next button.

4. Select (new) in the Policy column dropdown to create a new policy.


11/32

11

5. Name the new policy and set its type to Utilization. Here the name chosen is

CPUUtil_Min1_Max7. Set the Min Size value to 1.0 to represent one core. Set the Max Size value

to 7.0 for seven cores. Then select the OK button. (Although WLM requires you to specify a

priority through the pri keyword, gW LM assigns a default priority of 100. You can change the

priority after selecting the Show advanced policy configuration options checkbox.)

6. Set Compartment Type to fss. The workload field, which used to be haiti2a, is now

haiti2a.OTHER.


12/32

12

7. Change the policy for the workload to the CPU_Utilization policy.

8. Select the Add button to add a row for another workload. Set the policy for the new workload to

the new policy CPUUtil_Min1_Max7 . Select (new) in the Workload column dropdown to create

the new workload.


13/32

13

9. Specify a name for the new workload, app_dev_wkld. To add application records for the

workload, set workload definition criteria to by executable in the dropdown. Then fill in the fields

and select [Add to definition]. The graphic below shows one application record, for

/ opt/ perl/ bin/ perl with an alternate name of myperlscript.pl, has already been added. A second

record, / opt/ myapp/ bin/ myapp, is being added. When finished defining the workload, select

OK.


14/32

14

10. You will see the same screen you saw in step 8. As in step 8, select the Add button to add a row

for the workload. Set the policy for the new workload to CPUUtil_Min1_Max7. Select (new) in

the Workload column dropdown to go to the page to create the new workload. Name the

workload db_dev_wkld. This workload, shown below, has application records for a shell script

and for an Oracle instance. Select OK after defining the workload.

11. Now continue creating the SRD. The workloads and policies are set, so select the Next button.


15/32

15

12. The final step of the wizard allows you to review the SRD. Select Finish to begin managing the

workloads.

13. After you select Finish, you are taken to the Shared Resource Domain tab.


16/32

16

The gW LM configuration file

gW LM can display an XML version of the configuration file using gwlm export. (You can also

configure gW LM using XML. For more information, see the gwlmxml(4) manpage.)

The following command was used to display the XML for this configuration:

gwlm export \--srd=haiti2a.srd \--workload=haiti2a.OTHER \

--workload=app_dev_wkld \--workload=db_dev_wkld \--policy=CPUUtil_Min1_Max7 \--policy=CPU_Utilization

The XML file is:

1.08.0

3.075.03.01.0

100

0.04.02.075.02.0

0.0100

/opt/perl/bin/perlmyperlscript.pl

/opt/myapp/bin/myapp

/bin/shmyscript.sh

/oracle/u01/app/oracle/product/10.2.0/db_dev_1/bin/oracleora*MYINST*


17/32

17

0.057.902.00

haiti2a.rsn.hp.com10

0.057.903.00


0.057.903.00



18/32

18

Migration example: FSS-based workloads with stretch goals

In WLM, you can create a stretch goal for a workload by defining multiple SLOs, at distinct priorities,

for the workload.

The W LM configuration

In this example, we have another 8-core server split into two FSS-based workload groups sized by

CPU utilization. Each group has a CPU resource allocation at priority 1 and at priority 2. The priority

1 SLOs guarantee the workloads four cores each. The priority 2 SLOs (stretch goals) allow a

workload to borrow any resources that go unused after the priority 1 SLOs are satisfied. The

configuration also sets a minimum allocation of one core and a maximum allocation of seven cores

for both workloads. It also has several application records.

prm {groups = apps_grp : 2,

db_grp : 3;

# place a custom binary and perl script into apps_grp,# shell script and oracle instance into g3apps = apps_grp : /opt/perl/bin/perl "myperlscript.pl",

apps_grp : /opt/myapp/bin/myapp,db_grp : /bin/sh "myscript.sh",

db_grp : /oracle/u01/app/oracle/product/10.2.0/db_dev_1/bin/oracle"ora*MYINST*";}

slo apps_base_slo {pri = 1;goal = usage _CPU;mincpu = 100;maxcpu = 400;entity = PRM group apps_grp;

}

slo db_base_slo {pri = 1;goal = usage _CPU;

mincpu = 100;maxcpu = 400;entity = PRM group db_grp;

}

slo apps_stretch_slo {pri = 2; # NOTE lower prioritygoal = usage _CPU;mincpu = 100;maxcpu = 700;entity = PRM group apps_grp;

}

slo db_stretch_slo {pri = 2; # NOTE lower priority

goal = usage _CPU;mincpu = 100;maxcpu = 700;entity = PRM group db_grp;

}

tune {absolute_cpu_units=1; # 100 units is 100% of 1 CPU, not the whole server

}


19/32

19






In a WLM configuration, you can optionally specify the default user workload group OTHERS. In the

gW LM configuration though, the workload must be specified. It takes a name of the form

hostname.OTHER.

In this configuration, use an OwnBorrow policy. This type of policy behaves similar to W LMs

combination of a base goal and a stretch goal. We will use a gW LM-provided policy for the

hostname.OTHER workload and create a policy for the two user-defined workloads. (Although W LMrequires you to specify a priority through the pri keyword, gWLM assigns a default priority of 100.

You can change the priority after selecting the Show advanced policy configuration options

checkbox when setting up policies. However, HP recommends accepting the default priori ty.) Also,

while the WLM configuration explicitly uses absolute CPU units, gWLM uses such units by default.




20/32

20

2. Specify, using the table or the Additional Hosts field, the host that will be divided into fss-based

workloads. Then select the Next button.

3. Set Mode to Managed and select the Next button.


21/32

21

4. Select (new) in the policy dropdown to create a new policy.

5. Name the new policy and set its type to OwnBorrow. Here the name chosen is Owns_3-Max_8.

This policy is for the user-defined workloads. Set the Min Size value to 1.0 for one core. Any

workload with this policy will get at least one core. Set the Owned Size (cores) value to 3.0 for

three cores. The associated workload gets these three cores whenever needed. Set Max Size

(cores) to 8.0. If other workloads are not using their resources, the associated workload can

borrow those resources up to a total of eight cores. Select OK when done.

6. Set Compartment Type to fss. (The name for the workload changes to haiti2a.OTHER.)

7. Set the policy for the .OTHER workload to the gW LM-provided policy Owns_2-Max_4.

8. Select the Add button to add a row for another workload. Set the policy for the second workloadto Owns_3-Max_8.


22/32

22

9. Select (new) to define the new workload. Define the workload (app_dev_wkld) in the same

manner as in the section Migration example: FSS-based workloads with usage goals on page 8.

Select the Add button to add a row for another workload. Set the policy for this workload to

Owns_3-Max_8 as well. Select (new) to define the new workload (db_dev_wkld) also in the

same manner as the example just cited. Then select the Next button.

10. The final step of the wizard allows you to review the SRD. Select Finish to begin managing the

workloads.


23/32

23



gW LM can display an XML version of the configuration fi le using gwlm export. (You can also



gwlm export \--srd=haiti2a.srd \--workload=haiti2a.OTHER \--workload=app_dev_wkld \--workload=db_dev_wkld \

--policy=Owns_3-Max_8 \--policy=Owns_2-Max_4

The XML file is:

1.07.075.01.0

1.0100

0.02048.075.01.01.0


24/32

24

100

/opt/perl/bin/perlmyperlscript.pl

/opt/myapp/bin/myapp

/bin/shmyscript.sh

/oracle/u01/app/oracle/product/10.2.0/db_dev_1/bin/oracle

ora*MYINST*

0.057.902.70


0.057.902.65


0.057.902.65



25/32


26/32

26






gW LM does not require the multiple configuration files that WLM does. Also, there is no need to set a

priority; you can simply accept the default.



2. Specify the host and all the remaining virtual partitions in the server or nPartition. Here, there are

six virtual partitions specified. Select the Next button when done.


27/32

27

3. Set the Mode to Managed. (Notice that gWLM automatically changed the Resource Allocation

Interval to 85. gW LM changes the interval based on the type of workloads being managed.)

Select the Next button.

4. Set the policy for each workload to the CPU_Utilization policy provided by gW LM. Select the Next

button.


28/32

28

5. The final step of the wizard allows you to review the SRD. Select Finish to manage the workloads.



29/32

29


gW LM can display an XML version of the configuration fi le using gwlm export. (You can also



gwlm export \--srd=haiti2a.srd \--workload=haiti2a \--workload=haiti2b \--workload=haiti2c \--workload=haiti2d \--workload=haiti2e \--workload=haiti2f \--policy=CPU_Utilization

The XML file is:

0.0

2048.075.01.01.0

100

1

83

haiti2a.rsn.hp.comZ3e11d5b8fdef7289_P2_V00Haiti_Complex_USE4514JRL_P2


30/32

30

182

haiti2b.rsn.hp.comZ3e11d5b8fdef7289_P2_V01Haiti_Complex_USE4514JRL_P2

182

haiti2c.rsn.hp.comZ3e11d5b8fdef7289_P2_V02Haiti_Complex_USE4514JRL_P2

18

2haiti2d.rsn.hp.comZ3e11d5b8fdef7289_P2_V03Haiti_Complex_USE4514JRL_P2

182

haiti2e.rsn.hp.comZ3e11d5b8fdef7289_P2_V04

Haiti_Complex_USE4514JRL_P2

182

haiti2f.rsn.hp.comZ3e11d5b8fdef7289_P2_V05Haiti_Complex_USE4514JRL_P2


31/32

31

Integrating with Security Containment

The HP-UX feature Security Containment provides file and process isolation and is avai lable starting

with HP-UX 11 i v2. Combining that isolation with gWLM workloads based on psets or fss groups, you

can form Secure Resource Partitions, which give your workloads both isolation and automatic

resource allocation.

To integrate the two products:

1. Configure Security Containment compartments outside gW LM and activate them.

2. Create your gW LM workloads.

The processes in the Security Containment compartments will go in these workloads. You have two

options to create the workloads:

Use Application Discovery to add an application to a monitored workload that you then

manage. This application should be the same one running in the Security Containment

compartment that you want to manage.

Define your workload using a process map you create. (A process map is an executable that

returns a set of process IDs separated by white space. The identified processes are placed in the

workload.) The process map should return a list of all the processes in the Security Containment

compartment.Each Security Containment compartment will have a process map associated with it to identify its

processes.

3. Deploy an SRD that uses the new workloads.


32/32

Licensing and availability

WLM and gW LM are both licensed on a per-core basis. Both are in the VSE Suite for Integrity Servers

bundle. Additionally:

WLM is available through the:

Mission-critical Operating Environment (HP-UX 11i v2)

VSE Operating Environment and Data Center Operating Environment (HP-UX 11i v3) Quarterly AR media

gW LM is available through the:

Foundation Operating Environment (HP-UX 11i v2) (includes the trial agent)

VSE Operating Environment and Data Center Operating Environment (HP-UX 11i v3)

Quarterly AR media (includes the CMS, as part of the VSEMgmt bundle, and the trial agent)

For information on obtaining gWLM, contact your HP sales representative or your HP authorized

partner.

For more information

The following sites provide high-level product information:

http:/ / www.hp.com/ go/ wlm

http:/ / www.hp.com/ go/ gwlm

http:/ / www.hp.com/ go/ vse

The following white paper, HP Global Workload ManagerImproving server CPU utilizationtechnical overview, provides a number of use cases:

http:/ / h71028.www7.hp.com/ ERC/ downloads/ 5983-0505EN.pdf

The following site provides technical documentation for WLM, gW LM, and VSE Management

Software:http:/ / docs.hp.com/ en/ vse.html

2007-2008 Hewlett-Packard Development Company, L.P. The informationcontained herein is subject to change without notice. The only warranties forHP products and services are set forth in the express warranty statementsaccompanying such products and services. Nothing herein should be construedas constituting an additional warranty. HP shall not be liable for technical oreditorial errors or omissions contained herein.

wlm gwlm migration

Documents