On Thu, Jun 11, 2009 at 9:24 PM, Peter Tribble<peter.tribble at gmail.com> wrote: >> So, how about having such a setting in the AI manifest >> that works in conjunction with the AI client to provide >> the "just install this version of the OS once on this client" >> behavior? Would something like that work? > > You mean based on a version match of the installed OS already present > on the client? That wouldn't work. > > ?- We commonly install the same version of the OS over and over. Either to > test changes to the profile, or simply to redeploy a box, repeated installs of > the same OS version are common. > > ?- Certainly the way I work is that when a new version of the OS comes out > and is verified, the jumpstart server is updated so that any subsequent > installs > get the new version. Just because I've changed the version that would > get installed > doesn't mean that I want to overwrite a box by accident.
+1 to the above. What I have at work to handle such scenarios is a tftp boot menu which has "Boot from Local HArd Disk Drive" as the default option, and with kickstart installs for Redhat/CentOS/Ubuntu/Fedora as options later down the list. I haven't used AI yet - is it possible to invoke the AI client via an explicit TFTP boot menu option ? If this were possible, then I'd add a similar entry for opensolaris. In case I have the ability to point to an opensolaris AI install server via a TFTP Boot menu, then here's how I'd solve a scenario where 50 computers need a force install, while the rest do not: - specify a custom TFTP boot menulist for those specific MAC addresses. - this custom TFTP boot menu list would have "force install opensolaris" as the default menu option. > > Thanks, > > -- > -Peter Tribble > http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
