Software Installation With Provisioning System; Zone Migration Among Systems - Sun Microsystems SOLARIS 10 Manual

Version 3.1-en
Solaris 10 Container Guide - 3.1 5. Cookbooks

5.3.4. Software installation with provisioning system

[ug] The N1 SPS software can provision software in zones as well. The requirements are:
A writable directly where the software can be installed. This can be / op t . / op t is not
allowed to be configured as i n h e r i t - pk g -d ir in this case.
If the software need to be installed under / us r or in a different system directory, this can be
implemented either with a whole-root zone or with a writable directory (e.g. / us r/ l oc al )
available in the / u s r - tree (created with zonecfg:add fs).
The software needs to be able to run in a zone (see above).

5.3.5. Zone migration among systems

[dd] Starting with Solaris 10 11/06, zones can be moved among physical systems. This can be
achieved with z o n e a d m d e t a c h / a t t a c h . The following conditions must be observed before
zones can be migrated:
Zones must be stopped prior to migration
The patch and package status between the two systems must be identical
A local zone can be migrated as follows between systems:
Detach the zone with z o n e a d m - z < zo n e> d e ta ch
Move the z o n e p a t h directory to the target system, e.g. in the SAN or with ta r/ c p
Set up the zone configuration z o n e c f g -z <z on e > cr e at e -a <z on e pa th >
Attach the zone z o n e a d m - z < z o n e > at t ac h
An installed local zone is detached prior to migration. This process generates all information required
to attach this zone
< zo nep at h> / S U N W d e t a c h e d . x m l .
" in sta ll ed " to " c o n f i g u r e d " . Thus, this zone will subsequently no longer be considered
for package installations, patches, booting, etc.
Prior to attaching, the zone configuration can be generated from the SU N Wd et a ch ed . xm l file.
Running at tac h will check on the target system whether the local zone fits on the target system. In
addition, it is checked whether the installed packages and patches in the migrated zone and the
global zone of the target system have the same version.
to another system.
The
The information is
status of the zone
Effective: 30/11/2009
stored in the file
is converted from
97