(Click to open topic with navigation)
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:
As part of the Moab modularity, introduced in version 9.0.1, Moab features can be licensed separately. See Module-Based Features in the Moab Workload Manager Administrator Guide.
With the 9.1.0 release, Moab now uses an RLM Server to manage licenses. For the Moab core and for most Moab features, an RLM Server is not required. The new Moab "core" license will have a new name to reflect the RLM generation. Do not rename this license to moab.lic. See 1.3 RLM Licensing Model for more information about RLM licensing.
Elastic Computing, beginning with 9.1.0, requires an RLM Server as part of your configuration.
The 9.1.0 licensing change does not affect legacy licenses; however, a module-based licensed may be required to use newer functionality.
If your site is running firewall software on its hosts, you will need to configure the firewall to allow connections to the necessary ports.
Location | Ports | Functions | When Needed |
---|---|---|---|
Moab Server Host | 42559 | Moab Server Port | 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 |
See 2.11 Opening Ports in a Firewall for general instructions and an example of how to open ports in the firewall.
3.8.3 Obtain and Install the Elastic Computing License
If using Elastic Computing, Moab requires access to an RLM license server to record usage.
These instructions assume you already have access to an RLM Server. See 3.13 Installing RLM Server for instructions on how to set up a new RLM Server.
Do the following:
[root]# /opt/rlm/rlmhostid
You should see output similar to the following.
rlmhostid v12.1 Copyright (C) 2006-2016, Reprise Software, Inc. All rights reserved. Hostid of this machine: 00259096f004
[root]# /opt/rlm/rlmhostid host
You should see output similar to the following.
rlmhostid v12.1
Copyright (C) 2006-2016, Reprise Software, Inc. All rights reserved.
Hostid of this machine: host=<your-host-name>
[root]# cd /opt/rlm
[root]# chown rlm:rlm <licenseFileName>.lic
[root]# vi /opt/rlm/moab_elastic_tracking.lic ISV adaptiveco port=5135
The license file already references the RLM Server port (5053 by default).
If the RLM Server in your configuration uses different ports, you will need to modify the license file to reflect the actual ports. See the instructions to open necessary ports in the 2.6 Installing RLM Server (manual installation method) or 3.13 Installing RLM Server (RPM installation method) for more information.
[root]# chown rlm:rlm adaptiveco.set
[root]# /opt/rlm/rlmreread
On the Moab Server Host do the following:
[root]# zypper install moab-workload-manager moab-workload-manager-hpc-configuration
[root]# zypper install moab-torque-client
[root]# zypper install moab-accounting-manager
[root]# . /etc/profile.d/moab.sh
[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:
New RLM-Based License (version 9.1.0 or after)
$ moab --about | grep License Moab Workload Manager Version 'master' License Information: Current License: (moab_license) Valid Until - 15-jan-2018 Current License: Max Sockets = 1000000 Current License: (moab_grid) Valid Until - 15-jan-2018 Current License: (moab_green) Valid Until - 15-jan-2018 Current License: (moab_provision) Valid Until - 15-jan-2018 Current License: (moab_vms) Valid Until - 15-jan-2018 Current License: Max VMs = 1000000 Current License: (moab_elastic) Valid Until - 15-jan-2018 Current License: (moab_groupsharing) Valid Until - 15-jan-2018 Current License: (moab_advancedrm) Valid Until - 15-jan-2018 Current License: (moab_workflow) Valid Until - 15-jan-2018 Current License: (moab_accounting) Valid Until - 15-jan-2018
Legacy License Format
Moab Workload Manager Version '9.1.1' License Information: Current License: Max Procs = 10000 Current License: Valid Until - Jul 13 19:42:10 2018
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:
[root]# echo <Torque_server_hostname> > /var/spool/torque/server_name
[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_FQDN><Torque_server_hostname>
[root]# systemctl start trqauthd.service
[root]# systemctl start moab.service
3.8.5 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:
[root]# qmgr Qmgr: set server managers += root@<moab_server_hostname> Qmgr: set server submit_hosts += <moab_server_hostname> Qmgr: exit
If you have a resource manager configured, verify that the scheduler is able to schedule a job. Do the following:
[root]# su - adaptive [adaptive]$ echo sleep 150 | msub [adaptive]$ showq [adaptive]$ exit
Related Topics