As virtual instances of a physical system, zones use the hardware resources of their hosts. Therefore, the more resources on the host system, the greater the flexibility for an administrator to create and configure zones.
The following sections discuss important considerations when planning to create zones.
Zones use the following hardware resources:
Disk space requirements for a zone depend on two factors:
Packages you intend to install on the zone.
Available disk space on the host after the installation of the standard Oracle Solaris OS packages.
Calculate at a minimum 1GB of disk space to allocate to each zone that you plan to install.
As an option, consider adding 40 MB of system memory for each zone to be configured. Disk space resources on the host is a factor in configuring swap space. If you configure sufficient swap space on the host system, then additional memory might not be necessary.
As an administrator, you can further control the size of a zone by setting the quota and reservation ZFS properties, which determine the maximum amount of disk space that a zone can consume. The properties are set on the zone's dataset that is located on the zonepath defined for that zone. For more information about these properties, see the zfs(8) man page and Chapter 7, Managing Oracle Solaris ZFS File Systems in Managing ZFS File Systems in Oracle Solaris 11.4.
As an alternative, you can create ZFS volumes with fixed sizes and install zones in the volume's datasets. The volumes limit the sizes of the zones installed on the volumes. See ZFS Volumes in Managing ZFS File Systems in Oracle Solaris 11.4.
Assign a zone name by which the zone can be identified from the global zone and to distinguish it from other zones on the system. Later, during the configuration of the zone's system information, you would be prompted for a computer name or a host name, similar to how physical systems have host names.
If you are not using DHCP, then you need to assign fixed IP addresses to the zones. Zones support both IPv4 and IPv6 addresses. Use IPv6 stateless address autoconfiguration to assign IPv6 addresses more easily.
By default, zones are automatically created as having an exclusive IP configuration, which means the zones have their own network layout different from and separate from the layout of the global zone. See About Zone Network Interfaces in Oracle Solaris Zones Configuration Resources.
Zones in Oracle Solaris are branded. A zone is branded when you create it, as specified in the zone's template. After a zone is installed, you can no longer change its brand. Oracle Solaris 11.4 supports the following brands:
solaris – Creates a zone that will contain the same software as the global zone. Unless you specify differently, all non-global zones automatically receive the solaris brand, which is based on the SYSsolaris template.
solaris-kz – Creates a kernel zone. The brand is based on the SYSsolaris-kz or SYSsolaris-kz-minimal template. See Creating and Using Oracle Solaris Kernel Zones.
solaris10 – Enables Solaris 10 binary applications to run unmodified on a host with the Oracle Solaris 11.4 kernel. The brand is based on the SYSsolaris10 template. See Creating and Using Oracle Solaris 10 Zones.
labeled – Implements Trusted Extensions. See Zone Creation in Trusted Extensions in Trusted Extensions Configuration and Administration and Installing and Enabling Trusted Extensions in Trusted Extensions Configuration and Administration.
For more details about brands, see the brands(7) man page.