HP-UX Containers (SRP) A.03.01 Administrator's Guide

2 Installing HP-UX Containers

You can acquire and install HP-UX Containers free of charge from HP Software Depot:

http://www.software.hp.com

For system and environment requirements, see the HP-UX Containers (SRP) A.03.01 Release Notes

located at:

www.hp.com/go/virtualization-manuals

Select the HP-UX Containers (SRP) Software product.

2.1 Upgrading to HP-UX Containers A.03.01

If your system has an operating system older than HP-UX 11i, March 2011 Release, then you must

first update your system to March 2011 (or later) before installing HP-UX Containers A.03.01.

HP-UX Containers A.03.01 supports upgrade from HP-UX SRP A.02.02 only. If you have workload

SRPs configured using HP-UX SRP A.02.02 and you need to continue using them, you can migrate the

workload SRPs to workload containers after the upgrade.

For more information about updating your system from HP-UX SRP A.02.02 with existing containers

configured, please refer to the HP-UX Containers (SRP) A.03.01 Release Notes.

2.2 Resource considerations for containers

The system container with shared file system requires a minimum of 4.5 GB disk space and the system

container with private file system subtype requires minimum of 9.0 GB disk space. The workload

container requires 700 KB disk space (see 1.5 Container types and 14 Container types for a

description of container types). Other than additional disk space, containers do not have any

hardware or additional capacity requirements.

Memory, CPU, nprocs, nfiles, and nthreads have the same settings as those used for hosting

the same set of applications without containers. The kernel tunable adjustment may be required when

the system hosts a larger set of workloads.

There is a negligible additional overhead in terms of processes and virtual memory consumed for a

started system container that has no additional applications deployed. Containers that are not started

or active do not require resources with the exception of disk space.

NOTE: Processor cores assigned to a container using PRM as PSET are completely dedicated and will

not be available for other use, even if the container is in the stopped state.