Moab HPC Suite – Basic Edition7.1.4Installation Guide

March 2013

© 2013 Adaptive Computing Enterprises, Inc. All rights reserved.

Distribution of this document for commercial purposes in either hard or soft copy form is strictly prohibited without prior writtenconsent from Adaptive Computing Enterprises, Inc.

Adaptive Computing, Cluster Resources, Moab, Moab Workload Manager, Moab Viewpoint, Moab Cluster Manager, Moab ClusterSuite, Moab Grid Scheduler, Moab Grid Suite, Moab Access Portal, and other Adaptive Computing products are either registeredtrademarks or trademarks of Adaptive Computing Enterprises, Inc. The Adaptive Computing logo and the Cluster Resources logoare trademarks of Adaptive Computing Enterprises, Inc. All other company and product names may be trademarks of theirrespective companies.

Adaptive Computing Enterprises, Inc.1712 S. East Bay Blvd., Suite 300Provo, UT 84606+1 (801) 717-3700www.adaptivecomputing.com

Scan to open online help

ii

iii

Welcome v

Installation overview 1

Installing TORQUE 3

Installing Moab Workload Manager 5

Installing Moab Web Services 11

Installing Moab Viewpoint 17

Installing Moab Cluster Manager 21

Component documentation 23

Contents

WelcomeWelcome to the Moab HPC Suite – Basic Edition 7.1.4 Installation Guide, which will help you install yourMoab HPC Suite. This guide includes detailed instructions for installing each component of the suite so thatyou can quickly get up and running.

This guide is intended for system administrators who are responsible for installing the Moab HPC Suite –Basic Edition.

The Moab HPC Suite – Basic Edition version 7.1.4 contains the following components:

l Moab Workload Manager 7.1.4

l TORQUE 4.1.4

l Moab Web Services 7.1.4

l Moab Viewpoint 7.1.4

l Moab Cluster Manager 7.1.4

To get started with installing your Moab HPC Suite, please see Installation overview on page 1.

v

Installation overviewThe installation process of the Moab HPC Suite includes installing the separate components in the suite.This guide contains detailed instructions for installing each component.

