3.2. Starting the Install

Log into the machine as root and install the Red Hat HPC bootstrap RPM:

	# yum install ocs mod_ssl

After installing the ocs RPM, source the OCS environment:

# source /etc/profile.d/kusuenv.sh

Run the installation script:

# /opt/kusu/sbin/ocs-setup

The script detects your network settings and provide a summary per NIC:

NIC: eth0 
============================================================
     Device = eth0            IP = 172.25.243.44
     Network = 172.25.243.0   Subnet = 255.255.255.0
     mac = 00:0C:29:C4:61:06  Gateway = 172.25.243.2
     dhcp = False             boot = 1

Note

Red Hat HPC cannot provision over DHCP configured NICs, only statically configured NICs. The OCS installer asks if you want to provision on all networks, and if not which ones to provision on.

Red Hat HPC creates a separate DNS zone for the nodes it installs. The tool prompts for this zone.

Warning

Do not use the same DNS zone as any other in your organization. Using an existing zone causes DNS name resolution problems.

Note

The Red Hat HPC Solution tries to generate IP addresses for the individual Compute Nodes by incrementing from the Installer Node's IP address in the private cluster network. The Installer Node therefore has a low IP address in that network and a free range following that IP address, or the user must adjust the Starting IP for provisioned Compute Nodes using the “netedit” tool.

The Red Hat HPC Solution stores a copy of the OS media and installation images. The OCS installer prompts for the location of the directory to store the operating system. The default is /depot. A symbolic link to /depot is created if another location is used.

The OCS installer builds a local repository using the OS media. This repository is by OCS when provisioning compute nodes.

The OCS installer asks for the physical DVD or CDs (in the optical drive physically connected to the installer host), a directory containing the contents of the OS media, or an ISO file providing the media.

Note

if using the “file(system)” option to provide the OS media (via a subdirectory) to the OCS installer, answer “N” to the prompt for additional disks when prompted.

After the OS media is successfully imported (approximately 5-10 minutes when importing from a physical optical drive) and the local OCS repository created, a sequence of scripts runs to configure the OCS cluster for the installation.

The default firewall rules for a RHEL installation blocks the ports needed to provision nodes. The script provided configures the firewall to allow these ports. When the script runs, it opens the ports necessary for provisioning the nodes. It also configures Network Address Translation (NAT) on the installer node, so that the provisioned nodes can access the non-provisioning networks connected to the installer on other interfaces.

To run the script to configure the firewall as root, run:

		# /opt/kusu/bin/kusurc /opt/kusu/etc/S02KusuIptables.rc.py

Once the installation has completed the following message appears:

Congratulations! The base kit is installed and configured to provision on:	
Network 1.2.3.4 on interface  ethX

The installer node is ready to begin installing other nodes in the cluster.

Prior to installing the compute nodes it is best to add all the desired kits, and customize the node groups. If the kits are added after the Compute Nodes have been installed it is necessary to run the following command to get Nagios® and Cacti® to display the nodes in their respective web interfaces:

# addhost -u

This causes re-generation of many of the application configuration files.