I have to upgrade SUNWexplo across 400 or so Sun servers, and it is a pain.
Currently i have a wrapper script that generates a pkgask file for each server i install it on, but i would much rather have a single pkgask file so i can do
$ pkgadd -a <admin> -r SUNWexplo.pkgask SUNWexplo
instead of running the wrapper script (so i can make use of a package administrator system for installing/upgrading/removing packages).
I have attempted to put some logic into the pkgask file (as i assume it is .'ed , i.e. ". <path>/SUNEexplo.pkgask" but this doesnt work.
What do you lot do, for both initial installs and for upgrades across multiple servers?
Currently i have a wrapper script that generates a pkgask file for each server i install it on, but i would much rather have a single pkgask file so i can do
$ pkgadd -a <admin> -r SUNWexplo.pkgask SUNWexplo
instead of running the wrapper script (so i can make use of a package administrator system for installing/upgrading/removing packages).
I have attempted to put some logic into the pkgask file (as i assume it is .'ed , i.e. ". <path>/SUNEexplo.pkgask" but this doesnt work.
What do you lot do, for both initial installs and for upgrades across multiple servers?