Sarah,

    There are couple of comments that may not directly involved with the 
document but I want to bring to your attention.

    1. We need to add the functionality of discovering boot environment 
as part of target discovery
    2. The GUI installer and AI has too much knowledge about 
liborchestrator and when we redesign the install engine, we need to make 
the interface cleaner.

Thanks,
Sundar

Sarah Jelinek wrote:
> I should have mentioned.. you will see many functional groupings in 
> the document we posted. Not all of these are considered part of what 
> an install engine should provide. As noted on the project page we will 
> identify areas that have common/overlapping functionality in the 
> Caiman components that may be out of scope in terms of design for this 
> project. They will however be tracked by other projects, current or TBD.
>
> At a high level we are thinking that an install engine should provide 
> the following functionality:
>
> -Target discovery
> -Target instantiation
> -Transfer of bits
> -checkpointing
> -setup of postinstall tasks
> -Observability in to installation
> -Error handling for engine functionality
>
> While we consider the following consumer specific functionality:
> -Processing of user specified, or derived input
> -Post install processing
> -Consumer error handling
>
> Just some data for clarification.
>
> thanks,
> sarah
> *****
>> Hi All,
>>
>> There are updates posted to the Caiman Unified Design Page. 
>> Specifically, addition of a description of this project, an overview 
>> of the deliverables expected.
>>
>> Project web page:
>> http://opensolaris.org/os/project/caiman/CUD
>>
>> Also, we posted a new document:
>>
>> Current Caiman Components: common and redundant functionality(with 
>> differences noted):
>> http://opensolaris.org/os/project/caiman/CUD/caiman_common.pdf
>>
>> This document describes the areas of common and overlapping 
>> functionality offered by the current Caiman components, grouped in 
>> functionality groups. The differences are also noted for completeness 
>> and to ensure that during the design phase we account for these.
>>
>> We are currently working on a draft document that will list the 
>> requirements for a Caiman unified install engine. This will be posted 
>> to the alias and we will have a meeting to discuss these next week.
>>
>> Please review the new document and send feedback and questions to the 
>> alias.
>>
>> thanks,
>> sarah
>> _______________________________________________
>> caiman-discuss mailing list
>> caiman-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss


Reply via email to