I have three (hopefully) quick questions:

- Are there any current (S10) or future incompatibilities with zone roots on
- Are there any current (S10) or future incompatibilities with zone roots on
  SVM disk sets?
- Are there any current (Nevada) or future incompatibilities with
  having one zfs pool per zone?  Zone cloning with zfs clones will be
  broken - anything else?

And here's why I ask...

I'm working on some improvements to my existing zone configuration and
management methodology.  As much as possible I am looking to have the
improvements be future looking enough that as future improvements come
about I have to do the minimal rework.

My understanding is that:

- Today each zonepath must exist on a UFS (or VxFS or possibly QFS)
  file system.  Read another way, ZFS is not supported for zones
  today.  The key reason for this is the lack of support for upgrade
  and sporadic support for patching of zones on ZFS.
- In the next release of Solaris, zones will have to be on ZFS due to
  expected changes in packaging, patching, and installation.
- There will be a transition period between "zfs not supported" and
  "zfs required" that will likely start with the release of S10U6.

My anticipated direction is to discontinue the use of local (within
the server chassis) storage for zone roots and transition to using
(likely) one or more iSCSI LUNs per zone.  Initially, the iSCSI LUNs
would either have UFS file systems on them directly or use SVM
disksets to allow soft partitions.  When the time is right, new LUNs
would be allocated for ZFS and data will be migrated.  Any SVM disk
sets will be destroyed in favor of using ZFS.

Mike Gerdts
zones-discuss mailing list

Reply via email to