SUMMARY: 

	This fast-track enhances the Zones [1] subsystem
	to address two existing RFEs.  The first [2] enables non-global
	zones to be relocated from one point on the filesystem to another;
	this may involve actually moving the bits and requires changing the
	associated metadata (the "zonepath").   The second [3] enables
	administrators to rapidly provision new non-global zones, once
	one has been set up, by allowing installation via copying from
	another (non-global) zone.

	Patch binding is requested for these sub-commands and the stability
	of the interfaces is "evolving".

DETAILS:

	We will add two new sub-commands to the zoneadm command.

	The syntax for moving a zone will be:

		# zoneadm -z my-zone move /newpath

	where /newpath specifies the new zonepath for the zone.  This will
	be implemented so that it works both within and across filesystems,
	subject to the existing rules for zonepath (e.g. it cannot be on an
	NFS mounted filesystem).  When crossing filesystem boundaries the
	data will be copied and the original directory will be removed.
	Internally the copy will be implemented using cpio with the proper
	options to preserve all of the data (ACLs, etc.).  The zone must be
	halted while being moved.

	The syntax for cloning a zone will be:

		# zoneadm -z new-zone clone [-m method] method_params

	Cloning a zone is analogous to installing a zone.  That is, you
	first must configure the new zone using the zonecfg command.  Once
	you have the new zone in the configured state you can use clone to
	set up the zone root instead of installing.  This allows all
	customizations (configuration, pkgs, etc.) from the source zone to
	be directly instantiated in the new zone.  The new zone will be left
	in the sys-unconfigured state even though the source zone is likely
	to be fully configured.  The source zone must be halted while the
	clone is running.

	The zoneadm command will be enhanced to perform additional
	verification when cloning.  Appropriate warnings and errors will 
	be printed if the new zone and source zone are configured
	inappropriately. 

	The -m option specifies the method used to clone the source.  The
	default and initial -m method will be "copy".  This will copy the
	data from the source zone (specified as the method_param) zonepath
	to the new-zone zonepath (implemented using cpio as with the move
	sub-command).

	In the future we anticipate supporting other cloning methods, such
	as ZFS clones, where we would specify a ZFS snapshot in the method
	parameter.  However, use of ZFS clones is not part of the current
	proposal.   We currently lack upgrade support for zones on ZFS
	filesystems so use of a ZFS filesystem for the zonepath is not
	recommended [4].  Once this issue is addressed we expect to
	submit a fast-track to enhance clone support by using ZFS snapshots
	and clones.

REFERENCES

1. <a href="../../2002/174/">PSARC 2002/174</a> Virtualization and Namespace Isolation in Solaris
2. RFE: zoneadm move command.  Bugid <a href="http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4963361">4963361</a>
3. RFE: provide faster zone provisioning.  Bugid <a href="http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6292928">6292928</a>
4. BUG: zfs datasets can't be used to provide space for zone roots.  Bugid <a href="http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6356600">6356600</a>