2: jumpstart configuration files question

2007-12-25 10:49:00

Hello,

I got another suggestion about installing patches via jumpstart

after I sent my summary.

This is from Luke Kanies:

you don't need to maintain

separate directories at all for separate versions of solaris. The vast

majority of your packages will be the same for either version, you can

maintain updated patches in the jumpstart image itself (in

'Solaris_X/Patches'; if you want to put a new cluster in, remove the old

one, and then have a script go through and touch each patch dir in the

order of install, with a one second sleep between touches--jumpstart

installs patches in order of last modification time).

Luke writes over what is in the Solaris_X/Patches directory with

the newest cluster patch. Then, when jumpstart runs, the last

thing it does before running the finish script is install the

patches from this directory.

Thanks!

Nicole

First summary and original post:

Hi,

I got a several responses to my question. Some of the

suggestions were:

1) Check out the code at ftp.wins.uva.nl:/pub/solaris/auto-install, which

could be used for table driven install including sharing rules and

scripts files between different Solaris versions.

2) Have one script that checks the OS level and sets an OS variable. Then

you could use this variable in your other scripts to install

the correct patches, packages, etc.

For instance:

Check the OS level:

ARCH=`uname -r`

if [ $ARCH = 5.7 ]; then

OSLEVEL=SunOS_5.7

elif [ $ARCH = 5.6 ]; then

OSLEVEL=SunOS_5.6

else

echo "Can't determine OS Level, exiting"

exit 1

Then use OSLEVEL variable in a script like this example:

mkdir /a/patches

mount patchserver:/patches/$OSLEVEL /a/patches

cd /a/patches

for i in `cat patch_order`

patchadd ...

done

Or, use an "if" statement in a single script that will do different

things for different OS versions.

3) Continue to maintain two separate jumpstart directories, one for

each OS. Make hard links between all of the finish scripts

that are identical.

4) Identify the path to the begin/finish scripts in the rules file.

For instance:

any - <direcotry to begin>/begin_script = <directory to finish>/finish_script

People specified that the path had to be in the same filesystem

as the rules file. This is what I suspected.

5) Try using the begin/finish scripts to call scripts in other locations.

6) Make a subdirectory called finish for

the finish scripts. You could symlink one of the directories to the

other one, as long as it's exportable. Or link them both to

/jumpstart/finish

I have been trying out option #2. I've mave one rules file which will

call a begin/finish script. Here's an example line:

model SUNW,Ultra-4 && \

disksize c0t0d0 8000-9500 BEGIN/begin_9g = DRIVERS

/finish_driver

Then, in the same filesystem where the rules file is, I made BEGIN,

FINISH, and DRIVERS directories.

BEGIN - holds my begin scripts.

FINISH - holds all of the finish scripts for both versions (I've named

the OS specific scripts to be filename_26 or filename_7). The

DRIVERS - holds driver scripts that will call the finish scripts. I

added the code from option #2 to check for and set an OS version.

I then use an "if" statement in the driver script to run the

correct finish scripts. Once the OS specific scripts are run,

the driver scripts then run all of the non OS specific scripts.

As far as my custom configuration files are concerned (ie aliases, resolv.conf,

.cshrc etc.) I made one CONFIG directory that contains all of them.

I used to have two separate copies for each OS in different directories.

But, at this point I cannot think of any differences I'll have with these

files between OS versions, so I'll keep them in one directory. I hope

I don't run into problems with this later on.

I've done a few tests so far and it seems to be working ok. Hopefully

it will be ok for full production service.

Thanks again to the following people for your help and suggestions:

Casper Dik, Joe Muldoon, Lawrence J Salacup, Ken Nelson, Richard Cove,

Willi Burmeister, Bryan Moore, Arthur Darren Dunham, and Atmane

Nicole Skyrca

AppliedTheory Communications Inc. Phone: 315-453-2912 x5861

100 Elwood Davis Road Fax: 315-453-4594

Syracuse, New York 13212

----- Forwarded Message

Hello,

I have a Solaris 2.6 machine which acts as a jumpstart

install server for Solaris 2.6 and Solaris 7. I have

all of the packages and patches and a couple of config

files (like aliases, ntp.conf etc) in a directory

called /jumpstart/PACKAGE. I have two other directories,

/jumpstart/conf-2.6 and /jumpstart/conf-7, that hold

the custom jumpstart begin scripts, finish scripts and

rules files.

I'm finding that most of the begin and finish scripts

for both OS versions are identical (except for

the OS version of patches/packages I install). So, any changes made

in one place must be made in the other. Unless I'm

misunderstanding something,I thought that the begin/finish

scripts had to be in the same directory as the rules file.

Has anyone else run into this problem? If so, do you have

suggestions on how I could get around it?

Thanks in advance for your help!

Nicole Skyrca

AppliedTheory Corporation

U BEFORE POSTING please READ the FAQ located at

N ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/faq

. and the list POLICY statement located at

M ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/policy

A To submit questions/summaries to this list send your email message to:

N sun-managers@ececs.uc.edu

A To unsubscribe from this list please send an email message to:

G majordomo@codeprof.ececs.uc.edu

E and in the BODY type:

R unsubscribe sun-managers

S Or

. unsubscribe sun-managers original@subscription.address

L To view an archive of this list please visit:

I http://www.latech.edu/sunman.html

------- End of Forwarded Message