Sun HPC ClusterTools 8.1 Software Installation Guide

This chapter explains how to install and configure Sun HPC ClusterTools software on a Solaris OS-based non-NFS configuration using the installation utilities. For information about how to install the software in a Solaris OS-based NFS configuration, see Chapter 4. For information about how to install Sun HPC ClusterTools software on a Linux-based system, see Chapter 6.

The Sun HPC ClusterTools software CLI utilities are:

• ctinstall - Install the software on the cluster nodes.
• ctact - Activate the software on the cluster nodes (optional).
• ctdeact - Deactivate the software on the cluster nodes (optional).
• ctremove - Remove the software from the cluster nodes.

This chapter contains the following topics:

• Installing Sun HPC ClusterTools Software
• Activating Sun HPC ClusterTools Software
• Deactivating Sun HPC ClusterTools Software
• Removing Sun HPC ClusterTools Software

---

Installing Sun HPC ClusterTools Software

Before you can install and configure the software, you must make sure you have downloaded the correct software archive for your hardware platform. Once you have downloaded the software, you need to extract it to the correct directory. If you have installed a previous version of the software, there are additional steps you need to do to prepare for installation. The following procedure explains these steps.

1. Boot the cluster nodes.

2. Download and extract the archive file containing the Sun HPC ClusterTools software to a location (such as a shared file system) that is visible to all the nodes in the cluster.

a. Make sure that all the compute and administrative nodes have access to the shared file system.

b. Make sure that the file system is readable by superuser and accessible through a common path from all nodes.

For centralized installations, do this on the central host as well.

You can obtain the correct HPC ClusterTools archive file for your platform from the following location:

http://www.sun.com/clustertools/

3. Log in as superuser on the system from which you will be initiating the command: the central host or, if initiating the command locally, directly on a cluster node.

4. If the Sun HPC ClusterTools software has not been installed yet, change directory to one of the following:

a. If you are installing the software on a SPARC-based system, change directory to /sun-hpc-ct8.1-sparc/Product/Install_Utilities/bin

b. If you are installing on an x64-based system, change directory to /sun-hpc-ct-i386/Product/Install_Utilities/bin

If the software has already been installed, go to Step 5.

5. If the software was previously installed and you intend to perform such tasks as activation, deactivation, or removal of the software, change directory to $INSTALL_LOC/SUNWhpc/HPC8.1/bin/Install_Utilities/bin.

$INSTALL_LOC is the location where the software was installed.

You can now start using the CLI commands. They are described separately below, with examples of common applications given for each.

For usage information on any command, either enter the command without options or with the -h option.

# ./command

# ./command -h

ctinstall Options

Use the ctinstall command to install Sun HPC ClusterTools software on cluster nodes. See TABLE 3-1 for a summary of the ctinstall options.

-h

-l

-R

-x

-a

-c

-d

-p

-t

-g

-k

-n

-N

-r

-S

Installing the Software From a Central Host in a Non-NFS Configuration

This section discusses the following options for installing the software from a central host:

• To Install From a Central Host Using rsh
• To Install From a Central Host Using ssh
• To Install From a Central Host Using telnet
• To Install the Software and Save the Log Files
• To Install Specified Software Packages

This section shows examples of software installations in which the ctinstall command is initiated from a central host.

# ./ctinstall -n node1,node2 -r rsh

The following command installs the full Sun HPC ClusterTools software suite on node1 and node2 from a central host. The node list is specified on the command line. The remote connection method is rsh. This requires a trusted hosts setup.

The software will be ready for use when the installation process completes.

# ./ctinstall -n node1,node2 -r ssh

This example is the same as that in the previous section, except that the remote connection method is ssh. This method requires that the initiating node be able to log in as superuser to the target nodes without being prompted for any interaction, such as a password.

# ./ctinstall -N /tmp/nodelist -r telnet

This command installs the full Sun HPC ClusterTools software suite on the set of nodes listed in the file /tmp/nodelist from a central host. A node list file is particularly useful when you have a large set of nodes or you want to run operations on the same set of nodes repeatedly.

The node list file has the following contents:

# Node list for the above example
 
node1
node2

The remote connection method is telnet. All cluster nodes must share the same password. If some nodes do not use the same password as others, install the software in groups, each group consisting of nodes that use a common password.

The software will be ready for use when the installation process completes.

# ./ctinstall -N /tmp/nodelist -r telnet -k /tmp/cluster-logs -g

The command in this section is the same as that shown in the previous section, except that it includes the -k and -g options.

In this example, the -k option causes the local log files of all specified nodes to be saved in /tmp/cluster-logs on the central host.

The -g option causes a pair of node list files to be created on the central host in /var/sadm/system/logs/hpc/nodelists. One file, ctinstall.pass$$, contains a list of the nodes on which the installation was successful. The other file, ctinstall.fail$$, lists the nodes on which the installation was unsuccessful. The $$ symbol is replaced by the process number associated with the installation.

These generated node list files can then be used for command retries or in subsequent operations using the -N switch.

The following command installs only the specified software packages.

# ./ctinstall -N /tmp/nodelist -r telnet -p SUNWompi,SUNWompimn

This command installs the packages SUNWompi and SUNWompimn on the set of nodes listed in the file /tmp/nodelist. No other packages are installed. The remote connection method is telnet.

