[olug] Question: package / system for administrating multiple very similar systems ?

[Jim O'Gorman]

You bring up a good point. I have been meaning to get around to throwing in
some example scripts that people could bootstrap with. I will have to make
that a priority.

As an example, here is my http install script:

bash-3.00# cat my_httpd_v1.sh
#!/bin/sh -x
PATH=/usr/sbin:/usr/bin:/opt/csw/bin:/opt/csw/sbin:/usr/sfw/bin:/usr/ccs/bin:/mine/apps/SUNWspro/bin

# Download the source
# Untar, configure, make, make install

cd $builddir
/usr/sfw/bin/wget -q $repbase/$repfiles/$archive
/usr/bin/gunzip -c $archive | /usr/sbin/tar xf -
rm $archive

cd  $builddir/$basedir

./configure --prefix=$installlocation --enable-so --enable-ssl
--with-ssl=$installlocation
if [ "$?" != "0" ]; then
        exit 1
fi

make
if [ "$?" != "0" ]; then
        exit 1
fi

make install
if [ "$?" != "0" ]; then
        exit 1
fi
cd ..
rm -r $builddir/$basedir

This is on Solaris, so locations etc are different. I also like to run with
a /companyname/apps /companyname/soruce etc structure as it keeps everything
clean under one tree.

Any other feedback you might have would be great. As I said, this is
something I use, so it makes a lot of sense to me. It is still up in the air
as to how well I have explained it, how accessible this is to others.

Thanks
Jim

On 4/24/07, Will Langford <unfies at gmail.com> wrote:
>
> On 4/20/07, Jim O'Gorman <jameso at elwood.net> wrote:
> >
> > For the heck of it, I put up a system I created and am using on
> > sourceforge
> > a couple of weeks back: https://sourceforge.net/projects/autodeploy/
> >
> > I use it in order to enforce repeatable builds across my systems. Idea
> is
> > to
> > do the work in the creation of the templates, and never have to do any
> > work
> > on the individual systems at all. Give it a look and see if it might
> help
> > you at all. As I said, I am using it with success, however I do not know
> > or
> > think anyone else has ever given it an attempt.
> >
> > Jim
> >
>
> Looking at autodeploy first.... seems like it's as simple as i'd like...
> documentation isn't too bad... but in the example section ya list examples
> of deployable packages... but there's an important piece of example I
> think
> is missing.  What does the installation script look like ?
>
> Files of interest listed in the examples would be:
>
> openssl_v1.sh
> wwwserverlocalsetup_v3.sh
> httpd_v1.sh
>
> Do they just untgz make install ?
>
> -Will
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> http://lists.olug.org/mailman/listinfo/olug
>