A. Rich <[email protected]> wrote: > I'm in the process of looking at how to automate solaris zone deployment and > configuration management across about 200 physical machines (multiple zones > each), and was wondering what other people had done so far. I want to make it > as scriptable and flexiable as possible since we have a number of machines to > handle. Right now all of our non-zone deployment and management is handled by > a combination of jumpstart, cfengine, and mysql, but I'm not certain that's > the way to go for zones.
I wrote a ~250 line shell script a few years back to do just this. It takes a few command line arguments and does its thing which basically boils down to: 1- automagic zonecfg/zoneadm invocations 2- sysidcfg generation for the zone 3- automagic ost (http://web.taranis.org/ost/) invocation in single user mode on first zone boot 4- some minor tweaking It works nicely, although I've had to update it more than I would've liked to keep up with small changes in the zone setup process, but that isn't very different from jumpstart tweaks needed every now and then. Steps 1 & 2 basically allow for a jumpstart-like setup. We do #3 during the final jumpstart phase, but it works just fine on the first boot for zones. > On a related topic, how are people handling third party software and sparse > zones? For software that requires its own config file, do you inherit the > software directory (/opt/csw, /usr/local, whatever) and use a symlink back to > the local zone for the config directory? Do you instead install packages > locally in each zone? We always build software to look in /etc for configuration, so it isn't an issue. Hope this helps. _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
