Monday Oct 25, 2010

JET 4.8 Now available

 It has been a long while. We've had about 6 internal releases of JET 4.7.1, .2, .3 etc, but we've recently gone to 4.8

The main highlight is that JET 4.8 has the new sysidcfg variables required for the unattended installation of Solaris 10 09/10. It also knows about the "new" Solaris 10 Recommended patch structure.

The best way to get it is to click the link at the top of the wiki site.

JET 4.8 Changes:

As mentioned above the main JET change is the addition of a new base_config_sysidcfg variable to allow the auto-registration stuff to be configured. 

Other changes:

Ksh93

All the modules have been updated to be ksh93 compliant, for those of you who are using OpenSolaris/Nevada/Solaris 11 Express Jumpstart servers.

Recommended Patches

The Solaris 10 Recommended patches (since around this time last year) have had a different directory structure, a better installation script, and a "password" to ensure that you've read the "README". JET understands this new structure and uss the installer script if present. A new base_config variable: base_config_recpatch_passcode has been added to supply the password.

Assorted Bug fixes

I've fixed an issue with the hosts file with DHCP Sparc hosts, check_client for custom checks f and m scripts, nfsmapid is started in the miniroot so nfsv4 shared files have the right perms, search items are now first in resolv.conf, use of correct awk in get_matrix_byname, added clearer fdisk comments, fixed an update_template bug, stopped n-1 custom from forcing another boot, made setupdumpdevice work only in a global zone, further refined run_sshkeygen, updated pkginfo to install only in "THISZONE".

Menu.lst enhancements

There's now a bit more flexibility in dealing with the menu.lst file. JET has always had the capability of simply appending a file to the menu.lst file using base_config_menulst_append. I've added 3 more variables to allow even more control:

1: base_config_grub_append: lets you add arguments to the boot line in the menu.lst file.

2: base_config_grub_timeout: change the default timeout from 2 seconds to whatever you set here.

3: base_config_grub_singleuser: add a boot option in menu.lst to boot net single user.

Custom Files enhancements:

You can now optionally specify owner:group:mode for each files that custom_files copies. Under normal circumstances JET simply duplicates the perms of the file on the JET server. In implementing this, I discovered an interesting bug with NFS permissions in the net-booted Solaris, which meant I had to work around that by manually starting nfsmapid in the Jumpstart phase to ensure correct and consistent permisssions.

Auto-Reg

Implemented the auto_reg functionality. Probably easier to simply paste the comments in the Template here:

#
# From Solaris 10 Update 9 onwards, a new sysidcfg keyword exists: auto_reg
# This allows automatic Solaris registration to take place.
# auto_reg can be all, noproxy, anon, none or disable
#
base_config_sysidcfg_auto_reg=disable
#
# "all" requires ALL additional fields to be filled in
# "noproxy" requires only oracle_user and oracle_pw fields to be filled in
# "anon" requires all the http_proxy fields to be filled in
# "none" or "disable" do not need any additional fields.

base_config_sysidcfg_auto_reg_oracle_user=""
base_config_sysidcfg_auto_reg_oracle_pw=""
base_config_sysidcfg_auto_reg_http_proxy_host=""
base_config_sysidcfg_auto_reg_http_proxy_port=""
base_config_sysidcfg_auto_reg_http_proxy_user=""
base_config_sysidcfg_auto_reg_http_proxy_pw=""

Other Modules

Some minor changes/updates have been made to some of the modules JetSDS, JetZFS, JetZONES. Mainly bugfixes and error reporting enhancements, so no huge functionality changes, but you might want to scan through the comments in the templates as I have rewritten some of them to make some of the existing functionality clearer.

Summary

As usual, we maintain backwards compatibility, so your existing templates will continue to work. To make use of the new functionality, you'll need to refresh your templates. All new clients (created with make_template) will automatically have the new variables. (Have a scan through sample.template in /opt/SUNWjet/Templates to see what's changed.)

In case anyone asks. Upgrading JET is as simple as pkgrming your existing JET modules, and then pkgadding the new ones. JET won't remove any of your existing configuration, Template or Client files.


tags:

About

mramcha

Search

Archives
« October 2010 »
MonTueWedThuFriSatSun
    
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
26
27
28
29
30
31
       
Today