aix workload partions - ibmpublic.dhe.ibm.com/systems/power/community/aix/central... · 2013. 5....

© 2008 IBM Corporation

AIX Workload Partions

Viraf [email protected]

2

IBM Systems Group


Agenda

Introduction to AIX Workload Partitions (WPAR)

WPAR characteristics and positioning

System WPARs

Application WPARs

WPAR administration

Summary

3

IBM Systems Group


What are AIX Workload Partitions?Created via software as virtualized environments in a single AIX instance

Partitioned system capacity Each Workload Partition obtains a regulated share of the processor and memory resources

Each Workload Partition has separate network and filesystems and many system services (e.g. telnetd, etc.)

Separate Administrative controlEach Workload partition is a separate administrative and security domain

Shared system resourcesI/O DevicesProcessorOperating systemShared Library and Text

WorkloadPartitionApp Svr

WorkloadPartitionWeb Svr

WorkloadPartition

Billing Svr

AIX Image

WorkloadPartitionTest Svr

WorkloadPartition

E

4

IBM Systems Group


Single System or

LPAR

Sys1

Sys2

Sys3

Application AApplication BApplication C

Benefits of IBM AIX Workload Partitions

AIX Partition #1

AIX Partition #2

AIX Partition #3

reduced administration expense by leveraging a single AIX imagedrive higher system utilizationreduce the number of system images to maintain“good enough” isolation for many workloads

5

IBM Systems Group


AIX Workload Partitions can be used in LPARs

LPARAsia

LPAR LPAREMEA

LPARAmericas

VIOServer

MicroPartition Processor PoolDedicated Processor

LPARFinance

Dedicated Processor

LPARPlanning

POWER Hypervisor

WPAR #1Bus Dev

WPAR #1MFG

WPAR #2Planning

WPAR #1eMail

WPAR #2Test

WPAR #3Billing

IBM Systems Group

© 2007 IBM Corporation6

IBM System p5 Flexible Resource Management

AIX Workload Partitions complement System p5 Logical Partitions

Workload Isolation

Eas

e of

Adm

inis

tratio

n

Workload Manager

Dedicated Processor

LPAR

MicroPartitionLPAR

AIXWorkloadPartitions

IBM Systems Group


WPAR Implications

What workloads to use on WPARs?Need for dedicated I/O resourcesIsolation and security

Security/backup/management standards for WPARs

When to use Application WPARs versus System WPARs

IBM Systems Group


Technologies for server consolidation pain points

Workload PartitionsClient needs to consolidate multiple workloads on a single system for highest efficiency and minimize the number of AIX operating systems to manage

Application Mobility

Partition Mobility

Partition Mobility orApplication Mobility

MicroPartitions

MicroPartitions orWorkload Partitions

MicroPartitions

AIX Technology

Client needs automatic, policy based relocation of workloads between systems

Client needs to balance workloads by relocating workloads between systems with minimum delay

Client needs to balance workloads by relocating workloads between systems

Client needs to consolidate multiple workloads on a single system for highest efficiency and maximize the flexibility to support different environments

Client needs to consolidate multiple workloads on a single system for highest efficiency

Client workload requires the maximum amount of isolation between workloads on a single server

Pain point

IBM Systems Group


When to use Workload Partitions

x

x

x

x

Workload Partitions

xMove workload between systems

xCross system workload management

xGreatest FlexibilityxServer Consolidation

Minimal number of AIX images

xHardware enforced Isolation

MicroPartitionsRequirement

IBM Systems Group


WPAR Terminology

Global environment

Checkpoint and restart

Mobility

Departure system

Arrival system

IBM Systems Group


WPAR Types

There are 2 types of WPARSSystem WPARApplication WPAR

Both WPAR type can be configured for mobility via the AIX Workload Partition Manager product

IBM Systems Group


Characteristics of WPARs

DevicesManaged and administered in the global environment Support pseudo-devices in WPARs

NetworkingSupport multiple addresses for login and network servicesWPARs IP address is aliased to IP address in the global

environmentConfigurable at creation time or later

SecurityLimited interaction with global environmentLimited interaction with persistent objects

IBM Systems Group


Characteristics of WPARs

WPAR isolationSystem WPARs and application WPARs are isolated from each otherSystem WPARs are integrated with AIX RBAC facility which is not true for Application WPARs

Resource ControlAbility to change resources dynamically within a WPARAllows share based allocation or percentage based

allocation for processor and memory resources

IBM Systems Group


Devices in a WPAR

Unavailable/dev/mem/dev/nvram

Storage available from global environment via a mounted file system

Network addressing through IP address aliasing from the global environment

IBM Systems Group


WPAR filesystem

System WPAR localized view of filesystem//usr/opt/tmp/var/home