Many individual components have dependencies on other components. (These dependencies arelisted in the "Requirements" section of each component's installation instructions.) However, if youdo not require a certain component (Moab Viewpoint, for example), you do not have to install it.

The install instructions for each component include information about system requirements anddependencies. Some include prerequisite instructions that you will need to complete before you begin theinstall. Please read this information carefully, and make sure you have installed all the dependencies andpackages that are necessary in order to avoid errors during the Moab HPC Suite install process.

To install the Moab HPC Suite, install the packages in the following order:

1. Install TORQUE (see Installing TORQUE on page 3).

2. Install Moab Workload Manager (see Installing Moab Workload Manager on page 5).

3. Install Moab Web Services (see Installing Moab Web Services on page 11).

4. Install Moab Viewpoint (see Installing Moab Viewpoint on page 17).

5. Install Moab Cluster Manager (see Installing Moab Cluster Manager on page 21).

Related topics

l Welcome on page v

1

Installing TORQUEThese instructions describe how to install and start TORQUE.

Requirements

The following software is required to run TORQUE 4.1.4:

l libxml2-devel package (package name may vary)

l openssl-devel package (package name may vary)

l ANSI C compiler. The native C compiler is recommended if it is ANSI; otherwise use gcc.

l A fully POSIX make. If you are unable to "make" PBS with your make, we suggest using gmakefrom GNU.

l Tcl/Tk version 8 or higher if you plan to build the GUI portion of TORQUE or use a Tcl basedscheduler.

l If you use cpusets, libhwloc 1.1 or later is required (for TORQUE 4.0.0 and later)

Dependencies and packages installation

Use the following commands to install the required TORQUE dependencies and packages (listed in theRequirements section above).

RHEL

[root]# yum update[root]# yum install make libxml2-devel openssl-devel gcc gcc-c++

CentOS

[root]# yum update[root]# yum install make libxml2-devel openssl-devel gcc gcc-c++

Prerequisites

TORQUE requires certain ports to be open for essential communication:

l For client communication to pbs_server, all privileged ports must be open (ports under 1024).

l For pbs_server communication to pbs_mom, the default port is 15003.

l For pbs_mom to pbs_server, the default port is 15001.

For more information on how to configure the ports that TORQUE uses for communication, seeConfiguring Ports.

3

Installing TORQUE

To install TORQUE

1. Run each of the following commands in order.

[root]# tar xzvf torque-4.1.4.tar.gz[root]# cd torque-4.1.4[root]# ./configure[root]# make[root]# make install

For information on what options are available to customize the ./configure command, see Customizingthe install.

2. Configure the trqauthd daemon to start automatically at system boot.

[root]# cp contrib/init.d/trqauthd /etc/init.d/[root]# chkconfig --add trqauthd[root]# echo /usr/local/lib > /etc/ld.so.conf.d/torque.conf[root]# ldconfig[root]# service trqauthd start

3. The make packages command can be used to create self-extracting packages that can be copied andexecuted on your nodes. For information on creating packages and deploying them, see Compute nodes.

You will also want to scp the init.d scripts to the compute nodes and install them there.

4. Populate the /var/spool/torque/server_name file with the hostname of the pbs_server.

[root]# echo <pbs_server's_hostname> > /var/spool/torque/server_name

5. Initialize serverdb by executing the torque.setup script.

[root]# ./torque.setup root

6. Add nodes to the /var/spool/torque/server_priv/nodes file. As an example, a single node withtwo processors could be specified with mgtnode np=2. For information on syntax and options forspecifying compute nodes, see Specifying compute nodes.

7. Configure pbs_server and pbs_mom to start automatically at system boot, and then start theirdaemons.

[root]# cp contrib/init.d/pbs_server contrib/init.d/pbs_mom /etc/init.d[root]# chkconfig --add pbs_server[root]# chkconfig --add pbs_mom[root]# chkconfig pbs_mom on[root]# chkconfig pbs_server on[root]# service pbs_server restart[root]# service pbs_mom start

Related topics

l Installation overview on page 1l Installing Moab Workload Manager on page 5l Component documentation on page 23

4

Installing Moab Workload ManagerThese instructions describe how to install and start Moab Workload Manager (MWM).

Requirements

Hardware requirements:

l Quad-core processor

l At least 12 GB of RAM

l 100 GB disk space

Supported operating systems:

MWM has been tested on the following variants of Linux:

l CentOS (5.7, 6.0, and 6.2)

l Red Hat (5 and 6.1)

l Scientific Linux (6.1)

l SuSE (11 SP1 and 11 SP2)

MWM has historically worked, but has not been tested, on the following operating systems:

l Debian

l AIX

Host operating system software dependencies:

l ExtUtils::MakeMaker Perl module

l XML::LibXML Perl module (perl-XML-LibXML)

l libcurl

l perl-libwww-perl (may be named differently on non-RHEL distributions)

Supported architectures:

l Intel IA-64

l Intel/AMD x86-64

Supported resource managers:

l TORQUE

l SLURM

5

Installing Moab Workload Manager

Dependencies and packages installation

Use the following commands to install the required Moab Workload Manager dependencies andpackages (listed in the Requirements section above).

RHEL

[root]# yum update[root]# yum install make perl-ExtUtils-MakeMaker perl-XML-LibXML libcurl perl-libwww-perl

CentOS

[root]# yum update[root]# yum install make perl-ExtUtils-MakeMaker perl-XML-LibXML libcurl perl-libwww-perl

To install Moab Workload Manager

If you have not met the hardware and host operating system software requirements listed above,you will likely encounter errors when trying to install Moab Workload Manager.

1. Run each of the following commands in order:

[root]# tar xzvf moab-7.1.0-xxxx.tar.gz (where xxxx can be one of: generic, generic-odbc, torque, torque-odbc)[root]# cd moab-7.1.0[root]# ./configure <option>[root]# make perldeps[root]# make install

In some cases, you might want to customize the location of the MWM home directory, the serverdaemon, and the client commands. You can make these configurations by using the ./configureoptions. (For a complete list of ./configure options, use ./configure --help.)

We strongly recommend that you configure Moab with the --with-init and --with-profileoptions.

Here are some examples of commonly used ./configure options:

Option Description Example

--with-homedir

Specifies the location of the Moab configuration directory and theMOABHOMEDIR environment variable.The default location is /opt/moab.

MOABHOMEDIR is automatically set on some distributions duringinstallation, when the --with-profile option is enabled.

[root]#./configure --with-homedir=/var/moab

6

Installing Moab Workload Manager

Option Description Example

--with-init

Enables the installation of a distribution-specific /etc/init.d/moabservice startup script.This option is required if you want to install this script onto a new system. Ifyou do not set this option, you must manually set up the MWM daemonservice.The startup script is located at OS/EL/etc/init.d/moab.

[root]#./configure --with-init

--prefix Specifies the location of the binaries and libraries of the MWM install.The default location is /opt/moab.

[root]#./configure --prefix=/usr/local

--with-profile

Enables the installation of distribution-specific /etc/profile.d/moab.[c]sh setup script for bash and cshell.The MOABHOMEDIR, PERL5LIB, PATH and MANPATH environmentvariables are setup to specify where the new moab configuration, scripts,binaries and man pages reside. If you do not set this option, these scriptsare not installed, and you must manually perform this set up.The environment setup scripts are located atOS/EL/etc/profile.d/moab.[c]sh.

[root]#./configure --with-profile

2. (ONLY if installing on non-RHEL distributions)

Copy the appropriate init.d file, set the permissions on it, and configure MWM to startautomatically at system boot.

* If Debian distribution, do the following *[root]# cp contrib/init.d/moab_debian_init /etc/init.d/moab

* If SLES distribution, do the following *[root]# cp contrib/init.d/moab_sles_init /etc/init.d/moab

[root]# chmod 755 /etc/init.d/moab[root]# chkconfig --add moab

* If chkconfig doesn't work, try the following *[root]# update-rc.d moab defaults

3. Modify the MWM configuration file.

[root]# vim /opt/moab/etc/moab.cfg

Do the following:

a. Verify that SUBMITCMD is set up for your TORQUE resource manager (change RMCFG[hostname]to RMCFG[torque]), and that it points to a valid qsub executable. For example:

RMCFG[torque] SUBMITCMD=/usr/local/bin/qsub

7

Installing Moab Workload Manager

b. ONLY if you are using Moab Viewpoint, add "tomcat" to the list of administrator USERS. Forexample:

ADMINCFG[1] USERS=root,tomcat

Also, make sure that you set ENABLEPROXY to "true":

ADMINCFG[1] ENABLEPROXY=TRUE

4. If you ran the ./configure --with-profile option, source the following file to add the MWM homedirectory to your current shell $PATH environment.

[root]# . /etc/profile.d/moab.sh

5. Copy your license file into the same directory as moab.cfg (/opt/moab/etc/ by default). Forexample:

[root]# cp moab.lic $MOABHOMEDIR/etc/moab.lic

To verify the current status of your license, use moab --about.

MWM checks the status of the license every day just after midnight. At 60 and 45 days before, and dailyfrom 30 days before license expiration to and including the license expiration date, MWM sends an e-mail to all level 1 administrators informing them of the pending MWM license expiration. A log recordis also made of the upcoming expiration event. For the notifications to occur correctly, you must enableadministrator email notification (see "Notifying Administrators of Failures" in the Moab WorkloadManager Administrator Guide) and moab.cfg must contain email addresses for level 1 administrators.For example:

ADMINCFG[1] USERS=u1,u2,u3[,...]

USERCFG[u1] u1@company.comUSERCFG[u2] u2@company.comUSERCFG[u3] u3@company.com

MAILPROGRAM DEFAULT

MWM has an internal license that enables some functionality for a limited time for evaluationpurposes. If you want to enable adaptive energy management, dynamic multi-OS provisioning,grid management, and other features, or if you want to evaluate MWM for a longer period,contact evaluation support. Use mdiag -S -v to see which features your license supports.

6. Start MWM.

[root]# service moab start

7. Submit a sleep job as a non-root user and verify the job is running.

[root]# su - user[user]$ echo sleep 150 | msub[user]$ showq

Related topics

l Installation overview on page 1l Installing TORQUE on page 3

8

Installing Moab Workload Manager

l Component documentation on page 23

9

Installing Moab Web ServicesThese instructions describe how to deploy Moab Web Services (MWS) to a Tomcat server.

Requirements

Hardware requirements:

l Dual core processor

l At least 4 GB of RAM

Software requirements:

l Moab® Workload Manager 7.1.4

l Oracle®/Sun® Java® 6 Runtime Environment

l Apache Tomcat™ 6

l MongoDB® 2.0.1 or later

Dependencies and packages installation

Use the following commands to install the required Moab Web Services dependencies and packages(listed in the Requirements section above).

RHEL

[root]# yum update[root]# yum install tomcat6

CentOS

The correct version of Tomcat is not automatically installed on CentOS 5. The example below ensuresthat the right build of Tomcat 6 is installed.

[root]# rpm -Uvh 'http://plone.lucidsolutions.co.nz/linux/centos/images/jpackage-utils-compat-el5-0.0.1-1.noarch.rpm'[root]# cd /etc/yum.repos.d[root]# wget 'http://www.jpackage.org/jpackage50.repo'[root]# yum update[root]# yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps

To install Moab Web Services

You must deploy Moab Web Services on the same server as Moab Workload Manager.

11

Installing Moab Web Services

1. Make sure that you have first installed and configured Moab Workload Manager as desired (for details,see Installing Moab Workload Manager on page 5).

2. Generate a secret key to be used for communication between MWM and MWS.

Here is a suggested script that you can use to generate the key:

dd if=/dev/urandom count=18 bs=1 2>/dev/null | base64 > /opt/moab/etc/.moab.keychown root /opt/moab/etc/.moab.keychmod 400 /opt/moab/etc/.moab.keyln -f /opt/moab/etc/.moab.key /opt/moab/.moab.key

3. Start MWM.

service moab start

4. Install MongoDB version 2.0.1 or later on the MWM server using packages (recommended) or manualinstallation.

Installationmethod Instructions

Packages(recommended)

Install the packages (available from the Mongo-provided repositories for CentOS and Fedoraor Ubuntu and Debian).After installing the packages, start MongoDB and arrange for it to start automatically duringserver startup.l For CentOS and Fedora, here are some examples:

/sbin/chkconfig mongod on

/etc/init.d/mongod start

l For Ubuntu and Debian examples, see these instructions.

Manual (notrecommended)

Follow these instructions.

Be sure to start the Mongo server (mongod) after installation and arrange for it tostart automatically during server startup (for example, by writing and registering an/etc/init.d script).

5. Install and enable the 64-bit version of Oracle Java SE 6 JRE. For example:

sh jre-6u33-linux-x64-rpm.binrm -f /usr/bin/javaln -s /etc/alternatives/java /usr/bin/java/usr/sbin/alternatives --install /usr/bin/java java /usr/java/latest/bin/java 1/usr/sbin/alternatives --set java /usr/java/latest/bin/java

You can verify the Java installation by running the following command:

java -version

The output should look similar to this:

12

Installing Moab Web Services

java version "1.6.0_33"Java(TM) SE Runtime Environment (build 1.6.0_33-b03)Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)

