The clzonecluster boot subcommand provides two options that enable the global zone administrator to manually boot an immutable zone cluster with either a writable root file system or with a transient writable root file system. The zone cluster is in writable mode only until the next reboot.
Manually boot the zone cluster with a writable root file system.
Manually boot the zone cluster with a transient writable root file system. The system is rebooted automatically when the self-assembly-complete milestone is reached. The reboot places the zone cluster under control of the MWAC policy again. This option is permitted when the zone cluster has an MWAC policy of none.
Both the –W and –w options are ignored for zone clusters that are not immutable zone clusters.
Since login to a zone that is part of the immutable zone cluster is no different from a standalone immutable Oracle Solaris zones, you can use the zlogin command to access immutable zones. See the zlogin(1) manpage for more information.
For additional information about immutable zones, see Administering an Immutable Zone by Making It Writable in Creating and Using Oracle Solaris Zones.Example 18 : Making the Immutable Zone Cluster Writable
The following example shows the console output when immutable zone clusters are used. You must make the immutable zone clusters writable, using the clzc reboot -w option, before performing administrative tasks. This example shows making the immutable zone cluster writable, and then installing a package after the zone boots into writable mode. For more information see Administering an Immutable Zone Cluster by Making It Writable.
phys-schost-1:~# clzc status zc1 === Zone Clusters === --- Zone Cluster Status --- Name Brand Node Name Zone Host Name Status Zone Status ---- ----- --------- -------------- ------ ----------- zc1 solaris dev1501 phys-schost-1 Online Running dev1502 phys-schost-2 Online Running phys-schost-1:~# zoneadm list -p 0:global:running:/::solaris:shared:-:none: 76:zc1:running:/system/zones/zc1:aafa7556-fa2a-4a94-bf32-ad9b5832f6e1:solaris:excl:R:fixed-configuration: phys-schost-1:~# phys-schost-1:~# clzc reboot -w zc1 Waiting for zone reboot -w commands to complete on all the nodes of the zone cluster "zc1"... phys-schost-1:~# clzc status === Zone Clusters === --- Zone Cluster Status --- Name Brand Node Name Zone Host Name Status Zone Status ---- ----- --------- -------------- ------ ----------- zc1 solaris dev2403 phys-schost-3 Online Running dev2404 phys-schost-4 Online Running phys-schost-1:~# zoneadm list -p 0:global:running:/::solaris:shared:-:none: 3:zc1:running:/system/zones/zc1:be902772-98c8-4057-b2d4-c4744286c33e:solaris:excl:W:fixed-configuration: phys-schost-1:~# phys-schost-1:~# phys-schost-1:~# zlogin zc1 [Connected to zone 'zc1' pts/2] Last login: Thu May 17 04:36:00 2018 on console Oracle Corporation SunOS 5.11 st_019.server April 2018 phys-schost-1:~# phys-schost-1:~# phys-schost-1:~# pkg info -r pkg://solaris/developer/versioning/mercurial Name: developer/versioning/mercurial Summary: The Mercurial Source Control Management System Description: A fast, lightweight source control management system designed for efficient handling of very large distributed projects. Category: Development/Source Code Management State: Not installed Publisher: solaris Version: 4.1.3 Branch: 18.104.22.168.0.21.0 Packaging Date: Mon May 14 18:02:27 2018 Size: 927.40 kB FMRI: pkg://firstname.lastname@example.org:20180514T180227Z Project URL: http://mercurial-scm.org/ Source URL: https://www.mercurial-scm.org/release/mercurial-4.1.3.tar.gz phys-schost-1:~# phys-schost-1:~# phys-schost-1:~# pkg install pkg://solaris/developer/versioning/mercurial Packages to install: 2 Create boot environment: No Create backup boot environment: No DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 2/2 681/681 4.7/4.7 4.6M/s PHASE ITEMS Installing new actions 718/718 Updating package state database Done Updating package cache 0/0 Updating image state Done Creating fast lookup database Done Updating package cache 2/2 phys-schost-1:~#