3 primary forms of file system accessShared-system

– /usr and /opt are shared read-only from the global environment via namefs mounts

nfs hosted– Set of fs’s which can include /usr and /opt mounted ro or rw via a nfs host server

Non-shared– /usr and /opt are separate local filesystems (jfs/jfs2) within the WPAR

IBM Systems Group


Specification file

To use a specification file to create a system WPARmkwpar -f /tmp/specfile1

To create a specification file as part of the WPAR creation process

mkwpar -n wpar_name -o /tmp/specfile

To generate a specification file without creating the WPAR, mkwpar -o /tmp/specfile3 -w

/usr/samples/wpars/sample.spec file.

IBM Systems Group


Attributes before creating system WPAR

root@sq18 (/) > oslevel -s6100-00-00-0000

root@sq18 (/) > uname -aAIX sq18 1 6 00C1677E4C00

root@sq18 (/) > df -kFilesystem 1024-blocks Free %Used Iused %Iused Mounted on/dev/hd4 131072 99376 25% 1798 7% //dev/hd2 1703936 283116 84% 33477 34% /usr/dev/hd9var 196608 183904 7% 440 2% /var/dev/hd3 196608 195828 1% 18 1% /tmp/dev/hd1 917504 917000 1% 7 1% /home/proc - - - - - /proc/dev/hd10opt 786432 730492 8% 1108 1% /opt/dev/fslv00 2097152 1394432 34% 482 1% /0728a

Can create WPARs using specification file or image.data filemkwpar –o /tmp/spec1 –w (generate specification file)mkwpar –I image.data file –n wpar_name

IBM Systems Group


Attributes before creating system WPAR

root@sq18 (/) > netstat -niName Mtu Network Address ZoneID Ipkts Ierrs Opkts Oerrs Collen0 1500 link#2 0.9.6b.dd.43.ba 4777662 0 560011 4 0en0 1500 9.19.51 9.19.51.54 4777662 0 560011 4 0lo0 16896 link#1 83775 0 83786 0 0lo0 16896 127 127.0.0.1 83775 0 83786 0 0lo0 16896 ::1 0 83775 0 83786 0 0

root@sq18 (/) > ifconfig en0en0:

flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>

inet 9.19.51.54 netmask 0xffffff00 broadcast 9.19.51.255tcp_sendspace 131072 tcp_recvspace 65536

Note :- you can edit /etc/hosts and insert entry for new WPARs - you can use clogin from global environment to access wpar

IBM Systems Group


Creating System WPARroot@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec10 T A ec10 /ec12 A S ec12 /wpars/ec12

root@sq18 (/) > mkwpar -n ec09mkwpar: Creating file systems...

//home/opt/proc/tmp/usr/var

…………mkwpar: Workload partition ec09 created successfully.To start the workload partition, execute the following as root: startwpar [-v] 'ec09‘

root@sq18 (/) > startwpar -v ec09Starting workload partition ec09.

Invalid Script File...Mounting all workload partition file systems

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec09 A S ec09 /wpars/ec09ec10 T A ec10 /ec12 A S ec12 /wpars/ec12

IBM Systems Group


rootvg – before WPAP is created

root@sq18 (/wpars) > du -k /wpars0 /wparsSpace required is abt 384 Mbyes for a WPAR

IBM Systems Group


rootvg after WPAR is created

root@sq18 (/) > du -k /wpars 1849472 /wpars/ec091849472 /wpars

IBM Systems Group


Creating WPAR on P5 system

root@sq18 (/) > lswparroot@sq18 (/) > mkwpar -n ec20mkwpar: Creating file systems...

//home/opt/proc/tmp/usr

/var……….

root@sq18 (/) > clogin ec20Workload partition ec20 is not active.

root@sq18 (/) > startwpar -v ec20Starting workload partition subsystem cor_ec20Return Status = SUCCESS

root@sq18 (/) > clogin ec20*************************************************************************************************** ** ** Welcome to AIX Version 6.1! ** ** ** Please see the README file in /usr/lpp/bos for information pertinent to ** this release of the AIX Operating System. ** ** ***************************************************************************************************

mkwpar: Workload partition ec20 created successfully.To start the workload partition, execute the following as root: startwpar [-v] 'ec20'

real 3m57.74suser 1m30.02ssys 0m48.23s

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec20 A S ec20 /wpars/ec20

IBM Systems Group


Creating WPAR on a P6 system

# lswparName State Type Hostname Directory-----------------------------------------ec08 D S ec08 /wpars/ec08

# time mkwpar -n ec30mkwpar: Creating file systems...

//home/opt/proc/tmp/usr/var

………………

mkwpar: Workload partition ec30 created successfully.To start the workload partition, execute the following as root: startwpar [-v] 'ec30'