6. Create the MWS home directory (for more information, see the "Configuration" section of the MoabWeb Services Reference Guide), and the etc, hooks, plugins, and log subdirectories. You will needto give the Tomcat user "read" access to all directories and "write" access to the plugins and logdirectories.

The default location for the MWS home directory is /opt/mws. These instructions assume thedefault location.

Here is an sample script for this setup:

mkdir -p /opt/mws/etc /opt/mws/hooks /opt/mws/plugins /opt/mws/logchown -R tomcat /opt/mws # Depending on your OS, the Tomcat username might betomcat6.chmod -R 555 /opt/mwschmod u+w /opt/mws/plugins /opt/mws/log

7. Extract the contents of the MWS download tarball into a temporary directory. For example:

mkdir /tmp/mws-installcd /tmp/mws-installtar xvzf $HOME/Downloads/mws-7.1.0.tar.gzcd /tmp/mws-install/mws-7.1.0

8. Set up the MWS configuration file by doing the following:

a. Copy mws-config-hpc.groovy to the MWS home etc/ sub-directory, and rename it to mws-config.groovy.

cp mws-config-hpc.groovy /opt/mws/etc/mws-config.groovy

b. Give the Tomcat user "read" access to the /opt/mws/etc/mws-config.groovy file.

c. In the /opt/mws/etc/mws-config.groovy file, make the following changes:

l Modify the moab.secretKey setting to match the MWM secure key you generated earlier(contained in /opt/moab/etc/.moab.key).

l Change the default MWS password (auth.defaultUser.password) to a password of yourchoosing.

l (Optional) Change the default MWS username (auth.defaultUser.username) to any value youlike.

[root]# vi /opt/mws/etc/mws-config.groovy

...moab.secretKey = "<ENTER-KEY-HERE>"moab.server = "localhost"moab.port = 42559

// Change these to be whatever you like.auth.defaultUser.username = "admin"auth.defaultUser.password = "adminpw"

13

Installing Moab Web Services

If you do not change auth.defaultUser.password, your MWS will not be secure(because anyone reading these instructions would be able to log into your MWS). Hereare some tips for choosing a good password.

9. Set the following parameters in your Tomcat CATALINA_OPTS:

CATALINA_OPTS="-Xms256m -Xmx3g -XX:MaxPermSize=384m -DMWS_HOME=/opt/mws"

Where you choose to store CATALINA_OPTS depends on various factors, including operating systemand sysadmin preference. Here are some suggestions:

l CentOS™ 5 and 6: /etc/tomcat6/tomcat6.conf

l Red Hat® Enterprise Linux 5 and 6: /etc/tomcat6/tomcat6.conf

