On Tue, Apr 13, 2004, David M. Fetter wrote: > Has anybody successfully been able to incorporate a binary build of > OpenPKG in shell script form into a Solaris Custom Jumpstart? Just > curious. I'm working on doing it now for our environment. > David, you're not alone. I know of at least two sites doing it and both are subscribed. Hopefully they are willing and allowed to contribute some information.
Not limited to jumpstart is a script I wrote for easy deployment (bootstrap, build/install and manage configuration) of OpenPKG instances - obmtool [1]. Just take the obmtool and create a obmtool.conf and you're ready to run. It will download, build and install. You can put SRPMs along with the two files to skip the download and you can provide binaries to skip the build. The choice is yours. Kolab is using this tool as can be seen at ZfOS [2]. Regarding jumpstart I was told that it is a good idea to not attempt running OpenPKG download, build, install etc. during the jumpstart process because the environment is different from the finished system. A good practice seems to be using jumpstart for downloading and placing files in a reasonable location and create a rc script which does the actual install at the first run of the finished machine. If someone is interested I can collect and post some obmtool.conf sections I'm using next weekend. Some of them are quite simple, the most complex one upgrades OpenPKG 1.3 to 2.0 including intermediate step, database conversion, openpkg-tool deinstallation etc. and it configures ntp, openssh, rsync and postfix. Well, it's a shell script so at least the configuration part is pure shell code not really aided by the tool these days. Please understand that the scope of the tool is *deployment* with the cornerstones: start from scratch (really scratch - no OpenPKG available), break at any time and restart at a reasonable point and enforce installation of a given set of packages at the specified version (different versions will be up-/downgraded, missing packages installed, surplus packages can be erased etc.). It is *not* the intention of the tool to analyze what you have and automate the choice of dependent packages, versions and build/install ordering. That's the domain of "openpkg build". [1] ftp://ftp.zfos.org/comp/obmtool/ [2] ftp://ftp.zfos.org/brew/kolab/CFG/snapshot-20040407002609/ -- [EMAIL PROTECTED], Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
