Requirements
It is highly recommended that you first perform installations and upgrades in a test environment. Standard installation and upgrade procedures and use cases are tested prior to release. However, due to the wide range of possible configurations and customizations, it is important to exercise caution when deploying new versions of software into your production environments. This is especially true when the workload has vital bearing on your organization's day-to-day operations. We recommend that you test in an environment that mirrors your production environment's configuration, workflow and load as closely as possible. Please contact your Adaptive Computing account manager for suggestions and options for installing / upgrading to newer versions.
There are many different ways to install and configure Moab HPC Suite. Each environment has its own set of requirements and preferences. The following installation instructions are intended to help an administrator understand how each of the Moab HPC Suite components interact and how to install and configure each one. Two approaches have been documented: the “Manual installation” and the “RPM installation”. Only one approach is required for installation; do not try to follow both sets of instructions on a single system.
The diagram below provides a general topology of the Moab HPC Suite.
|
|
Click to enlarge |
Please note the following:
- Moab Accounting Manager is available only with the Moab HPC Enterprise Suite.
- Moab Insight and Moab Viewpoint are only available with the Moab HPC Enterprise Suite.
- Smaller environments may elect to consolidate the TORQUE Head Node with the Moab Head Node, including PBS Server in the list of components installed on the Moab Head Node.
- The Requirements section gives further clarification regarding what each component requires.
- Although Moab Workload Manager and Moab Accounting Manager may share the same database instance, it is not a requirement. Two database instances may be used, one for each component. See the Requirements section for more information about what databases are supported.
- Larger systems will require more dedicated resources for each component, in which case it may be necessary to move individual components from the Moab Head Node (i.e. databases, Moab Accounting Manager, and/or Viewpoint) to their own respective servers.
- The Message Queue component is fulfilled by ZeroMQ™. The libraries are provided with the components that use the message queue and are enabled via configuration; no special installation is necessary.
Where to Start
- Begin by reading the Requirements section below. Whether installing manually or with RPMs, it is important to be familiar with the hardware and software requirements.
-
Decide whether you will perform a manual installation or an RPM installation.
- The manual installation provides advantages to administrators who want to pick and choose what components to install and administrators who want non-standard configure options.
- The RPM installation provides advantages to administrators who want a fairly standard installation with TORQUE Resource Manager, Moab Workload Manager, and Moab Web Services installed on one server.
RPM installation only supports installation for small to medium (with out large throughput) installation types and only on Red Hat, CentOS, or Scientific Linux systems. For other system types or for other supported operating systems, refer to the manual installation instructions.
Then follow the appropriate installation instructions.
Code samples have been provided for convenience. Some code samples provide sample passwords (i.e. “changeme!”). We strongly recommend that you do not use these passwords during installation, as using the documented passwords could introduce unnecessary security vulnerabilities into your system.
-
The “Additional Configuration” section in both the manual and the RPM installation instructions provide additional information and instructions for optional, but recommended configurations (i.e. Configuring SSL in Tomcat, etc.).
- Refer to Troubleshooting for assistance in addressing common problems during installation and configuration.
- Refer to Component Documentation for links to additional administrator and reference guides.
Requirements
Moab HPC Suite
Hardware Requirements
The following are the minimum hardware requirements for an average environment. Larger environments should consider allocating more resources and/or spreading components across multiple servers. Please consult the table below for recommendations.
|
Type |
# of Compute Nodes |
Jobs/ week |
Minimum Requirements (per Head Node distribution) |
Recommended Requirements (targeting minimum number of servers) |
|---|---|---|---|---|
|
Proof of Concept / Small Demo |
50 |
<1k |
Moab+TORQUE Head Node:
Insight Server:
|
Same as minimum |
|
Medium |
500 |
<100k |
Moab+TORQUE Head Node:
Insight Server:
|
Moab+TORQUE Head Node:
Insight Server:
|
|
Medium with High Throughput or Larger |
>500 |
>100k |
Moab Head Node:
TORQUE Head Node:
Insight Server:
|
We recommend separating components onto separate servers where possible (some components should not be separated; see Requirements below). Specific requirements around the intended configuration and use of Moab HPC Suite will help determine suite topology and resource allocation. |
Please note the following:
- All requirements above (minimum and recommended) target a minimum number of management servers. Administrators are encouraged to separate the TORQUE and Moab head nodes where possible for better results, especially when High Throughput is enabled.
- Although many factors may have an impact on performance (network bandwidth, intended use and configuration, etc.), we consider High Throughput as something that makes a significant enough difference between minimum and recommended hardware requirements to merit mention in the table above.
- Moab and TORQUE are both multi-threaded and perform better with more processors.
- Due to the large amount of data Moab must send to Insight, Moab performs better without Insight enabled (for environments that do not require Viewpoint).
- Regarding disk space, consideration should be given to requirements related to log files, log depth, number of jobs/nodes/reservations (more objects impact database journal size), average number of events generated (more events take more space), etc.
Software Requirements
The installation documentation provides more details regarding how to install and configure the following software requirements. The information provided below is for your information only. No action is necessary.
Software requirements are listed per-component rather than suite-wide to make it easier for administrators who wish to install components on separate servers.
TORQUE
Supported Operating Systems
- CentOS 6.x
- Red Hat 6.x
- Scientific Linux 6.x
- SUSE Linux Enterprise Server 11
CentOS 5.9, Red Hat 5.9 and Scientific Linux 5.9 are supported, largely to continue support for clusters where the compute nodes operating systems cannot be upgraded. We recommend that the TORQUE head node run on the supported operating systems listed above.
Software Requirements
- libxml2-devel package (package name may vary)
- openssl-devel package (package name may vary)
- Tcl/Tk version 8 or later if you plan to build the GUI portion of TORQUE or use a Tcl based scheduler
- If you use cpusets, libhwloc 1.2 is required for TORQUE 5.1.0 or 5.0.x; 1.1 is required for TORQUE 4.2.9
If you intend to use TORQUE 5.1.0 with Moab Workload Manager, you must run Moab version 8.1.0 or 8.0.x. TORQUE 5.1.0 will not work with versions earlier than Moab 8.0.
If you build TORQUE from source (i.e. clone from github), the following additional software is required:
- gcc
- gcc-c++
- A posix compatible version of make
- libtool 1.5.22
- boost-devel 1.36.0
Moab Workload Manager
Supported Operating Systems
- CentOS 6.x
- Red Hat 6.x
- Scientific Linux 6.x
- SUSE Linux Enterprise Server 11
Software Requirements
- libcurl
- Perl 5.8.8 or later
- perl-cpan (package name may vary)
- libxml2-devel (package name may vary)
- (Optional) Moab Accounting Manager 8.1
- (Optional) MySQL, PostgreSQL, or Oracle with ODBC driver (see Database Configuration for details)
Supported Resource Managers
- TORQUE 5.1
- SLURM
Moab Accounting Manager
MAM is commonly installed on the same host as Moab Workload Manager; however, in some cases you might obtain better performance by installing them on separate hosts.
Supported Operating Systems
- CentOS 6.x
- Red Hat 6.x
- Scientific Linux 6.x
- SUSE Linux Enterprise Server 11
Software Requirements
- gcc
- perl-suidperl
- httpd
- mod_ssl
- rrdtool
- Moab® Workload Manager 8.1
- Perl modules
Depends On (not necessarily on the same server)
MAM uses an RDBMS as a back end. We recommend that the database used by MAM not be hosted on the same server as the database used by Insight.
- PostgreSQL 7.2 or later
Moab Web Services
MWS should be installed on the same host as Moab® Workload Manager.
Supported Operating Systems
- CentOS 6.x
- Red Hat 6.x
- Scientific Linux 6.x
- SUSE Linux Enterprise Server 11
Software Requirements
- Moab® Workload Manager 8.1
- Apache Tomcat™ 6
-
Oracle® Java® 7 Runtime Environment
Oracle Java 7 Runtime Environment is the recommended Java environment, but Oracle Java 6 is also supported. All other versions of Java, including OpenJDK/IcedTea, GNU Compiler for Java, and so on cannot run Moab Web Services.
- MongoDB® 2.4.x
Depends On (not necessarily on the same server)
- OpenLDAP or PAM (see Configuring Moab Web Services)