jan damborsky wrote:
> Hi all,
>
> preliminary version of design document for Target Instantiation Service
> which is part of Slim Install project has been posted on
>
> http://opensolaris.org/os/project/caiman/files/slim_ti_design-2.pdf
>
> It is the first draft with many issues still pending and many design details
> to be determined. Any comments, questions, suggestions are appreciated.
> If possible, please review the document by the COB 9/19/07.
>
> Thank you very much,
> Jan
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>   
Jan,

    These are my comments. In general you design assumes lot of changes 
in the orchestrator module. For example Orchestrator doesn't talk about 
ZFS. Are you planning to update the orchestrator design document with 
the changes?

Section 1: Assumptions

    - The project assumes that ZFS root/boot is available. Can you add 
the information whether it is already available or when it is expected 
to be available?

    - What is a basic environement? (The second bullet in the assumptions)


Section 2:

    - What is a Manager Module (MM)? Is it same as TI manager? The name 
sounds too generic. Can you change it to refer to the actual functionality?

Section 5.1.1:

    - Design is spelled as desifn

Section 5.2:

    -  Are we planning to support creation of zfs pool across multiple 
disks during installation?
    -  What is meant by "It is possible to install on unlabeled disks". 
How do we determine whether the disk doesn't have a label or it has a 
label we don't understand?
    -  I don't understand the third bullet "There should be possibility 
of utilizing unallocated disk space when creating new Solaris 
partition". Do you mean there will be an interface in MM to specify a 
special keyword to use all free space?
    - CLI tools fdisk and and Format can't be used from GUI. Why these 
CLI tools are mentioned here?
    - pfinstall and ttinstall manages fdisk partitions using the libspmi 
libraries.
    - I am not sure whether it is a good idea to create a label. We may 
destroy the user data.
    - Are you planning to use fdisk tool to create/modify fdisk table? 
Why can't use the existing libspmi interfaces?

Section 5.3.1:

    - Why install needs to create non-root ZFS pool?

Section 7:

    - If I want to use the existing target (fdisk partition), do have to 
use ti_target_create() from the orchestrator?
    - What about deleting a partition?

That is all for now.

- Sundar






Reply via email to