Hi William,
the overall document looks pretty good,
I have only couple of questions/comments -
please see below.
Thank you,
Jan
Slice and partition management actions
--------------------------------------
* Partition
Will be starting offset required ? What happens
is the partition overlaps the exiting one ?
I might recommend to support similar approach which
is to be taken for slices - specify only partition
size or allow AI to pick up the largest contiguous
chunk of available space.
Defining desired behavior
-------------------------
* <target_device_use_solaris_partition> = false
- partition information specified
What would be the format of partition information ?
Is user requested to specify complete partition
information - what is optional, what is mandatory ?
- no partition information
I might recommend not to take 'whole disk' as
default if no partition information is specified.
This seems dangerous - I think that if user wants
to wipe out all the disk, it should be explicitly
stated in the manifest.
Current behavior
----------------
Only to confirm - it seems this section describes current
implementation in AI - might it be correct ?
To be done for November
-----------------------
- What will be implemented as fas as creating Solaris2
partition is concerned ?
- With respect to minimum and recommended sizes, they
are slightly different comparing with the ones
in GUI installer.
The reason is that we don't have /.image_info file for
AI, which might tell us, how much space is needed for
installation.
Current behavior is that if this information is not
available defaults are picked up by the orchestrator:
4GiB for minimum, ~12GiB for recommended.
- Switching to read_extvtoc() and write_extvtoc() will
allow to install on <1TB; 2TB) disks. Only 2TB will
be usable on >2TB disks.
William Schumann wrote:
> Slice (VTOC) and partition (fdisk) management for the Automated
> Installer have not yet been specified, yet safe and sensible behavior
> is expected.
>
> I have prepared a document (attached) with the following objectives:
> - document the expected features and behavior
> - document the current behavior
> - document what is yet to be coded
> - serve as a starting point so we may achieve consensus on what the
> proper behavior should be
>
> Please review the the attached document and comment. Check my
> assumptions, offer corrections and suggestions.
> William
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
