Moab Workload Manager®

2.2 Building and Installing Moab

• 2.2.1 Moab Server Installation
• 2.2.2 Moab Client Installation

After reading this section you will be able to:

• install the Moab server.
• install end-user commands on remote systems.

This section assumes a working knowledge of Linux or Unix based operating systems, including use of commands such as:

• tar
• make
• vi

Some operating systems use different commands (such as gmake and gtar instead of make and tar).

2.2.1 Moab Server Installation

Before installing Moab, view the Prerequisites to verify your platform is supported.

By default, the Moab server daemon is installed to /usr/local/sbin/, the client commands are installed to /usr/local/bin/, and the Moab home directory is configured as /opt/moab/. $MOABHOMEDIR is the location of the moab.cfg file and the /log/, /spool/, and /stat/ directories.

$MOABHOMEDIR is required whenever the Moab binary is started or when client commands are used. Cluster Resources recommends putting $MOABHOMEDIR in a global location, such as /etc/profile, /etc/bashrc, or /etc/environment.

Moab contains a number of architectural parameter settings that you can adjust for non-standard installations. See Appendix D - Adjusting Default Limits and make any needed changes prior to using make install.

To install Moab

1. Untar the distribution file.

   > tar -xzvf moab-5.3.0.tar.gz

2. Navigate to the unpacked directory.

   > cd moab-5.3.0

3. Configure the installation package.

You can customize the location of the Moab home directory, the server daemon, the client commands, and configure Moab to use a resource manager when using the ./configure command. For a complete list of options, use ./configure --help.

> ./configure

Configuring Moab (v 5.3.0)...
checking system configuration...

checking Makefile...  building new Makefile

OPSYS:         LINUX
COMPILER:      gcc
SECRET KEY:    11102
HOME DIR:      /opt/moab
INSTALL DIR:   /usr/local
PRIMARY ADMIN: root
SERVERHOST:    test.icluster.org

Do you want to use TORQUE/PBS? [Y|N] (Default: Y)           
PBS Target Directory: (default: /usr/local)

make -C src/moab clean
...

configure successful.

An example of some commonly used options for ./configure is provided below.

> ./configure --prefix=/opt/moab --with-homedir=/var/moab --with-torque=/var/spool/torque/

In the above example:

• The install (--prefix option) directory is configured as /opt/moab and the home (--with-homedir option) directory is configured as /var/moab/.
• The Moab server daemon installs to /opt/moab/sbin/.
• The Moab client commands install to /opt/moab/bin/.
• Moab is configured to work with the TORQUE resource manager.

All Moab executables are placed in $MOABHOMEDIR/bin (such as /moab-5.3.0/bin/) until the installation is performed.

4. Install Moab.

   Moab should be installed by root. If you cannot install Moab as root, please contact Customer Support.

   > sudo make install

   A default moab.cfg file will be created in the Moab home directory.
5. Copy the license file.

> cp moab.lic $MOABHOMEDIR/moab.lic

The license file should be placed in the same directory as moab.cfg (which is /opt/moab/ by default) before starting Moab. To verify the current status of your license, use moab --about.

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

6. Start Moab.

> moab

2.2.2 Moab Client Installation

Moab has several client commands that are used at remote locations to check various statistics. You can choose to copy all, or only a subset, of the client commands to a remote location. Below is a suggested list of client commands to install on end-user accessible nodes.

For more information on all client commands, see the Commands Overview.

2.2.2.1 Command Installation when Server and Client Have Similar Architecture

Moab commands are enabled on remote systems by copying desired command executables to the client machine (or to a shared network file system). To enable client communication with the Moab server, use a nearly-blank moab.cfg file on the client system that has only one line that defines the SCHEDCFG parameter with a SERVER attribute.

SCHEDCFG[Moab] SERVER=moabserver:42666

Place the file in /etc on the remote submission hosts.

The client commands and the Moab daemon must have the same version and revision number.

2.2.2.2 Command Installation when Server and Client Have Diverse Architecture

Moab clients need to be built for each client system that has different architechture from the server. If you are using secret key security (enabled by default), a common secret key must be specified for the client and server. Verify moab-private.cfg is configured properly.

See Also

• End User Commands