Is it a good idea to add current patch cluster to jumpstart server?

[kahn630]

Is it a good idea to add current patch cluster to jumpstart server?

 

[Annihilannic]

Yes, if you have tested the patch set and trust it, and don't want to apply it again to every server that you build.

Annihilannic.

 

[daFranze]

afaik, patching a jumpstart image does not aply the patches to the clients being installed by this server! It just patches the Jumpstart Image itself (the miniroot, which will be copied to the client first). If you want to patch the installed client you will have to write a script which aplies the patches to the client (afai remember it should be a /etc/rcS.d/S99 script which runs once after rebooting the host after installation)

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage

 

[Annihilannic]

Yep, I believe Franz is correct; I just checked our Jumpstart server and the patches I was thinking of are installed as part of one of our finish scripts, so of course we would use the latest proven patch bundle for that.

Apologies for any confusion caused!

Annihilannic.

 

[kHz]

In AIX if I wanted to perform this same task I would add the filesets to the lppsource and then create a new spot.

To upgrade the server to a new level I would run:
spbootins -r migrate -c 2 -h hdisk0,hdisk1 -v AIX510 -p PSSP-3.4 -l 3

This would migrate the server to the level of AIX 5.1 and PSSP 3.4 on the host (node 3) and this would be done from my control workstation.

What would the steps be for Jumpstart? Do you add the patches to image? Then how do you migrate to a new OS version or maintenance level? For an initial install you run a 'boot net - install' but how do you upgrade the level or version of OS using Jumpstart?

I have a lot of experience with AIX/PSSP. I can install clients using Jumpstart, but not upgrading clients with Jumpstart.

Thanks