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:
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 etc/ folder in $MOABHOMEDIR is the default location for the moab.cfg and moab-private.cfg files.
$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.
To install Moab
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-5.3.0/bin/) until the installation is performed.
A default moab.cfg file will be created in the Moab home directory.
> sudo make install
> 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 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.
18.104.22.168 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.
Place the file in /etc on the remote submission hosts.
22.214.171.124 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.
Searches Moab documentation only
|© 2001-2010 Adaptive Computing Enterprises, Inc.|