A Moab 6.1 hybrid build or later is required for setting up the hybrid system. Moab installation packages are readily available for all major architectures and operating systems. Full or evaluation licenses will work with any build.
Versions that work together include:
|Windows HPC Server 2008 R1 is not being developed and is not compatible with Moab 6.0 or higher.|
A provisioning-capable hybrid Moab license is also required in either case.
The following example shows the commands to do a basic installation from the command line for Moab. In this case, the install package for Moab 6.1 needs to be in the current directory.
> tar xvzf moab-6.1-linux-x86_64-torque.tar.gz > cd Moab > ./configure > make install > chmod 1777 /opt/moab/log
By default, Moab installs everything to the /opt/moab directory (pre-Moab 6.0 versions install binaries to /usr/local). The following example shows a sample ls -l output in /opt/moab.
drwxr-xr-x 2 root root 4096 2010-01-22 12:26 etc drwxr-xr-x 2 root root 4096 2010-01-22 12:26 log drwxrwxrwt 2 root root 4096 2010-01-22 12:42 spool drwxr-xr-x 2 root root 4096 2010-01-22 12:26 stats drwxr-xr-x 2 root root 4096 2010-01-22 12:26 tools
Note that the installation creates a default moab.cfg file in the etc/ folder. This file contains the global configuration for Moab that is loaded each time Moab is started. The definitions for users, groups, nodes, resource managers, quality of services, and standing reservations are placed in this file. The default moab.cfg file provided with an installation is simple. The installation process defines several important default values, but the majority of configuration needs to be done by the administrator, either through directly editing the file or using one of the provided administrative tools such as Viewpoint.
The following shows the default moab.cfg file without comments:
SCHEDCFG[MyMoab] SERVER=master:42559 ADMINCFG USERS=root RMCFG[Torque] TYPE=PBS
The first line of the configuration file defines a new scheduler named MyMoab. In this case, it is located on a host named master and listening on port 42559 for client commands. These values are added by the installation process, and should not be modified in most cases.
The second line, however, requires some editing by the administrator. The example on the second line specifies what users on the system have level 1 administrative rights—users who have global access to information and unlimited control over scheduling operations in Moab. Additional users can be added in a comma-separated list. Moab attempts to run as the first level 1 administrator, so root should not be removed from its position at the beginning of the list. Moab must run as root to submit jobs to the resource managers as the original owner. There are five default administrative levels defined by Moab, each of which is fully customizable.
The final line in this example is the configuration for the default resource manager. This particular distribution is for the TORQUE resource manager. Because TORQUE follows the PBS style of job handling, the resource manager is given a type of PBS. To differentiate it from other resource managers that may be added in the future, it is also given the name Torque.
|To increase system security, configure a security key that authenticates client commands to Moab. To do so, create a .moab.key file inside your Moab home directory (/opt/moab by default). Run chmod 400 .moab.key and start Moab. For more information, see these detailed instructions.|
This constitutes the basic installation of Moab. Many additional parameters can be added to the moab.cfg file to fully adapt Moab to your needs. A more detailed installation guide is available at the following URL:http://www.adaptivecomputing.com/resources/docs/mwm/2.0installation.php