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

NOTE: HP-UX 11.00 and HP-UX 10.20 environments usually work inside HP 9000 containers,
but these environments are not officially supported.
1.3 HP 9000 container types
HP 9000 Containers A.03.01 allows you to create two container types: HP 9000 system containers
(feature-rich) and HP 9000 classic containers (for compatibility with HP 9000 Containers A.01.0x).
Table 2 (page 10) lists the differences between the two types.
Table 2 Differences between HP 9000 system container and HP 9000 classic container
HP 9000 classic containerHP 9000 system container
Does not support inetd services (access only through SSH
based protocols)
Supports inetd services (access to container through
telnet, ftp, rlogin, remsh, and rexec [no telnet
yet for HP-UX 10.20])
Supports SSH based access even if SSH is not configured
in the HP 9000 image
Supports SSH based access only if SSH is available in the
HP 9000 image
Supports only non-SD patching inside the containerSupports SD patching inside the container
Only one classic container is supported on an HP-UX
instance
Can coexist with other HP 9000 system containers on the
same HP-UX instance
Cannot coexist with native HP-UX containersCan coexist with native HP-UX containers
A part of the HP 9000 file system is shared with the host
(mainly /etc, /dev, /tcb, and parts of /var)
Has private HP 9000 file system
User management is performed on the host systemSupports user management inside the container
Some commands report system-wide information inside
container
Most commands report container-related information inside
container
Supports partial run level inside containerSupports run level inside container
Does not support mount inside containerSupports mount inside container
SG integration is supported only in the application package
model
Supports SG integration in both SRP package and
application package models
User quotas can be enabled because user management is
performed on the host system
Does not support user quotas
Trusted mode support is similar to that on a native system
(managed entirely from the host)
Supports trusted mode inside container (with some
differences compared to native system)
HP SMH or SAM can be used from the host to manage
users
Does not support HP SMH or SAM to manage users
1.4 When to use HP 9000 Containers
HP 9000 Containers can be considered for transition when the following criteria are met:
• When upgrading or porting applications to native Integrity version is infeasible.
• If the license agreement for ISV software allows copying application-related files to a new
platform (or license can be migrated).
• If ISV supports the application on ARIES, or if ISV support is not a critical requirement for the
customer.
• If the applications to be transitioned are pure user-space and not related to system
administration or management.
• When traditional ARIES based migration is costly due to one or more of the following reasons:
10 Introduction