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

45
You can use the following notation to assign a value to a variable:
name=value, name='value', or name="value"
6.9.3 Best practices for exporting and importing a container
To simplify the export and import of a container across systems, HP recommends you to keep the
properties of containers atomic by not sharing files and data with other containers unnecessarily. The
following are the best practices for using the srp –export and srp -import commands:
• Maintain consistent OS versions and patch levels across systems
System containers require consistent OS versions and patch levels across the systems where a
container is being cloned. For workload containers, HP-UX Containers have minimal
requirements for OS levels and patches to be synchronized across systems, applications
utilized within the containers may have more specific requirements. By maintaining
consistency across systems, you will not have to manually track application dependencies
when determining a target system for the container to import.
• Consider using shared storage or file systems when creating a container that
will be cloned
For workload containers: By using shared storage for a container’s home directory and any
file systems mounted within the container, you will not need to export and import file sets,
and the data between containers will remain consistent.
For system containers: Containers should only share application directories and data across
systems.
• Keep files and directories used by the container within the container’s home
directory
For workload containers: locating files within the container home directory
(/var/hpsrp/container_name) will simplify exporting or mounting container file sets. For
system containers: All container files and directories must be located inside the container
home directory.
• Avoid cross-compartment security relationships
If you customize the container’s compartment configuration to include access rules specifying
other compartments, the other compartments must exist on the target system where the
container will be imported.
• Synchronize or centralize user and group management
For workload containers: By ensuring that all HP-UX Containers installed systems have the
same users and groups, a container’s login user and groups, as well as file and directory
ownership, will be consistent after importing a container to a different target system.
Consider defining a single group for all users of a given workload container.
For system containers: By ensuring that all system containers and the global view share the
same user and group definitions, mapping of user and group IDs to names from the global
view will be consistent with that of each system container.