l SUSE® Linux Enterprise Server 11: /etc/tomcat6/tomcat6.conf

l Ubuntu® 10.04: /etc/default/tomcat6

10. Start Tomcat, and deploy mws.war. For example:

chkconfig tomcat6 onservice tomcat6 startcp /tmp/mws-install/mws-7.1.0/mws.war /var/lib/tomcat6/webapps

11. Navigate to http://localhost:8080/mws/ in a web browser to verify that MWS is running (youwill see some sample queries and a few other actions).

12. Log in to MWS to verify that your credentials are working. (Your login credentials are theauth.defaultUser.username and auth.defaultUser.password values you set in the/opt/mws/etc/mws-config.groovy file.)

14

Installing Moab Web Services

If you encounter problems, or if the application does not seem to be running, see the steps in the"Troubleshooting Installation "section of the Moab Web Services Reference Guide.

Related topics

l Installation overview on page 1l Installing Moab Workload Manager on page 5l Installing Moab Viewpoint on page 17l Component documentation on page 23

15

Installing Moab ViewpointThese instructions describe how to install and start Moab Viewpoint.

Requirements

Hardware requirements:

l 16 GB disk space

Software requirements:

l Moab Workload Manager version 7.1.4

l Moab Web Services version 7.1.4

l Apache Tomcat™ 6

l MySQL version 5.1 or later

l JDBC Driver for MySQL (Connector/J) (available from MySQL or another trusted source)

Supported web browsers:

l Mozilla Firefox 3.5 or later

l Internet Explorer 7.0 or later

Dependencies and packages installation

Use the following commands to install the required Moab Viewpoint dependencies and packages (listedin the Requirements section above).

RHEL

[root]# yum update[root]# yum install tomcat6 mysql mysql-server

CentOS

The correct version of Tomcat is not automatically installed on CentOS 5. The example below ensuresthat the right build of Tomcat 6 is installed.

[root]# rpm -Uvh 'http://plone.lucidsolutions.co.nz/linux/centos/images/jpackage-utils-compat-el5-0.0.1-1.noarch.rpm'[root]# cd /etc/yum.repos.d[root]# wget 'http://www.jpackage.org/jpackage50.repo'[root]# yum update[root]# yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps mysql mysql-server

17

Installing Moab Viewpoint

To install Moab Viewpoint

1. Create the Viewpoint database.

MySQL 5.1 is the supported database for Moab HPC Suite. You must create the database and give theuser full access to that database. For information on creating databases and granting access with otherdatabase vendors, consult the documentation for that vendor.

