2.2 Building and Installing Moab

After reading this section you will be able to:

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

Note 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 home directory is configured as /opt/moab, the Moab server daemon is installed to /opt/moab/sbin/, and the client commands are installed to /opt/moab/bin/. $MOABHOMEDIR is the location of the etc/, log/, spool/, and stat/ directories. The default location for moab.cfg, moab-private.cfg, and moab.lic is /opt/moab/ and is the recommended location for the license and configuration files.


When planning for a Moab implementation a few things need to be taken into consideration related to the moab.cfg and the moab.dat files. The moab.dat file should be in the same directory as the moab.cfg file. This can either be in /opt/moab or /opt/moab/etc. First, Moab looks for moab.dat in the directory that contains moab.cfg. Second, Moab creates the moab.dat file (when doing changeparam -p) in the same directory as the moab.cfg file. If one file is moved then the other needs to be moved to the same location.

Although both locations work, Adaptive Computing recommends /opt/moab. The main reason for this is supportability. This directory is the default and Adaptive Computing references this location first when dealing with support issues.

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

Note 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-6.1.0.tar.gz
  2. Navigate to the unpacked directory.
    > cd moab-6.1.0
  3. Configure the installation package.
  4. 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.

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

    > /configure --prefix=/usr/local --with-homedir=/var/moab --with-torque=/var/spool/torque/

    In the above example:

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

    Note If you choose the default path (/opt/moab/), the administrator must update $PATH manually to include the new default folders.
    Note You can automatically install the Moab init script, allowing Moab to start automatically when the machine is booted, by using --with-init.
  5. Install Moab.
    NoteMoab 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.

  6. Copy the license file.
  7. > cp moab.lic $MOABHOMEDIR/etc/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 checks the status of the license every day just after midnight. At 60 and 45 days before, and daily from 30 days before license expiration to and including the license expiration date, Moab sends an e-mail to all level 1 administrators informing them of the pending Moab license expiration. A log record is also made of the upcoming expiration event. For the notifications to occur correctly, administrator e-mail notification must be enabled and moab.cfg must contain e-mail addresses for level 1 administrators:

    ADMINCFG[1] USERS=u1,u2,u3[,...]
    USERCFG[u1] [email protected]
    USERCFG[u2] [email protected]
    USERCFG[u3] [email protected]
    Note 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.
  8. Start Moab.
  9. > moab
    Note > moabd is an alternate method of starting Moab that sets the MOABHOMEDIR and LD_LIBRARY_PATH environment variables before calling the Moab binary. It is safe and recommended if things are not installed in their default locations, but can be used in all cases.

2.2.2 Moab Client Installation

After installing the Moab server on the head node, Moab can create a "client commands-only" tarball you can use to install just the Moab client commands on a login/client node. The tarball allows you to install the binary Moab client command files, with their man pages, using a single tar command. In addition, the tarball contains a moab.cfg file configured with the Moab host name and port number so you do not have to manually configure this information on the login/client node. Command Installation when Server and Client Have Similar Architecture

After installing Moab on the head node, enter the following command:

> make client-pkg

A tarball is created with the name "client.tgz". Copy the tarball to the root directory of the client node, log in to the client node as root, and install the client commands using the following command:

> tar xvf client.tgz

The Moab client commands are now available on the login/client node. Command Installation when Server and Client Have Diverse Architecture

Moab clients need to be built for each client system that has different architecture 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. For more information, see Configuring Peer-Specific Secret Keys.

Download the Moab build to the client node and then execute the following command to create the Moab client commands tarball for the architecture and operating system:

> ./configure --prefix=<install directory> --with-serverhost=<head node> --with-serverport=<port number>
Note If there is no moab.cfg file installed on the system when making the client commands tarball, the make command creates one using the ./configure arguments or other auto-generated defaults. If there is one already installed, it is packaged into the client commands tarball.

See Also

Copyright © 2012 Adaptive Computing Enterprises, Inc.®