(Click to open topic with navigation)
This topic contains instructions on how to install and start Moab Workload Manager (Moab).
In this topic:
Moab Workload Manager uses a configurable server port (default 42559) for client-server communication. If you intend to run client commands on a host other than the Moab Head Node, or if you will be using Moab in a grid, and if you have a firewall enabled, then you will need to configure the firewall to allow the server port.
[root]# iptables-save > /tmp/iptables.mod [root]# vi /tmp/iptables.mod # Add the following lines immediately *before* the line matching # "-A INPUT -j REJECT --reject-with icmp-host-prohibited" # Needed on the Moab server for off-host client communication -A INPUT -p tcp --dport 42559 -j ACCEPT [root]# iptables-restore < /tmp/iptables.mod [root]# service iptables save
[root]# vi /etc/sysconfig/SuSEfirewall2 # Add the following ports to the FW_SERVICES_EXT_TCP parameter as required # Needed on the Moab server for off-host client communication FW_SERVICES_EXT_TCP="42559" [root]# service SuSEfirewall2_setup restart
Dependencies and Installing Packages
Use the following commands to install the required Moab Workload Manager dependencies and packages.
[root]# yum update [root]# yum install make libcurl perl-CPAN libxml2-devel
[root]# zypper update [root]# zypper install make curl libxml2-devel
If Installing TORQUE on a Separate Server
If you are using TORQUE and are installing the TORQUE server on a separate TORQUE Head Node, you will need to install TORQUE on the Moab Head Node as well in order for Moab to interact with TORQUE. Follow the instructions in Installing TORQUE with these exceptions:
(Optional) Building a Custom RPM
[root]# yum install rpm-build
The variable marked <version> is the desired version of the suite; for example, 8.0-2014061017-8f96ac8d would be Moab 8.0 revision 2014061017 at changeset 8f96ac8d. The variable marked <OS> indicates the OS for which the build was designed.
Installing Moab Workload Manager
The variable marked <version> is the desired version of the suite; for example, 8.1.0-2015010514-ed0c40a would be Moab 8.1.0 revision 2015010514 at changeset ed0c40a. The variable marked <OS> indicates the OS for which the build was designed.
[root]# tar xzvf moab-<version>-<OS>.tar.gz [root]# cd moab-<version>-<OS>
Configure Moab. 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 and --with-profile options. The --with-profile option makes it easier to execute Moab commands (see step 8). The --with-init option allows Moab to automatically start at OS startup (see step 11).
[root]# ./configure <options>
[root]# make perldeps
[root]# make install
ONLY if you are installing on SLES.
Copy the appropriate init.d file, set the permissions on it, and configure Moab to start automatically at system boot.
# SLES: [root]# cp OS/SLES/etc/init.d/moab /etc/init.d/moab [root]# chmod 755 /etc/init.d/moab [root]# chkconfig --add moab
[root]# vi /opt/moab/etc/moab.cfg
Do the following:
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.
ADMINCFG[1] USERS=root,tomcat
[root]# . /etc/profile.d/moab.sh
[root]# cp moab.lic $MOABHOMEDIR/etc/moab.lic
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, 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.
[root]# chkconfig moab on [root]# service moab start
[root]# su - adaptive [adaptive]$ echo sleep 150 | msub [adaptive]$ showq
[adaptive]$ exit
Related Topics