3.8 Installing Moab Workload Manager

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

In this topic:

• 3.8.1 Understand Licenses
• 3.8.2 Open Necessary Ports
• 3.8.3 Obtain and Install the Elastic Computing License
• 3.8.4 Install Moab Server
• 3.8.5 Configure Torque to Trust Moab
• 3.8.6 Verify the Installation

3.8.1 Understand Licenses

As part of the Moab modularity, introduced in version 9.0.1, Moab features can be licensed separately. See Module-Based Features.

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.

Elastic Computing, beginning with 9.1.0, requires an RLM Server as part of your configuration.

3.8.2 Open Necessary Ports

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.

Do the following:

1. On the RLM server, obtain the hostid and hostname.
   • hostid

     [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

   • hostname

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

2. Email [email protected] for a license and include the hostid and hostname you just obtained.
3. Adaptive Computing will generate the license and send you the Elastic Computing license file (.lic) file in a return email.
4. On the RLM server, do the following:
   1. Download and install the license file.

      [root]# cd /opt/rlm
      [root]# chown rlm:rlm <licenseFileName>.lic

   2. If the RLM Server in your configuration uses a firewall, edit the license file to reference the ISV adaptiveco port for the Adaptive license-enabled products. This is the same port number you opened during the RLM Server installation. 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]# 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.

   3. If you did not install an RLM Server using the file available from Adaptive Computing (for example, because your system configuration already uses one), do the following:
      1. Download the 'adaptiveco.set' file from the Adaptive Computing Moab HPC Suite Download page.
      2. Install the 'adaptiveco.set' file.

         [root]# chown rlm:rlm adaptiveco.set

      3. Place the 'adaptiveco.set' file in the same directory where the Elastic Computing license resides. Typically, this is the RLM Server base directory (/opt/rlm); but may be different depending on your configuration
   4. Perform a reread on the RLM Server base directory to update the RLM Server with your license. For example:

      [root]# /opt/rlm/rlmreread

3.8.4 Install Moab Server

On the Moab Server Host do the following:

1. If you configuration uses firewalls, confirm you have opened the necessary ports. See 3.8.2 Open Necessary Ports .
2. If you have not already done so, complete the steps to prepare the Moab Server Host. See 3.3 Preparing for RPM Installs for more information.
3. Install RPM packages.
   1. Install the Moab Server RPMs.

      [root]# yum install moab-workload-manager moab-workload-manager-hpc-configuration

      

      If installing on RHEL, you may need to enable optional RHEL repositories in order to find some of the dependent packages.

      [root]# yum install --enablerepo=rhel-6-server-optional-rpms 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

   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

4. Source the following file to add the Moab executable directories to your current shell $PATH environment.

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

5. 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, 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-2017
       Current License:   Max Sockets    =  1000000
       Current License:   (moab_grid) Valid Until - 15-jan-2017
       Current License:   (moab_green) Valid Until - 15-jan-2017
       Current License:   (moab_provision) Valid Until - 15-jan-2017
       Current License:   (moab_vms) Valid Until - 15-jan-2017
       Current License:   Max VMs    =  1000000
       Current License:   (moab_elastic) Valid Until - 15-jan-2017
       Current License:   (moab_groupsharing) Valid Until - 15-jan-2017
       Current License:   (moab_advancedrm) Valid Until - 15-jan-2017
       Current License:   (moab_workflow) Valid Until - 15-jan-2017
       Current License:   (moab_accounting) Valid Until - 15-jan-2017

   • Legacy License Format

     Moab Workload Manager Version '9.1.0' License Information:
      Current License:  Max Procs   = 10000
      Current License:  Valid Until - 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.

6. 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_FQDN><Torque_server_hostname>

7. Start the trqauthd daemon.

   [root]# service trqauthd start

8. Start Moab.

   [root]# service moab start

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:

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

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

3.8.6 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

Related Topics 

Chapter 3 RPM installation Method

© 2016 Adaptive Computing