Anyone attending the AI Client redesign meeting: I am adding some quick text I composed that should help us in the meeting. William
Design changes in OpenSolaris Automated Installer ? disks, partitions, slices ------------------------------------------ I: Target disk selection: 2 categories ? disk specified with criteria, otherwise disk chosen by AI according to rules (default disk scenario) Algorithm for default disk selection Original design put safety over ease of use ? explicit partitioning and slices preferred for each disk only criterion - is disk large enough x86 ? Solaris partition must be present and is not created by default (requires preexisting or create action) 7544 suggests that 20% padding should be sought on 1st pass, and on 2nd pass, minimum fit 2 pass approach (for both default and specified criteria): on pass 1, select only disks with 20% additional space above requirement if not found, on pass 2, select disk with minimum requirement under AI manifest category: ai_target_device ai_target_device manifest schema elements concerning selection: target_device_name target_device_type target_device_vendor target_device_size target_device_use_solaris_partition proposed added elements for selection: target_device_volume_id_contains ? partial match on volume ID string ? only deterministic and reliable way to specify disk target_device_select_boot_disk ? use only the boot disk, and fail if not minimum size elements that are options or parameters: target_device_install_slice_number target_device_overwrite_root_zfs_pool proposed elements in the option/parameter category: target_device_overwrite_disk ? 6488 remove any partitioning and create a single partition using entire disk and use all of it for install slice pro: simple, easy to supplant an undesired operating system, old Solaris, etc. con: too simple to wipe out disk and all user data. What is the behavior if there is an existing Solaris and the manifest is re-used? Mutually exclusive elements, will fail to install if these combinations of elements are in manifest: target_device_use_boot_disk ? and any others pertaining to target selection (target_device_...) target_device_overwrite_disk and any partition/slice actions or target_device_install_slice_number Proposed: do not requrire Solaris2 partition for unformatted disk, just format it - Seems reasonable and useful --------------------------------------------------------- II. Slice/Partition: if create action for slice that already exists, install fails. pro: we want manifest to be explicit so that data is not deleted too easily pro: what if create action is specified differently than the original? Different size? Location? pro: user can use delete action to delete the existing slice first con: yes, since manifest is more re-usable proposed: fail if conflicting actions ? What consititutes conflicting actions? currently: actions are done sequentially, in order of appearance in manifest pro current method: can delete partitions, then create them differently Proposed: check size of install slice ? is it big enough? Fail if not. fix 7794: if delete/preserve slice and no size, installadm fails to validate ? bug assigned to me fix 7964: if target device is provided, other specifiers are still read and parsed ? documentation says that the other values are ignored suggested fix 1: make target_device_name mutually exclusive with any target device elements concerning disk selection, failing installation suggested fix 2: if disk name ctds type specified, just don't read other parameters fix cons: What's wrong with this (other than not working as documented)? Perhaps the user doesn't want to install to explicitly specified ctds disk name if it is not of a given vendor, size, or type ? is this possible? My proposals: partition/slice action ? purge ? delete all partitions or slices con: very similar to target_device_overwrite_disk (above) pro: but without other behavior associated with it pro: easy way to delete slices without changing partitions con: too easy to delete slices pro: doesn't affect partitions [end of meeting text] Susan Sohn wrote: > There will be meetings on Tue, Wed, and Thu this week to discuss > client redesign. > The topic for tomorrow's meeting will be disk selection (default and > specified) and > slice partitioning. William and Jean's presence is requested, anyone > else is welcome. > > Here are the meeting details: > > Client redesign meetings: > Tue, Wed, Thu 5/19,20,21 > 8m PT/9am MT/5pm Prague > > USA Toll-Free: 866-839-8145 > Caller Paid (Intl): 215-446-3660 > Participant Code: 9041875 > > Thanks, > Sue > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
