Installing Moab Workload Manager

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

[root]# yum update
[root]# yum install make curl libxml2-devel

[root]# yum update
[root]# yum install make libcurl perl-CPAN libxml2-devel

[root]# zypper update
[root]# zypper install make curl libxml2-devel

To build a custom RPM

1. Install rpm-build.

[root]# yum install rpm-build

2. Download the latest MWM build (moab-<version>-<OS>-linux-x86_64-<type>.tar.gz) from the Adaptive Computing website.
   

   The variable marked <version> is the desired version of the suite; for example, 7.5.0. The variable marked <OS> indicates whether you are using a RHEL/CentOS 5 operating system (EL5), a RHEL/CentOS 6 operating system (EL6), or a SUSE 11 operating system (SUSE11). The variable marked <type> is one of libtorque (TORQUE), generic (generic), libtorque-libodbc (TORQUE ODBC), or generic-libodbc (generic ODBC).

3. Untar the downloaded package.
4. Change directories into the untarred directory.
5. Edit the ./moab.spec file for RPM customization.
6. Run ./rpm-build.
7. Locate the custom RPM in rpm/RPMS/x86_64.

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. Download the latest MWM build (moab-<version>-<OS>-linux-x86_64-<type>.tar.gz) from the Adaptive Computing website.


The variable marked <version> is the desired version of the suite; for example, 7.5.0. The variable marked <OS> indicates whether you are using a RHEL/CentOS 5 operating system (EL5), a RHEL/CentOS 6 operating system (EL6), or a SUSE 11 operating system (SUSE11). The variable marked <type> is one of libtorque (TORQUE), generic (generic), libtorque-libodbc (TORQUE ODBC), or generic-libodbc (generic ODBC).

2. As the root user, run each of the following commands in order.

[root]# tar xzvf moab-7.5.0-xxxx.tar.gz (where xxxx can be one of: generic, generic-odbc, torque, torque-odbc)
[root]# cd moab-7.5.0

3. Configure Moab. The ./configure command allows you to specify some options. In some cases, you might want to customize the location of the MWM home directory, the server daemon, and the client commands. You can make these configurations by using the ./configure options (For a complete list of ./configure options, use ./configure --help or refer to Moab Workload Manager configuration options for a list of commonly used options.

   It is strongly recommended that you configure Moab with the --with-init, --with-profile, and --with-flexlm options. If you are using TORQUE as your resource manager, use the --with-torque option. If you are installing Moab Accounting Manager, configure Moab with the --with-am option.

   [root]# ./configure <options>

4. (Only if you are using green computing, or if you are using a resource manager other than TORQUE) Run the make perldeps command to install the necessary perl modules using CPAN. When first running CPAN, you will be asked for configuration information. It is recommended that you choose an automatic configuration. You will be prompted to provide input during module installation; running the make perldeps command with a script is not recommended.

[root]# make perldeps

5. Install Moab.

[root]# make install

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

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

   * If SLES distribution, do the following *
   [root]# cp OS/SLES/etc/init.d/moab /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

7. Modify the MWM configuration file.

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

Do the following:

1. 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

If you use a SLURM resource manager, see Moab-SLURM Integration Guide for configuration information. If you use a NATIVE resource manager, see Managing Resources Directly with the Native Interface for configuration information.

2. ONLY if you are using Moab Web Services or Moab Viewpoint, add tomcat to the list of administrator USERS. For example:

ADMINCFG[1] USERS=root,tomcat

Also, make sure that you set ENABLEPROXY to TRUE:

ADMINCFG[1] ENABLEPROXY=TRUE

Without this configuration, all jobs submitted in Viewpoint will be submitted as "root," regardless of the user who actually submitted the job.

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

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

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

[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 daily from 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 record is also made of the upcoming expiration event. For the notifications to occur correctly, you must enable administrator email notification (see "Notifying Administrators of Failures" in the Moab Workload Manager Administrator Guide) and moab.cfg must contain email addresses for level 1 administrators. For example:

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

USERCFG[u1] [email protected]
USERCFG[u2] [email protected]
USERCFG[u3] [email protected]

MAILPROGRAM DEFAULT



Moab will not run without a license. For information about obtaining a trial license, please contact Adaptive Computing.

10. Start MWM.

[root]# service moab start



If Moab fails to start because libodbc.so.1 cannot be found, you must create a symbolic link from libodbc.so.1 to libodbc.2.

[root]# ln -s /usr/lib64/libodbc.so.2 /usr/lib64/libodbc.so.1

For more information, see the Unix ODBC documentation.

11. 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

[user]$ exit

12. Connecting Moab to MongoDB

    If you will be installing Moab Web Services or Moab Viewpoint, connect MWM to MongoDB using the following instructions:

    

    The USEDATABASE parameter is unrelated to the MongoDB configuration.

    1. In /opt/moab/etc/moab.cfg, set the MONGOSERVER parameter to the correct location of the MongoDB server. By default, Moab assumes it is on the same server.

       MONGOSERVER <host>[:<port>]

    2. In the /opt/moab/etc/moab-private.cfg file, set the MONGOUSER and MONGOPASSWORD parameters to the MongoDB moab_user credentials you set (for details, see Installing MongoDB).

    MONGOUSER     moab_user
    MONGOPASSWORD secret2

    3. Verify that Moab is able to connect to MongoDB.

    [root]# service moab restart
    [root]# mdiag -S
    ...
    Mongo connection (localhost) is up (credentials are set)
    ...

13. Setting up message queue security

    Moab supports message queue security using AES. To enable message encryption, you must specify a MESSAGEQUEUESECRETKEY by following these instructions:

    1. Generate a secret key using this script:

    dd if=/dev/urandom count=16 bs=1 2>/dev/null | base64

    2. Set the MESSAGEQUEUESECRETKEY parameter in /opt/moab/etc/moab-private.cfg with the secret key that you generated above. Note that only 128-bit (16-byte) keys are supported, and keys must be encoded in Base64. For example:

    MESSAGEQUEUESECRETKEY 1r6RvfqJa6voezy5wAx0hw==

    

    The key you specify in the moab-private.cfg file is the same key you must also specify in the moab.messageQueue.secretKey property when installing and configuring MWS (see Installing Moab Web Services).

    

    Important: If MWS is configured to encrypt the message queue and Moab is not (or vice versa) then the messages from Moab will be ignored. Furthermore, all attempts to access the MWS service resource will fail.

    3. Save and close moab-private.cfg.
    4. Continue the message queue security setup, as outlined in Installing Moab Web Services.

Related topics 

• Installation overview
• Installing TORQUE
• Component documentation