Sun Microsystems 10 User Manual
Version 3.1-en
Solaris 10 Container Guide - 3.1 5. Cookbooks
Effective: 30/11/2009
5.3.4. Software installation with provisioning system
[ug] The N1 SPS software can provision software in zones as well. The requirements are:
[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 /opt. /opt is not
allowed to be configured as inherit-pkg-dir in this case.
allowed to be configured as inherit-pkg-dir in this case.
•
If the software need to be installed under /usr or in a different system directory, this can be
implemented either with a whole-root zone or with a writable directory (e.g. /usr/local)
available in the /usr-tree (created with
implemented either with a whole-root zone or with a writable directory (e.g. /usr/local)
available in the /usr-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 zoneadm detach/attach . The following conditions must be observed before
zones can be migrated:
[dd] Starting with Solaris 10 11/06, zones can be moved among physical systems. This can be
achieved with zoneadm detach/attach . 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 zoneadm -z <zone> detach
•
Move the zonepath directory to the target system, e.g. in the SAN or with tar/cp
•
Set up the zone configuration zonecfg -z <zone> create -a <zonepath>
•
Attach the zone zoneadm -z <zone> attach
An installed local zone is detached prior to migration. This process generates all information required
to attach this zone to another system. The information is stored in the file
<zonepath>/SUNWdetached.xml. The status of the zone is converted from
"installed" to "configured". Thus, this zone will subsequently no longer be considered
for package installations, patches, booting, etc.
to attach this zone to another system. The information is stored in the file
<zonepath>/SUNWdetached.xml. The status of the zone is converted from
"installed" to "configured". 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 SUNWdetached.xml file.
Running attach 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.
Running attach 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.
97