OpenLava Installation Procedure.pdf

Copyright Terapoc Inc. 2015 Page 1

OpenLava Installation Procedure

Last modified: March 17, 2015

Overview

Obtain OpenLava

Download OpenLava by visiting http://teraproc.com and following the OpenLava download links. After

filling in a short registration form you can select the version of OpenLava you wish to download and save

the rpm or deb install package locally. This procedure applies to both the current stable release

OpenLava as well as the beta release although there will be minor differences in file names and install

locations depending on which you select.

Prepare the Linux Cluster

 If you do not have a nameserver setup, you may need to manually enter IP addresses and

hostnames in the /etc/hosts file on each cluster node.

 OpenLava will send e-mail when jobs are completed, so while not necessary for OpenLava to

function, it is desirable to configure e-mail as well. This can be done after the OpenLava cluster

is installed and configured.

 Troubleshooting network issues can be tricky, so when installing the cluster, if your site policies

allow, you may want to temporarily disable the firewall on all nodes using “iptables service

stop” on RedHat, CentOS and Suse Linux or “ufw stop” on Ubuntu Linux. In the appendix we

provide additional guidance on how to manage firewalls across different Linux operating

systems.

Copyright Terapoc Inc. 2015 Page 2

In the installation example below, we have four Linux hosts. These happen to be RHEL 7.1 nodes. The

procedures described here may need to be adjusted depending on your environment and the specific

versions of Linux you are running.

Our cluster has the following hostnames.

Install OpenLava on the first host

should be the only one required, but additional information is provided below in case users encounter

difficulties with their environment.

You can elect to use rpm to install OpenLava instead. If you are installing on Ubuntu Linux (a Debian-

based distribution), instead of using the .rpm file you should use the .deb file provided by Teraproc and

use the dpkg command instead of yum or rpm. By default, recent versions of RHEL and CentOS do not

install TCL shared libraries (included in the TCL Developer’s package) or the “killall” command (included

in the “psmisc” package) required by OpenLava.

You can determine whether these packages are installed on your host using the commands below.