Appendix A lists the packages in the Sun HPC ClusterTools 8.1 installation.

The -p option can be useful if individual packages were not installed on the nodes by ctinstall.

# ./ctinstall -N /tmp/nodelist -r rsh

This command installs and activates the full Sun HPC ClusterTools software suite on the nodes listed in the file /tmp/nodelist. The remote connection method is rsh.

Installing Software Locally in a Non-NFS Configuration

This section shows examples of software installations in which the ctinstall command is initiated on the local node. The installation options shown in this example include:

• To Install the Complete Software Suite
• To Install Specified Software Packages

# ./ctinstall -l

This command installs the full Sun HPC ClusterTools software suite on the local node only.

# ./ctinstall -l -p SUNWompi,SUNWompimn

The command in this section installs the packages SUNWompi and SUNWompimn on the local node.

Appendix A lists the packages in the Sun HPC ClusterTools 8.1 installation.

---

Activating Sun HPC ClusterTools Software

In Sun HPC ClusterTools 8.1 software, the activation step sets up symbolic links to the program binaries. If you are running Sun HPC ClusterTools 8.1 only, you may skip the activation step and run Sun HPC ClusterTools 8.1 software from the directory in which it is installed (by default /opt/SUNWhpc/HPC8.1/bin).

ctact Options

Use the ctact command to activate Sun HPC ClusterTools software on cluster nodes. See TABLE 3-2 for a summary of the ctact options.

-h

-l

-R

-x

-c

-g

-k

-n

-N

-r

-S

Activating Nodes From a Central Host

This section shows examples of software activation in which the ctact command is initiated from a central host.

# ./ctact -n node1,node2 -r rsh

This command activates the software on node1 and node2. The remote connection method is rsh.

# ./ctact -n node1,node2 -r rsh -k /tmp/cluster-logs -g

This command is the same as the one in the previous section, except that it specifies the options -k and -g.

In this example, the -k option causes the local log files of all specified nodes to be saved in /tmp/cluster-logs on the central host.

The -g option causes files ctact.pass$$ and ctact.fail$$ to be created on the central host in /var/sadm/system/logs/hpc/nodelists. ctact.pass$$ lists the cluster nodes on which software activation was successful and ctact.fail$$ lists the nodes on which activation was unsuccessful. The $$ symbol is replaced by the process number associated with the activation.

These generated node list files can then be used for command retries or in subsequent operations using the -N switch.

Activating the Local Node

This section shows an example of software activation on the local node.

# ./ctact -l 

This command activates the software on the local node.

---

Deactivating Sun HPC ClusterTools Software

Use the ctdeact command to deactivate Sun HPC ClusterTools software on cluster nodes.

ctdeact Options

See TABLE 3-3 for a summary of the ctdeact options.

-h

-l

-R

-x

-g

-k

-n

-N

-r

-S

Deactivating Software From a Central Host

This section shows examples of software deactivation in which the ctdeact command is initiated from a central host.

# ./ctdeact -N /tmp/nodelist -r rsh

This command deactivates the software on the nodes listed in /tmp/nodelist. The remote connection method is rsh.

# ./ctdeact -N /tmp/nodelist -r rsh -k /tmp/cluster-logs -g

This command is the same as the command in the previous section, except that it specifies the options -k and -g.

In this example, the -k option causes the local log files of all specified nodes to be saved in /tmp/cluster-logs on the central host.

The -g option causes files ctdeact.pass$$ and ctdeact.fail$$ to be created on the central host. ctdeact.pass$$ lists the cluster nodes where software deactivation was successful. ctdeact.fail$$ lists the nodes where deactivation was unsuccessful. The $$ symbol is replaced by the process number associated with the software deactivation.

These generated node list files can then be used for command retries or in subsequent operations using the -N switch.

Deactivating the Local Node

This section shows software deactivation on the local node.

# ./ctdeact -l

This command deactivates the software on the local node.

---

Removing Sun HPC ClusterTools Software

Use the ctremove command to remove Sun HPC ClusterTools software from cluster nodes.

ctremove Options

See TABLE 3-4 for a summary of the ctremove options.

-h

-l

-R

-x

-p

-c 

-g

-k

-n

-N

-r

-S

Removing Nodes From a Central Host

This section shows examples of software removal in which the ctremove command is initiated from a central host.

# ./ctremove -N /tmp/nodelist -r rsh

This command removes the software from the nodes listed in /tmp/nodelist. The remote connection method is rsh.

# ./ctremove -N /tmp/nodelist -r rsh -k /tmp/cluster-logs -g

This command is the same as the command in the previous section, except that it specifies the options -k and -g.

# ./ctremove -N /tmp/nodelist -r rsh -p SUNWompi,SUNWompimn

This command removes the packages SUNWompi and SUNWompimn from the nodes listed in /tmp/nodelist. The remote connection method is rsh.

Removing Software From the Local Node

This section shows software removal from the local node.

# ./ctremove -l

This command removes the software on the local node.

# ./ctremove -l -p SUNWompi,SUNWompimn

This command removes the packages SUNWompi and SUNWompimn from the local node.

Sun HPC ClusterTools 8.1 Software Installation Guide

820-6792-10

Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.