2.4 Initial Moab Configuration
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:
- 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:
- 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:
|| 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.
- 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: