A couple of UI-related comments... jan damborsky wrote: > Attached is the current version of target instantiation (TI) task list. > > Target instantiation (TI) task list > > > [1] October release (only fresh install on x86 supported) > --------------------------------------------------------- > o removed dependency on pfinstall engine > > o Disk module > * support for "Use the whole disk" option in GUI Disk screen. If > this option is chosen, > TI will create Solaris2 partition on whole disk by means of "fdisk > -B" command. > > * slice configuration (VTOC) will be created within existing > Solaris2 partition > according to information received from orchestrator. Two slices > will be created > (one for ZFS root pool, one for swap). > > It is assumed in this point that fdisk Solaris2 partition will be > created > - either by selecting "Use the whole disk" option in GUI (see the > first task), > - or user will be responsible for creating the Solaris2 partition > before Installer is launched. > Creating Solaris2 partition by selecting "Partition the disk" > option in GUI Disk screen is > not supported for October release. Selecting but not creating/resizing Solaris2 partitions will require additional UI changes. Not huge, but not trivial. > > o ZFS module (will use zpool, zfs CLI tools for creating ZFS root pool > and datasets) > * ZFS root pool will be created according to information received > from orchestrator > (name of root pool, slice name, other parameters...) > * ZFS datasets will be created within root pool (there would be > separate file systems > created for /, /usr, /var, /opt, /export). Configuration will be > provided by orchestrator > and would be hard wired from user's point of view. GUI assumes default pool and dataset names. > > [2] March release (x86 & sparc? install & upgrade supported) > ------------------------------------------------------------ > o Disk module > * support for manipulating fdisk partition table on x86 (libfdisk ? > - so far it seems > that libfdisk will only provide interfaces for manipulating > logical volumes within > extended partition, other tool (fdisk?) would still need to be > used for manipulating > primary fdisk partitions) Re-enable fdisk partition creation/resizing in the installer GUI that was removed for Oct. (above) > > o ZFS module > * implementation might chang to utilize libzfs library instead of > CLI (zpool,zfs,...) tools ? > * interfaces necessary for Snap Upgrade and consumed by BE > management utilities - support for > - root as well as non-root ZFS pools > - mirrored ZFS configuration (across two disks) > - creating ZFS clones > - utilizing ZFS policies (quotas, TBD...) Do we expect to be able to install into a specific slice of an existing Solaris2 partition? Not in the current UI plans to deal with slices in any form, i.e. one ZFS pool per Solaris2 partition.
Frank
