In a previous post i showed how to add a system to a jumpstart configuration. Now i will show how to add a new release of Solaris to the jumpstart.

# cd /cdrom/cdrom0/Solaris_10/Tools

# ./setup_install_server /work/install/sol10_0508

This will copy all the files from the dvd to the appropriate directories on your jumpstart server. Be patient, this may take a long time.

Don’t forget to edit /etc/bootparams for existing systems in your environment that will want to install the older image.

Now that the JET install creates the server exactly how we like it let’s look at turning it into a flash archive (flar) image to use with jet. This will speed up even more the install process.

grolsch:/work # flarcreate -n “sb100 flar” -S -R / -x /work -x /export/home /work/sb100-snapshot.080318.flar
Full Flash
Checking integrity…
Integrity OK.
Running precreation scripts…
Precreation scripts done.
Creating the archive…
6080747 blocks
Archive creation complete.
Running postcreation scripts…
Postcreation scripts done.

Running pre-exit scripts…
Pre-exit scripts done.

grolsch:/work # ls -la
total 6083780
drwxr-xr-x 3 root root 512 Mar 18 09:51 .
drwxr-xr-x 23 root root 512 Mar 17 17:34 ..
-rw-r–r– 1 root root 3113352215 Mar 18 10:10 sb100-snapshot.080318.flar

We have to add the flash module to our template:

heineken:/opt/SUNWjet/bin # ./make_template -f -T grolsch grolsch flash
./make_template[119]: hostname
Adding product configuration information for
+ flash
./make_template[427]: hostname
Updating base_config template specifics
Client template created in /opt/SUNWjet/Templates

And we have to edit the template to include information on the flar:

flash_archive_locations=”nfs://10.0.0.10/work/jumpstart/flash/sb100-snapshot.080318.flar”

There, that template can now be used to quickly jump any sun4u system very quickly. It will be fully patched, include all extra packages we like and even be fully configured thanks to JET. Bear in mind the flar is used as a guide only and on its own does not contain all configuration settings. For example, if the flar was put into a blank template the hosts file, /etc/vfstab, defaultrouter, etc would not be set.

In part 2 of the series of posts on JET we added the sds module to our jet template but did not yet implement a mirror. That is what we will do now. The rootdisk will be set to c0t0d0 (as defined in OBP’s rootdisk alias). Most of the variable settings are very straight forward.

To the template. The first section asks us which cluster to install, which disk to use and to layout that disk. The below details will set the cluster to install all+OEM on rootdisk (c0t0d0), set root slice to 0 and use 8gb, swap to s1 with 1gb and var to s3 with 2gb.  I also want to remove a few packages from the complete install using the base_config_profile_del_packages setting.

base_config_profile_cluster=SUNWCXall
base_config_profile_usedisk=rootdisk.
base_config_profile_dontuse=”"
base_config_profile_root=8192
base_config_profile_swap=1024
base_config_profile_s3_mtpt=”/var”
base_config_profile_s3_size=”2048″
base_config_profile_s4_mtpt=”"
base_config_profile_s4_size=”"
base_config_profile_s5_mtpt=”/var”
base_config_profile_s5_size=”"
base_config_profile_s6_mtpt=”/usr”
base_config_profile_s6_size=”"

base_config_profile_del_packages=”SUNWaclg SUNWapch2d SUNWapch2r SUNWapch2u SUNWapchd SUNWapchr SUNWapchu SUNWtcatr SUNWtcatu SUNWmysqlr SUNWmysqlt SUNWmysqlu SUNWserweb SUNWipplr SUNWseru”

Now to configure the sds module in the template. As i am using Solaris 10 i have fmthard set to yes, which takes care of some automation for us. In this section i can set the metadevices to use and set some aliases for disks. Below are the settings i use:

sds_root_mirror=”c0t2d0″
sds_use_fmthard=”yes”
sds_database_locations=”rootdisk.s7:3″
sds_root_alias=”rootdisk”
sds_root_mirror_devalias_name=”rootmirror”
sds_device_numbers=”/:d0:d10:d20 /var:d3:d13:d23 swap:d1:d11:d21″

And that’s it, run another boot net - install and your system will come up with the custom disk layouts and fully mirrrored. There are many more options to create other metadevices but i use scripts for that as i wish to preserve current disk structures. For example i run the following script which sets up slice 5 and then i put a metadevice on it. This way whatever information was on slice 5 (or d40) is preserved.