While MySQL is the only supported database for Viewpoint, the use of other databases withMoab HPC Suite is possible. Please contact Adaptive Computing Support for more information.

For information on creating databases and granting access with other database vendors, consultthe documentation for that vendor.

Do the following:

a. Run these commands.

[root]# chkconfig mysqld on[root]# service mysqld start[root]# /usr/bin/mysql_secure_installation

b. When you are prompted for the current root password, press Enter. When you are asked to set theroot password, use p@ssw0rd and select y for all options.

c. Create the Viewpoint database and grant the following permissions (remember to run commands incontext):

[root]# mysql -u root -pEnter password:mysql> CREATE DATABASE viewpoint;Query OK, 1 row affected (0.08 sec)mysql> GRANT ALL ON viewpoint.* TO viewpoint@localhost IDENTIFIED BY 'p@ssw0rd';Query OK, 0 rows affected (0.31 sec)mysql> GRANT ALL ON viewpoint.* TO viewpoint@127.0.0.1 IDENTIFIED BY 'p@ssw0rd';Query OK, 0 rows affected (0.31 sec)FLUSH PRIVILEGES;Query OK, 0 rows affected (0.31 sec)

2. Untar the Viewpoint tarball, and create the initial tables required for an HPC Viewpoint.

[root]# tar xzvf viewpoint-7.1.4.tar.gz[root]# mysql -u root -p viewpoint < viewpoint-7.1.4/sql/mysql/setup_hpc.sql

3. Verify that the script ran correctly by running a third party client such as SQuirrel SQL or by usingyour database vendor's own client tool (for instance, run mysql -u <username> -p <password>).

As a best practice, create a schema if you are running PostgresSQL. It is recommended that youcall the schema viewpoint. If you choose not to create one, set public as the schema namewhen you configure the setup.properties file.

4. Install the JDBC Driver for MySQL (available from MySQL or another trusted source).

[root]# tar xvzf mysql-connector-java-x.x.x.tar.gz[root]# cd mysql-connector-java.x.x.x[root]# cp mysql-connector-java.x.x.x-bin.jar /usr/share/tomcat6/lib

5. Create the Viewpoint home directory.

18

Installing Moab Viewpoint

[root]# mkdir /opt/viewpoint

6. Navigate to the Viewpoint extraction directory, and deploy the war files (reporting.war is optional).

[root]# cd viewpoint-7.1.0/[root]# cp dist/*.war /var/lib/tomcat6/webapps/

It is recommended that you do not run more than one instance of Viewpoint within Tomcat.

7. Copy the setup.properties.[db_type] file to the Viewpoint home directory and change the nameto setup.properties (removing the .[db_type] extension).

[root]# cp templates/setup.properties.mysql /opt/viewpoint/setup.properties

8. Open setup.properties for modification.

[root]# vi /opt/viewpoint/setup.properties

Change the username and password to what you set when you configured the database.

dbUser=<viewpoint>dbPassword=<p@ssw0rd>

9. Set the Tomcat user as the owner of the Viewpoint home directory. Restart Tomcat.

[root]# chown -R tomcat:tomcat /opt/viewpoint[root]# service tomcat6 restart

If you are running Fedora, you must start Tomcat by navigating to $CATALINA_home/bin/ andrun startup.sh as root:

[root]# $CATALINA_HOME/bin/startup.sh

10. Verify that Viewpoint was correctly installed by directing your browser to the Viewpoint URL (forexample: http://[hostname or ip address]:8080/moab), and logging in with the defaultusername and password (admin/admin).

11. Update the Viewpoint connection to MWS.

a. From the Administration > Configuration menu, click MWS connection.

b. Update the Username and Password fields to match the username and password you configured inthe /opt/mws/etc/mws-config.groovy file and click Update.

c. Restart Tomcat.

[root]# service tomcat6 restart

Related topics

l Installation overview on page 1l Installing Moab Workload Manager on page 5l Installing Moab Web Services on page 11l Component documentation on page 23

19

Installing Moab Cluster ManagerThese instructions describe how to install and start Moab Cluster Manager (MCM).

Requirements

l Moab Workload Manager 7.1.4

Prerequisites

You will need to install Oracle®/Sun® Java® SE 6 or higher, which includes a Java RuntimeEnvironment (JRE) version 1.6 or higher.

You must obtain a JRE from Oracle. MCM will not run correctly on JREs from other vendors, suchas GCJ or OpenJDK. The Linux and Windows builds of MCM come bundled with the correct JRE.However, if you install the generic Unix version of MCM, you will need to download a JREseparately.

You can check which version of Java you have installed by running the following command:

$ java -version

The output should look similar to this:

java version "1.6.0_33"Java(TM) SE Runtime Environment (build 1.6.0_33-b03)Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)

