15.2 Preparing for Remote Installation

Before running pse-remote-install , you should perform the following tasks, which are explained in this section:

Set the PSE kit location
Copy the software subsets to the default kitpath directory
Create a system file
Create a License Product Authorization Kit (License PAK) file
Establish rsh access the remote host

15.2.1 Setting the PSE kit location

In order for pse-remote-install to install, delete, or verify software subsets, a directory path name (kitpath) must be defined where the software subsets are located. By default, pse-remote-install expects this directory pathname to be /var/adm/PSE/pse-remote-install/ALPHA . You can change this default by specifying the -k path name option. There are two methods for populating the kitpath directory with software subsets:

Directly using the CD-ROM containing the software subsets - Mount the CD-ROM device (for example /dev/rz4c ) to /cdrom using the command mount -r /dev/rz4c /cdrom . You can specify the -k /cdrom/PRODUCT/kit option to pse-remote-install where PRODUCT is any of the layered product subdirectory under the /cdrom directory.
For example, the following commands summarizes these steps:
```
% su
Password:
# mkdir/cdrom
# mount -r /dev/rz4c /cdrom
# cd /var/adm/PSE/pse-remote-install
# ./pse-remote-install -k /cdrom/pse120/kit  . . .
```
The benefit of using the CD-ROM directly, is that you do not need to copy the software subsets to any other directory. The disadvantage is that you must have the CD-ROM mounted, and that you have to run pse-remote-install several times for each PRODUCT directory you want to install.
Copying the software subsets to the default kitpath directory - You also have the option of populating the default /var/adm/PSE/pse-remote-install/ALPHA directory with the software subsets that you want to install, delete, or verify. To do this, you have to copy the software subsets from the CD-ROM to the default kitpath directory.
The following commands give an example how to copy software subsets from two products PSE120 and f9a400:
```
% su
Password:
# mkdir /cdrom
# mount -r /dev/rz4c /cdrom
# cd /cdrom
# /bin/csh
# foreach PRODUCT in (pse120 f9a400)
> cd/cdrom/$PRODUCT/kit
> tar cvpf - . | (cd /var/adm/PSE/pse-remote-install/ALPHA; tar xpf -)
> end
```
The main advantages of populating the default kitpath are performance (the hard disk is faster than the CD-ROM device) and the ability to install several software products from a single pse-remote-install command.

Before you install any software subsets other than the ones from the PSE kit, refer to Section 15.5 for some restrictions.

15.2.2 Creating a System File

One of the required options for pse-remote-install is a system file containing a list of host names on which remote installation is to take place. This file must be created within the /var/adm/PSE/pse-remote-install directory. The system file can have any name, and this filename is specified as a parameter to the pse-remote-install command. The format of the system file is one host name per line.

For remote installation of a basic PSE cluster, create a file named psecluster.nodes containing a list of nodes for remote installation.

For customized PSE clusters, the PSE cluster database editor, psedbedit , creates a clustername.nodes file in the /var/adm/PSE/pse-remote-install directory when new cluster members are added to the PSE cluster database. You can use the clustername.nodes file as the system file to install the PSE kit to the hosts listed in the file. Note that the clustername.nodes file is overwritten anytime you use psedbedit to add new PSE cluster members.

15.2.3 Creating a License PAK File

The pse-remote-install command lets you optionally install or delete software License PAKs when you install or delete software subsets. Typically, a software License PAK for a software product is unique for each system. For pse-remote-install to install this license PAK to the remote hosts, the license PAKs for each host have to be stored in the /var/adm/PSE/pse-remote-install/pak directory. The license PAK file names have the following conventions:

The file name format is prefix.hostname, where prefix is any name that is unique for a particular software product, and hostname is the host name on which the License PAK is to be installed. To guarantee uniqueness for prefix, Digital recommends using the Product Name entry in the license PAK, for example, PSE-O for the PSE kit.
You must create a License PAK file in the /var/adm/PSE/pse-remote-install/pak directory for each software product you want to install and for each host where the product is to be installed. You can use the /var/adm/PSE/pse-remote-install/pak/pak.template as a template to create the License PAK file and fill in the entries within this template with the information from the License PAK you obtained.

For example, suppose you want to install the PSE and Fortran 90 kit on host1 and host2 :

% su
Password:
# cd /var/adm/PSE/pse-remote-install/pak
# cp pak.template PSE-O.host1
# cp pak.template PSE-O.host2
# cp pak.template FORTRAN90-O.host1
# cp pak.template FORTRAN90-O.host2
# vi PSE-O.host1       (filling the entries with the information from the)
                        PSE-O license PAK you obtained for host1)
# vi PSE-O.host2       (filling the entries with the information from the)
                        PSE-O license PAK you obtained for host2)
# vi FORTRAN90-O.host1 (filling the entries with the information from the)
                        FORTRAN90-O license PAK you obtained for host1)
# vi FORTRAN90-O.host2 (filling the entries with the information from the)
                        FORTRAN90-O license PAK you obtained for host2)

15.2.4 Establishing rsh Access to the Remote Host

In order for pse-remote-install to perform its tasks on the target hosts, the target hosts must allow the install server (where pse-remote-install is run) to run remote shell (rsh) to the target hosts as root. This is done by adding the install server's host name to the /.rhosts file on each target host. The /.rhosts file must be edited locally on each target host.