Ethan Quach wrote: > Sarah, > > 1.4.a Can you clarify whether or not we're discovering > UFS instances of Solaris? Or does the lack of > specification imply UFS and ZFS? > > 1.7 Same comment as above really. > > 1.6 and 2.9 I don't recall. Are these requirements > meant to satisfy usage by libbe, or to express > functionality provided by libbe? > > thanks, > -ethan > > > > Sarah Jelinek wrote: >> Please review and provide comments by COB Wed, 6/17. >> >> thanks, >> sarah >> **** >> >>> Hi All, >>> >>> I have posted a set of requirements defined for the Caiman unified >>> engine. They are located at: >>> >>> http://opensolaris.org/os/project/caiman/CUD/cud_req.txt >>> >>> There are some more details that need to be added, specifically with >>> regard to observability requirements. A lot of that depends on the >>> consumers of the unified engine. Along with the error handling section. >>> >>> Please review and send comments. >>> >>> Regards, >>> 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 > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
JJV Item 1: ----------- 5. Must provide support for development and testing. Should support for remote access be called out here? For example both the GUI and AI provide a mechanism to enable SSH to aid in testing and diagnoses. Should providing this type of hook be a requirement of the engine? or would this fall under #7? JJV Item 2: ----------- 9. Must provide a way for consumers to specify an override for any of the functional pieces provided by the installation engine. Sorry but I'm just a bit confused as to what this point means. Is the intent to allow users to provide there own plug-n-play mechanism to provide a specific engine function? I think this should be more specific. What are all of the functional pieces provided by the engine we expect to allow users to override? Thanks! Joe
