On Tue, 2004-04-13 at 14:07, Thomas Lotterer wrote: > 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. >
Well, I for one know that I can contribute and I will once I have things ironed out. I like to get all of the issues hammered out before I write up a document on how to recreate the work. > 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]. > Hmmm. I will look into this. I checked out kolab but it didn't exactly have the features we needed. That was a brief overview of it mind you. :-) > 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. > Yes, we already have an after jumpstart reboot rc script for such things. > 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. > I'm interested. Right now, what I'm doing is setting it up so we have a Solaris 9 and RHEL3 apt repositories. The process then would be to build the binary versions of each piece of software we want to distribute, then sync the results to the repositories. The shell binary for openpkg itself will get installed as part of the jumpstart process. Once it is installed it will apt-get the rest of the packages from our own custom repository. The software selection will be the same on all systems. We are using cfengine to handle the management of all of the configuration files for the servers. Our cfengine implementation will also be part of jumpstart. The end result is a fully automated system build using either jumpstart or kickstart with a core install of the OS, openpkg installation for the software bits and cfengine to deploy the custom configs for the server based on it's function. > 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] -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
