HP-UX Containers (SRP) A.03.00 Release Notes

3. Verify that all containers have been successfully migrated and are recognized by the system:

# srp –status

The migrated workload containers will be in the stopped state by default.

4. HP-UX Containers Version A.03.00 delivers new default configuration in the following

configuration files:

/etc/opt/hpsrp/cmpt/base.srp_incl

/etc/opt/hpsrp/templates/srpdefaults.cst

If you have modified these two configuration files in A.02.02, then you need to manually

incorporate your A.02.02 changes into the A.03.00 version of these two files. The A.02.02

version of these files will be renamed to base.srp_incl.old and

srpdefaults.cst.old if they have been modified previously before the upgrade.

1.7 Limitations for HP-UX Containers A.03.00

When the HP-UX Containers A.03.00 bundle is installed on the system, the following features

will not be available:

1. HP-UX Containers is not supported on a system with Trusted Systems enabled.

2. The HP-UX WhiteListing product cannot be installed on a system with HP-UX Containers

A.03.00 installed.

3. Installation from a remote network registered SD depot is not supported for software

installation. See the HP-UX Containers (SRP ) A.03.00 Administrator’s Guide for alternative

options.

4. Only the non-interactive command line interface (CLI) for the SD commands is supported

when one or more system containers are configured.

5. Creating a golden image using Ignite-UX with system containers configured on the system is

not supported.

6. DRD clone and modifications with system containers configured on the system is not

supported.

7. Update-UX with system containers configured on the system is not supported.

1.8 Restrictions on system containers

System containers provide the image of an individual system with its own root file system, system

services, hostname, private user/group management that enable similar or different workloads to

execute independently on the same physical system. Although each system container appears to be a

separate system to the local user, all system containers are executing within a single instance of the

operating system and share hardware resources for efficient use. To protect one system container from

affecting other containers or the system as a whole, certain restrictions are in place. These restrictions

may lead to behavioral differences in a system container when compared to an individual physical

system.