(Click to open topic with navigation)

Installing Moab Workload Manager

Installing Moab Workload Manager

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

ClosedRequirements

Hardware requirements:

  • Quad-core Intel/AMD x86-64 processor
  • At least 12 GB of RAM
  • 100 GB disk space

Supported operating systems:

MWM has been tested on the following variants of Linux:

  • CentOS (5.7 and 6.3)
  • Red Hat (5.7 and 6.3)
  • Scientific Linux (6.3)

  • SUSE Linux Enterprise Server 11 SP2

MWM has historically worked, but has not been tested, on the following operating systems:

  • Debian
  • AIX

Host operating system software dependencies:

  • libcurl
  • unixODBC and unixODBC-devel (if you are using an ODBC database)
  • perl-CPAN (This package may be named differently on non-RHEL systems.)
  • Perl version 5.8.8 +
  • libxml2-devel (This package may be named differently on non-RHEL systems.)

Supported resource managers:

  • TORQUE
  • SLURM
ClosedDependencies and packages installation

Use the following commands to install the required Moab Workload Manager dependencies and packages (listed in the Requirements section above).

RHEL 5 and CentOS 5:

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

RHEL 6 and CentOS 6, and Scientific Linux 6:

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

SLES: 

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

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.

    2. The variable marked <version> is the desired version of the suite; for example, 7.2.9. 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.
    3. [root]# tar xzvf moab-7.2.0-xxxx.tar.gz (where xxxx can be one of: generic, generic-odbc, torque, torque-odbc)
[root]# cd moab-7.2.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 the table of commonly used ./configure options in the Installing Moab section of the Moab Workload Manager Administrator Guide.).

    4. 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.
    5. [root]# make perldeps
  5. Install Moab.
    6. [root]# make install
  6. Closed(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/SUSE/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.
    8. [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:
      2. 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:
      3. 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 home directory to your current shell $PATH environment.
    9. [root]# . /etc/profile.d/moab.sh
  9. Copy your license file into the same directory as moab-server.cfg (/opt/moab/etc/ by default). For example:
    10. [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

    MWM 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 MWM for a longer period, contact evaluation support. Use mdiag -S -v to see which features your license supports.

  10. Start MWM.
    11. [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.

If you do not have a resource manager configured, skip this step. For TORQUE, you can configure a basic queue.

qmgr -c "set server scheduling=true"

qmgr -c "create queue batch queue_type=execution"

qmgr -c "set queue batch started=true"

qmgr -c "set queue batch enabled=true"

qmgr -c "set queue batch resources_default.nodes=1"

qmgr -c "set queue batch resources_default.walltime=3600"

qmgr -c "set server default_queue=batch"

    [root]# su - user
[user]$ echo sleep 150 | msub
[user]$ showq
  1. ClosedConnecting Moab to MongoDB

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

    1. In /opt/moab/etc/moab.cfg, set the MONGOSERVER parameter to the correct location of the MongoDB server. This may be set to localhost. By default, Moab assumes it is on the same server.
      2. 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 Install MongoDB).
      3. MONGOUSER     moab_user
MONGOPASSWORD secret2
    3. Verify that Moab is able to connect to MongoDB.
      4. [root]# service moab restart
[root]# mdiag -S
...
Mongo connection (localhost) is up (credentials are set)
...

Related topics 

© 2014 Adaptive Computing