6.33 Installing Moab Workload Manager

This topic contains instructions on how to install, configure, and start Moab Workload Manager (Moab).

For Cray systems, Adaptive Computing recommends that you install Moab and Torque Servers (head nodes) on commodity hardware (not on Cray compute/service/login nodes).

However, you must install the Torque pbs_mom daemon and Torque client commands on Cray login and "mom" service nodes since the pbs_mom must run on a Cray service node within the Cray system so it has access to the Cray ALPS subsystem.

See Installation Notes for Moab and Torque for Cray in the Moab Workload Manager Administrator Guide for instructions on installing Moab and Torque on a non-Cray server.

In this topic:

6.33.1 Open Necessary Ports
6.33.2 Install Moab Server
6.33.3 Configure Torque to Trust Moab
6.33.4 Verify the Installation

6.33.1 Open Necessary Ports

Moab uses a configurable server port (default 42559) for client-server communication. If you intend to run client commands on a host different from the Moab Server Host, 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.

On the Moab Server Host, do the following:

[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]# firewall-cmd --add-port=42559/tcp --permanent
[root]# firewall-cmd --reload

[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 restart

6.33.2 Install Moab Server

If your configuration uses firewalls, you must open the necessary ports before installing the Moab Server. See 6.33.1 Open Necessary Ports.

On the Moab Server Host do the following:

If you configuration uses firewalls, confirm you have opened the necessary ports. See 6.33.1 Open Necessary Ports.
If you have not already done so, complete the steps to prepare the Moab Server Host. See 6.31 Preparing the Host – Typical Method or 6.30 Preparing the Host – Offline Method.
Install RPM packages.
1. Install the Moab Server RPMs.
```
[root]# yum install moab-workload-manager moab-workload-manager-hpc-configuration
```
  If installing on RHEL, some package dependencies required by Moab are not be provided in the default-enabled RHEL distribution repositories. However, they can be found by enabling the RHEL server optional RPMs and EPEL repositories. You can choose whether to temporarily or permanently enable the additional repositories.
  
  For example, on RHEL 7 systems:
  - Temporarily: When installing the Moab Workload Manager RPM, use this command instead:
    [root]# yum install --enablerepo=epel,rhel-7-server-optional-rpms moab-workload-manager moab-workload-manager-hpc-configuration
  - Permanently:
    - Before installing the Moab Workload Manager RPM run this command:
      [root]# subscription-manager repos --enable rhel-7-server-optional-rpms
    - Then install the Moab Workload Manager RPM as normal.
      [root]# yum install moab-workload-manager moab-workload-manager-hpc-configuration
```
[root]# zypper install moab-workload-manager moab-workload-manager-hpc-configuration
```
2. If you are using Torque as a resource manager and installed the Torque Server on a different host (Torque Server Host; recommended) from the Moab Server (Moab Server Host), you will need to install the Torque client RPM on the Moab Server Host in order for Moab to interact with Torque.
```
[root]# yum install moab-torque-client
```
```
[root]# zypper install moab-torque-client
```
3. If you are using Moab Accounting Manager and will be using the Native (custom script) accounting manager interface, and are installing the Moab Accounting Manager Server on a different host from the Moab Server (Moab Server Host) you will need to the install Moab Accounting Manager client on the Moab Server Host in order for the custom scripts to use the MAM API.
```
[root]# yum install moab-accounting-manager
```
```
[root]# zypper install moab-accounting-manager
```
Source the following file to add the Moab executable directories to your current shell $PATH environment.

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

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

[root]# cp moab.lic $MOABHOMEDIR/etc/moab.lic

To verify the current status of your license, run the following command:

[root] # moab --about 2>&1 | grep License

You should get something similar to the following in the response:

Moab Workload Manager Version '9.0.2' License Information:
 Current License:  Max Procs   = 10000
 Current License:  Valid Until - Thu Jul 13 19:42:10 2017

A license is required for Moab. A trial license may be included in your Moab installation enabling you to run Moab for a limited time and with limited features. Email [email protected] for information on obtaining licenses.

If you are using Torque as your resource manager and you installed the Torque Server on a different host (Torque Server Host) from the Moab Server (Moab Server Host), do the following:
1. Create or edit the /var/spool/torque/server_name file to contain the hostname of the Torque Server.
```
[root]# echo <Torque_server_hostname> > /var/spool/torque/server_name
```
2. Verify that the Torque Server hostname used is exactly the name returned by a reverse hostname lookup.
```
[root]# cat /var/spool/torque/server_name | perl -lpe '$_=(gethostbyname($_))[0]'
```
  If different, take the necessary steps to make them match. For example, it may be necessary to add the Torque Server hostname to the /etc/hosts file on the Moab Server Host.
```
[root]# vi /etc/hosts

<Torque_server_ip_address> <Torque_server_hostname> <Torque_server_FQDN>
```
3. Start the trqauthd daemon.
```
[root]# service trqauthd start
```
```
[root]# systemctl start trqauthd.service
```
```
[root]# systemctl start trqauthd.service
```

Start Moab (assumes Moab configured with the ‑‑with‑init option).

[root]# service moab start

[root]# systemctl start moab.service

[root]# systemctl start moab.service

6.33.3 Configure Torque to Trust Moab

If you are using Torque as a resource manager and you installed the Torque Server on a different host (Torque Host); recommended, do the following:

On the Torque Host, add the name of the Moab Server Host (where Moab Server is installed) as a manager, and submit the host.

[root]# qmgr
Qmgr: set server managers += root@<moab_server_hostname>
Qmgr: set server submit_hosts += <moab_server_hostname>
Qmgr: exit

6.33.4 Verify the Installation

If you have a resource manager configured, verify that the scheduler is able to schedule a job. Do the following:

Submit a sleep job as a non-root user (adaptive is used in this example) and verify the job is running.
```
[root]# su - adaptive
[adaptive]$ echo sleep 150 | msub
[adaptive]$ showq
[adaptive]$ exit
```