So, I think we are basically agreeing on what phase 1 should look like:

-Add attributes for post-install action, ip-assignment to the existing
SIS-db (perhaps with site/image/client cascading defaults).
-Modify the appropriate SIS commands to set/display these
(mksiimage,mksimachine).
-Change mkautoinstallscript to read the db for these values.
-Change mkautoinstallscript to create aiscripts per-client (perhaps
optionally).
-Add some flags to mkautoinstallscript to take client specifiers (--all,
--client <name>)

If we consider this as phase 1 and code/ship this before attacking some
other of the items that we don't agree on yet, we'll get a lot of
benefit quickly and still be able to consider the other functions for
the future.

Mike
 
-- 
Michael Chase-Salerno <[EMAIL PROTECTED]>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Sisuite-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to