On Mon, May 11, 2009 at 3:32 AM, Michael Ramchand <michael at ramchand.net> wrote: [very good stuff snipped] > 1: Doing a net install, and running the interactive Solaris Installer. > (add_install_client, provide mac address, IP address) > > 2: Non-interactive net-install: (add_install_client, provide mac address, IP > address, rule pointing to profile, sysidcfg): Solaris installs unattended. > > 3: Non-interactive net-install: (add_install_client, provide mac, ip, rule > pointing to profile and finish script, sysidcfg): Solaris installs > unattended, plus installs all the cool and interesting stuff that customers > actually want to run. > > Obviously level 1 and level 2 are just building blocks to 3, but it seems > that all the focus on AI is on Level 2, while the customer value actually > derives from 3. If you look at JET, the SUNWjet package deals with level 2, > all the other modules are the things that do all the level 3 stuff.
Well said. > (And Mike Gerdts, sorry if someone missold JET to you as a PS only thing, > I've checked the archives of the external JET mailing list, and you never > asked that list for anything.... we've given away pretty much every module > once we knew it wouldn't create a support burden, and most of them are > available in the sun.com/download bundle anyway) > ?(http://wikis.sun.com/display/JET ) Some of this could be history from several years ago - potentially attached to an N1 SPS POC. Since I already had JASS fully functional (including postinstall customizations unrelated to security) there seemed to be very little reason to convert over to JET. Perhaps incremental updates over the years would have been easier, but outside of Sun it was hard to guess which one would be easier to deal with in the long term. I think that I could have found similar levels of happiness and frustration on each path. -- Mike Gerdts http://mgerdts.blogspot.com/
