HP 9000 Containers A.03.01 on HP Integrity Server Administrator Guide HP-UX 11i v3 (5900-3112, June 2013)

Complete information about the application inventory such as list of applications,
executables, libraries, configuration files, or dependencies is not available.
◦
◦ The number of servers targeted for migration is large and resources are limited to carry
out individual application transition.
◦ There is a dependency on legacy stand-alone development environments, which are not
supported by HP XPADE. For more information about HP XPADE, see http://www.hp.com/
go/xpade.
• When the limitations of HP 9000 Containers are acceptable. For more information about
limitations, see Chapter 11 (page 73).
• When it is possible to perform a detailed Proof-of-Concept testing prior to moving to production.
This testing is required because latent application or emulation defects might get exposed in
the container environment.
1.5 Consolidating HP 9000 servers using HP 9000 Containers
Multiple options are available for consolidating HP 9000 servers using HP 9000 Containers:
• Use multiple HP 9000 system containers.
• Use HP 9000 containers in HP Integrity VM guests.
• Use HP 9000 containers in HP-UX vPars.
Multiple HP 9000 system containers can be used when the following conditions are satisfied:
• Complete isolation of application environments is not required (multiple containers share the
same kernel).
• Dynamic migration of resources (memory and CPU) is not needed.
• Online migration is not needed at container level.
• There are no conflicting requirements for kernel tunable parameters.
• There are no conflicting manageability requirements (management applications must run on
the host system in the global container).
• Application downtimes can be coordinated easily when the server needs a reboot.
• Enough resources (memory, CPU) are available to account for emulation overhead.
• Some legacy 32-bit PA-RISC applications require the kernel tunable parameter shmmax to be
less than 0x40000000. This limits the number of applications that can be stacked together if
the applications use shared memory.
• Concurrent processes on a system hosting legacy containers is not more than 30000 (large
PIDs cannot be supported with legacy commands and applications).
1.6 Sizing an HP 9000 container
The guidelines to size an HP 9000 container (accounting for the ARIES emulation overhead and
also for the loss in performance because the applications were not compiled to take advantage
of the Itanium processor architecture) are as follows:
• ARIES might incur an average memory overhead of 10 MB per process. To compute the total
requirement, find the number of processes that concurrently run on the HP 9000 server at
peak load and account for an additional 10 MB for each of them. You must consider all the
processes that run on the HP 9000 server at peak load, including processes related to user
sessions, which are also emulated in the container.
• HP-UX 11i v3 kernel has a larger memory foot print (more than 20%) compared to earlier
versions, which must be accounted.
1.5 Consolidating HP 9000 servers using HP 9000 Containers 11