Evaluating the Current System Setup
Zones can be used on any machine that runs the Solaris 10 or later release. The following primary machine considerations are associated with the use of zones.
Disk Space Requirements
There are no limits on how much disk space can be consumed by a zone. The global administrator is responsible for space restriction. The global administrator must ensure that local storage is sufficient to hold a non-global zone's root file system. Even a small uniprocessor system can support a number of zones running simultaneously.
The nature of the packages installed in the global zone affects the space requirements of the non-global zones that are created. The number of packages and space requirements are factors.
Sparse Root Zones
Non-global zones that have inherit-pkg-dir resources are called sparse root zones.
The sparse root zone model optimizes the sharing of objects in the following ways:
In this model, all packages appear to be installed in the non-global zone. Packages that do not deliver content into read-only loopback mount file systems are fully installed. There is no need to install content delivered into read-only loopback mounted file systems since that content is inherited (and visible) from the global zone.
An additional 40 megabytes of RAM per zone are suggested, but not required on a machine with sufficient swap space.
Whole Root Zones
The whole root zone model provides the maximum configurability. All of the required and any selected optional Solaris packages are installed into the private file systems of the zone. The advantages of this model include the capability for global administrators to customize their zones file system layout. This would be done, for example, to add arbitrary unbundled or third-party packages.
The disk requirements for this model are determined by the disk space used by the packages currently installed in the global zone.
Note - If you create a sparse root zone that contains the following inherit-pkg-dir directories, you must remove these directories from the non-global zone's configuration before the zone is installed to have a whole root zone :
Restricting Zone Size