real 4m0.22suser 1m4.13ssys 0m37.17s

IBM Systems Group


Creating WPAR on a P6 system - SMIT

IBM Systems Group


Creating WPAR on a P6 system – Systems Director AIX Console

IBM Systems Group


Starting WPARs# startwpar -v ec09Starting workload partition ec09.

Invalid Script File...Mounting all workload partition file systems.Mounting /wpars/ec09.Mounting /wpars/ec09/home.Mounting /wpars/ec09/opt.Mounting /wpars/ec09/proc.Mounting /wpars/ec09/tmp.Mounting /wpars/ec09/usr.Mounting /wpars/ec09/var.Loading workload partition.$corral_t = {

'vips' => [['en0','9.19.51.136','255.255.255.0','9.19.51.255'

]],

'opts' => 4,'name' => 'ec09','path' => '/wpars/ec09','hostname' => 'ec09','id' => 0,'key' => 7

};Exporting workload partition devices.Starting workload partition subsystem cor_ec09.0513-059 The cor_ec09 Subsystem has been started. Subsystem PID is 405548.Verifying workload partition startup.Return Status = SUCCESS.

IBM Systems Group


Viewing WPARs from global environment

root@sq18 (/) > cd /wparsroot@sq18 (/) > lsec08 ec09

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec09 A S ec09 /wpars/ec09ec10 A S ec10 /wpars/ec10ec11 A S ec11 /wpars/ec11

IBM Systems Group


Viewing WPARs filesystems from global environment

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec09 A S ec09 /wpars/ec09ec10 T A ec10 /ec12 A S ec12 /wpars/ec12

root@sq18 (/) > df -kFilesystem 1024-blocks Free %Used Iused %Iused Mounted on/dev/hd4 131072 69524 47% 1820 9% //dev/hd2 1703936 283080 84% 33479 34% /usr/dev/hd9var 196608 183652 7% 452 2% /var/dev/hd3 196608 195804 1% 38 1% /tmp/dev/hd1 917504 917000 1% 7 1% /home/proc - - - - - /proc/dev/hd10opt 786432 730492 8% 1108 1% /opt/dev/fslv00 2097152 1394432 34% 482 1% /0728a/dev/fslv01 65536 46372 30% 1631 14% /wpars/ec12/dev/fslv02 65536 64136 3% 7 1% /wpars/ec12/home/opt 786432 730492 8% 1108 1% /wpars/ec12/opt/proc - - - - - /wpars/ec12/proc/dev/fslv03 131072 128348 3% 13 1% /wpars/ec12/tmp/usr 1703936 283080 84% 33479 34% /wpars/ec12/usr/dev/fslv04 131072 118728 10% 395 2% /wpars/ec12/var/dev/fslv05 65536 46964 29% 1631 14% /wpars/ec09/dev/fslv06 65536 64136 3% 7 1% /wpars/ec09/home/opt 786432 730492 8% 1108 1% /wpars/ec09/opt/proc - - - - - /wpars/ec09/proc/dev/fslv07 131072 128348 3% 13 1% /wpars/ec09/tmp/usr 1703936 283080 84% 33479 34% /wpars/ec09/usr/dev/fslv08 131072 118756 10% 396 2% /wpars/ec09/var

IBM Systems Group


WPAR listing and ip address aliasing view

lswparName State Type Hostname Directory-----------------------------------------ec09 A S ec09 /wpars/ec09ec10 A S ec10 /wpars/ec10

netstat -niName Mtu Network Address ZoneID Ipkts Ierrs Opkts Oerrs Collen0 1500 link#2 0.9.6b.dd.43.ba 3119936 0 433744 4 0en0 1500 9.19.51 9.19.51.54 3119936 0 433744 4 0en0 1500 9.19.51 9.19.51.136 8909 0 10740 0 0en0 1500 9.19.51 9.19.51.137 1067 0 2045 0 0lo0 16896 link#1 20997 0 21007 0 0lo0 16896 127 127.0.0.1 20997 0 21007 0 0lo0 16896 ::1 0 20997 0 21007 0

ifconfig en0en0:

flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>

inet 9.19.51.54 netmask 0xffffff00 broadcast 9.19.51.255inet 9.19.51.136 netmask 0xffffff00 broadcast 9.19.51.255inet 9.19.51.137 netmask 0xffffff00 broadcast 9.19.51.255tcp_sendspace 131072 tcp_recvspace 65536

lswpar -N ec08Name Interface Address Netmask Broadcast---------------------------------------------------------ec08 en0 9.19.51.154 255.255.255.0 9.19.51.255

IBM Systems Group


Application WPARs

Provide path to the application or command that requires the application WPAR

Use specification file or command line argument

Not necessary to specify WPAR name explicitly at creation

IBM Systems Group


Creating Application WPARs

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec12 A S ec12 /wpars/ec12

root@sq18 (/) > wparexec -n ec10 /usr/local/loadgen -t 10 /usr/bin/ps –ef > ps.outwparexec: Verifying file systems...wparexec: Workload partition ec10 created successfully.

Invalid Script File...

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec10 A A ec10 /ec12 A S ec12 /wpars/ec12

root@sq18 (/) > clogin ec10

root@ec10 (/) > uname -aAIX ec10 1 6 00C1677E4C00

IBM Systems Group


Application WPAR listing and ip address aliasing view

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec10 A A ec10 /ec12 A S ec12 /wpars/ec12

root@sq18 (/) > netstat -niName Mtu Network Address ZoneID Ipkts Ierrs Opkts Oerrs Collen0 1500 link#2 0.9.6b.dd.43.ba 5196841 0 569426 4 0en0 1500 9.19.51 9.19.51.54 5196841 0 569426 4 0en0 1500 9.19.51 9.19.51.139 1540 0 1073 0 0en0 1500 9.19.51 9.19.51.137 9 0 0 0 0lo0 16896 link#1 91272 0 91289 0 0lo0 16896 127 127.0.0.1 91272 0 91289 0 0lo0 16896 ::1 0 91272 0 91289 0 0

root@sq18 (/) > ifconfig en0en0: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>

inet 9.19.51.54 netmask 0xffffff00 broadcast 9.19.51.255inet 9.19.51.139 netmask 0xffffff00 broadcast 9.19.51.255inet 9.19.51.137 netmask 0xffffff00 broadcast 9.19.51.255tcp_sendspace 131072 tcp_recvspace 65536

IBM Systems Group


Removing WPARs

# rmwpar ec09rmwpar: Workload partition 'ec09' is running.rmwpar: Specify -s or -F to stop the workload partition before removing.rmwpar: Return Status = FAILURE

# rmwparA workload partition name must be specified.Usage: rmwpar [-F] [-p] [-s] wparNameFlags:

-F = Forced remove. The '-s' flag is implied.-p = Preserve file systems (system workload partitions only).-s = Stops the workload partition before removing (system workload partitions

only - application workload partitions should use the stopwpar command).

IBM Systems Group


Removing WPARs

# rmwpar -s ec09rmwpar: Removing workload partition ec09rmwpar: Stopping workload partition ec09Stopping workload partition ec09.Stopping workload partition subsystem cor_ec09.0513-044 The cor_ec09 Subsystem was requested to stop.stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.Advanced Accounting is not running.stopwpar: 0960-231 ATTENTION: /usr/lib/wpars/wparinstcmd failed with return code 1.Shutting down all workload partition processes.

IBM Systems Group


Removing WPARs

# rmwpar -F ec09rmwpar: Removing workload partition ec09rmwpar: Stopping workload partition ec09stopwpar: 0960-254 Workload partition ec09 is not currently active.rmwpar: Removing file system /wpars/ec09/var.rmlv: Logical volume fslv08 is removed.rmwpar: Removing file system /wpars/ec09/usr.rmwpar: Removing file system /wpars/ec09/tmp.rmlv: Logical volume fslv07 is removed.rmwpar: Removing file system /wpars/ec09/proc.rmwpar: Removing file system /wpars/ec09/opt.rmwpar: Removing file system /wpars/ec09/home.rmlv: Logical volume fslv06 is removed.rmwpar: Removing file system /wpars/ec09.rmlv: Logical volume fslv05 is removed.rmwpar: Return Status = SUCCESS

# lswparName State Type Hostname Directory-----------------------------------------ec08 D S ec08 /wpars/ec08

IBM Systems Group


WPAR administration – backup and restore

WPARs are backed up using the “mkwpardata” command

Image files are generated using the “savewpar” command

WPARs are restored using “restwpar” commandroot@sq18 (/) > restwpar -f /dev/rmt1

root@sq18 (/) > lswparName State Type Hostname Directory-----------------------------------------ec12 A S ec12 /wpars/ec12root@sq18 (/) > savewpar ec12

0512-057 savewpar: Device /dev/rmt0 is not in the available state or is not a tape device or valid file name.

IBM Systems Group


Summary

WPARs reduce administration expense by leveraging a single AIX image

LPARs and WPARs drive higher system utilization and optimize the customers investment

WPARs provide dynamic resource allocation capabilities

WPARs provide “good enough” isolation for many workloads

Simple, lightweight, centralized partition administration

aix workload partions - ibmpublic.dhe.ibm.com/systems/power/community/aix/central... · 2013. 5....

Documents