Initial Moab Configuration

2.0 Installation and Initial Configuration > Initial Moab Configuration

2.5 Initial Moab Configuration

2.5-A Configuring an RPM-based install of Moab

When Moab is installed via an RPM source, such as with the Moab HPC Suite or Moab Cloud Suite, the moab.cfg file contains only one directive - an #IMPORT line that imports all the configuration files in /opt/moab/etc. The usual configuration settings that are normally contained in moab.cfg have been moved to moab-server.cfg. Moab still reads the moab.cfg file and, due to the #INCLUDE directive, reads in all the other configuration files as well.

To configure Moab in the case of an RPM install, you can modify the moab.cfg file, the moab-server.cfg file, or any of the configuration files that are read in by moab.cfg such as the accounting manager configuration file (am.cfg) or the resource manager configuration file (rm.cfg).

The RPMs allow for a client install of Moab, instead of a server install. In this instance, the moab-server.cfg file is replaced with a moab-client.cfg file. The server and client RPMs cannot be installed on the same machine.

2.5-B Basic configuration of Moab

After Moab is installed, there may be minor configuration remaining within the primary configuration file, moab.cfg. While the configure script automatically sets these parameters, sites may choose to specify additional parameters. If the values selected in configure are satisfactory, then this section may be safely ignored.

The parameters needed for proper initial startup include the following:

Parameter	Instructions
SCHEDCFG	The SCHEDCFG parameter specifies how the Moab server will execute and communicate with client requests. The SERVER attribute allows Moab client commands to locate the Moab server and is specified as a URL or in <HOST>[:<PORT>] format. For example: SCHEDCFG[orion] SERVER=cw.psu.edu The SERVER attribute can also be set using the environment variable $MOABSERVER. Using this variable allows you to quickly change to Moab server that client commands will connect to. > export MOABSERVER=cluster2:12221
ADMINCFG	Moab provides role-based security enabled via multiple levels of admin access. Users who are to be granted full control of all Moab functions should be indicated by setting the ADMINCFG parameter. The first user in this USERS attribute list is considered the primary administrator. It is the ID under which Moab will execute. For example, the following may be used to enable users greg and thomas as level 1 admins: ADMINCFG[1] USERS=greg,thomas Moab may only be launched by the primary administrator user ID. The primary administrator should be configured as a manager/operator/administrator in every resource manager with which Moab will interface. If the msub command will be used, then "root" must be the primary administrator. Moab's home directory and contents should be owned by the primary administrator.
RMCFG	For Moab to properly interact with a resource manager, the interface to this resource manager must be defined as described in the Resource Manager Configuration Overview. Further, it is important that the primary Moab administrator also be a resource manager administrator within each of those systems. For example, to interface to a TORQUE resource manager, the following may be used: RMCFG[torque1] TYPE=pbs