On 04/23/10 10:47 PM, Ethan Quach wrote:
I have posted a revision to the derived manifest design.
(I've removed the pieces about an interactive manifest CLI on
the server side, as that needs to be a separate design.)
http://hub.opensolaris.org/bin/download/Project+caiman/DerivedManifests/DerivedManifestsDesignSpec.pdf
Already discussed these offline, but for the formal record:
Introduction - It's probably tangential to this work, but it may be
worth considering whether the criteria mechanism should be made usable
on the bootable AI media, to assist with self-contained turnkey media
installation solutions. Architecturally is there a reason why it
shouldn't be usable?
5.2.4 Might want to clarify here that these are Python API's? Also,
maybe "validate()" instead of "verify()" (and for the command argument
in 5.2.5). Finally, how about making load() incremental, so blocks can
be pulled in wholesale rather than constructed piecemeal with set()?
5.2.6 Aren't necessarily restricted to a script, are we? A Python or
other executable would seem to be equally valid.
5.2.6.1 Ought to cover the principle ("full read, limited write") in the
aiuser account authorizations.
5.2.7 The disk arrays seem clumsy to use; maybe ksh associative arrays
would be better? Also, more on the rationale behind providing these
variables as committed interfaces.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
