Sarah,
A few answers that I felt I could provide:
>
> -Whole disk or existing Solaris partition only acceptable targets is current
> requirement for Slim.
>
> -Target discovery via orchestrator will still returns all data, gui must
> filter
> appropriately. This results in no change to target discovery interfaces.
> However, this results in a potential performance issue since the discovery
> of upgrade instances is unnecessary.
>
> -We could separate out os discovery from this. Currently it is
> done after disk discovery via handle_disk_discovery. Should we do this?
>
I wouldn't worry about it. The primary target here are people who don't
have Solaris, so there won't be anything to check.
> -What about liborchestrator dependencies? I assume the pkgs that
> contain these dependencies, and the libtd dependencies are on
> the cd?
>
We appear to have everything already - my prototype runs the Dwarf
Installer to the point of trying to actually do the configuration and
installation.
> -what is the zfs root pool configuration for slim? mirrored or not?
> I assume not mirrored but not sure. Since we are creating
> a separate swap slice, outside the root pool, we will at a minimum
> have to create a pool with the slice(s). Not sure if we are allowing
> more than 1 disk to be included in the pool?
>
> -Why do we need the filesystem mountpoint specification in the nvlist
> when creating a target?
>
> -Passing in fdisk data to TI? How will this be done?
>
> -root pool properties to TI? Or for slim is this assumed to be 1 type of
> root pool?
>
> ****For setting up zfs root pools we need to:
>
> -Autogenerated filesystems to be created by TI? See zfsboot stuff
> on opensolaris.org
>
> -Setting up zpool.cache?
>
> -Setting up grub for root pool?
> -menu.lst changes?
>
We have a version of install-finish which does these two above
reasonably correctly already from Lori.
> -Extended partition support? What are we going to do for Oct? Orchestrator
> will need to be modified for this support as well.
>
Nothing for October. Extended partition support isn't integrated yet.
> -We will need to create vtoc slice for swap. How big is it going to be?
> Based on disk size as Dwarf does this? Also, do we pass this data
> in to the TI module?
>
> ****Postinstall tasks. We wil likely need a postinstall service to handle
> these.
> pfinstall/libspmi currently do this for us automatically.
> 1. transferlist
> 2. create boot archive
> 3. XXX whatever else is in finish script.
> 4. Moving, copying the logs
>
See above about modified install-finish that I used with the Live Media
proto-installer.
> ****Changes required in the orchestrator:
>
> typedef struct {
> char *pool_name; /* More info will be added */
> + zfs_dset_t *set_list; /* data sets in pool */
> + boolean_t is_root; /* root pool */
> } zfs_instance_t;
>
OK for now, but beyond October, I'd like us to discuss getting away from
structures and use nvlists in the orchestrator instead.
> -GUI will pass in the fdisk partition data to the orchestrator as
> usual, the difference will be that the user does not select anything other
> than the disk.
>
> -What to pass to TI:
> -disk name
> -use whole disk or not
> -pool name
>
> -What to pass to Transfer:
> -root pool name
> -dataset layout
> -locales chosen
>
There aren't any locales to choose in October, actually. I'd think the
dataset layout shouldn't matter to transfer, it just needs to be pointed
at where the "BE" is mounted and move the bits.
> -What we will need is the size of the image we are installing. To ensure
> that the size of the partition/disk is sufficient.
>
It's less than 2 GB, but that's not really the right question, since the
point is to add the things you want later to what we've included on the
media. Sizes similar to SXDE are probably OK for the moment.
> ****Changes for new Transfer module. Need to get api's to pass in:
> -Target data - including pool info, datasets
> -Language selection data - how are we going to handle this?
> download from repository?
>
> -Tools install, does this still happen with Slim? If not, we need to remove
> this from the orchestrator.
>
No, there is no Tools install. They aren't on the media.
> -Need new milestones for target instantiation and transfer service
> -Disk partitioned, - estimated percentage of overall process time
> -VTOC created - estimated percentage of overall process time
> -zpool created - estimated percentage of overall process time
> -datasets created - estimated percentage of overall process time
>
I don't know that we need to break these down that finely; these are all
almost instantaneous operations. Maybe for later, but initially just a
"TI done" at say 5% would probably do it.
> -Need new milestones for Transfer service actions
> -Total size of image we are transfering
> -Regular updates, percent of total installed
>
> -Orchestrator will call TI and Transfer service. GUI will call
> om_perform_install. GUI will have to be modified to understand the
> new/additional
> milestones.
>
> TI notes:
> -Will TI create swap partition? So, size of partition will need to be
> passed in?
>
I'd assume so.
Dave