To install Moab Cluster Manager on a Linux/Unix system

1. Download the latest 7.1.4 build of the tar file from the Adaptive Computing website:

l The mcm-7.1.x-[build number].linux.tar.gz builds come with a bundled JRE.

l The mcm-7.1.x-[build number].tar.gz builds do not include a JRE.

2. Move the tar file to your home directory, or another directory you have access to (for example,/home/username/), and unpack the tar file (tar -xzvf xxxx.tar.gz).

3. Change directories to the newly unpacked MCM directory.

4. Start MCM by running the following script:

$ mv mcm-7.1.x-xxxx.tar.gz /home/bob$ cd /home/bob$ tar zxvf mcm-7.1.x-xxxx.tar.gz$ cd mcm-7.1.x-xxxx/$ ./mcm &

5. The MCM script checks for the existence of a compatible JRE and then runs MCM.

21

Installing Moab Cluster Manager

After you accept the license, you will see the Connection Wizard. For information about configuringMCM to connect to Moab Workload Manager, see the "Connection Wizard" section in the Moab ClusterManager User Guide.

To install Moab Cluster Manager on a Windows system

1. Download the latest 7.1.4 build executable from the Adaptive Computing website.

2. Double-click the installation file.

3. Follow the MCM installer instructions to install MCM.

Once it has completed, the installer creates Start Menu and Desktop icons that you can use to startMCM.

The default destination folder for MCM is either C:\Program Files\Moab ClusterManager or C:\Program Files\(x86)\Moab Cluster Manager (depending on whatversion of Windows you are running).

4. Double-click the Moab Cluster Manager icon on the Desktop to run MCM.

After you accept the license, you will see the Connection Wizard. For information about configuringMCM to connect to Moab Workload Manager, see the "Connection Wizard" section in the Moab ClusterManager User Guide.

MCM will not have permissions to create log files if you are installing on a Windows 7 system. (Thisis because MCM does not have permission to write to sub-folders of C:\Program Files orC:\Program Files (x86) unless it is run as an administrator.)

If you are running Windows 7 and need to see log files, you can change the log file path to a locationwhere the user running MCM has write permissions. You can make this configuration in theC:\Program Files (x86)\Moab Cluster Manager\conf\long4j.properties file bysetting the log4j.appender.ROLL.File property.

For example, if you want logs to be written to C:\Users\Bob\AppData\Local (where Bob is theuser running MCM), modify the log4j.appender.ROLL.File property as follows:

log4j.appender.Roll.File=${user.home}/AppData/Local/mcm.log

Related topics

l Installation overview on page 1l Installing Moab Workload Manager on page 5l Component documentation on page 23

22

Component documentationThe individual components of the suite have more options and allow for more configuration than can becontained in this guide. Refer to the individual component guides for more information.

TORQUE

l TORQUE 4.1.4 Administrator Guide: HTML – PDF

Moab Workload Manager

l Moab Workload Manager 7.1.4 Administrator Guide: HTML – PDF

Moab Web Services

l Moab Web Services 7.1.4 Reference Guide: HTML – PDF

Moab Viewpoint

l Moab Viewpoint for Moab HPC Suite 7.1.4 Setup Guide: HTML – PDF

l Moab Viewpoint for Moab HPC Suite 7.1.4 User Guide: HTML – PDF

Moab Cluster Manager

l Moab Cluster Manager 7.1.4 User Guide: HTML – PDF

Related topics

l Installation overview on page 1l Welcome on page v

23