Updating the Toolkit and Associated Modules.
The toolkit framework is supplied in pkgadd format; to update it, pkgrm the old version and then pkgadd the updated version. The dependency checking will inform you that any installed modules are dependent on it, but you should continue.
Any other modules should be updated in the same fashion.
Where possible, updates to the toolkit will continue to support templates created with older versions of the toolkit. If enhancements have been made to the toolkit supplied 'base_config' or 'custom' modules, or the individual modules have been improved, it may require the creation of new templates to fully realise the new features.
Since the templates are simply bourne shell scripts, any additional variables available in new templates may simply be manually inserted into existing templates to enable those features.
Exporting the media, pkgs and patches directory
The utility scripts provided with JumpStart have basic functionality for adding the NFS share of the target servers boot directory at configuration time, however, they do not encompass the additional requirements of the JumpStart Enterprise Toolkit.
It is suggested that your chosen location for the media repository is shared; for example, the following lines could be added to the /etc/dfs/dfstab file:
share -F nfs -o ro,anon=0 /export/install
 | ENSURE THAT YOU SHARE THE ABOVE DIRECTORIES AS ro,anon=0 AS CORRUPTION OF THE SOLARIS IMAGE CAUSES VERY STRANGE ERRORS THAT ARE DIFFICULT TO FIND AND RESOLVE! |
The above example assumes that you have chosen the default locations for media, packages and patches. If not, you must ensure that your seelcted directories, as found in '/opt/SUNWjet/etc/jumpstart.conf' have been properly shared.
The '/opt/SUNWjet' directory share is added automatically during the package installation; if for any reason it is not added, please add it as per the example above.
If your media locations are on a ZFS filesystem, then you should use the sharenfs property of ZFS for those filesystems, not the /etc/dfs/dfstab file.
 | Note: There may be issues with running add_install_client on older Solaris releases when the media is a ZFS filesystem as it may not detect that the filesystem is shared. |
Product Media Installation
Product Packages
If you are using additional modules which require media, the packages required for the modules, such as Solaris Volume Manager, can be added to the JumpStart server using the command '/opt/SUNWjet/bin/copy_product_media'.For example:
# copy_product_media <module> <version> <src media>
The versions the module supports should be defined in the documentation that accompanied it, or inspect '/opt/jet/Products/<module>/package.matrix' if it exists.
Product Patches
The patches required for a particular module can be copied using the '/opt/SUNWjet/bin/copy_product_patches' script. For example:
# copy_product_patches <module> <version> <src media>
Package and Patch Definitions
Most of the modules that have already been developed by Sun, use two files within the module directory to define what packages and patches are required for a specific version of the product. By using this mechanism, the logic of how to install the particular product remains unchanged and new versions can be added quickly without risk of corrupting a script.
The two files are called 'package.matrix' and 'patch.matrix' and can be found in the '/opt/SUNWjet/Products/<module name>' directory for each module.
The files themselves are colon delimited lines which define the set of packages or patches to install on a per operating system release, per hardware platform and per product version basis.
As new product patches become available over time, it will be necessary to update the relevant patch.matrix.
New patches should be thoroughly tested before being implemented in a production environment.
The JumpStart Enterprise Toolkit has a pre-defined set of patches for the modules supplied, but given the nature of software patches, these definitions will become out of date, and the patch.matrix file will need to be updated.