format -f /mnt/files/fmt-disk c0t0d0s0
format -f /mnt/files/fmt-disk c0t2d0s0
metainit d40 2 1 c0t0d0s5 1 c0t2d0s5

The contents of fmt-disk (print -> print -> slice 5 -> enter -> enter -> starting point 28115 -> size 10674c -> label -> quit -> quit):

p
p
5

28115
10674c
l
q
q
Next post will look at creating a flar to speed the whole process up even more.

In the last post on JET we created a very basic template but other than the bare minimum there was absolutely no added functionality that makes JET so powerful and easy to use. So in this post i want to show how to add explorer and custom patches and packages. This still is touching on the basics, but it’s a start to showing the extra features over regular jumpstart.

I will keep using the custom template i build in the last post but add sds and explo modules to the template. In a later post i will show how to use sds for mirroring but i will add it now.

heineken:/opt/SUNWjet/bin # ./make_template -f -T grolsch grolsch sds explo
Adding product configuration information for
+ sds
+ explo
Updating base_config template specifics
Client template created in /opt/SUNWjet/Templates

Download and unpack the explorer package. In this instance it resides in /work:

heineken:/work # pkginfo -d /work/ -l | egrep ‘(PKGINST|VERSION)’
PKGINST: SUNWexplo
VERSION: 5.10,REV=2007.09.20.19.12
PKGINST: SUNWexplu
VERSION: 5.10,REV=2007.09.20.19.12

Now, this is very important. We have to check and possibly edit the /opt/SUNWjet/Product/explo/package.matrix file. We have to ensure there is an entry for the latest version of explorer, in this case 5.10. I added the line below to the file and then added the package to the toolkit.

heineken:/opt/SUNWjet/Products/explo # vi package.matrix
5.10:5.10:SUNWexplo SUNWexplu

heineken:/opt/SUNWjet/bin # ./copy_product_media explo 5.10 /work sparc
Transferring <SUNWexplo> package instance
Transferring <SUNWexplu> package instance

Packges copied.

So, let’s confirm it’s all there.

heineken:/work/jumpstart/install/pkgs # ls -la
total 6
drwxr-xr-x 3 root root 512 Mar 3 11:35 .
drwxr-xr-x 5 root root 512 Feb 14 13:16 ..
drwxr-xr-x 3 root root 512 Mar 3 11:35 explo

heineken:/opt/SUNWjet/bin # ./list_product_versions
Product Versions
——- ——–
explo 5.10

You’ll need to modify the explorer module inside the template file, especially where it asks the version of the explorer. You can also fill in the explorer defaults straight away.

Ok, that’s that. But that was how to add the explorer package which comes with its very own module. What about packages from say sunfreeware.com.

Let’s install sudo. Download SMCsudo, SMCgcc and SMCliconv from www.sunfreeware.com. In my case i will download them to /tmp. To add them to the jumpstart is a two command process for every package.

heineken:/opt/SUNWjet/bin # pkgtrans /tmp/gcc-3.4.6-sol10-sparc-local /work SMCgcc
Transferring <SMCgcc> package instance
heineken:/opt/SUNWjet/bin # ./copy_custom_packages /work sparc SMCgcc
Transferring <SMCgcc> package instance
Packages copied

heineken:/opt/SUNWjet/bin # ./list_product_versions
Product Versions
——- ——–
custom sparc
explo 5.10

heineken:/work/jumpstart/install/pkgs/custom/sparc # ls -la
total 8
drwxr-xr-x 4 root root 512 Mar 4 11:45 .
drwxr-xr-x 3 root root 512 Mar 4 11:40 ..
drwxr-xr-x 3 root root 512 Mar 4 11:59 SMCgcc
drwxr-xr-x 3 root root 512 Mar 4 11:45 SMCliconv
drwxr-xr-x 3 root root 512 Mar 4 11:40 SMCsudo

Now we have to update the custom_packages line in the template:

custom_packages=”SMCgcc SMCliconv SMCsudo”

And add a patch. Let’s add the daylight savings patch to the /work/jumpstart/patches/custom directory and update the template.

custom_patches=”125378-05″

Update the client and do another boot net - install:

heineken:/opt/SUNWjet/Templates # ../bin/make_client -f grolsch