I'm sponsoring this case for Frank Batschulat. I've marked it closed
approved automatic but if anyone has concerns, I can change this to
a fast-track for further discussion.
Thanks,
Jerry
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2010 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Remove zoneadm install sub-option "-x nodataset"
1.2. Name of Document Author/Supplier:
Author: Frank Batschulat
1.3 Date of This Document:
07 January, 2010
4. Technical Description
Remove zoneadm(1M) install sub-option "-x nodataset"
The zoneadm(1M) install "-x nodataset" sub-option was introduced into nevada
build 39 via the following ARC case/RFE:
PSARC/2006/153 Zones ZFS Integration
6383119 RFE: add support for using zfs clones when cloning a zone
This option instructs zoneadm to avoid automatically creating a ZFS dataset
for the zone.
At the time, zones did not yet support BrandZ so there was no discussion
of this option and its interaction with various brands.
Although the "-x nodataset" sub-option to zoneadm(1M) install appears to work
with all zone brands, it doesn't. It applies specifically to the "native"
brand (see native(5)), which is currently the default brand for non-global
zones in ONNV and Solaris 10. Most new brands can't support the sub-option.
The "native" brand, which was the primary consumer of the sub-option, will
disappear when SXCE dies. The "ipkg" brand is the "native" brand going
forward for OpenSolaris/Solaris.Next. However, the "ipkg" brand (as well
as the solaris10(5) brand (PSARC 2009/253)) requires that ZFS datasets back
zone roots in order to leverage IPS/pkg(1) and beadm(1M) functionality and
thus those brands do not support the "-x nodataset" sub-option.
This proposal will remove the zoneadm(1M) install sub-option "-x nodataset"
from zoneadm and thus removes the ability to install zones into zoneroot
paths on ZFS without also creating a corresponding separate ZFS dataset.
This case seeks minor release binding.
I've raised this proposal in public on the zones-discuss at opensolaris.org
email list without causing any concern:
http://opensolaris.org/jive/thread.jspa?threadID=119493
I also raised this proposal to Sun internally on the appropriate email
aliases without causing any concern.
The OpsCenter product will not be affected because it only installs
zones into xVM(5)-managed storage, which exclusively uses zfs datasets.
I also checked the well-known OpenSolaris community tool "Zone Manager"
(http://hub.opensolaris.org/bin/view/Project+zonemgr/) and it does not
make use of the "-x nodataset" sub-option either.
Interfaces:
exported interfaces as introduced via PSARC/2006/153 that will be removed:
zoneadm subcommands
install [-x nodataset] Evolving
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: Automatic
6.6. ARC Exposure: open
