Moab Workload Manager®

2.1 Building and Installing Moab

• 2.1.1 Moab Source Installation
• 2.1.2 Moab Binary Installation
• 2.1.3 Moab Client Installation
• 2.1.4 Supported Platforms

This section describes how to do the following:

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

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

• tar
• make
• vi

If you require a more basic installation overview, see the Moab Installation Guide for Beginners.

2.1.1 Moab Server Installation

• Building Moab

To install Moab, untar the distribution file, enter the moab-<VERSION> directory, then run configure and make as shown in the following example:

Note: To configure the Moab configuration file to facilitate communication between Moab and the resource manager, when running configure use the --with-<resource manager you are using> configuration option. For a complete list of all resource managers and other configuration options, use the --help configuration option.

> tar -xzvf moab-4.5.0.tar.gz
> cd moab-4.5.0
> ./configure
> make

Note: The install directory and home/var directory can be specified using configure's --instdir and --homedir options respectively.

• Installing Moab (Optional)

When you are ready to use Moab in production, you may install it into the install directory you have configured using make install.

> make install

Note: Until the install step is performed, all Moab executables will be placed in $MOABHOMEDIR/bin. (For example: moab-5.0.0/bin.)

Note: Moab is designed to satisfy the needs of the vast majority of organizations. However, it contains a number of architectural parameter settings that may need adjustment for non-standard installations. If the target cluster may fit in this category, see Appendix D, Adjusting Default Limits and make any needed changes prior to issuing the make command.

Note: Some systems will necessitate the use of different commands (such as gmake and gtar instead of make and tar).

Note: If installing a licensed binary, copy the license file provided by your vendor to $MOABHOMEDIR/moab.lic before starting Moab.

2.1.2 Moab Binary Installation

The Moab binary installation is split into two sections. The Moab binary and the client commands are configured to install to /usr/local/sbin and /usr/local/bin respectively. The MOABHOMEDIR is configured to /opt/moab. MOABHOMEDIR is the location of the moab.cfg file and the log, spool, and stat directories. You can change these locations before installation by modifying the Makefile that ships with Moab and by changing the two parameters at the top—MSCHED_HOME and INST_DIR—to site specific locations.

The Moab binaries are compiled to look for the moab.cfg file in 2 locations, the first being MOABHOMEDIR (/opt/moab/moab.cfg), the second being /etc/moab.cfg. To override this, the environment variable MOABHOMEDIR can be set up to point to the directory containing the moab.cfg file. Because this environment variable will need to be present whenever the Moab binary is started and whenever the client commands are used, it is best to put it into a global location (such as /etc/profile, /etc/bashrc, /etc/environment, or whatever the default is for a particular site).

Example Setup (as root):

> tar zxf moab-5.0.0-bin.tar.gz
> cd moab-5.0.0-bin/
> ./configure
> make
> make install
> cp moab.lic /opt/moab/moab.lic

When a license file is needed, the file moab.lic should be placed in the same directory as moab.cfg (which is /opt/moab by default). To verify the current status of your license, you can issue the command showq --about.

2.1.3 Moab Client Installation

If you need to supply Moab commands on remote systems, you can make them available in one of two ways based on the architecture of the remote client systems. In either case, sites may choose to copy out all commands or only the subset of commands preferred for users. Initially, some sites choose to only install the following client commands on end-user accessible nodes:

The full list of client commands is provided in the Commands Overview.

2.1.3.1 Common Architecture Client and Server

If the client and server architectures are identical, Moab commands can be enabled on the client systems by copying the desired command executables to the client machine (or into a shared network file system). In addition, a moab.cfg file, which points to the moab server, must also be made available. To enable client communication, the remote moab.cfg file need only contain the SCHEDCFG parameter with the SERVER attribute.

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

2.1.3.2 Diverse Architecture Client and Server

If the client and server possess different architectures, Moab clients will need to be built for each architecture. If using secret key security (the default), it is important that a common secret key be specified for both the client and the server or that the moab-private.cfg file be properly configured. Once the architecture specific binary is created, the steps just described in the Common Architecture Client and Server section can be followed.

2.1.4 Supported Platforms

Moab supports a broad array of platforms including most commonly used resource managers, operating systems, and architectures. The following sections list some of the platforms supported.

2.1.4.1 Supported Resource Managers

2.1.4.2 Supported Operating Systems

2.1.4.3 Supported Architectures

See Also

• Moab Installation Guide for Beginners
• End User Commands