Wednesday, May 26, 2010

Branded Zones:

Branded zones are available beginning with the Solaris 10 8/07 release.
The Branded zone (BrandZ) provides the framework to create non-global branded zones that contain non-native operating environments used for running applications.

Every zone is configured with an associated zone. The default is the native brand, Solaris. A branded zone will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environment.

Note :

1. Cannot run Solaris applications inside an lx zone. However, the lx zone enables us to use the Solaris system to develop[, test, and deploy Linux applications. For eg, we can place a Linux application in an lz zone and analyze it using Solaris tools run from the global zone.
2. We can change the brand of a zone in the configured state. Once a branded zone has been installed, that brand cannot be changed or moved.
3. The system must be either x64 or x86 based.
4. The lx (Linux) brand supports only the whole root model, so each installed zone will have its own copy of every file.
5. There are no limits on how much disk space can be consumed by a zone. The global administrator is responsible for space restriction.
6. Currently lx brand installer supports only Red Hat Enterprise Linux 3.x and the equivalent CentOS distributions.

we can download the CentOS tarball from the above link.
7. Regarding, assigning the name to be branded zone, rules is similar to a non-global zone.


1. To display the arch of the system, where brandz zones are implemented.

bash-3.00# arch

2. To display the release of the Solaris Operating System

bash-3.00# cat /etc/release
Solaris 10 10/09 s10x_u8wos_08a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 September 2009

3. Configuring BrandZ zone:

bash-3.00# mkdir -m 700 /export/home/linux_brandz
bash-3.00# zonecfg -z linux_brandz
linux_brandz: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:linux_brandz> create -t SUNWlx
zonecfg:linux_brandz> set zonepath=/export/home/linux_brandz
zonecfg:linux_brandz> add net
zonecfg:linux_brandz:net> set physical=e1000g0
zonecfg:linux_brandz:net> set address=
zonecfg:linux_brandz:net> end
zonecfg:linux_brandz> commit
zonecfg:linux_brandz> exit
bash-3.00# zoneadm -z linux_brandz install -d /Desktop/centos_fs_image.tar.bz2

-d = specifies the path of the non-native OS tarball/image.
Installing zone 'linux_brandz' at root directory '/export/home/linux_brandz'
from archive '/Desktop/centos_fs_image.tar.bz2'

This process may take several minutes.
Setting up the initial lx brand environment.
System configuration modifications complete.
Setting up the initial lx brand environment.
System configuration modifications complete.

Installation of zone 'linux_brandz' completed successfully.

Details saved to log file:
bash-3.00# zoneadm list -iv
0 global running / native shared
- linux_brandz installed /export/home/linux_brandz lx shared
bash-3.00# zoneadm -z linux_brandz boot
bash-3.00# zoneadm list -iv
0 global running / native shared
1 linux_brandz running /export/home/linux_brandz lx shared
bash-3.00# zlogin linux_brandz
[Connected to zone 'linux_brandz' pts/4]

Welcome to your shiny new Linux zone.

- The root password is 'root'. Please change it immediately.

- To enable networking goodness, see /etc/sysconfig/network.example.

- This message is in /etc/motd. Feel free to change it.

For anything more complicated, see:

You have mail.
-bash-2.05b# uname -a
Linux linux_brandz 2.4.21 BrandZ fake linux i686 i686 i386 GNU/Linux
-bash-2.05b# hostname

Wow...!!! It works's, Fabulous.

Thursday, May 6, 2010

Solaris : Advanced Installation

JumpStart Installation:
There are 2 versions of JumpStart:

1. JumpStart : Automatically install the Solaris software on SPARC based system just be inserting the Solaris CD and powering on the system. Need not to specify the boot command at OK prompt. The software that is installed in specified a default class file that is chosen based on the system’s model and the size of its disks; can’t choose the software that is to be installed. For new SPARC systems shipped from Sun, this is the default method of installing the operating system when the system is first powered on.

2. Custom JumpStart : Method of installing the operating system provides a way to install groups of similar systems automatically and identically. At a large site with several systems that are to be configured exactly the same, this task can be monotonous and time consuming. In addition, there is no guarantee that each system is setup is same. Custom JumpStart solves this problem by providing a method to create sets of configuration files earlier, so that the installation process can use them to configure each system automatically.

Flash Installation :
A complete snapshot of a Solaris operating system, including with patches and applications.
Limitation: Used to perform an initial installation, Flash cannot be used to upgrade a system.

Flash archive:
Provides a method to store a snapshot of the Solaris operating system complete with all installed patches and applications. This archive can be stored on disk, Optical media or tape
media. This archive can be used for disaster recovery purposes or to replicate an environment on one or more other systems.

Solaris Live Upgrade:

Provides a method of upgrading a system whilst the system continues to operate.
While the current boot environment is running, it’s possible to duplicate the boot environment, and then upgrade the duplicate. Alternatively, rather than upgrading, it’s possible to install a Solaris Flash archive.
The original/current system configuration remains fully functional and unaffected by the upgrade or installation of an archive.
When ready, can activate the new boot environment by rebooting the system. If a failure occurs, can quickly revert to the original boot environment with a simple reboot.

Solaris Live Upgrade Process – Phase:
1. Creating an alternate boot environment (ABE) by cloning a current Solaris OS instance. The source for this cloning could also be a flash archive.
2. Changing the state of the system in the ABE for reasons including the following:
a. Upgrading to another OS release
b. Updating a release with patches or updates
3. Activating the new boot environment (BE).
4. Optionally falling back to the original BE.

Solaris Live Upgrade are supported by the following version:

Solaris 8 OS
Solaris 9 OS
Solaris 10 OS

Note - 1:
The only limitation to upgrading involves a Solaris Flash archive. When Solaris Flash archive is used to install, an archive that contains non-global zones are not properly installed on the system.

Note - 2:
Correct operation of Solaris Live Upgrade requires that a limited set of patch revisions be installed for a particular OS version. Before installing or running Solaris Live Upgrade, it’s required to install these patches.

Note - 3:
To estimate the file system size that is needed to create a boot environment, start the creation of a new boot environment. The size is calculated. Then abort the process.

Note - 4:
Solaris Live Upgrade packages are available from the release Solaris 10 05/09.
If the release is older, the packages can be installed by using the command # pkgadd.
Packages required:
Make a note that these packages MUST be installed in this order.