Moab HPC Suite Enterprise Edition Download

Version Advisories:

• Recommendation for using new RPM installs: the RPM install process will assume that the Moab HPC Suite components are the only software on the head server and all components will install on that one server. It is strongly recommended that all other software be removed from the Moab HPC Suite head server. If you have a non-standard configuration of Moab, it is recommended that you contact support to discuss considerations before using the RPM installation to upgrade.
• Customers using or planning to use Moab Web Services or the Moab Viewpoint portal: implement Moab 7.2 only on CentOS /RHEL 6 as full functionally for these components are only supported on these versions.
• Customers upgrading from 6.1 should contact support and plan on upgrading directly to 7.2. Moab HPC Suite 7.2.x is the current recommended upgrade for customers running Moab HPC Suite 7.1.x or 7.0.x. Customers using Moab HPC Suite 6.0.x or earlier should request upgrade product builds from support. See individual component documentation for more information on upgrading.
• If you are using Moab Accounting Manager or Gold Allocation Manager with your current Moab solution, you will need to upgrade to the new Moab Accounting Manager 7.2.x at the same time you upgrade to Moab Workload Manager 7.2.x. Moab Accounting Manager is available to customers with Moab HPC Suite – Enterprise Edition.
• Moab requires an x64-bit architecture for deployment or upgrade beginning with version 7.1.

Access 7.2.3 documentation
Access Moab Plugin Downloads

Version Advisories:

• Refer to the new Moab HPC Suite – Enterprise Edition Installation Guide prior to beginning installation for recommended installation order, and pre-requisite considerations and tasks.
• Customers upgrading from 6.1 should contact support and plan upgrading directly to 7.1. Moab HPC Suite 7.1.x is the current recommended upgrade for customers running Moab HPC Suite 7.0.x. Customers using Moab HPC Suite 6.0.x or earlier should request upgrade product builds from support. See individual component documentation for more information on upgrading.
• If you are using Moab Accounting Manager with your current Moab solution, you will need to upgrade to the new Moab Accounting Manager 7.1.x at the same time you upgrade to Moab Workload Manager 7.1.x. Moab Accounting Manager is available to customers with Moab HPC Suite – Enterprise Edition.
• If you are using Gold Allocation Manager with your current Moab solution, you will need to migrate to Moab Accounting Manager 7.1.x at the same time you upgrade to Moab Workload Manager 7.1. Gold Allocation Manager is incompatible with Moab Workload Manager 7.0.x and later. Moab Accounting Manager is available to customers with Moab HPC Suite – Enterprise Edition.
• Cray customers may choose between using TORQUE 4.1.1 and 4.1.2 with their Moab HPC Suite 7.1 deployment. The 4.1.1 contains fixes and updates from 4.1.0 while the 4.1.2 version contains these fixes as well as supports the new dual-domain job submission feature enabling a single job to run simultaneously on a Cray cluster and non-Cray compute nodes. See the Moab Workload Manager 7.1.2 Administrator Guide, Appendix G.1 Computer Resource Managers “Cray XT/Torque – Integration Guide”, for details on how to enable and use this new 4.1.2 feature.
• Customers Using TORQUE 3.0.x or 2.4.x should note that Adaptive Computing will no longer be developing or making updates to the 3.0.x branch or 2.4.x branch. TORQUE 3.0.6 and 2.4.17 are the final updates available. Adaptive Computing will end support for 2.4.x on August 31, 2012 and for 3.0.x on December 31, 2012. If considering upgrading to Moab HPC Suite 7.1, it is recommended that you also consider updating to TORQUE 4.1 which is optimized for the Moab HPC Suite 7.1 release. This will also help ensure you are on a supported release of TORQUE.
• NUMA customers upgrading to TORQUE 4.x should note that some names have changed from 3.0.x to 4.x in the mom.layout file and nodes file. Making the following updates to your mom.layout and nodes file will avoid issues:
  • The 3.0.x mom.layout of “cpus=0-11 mem=1” must now appear as ”nodes=1”. The indices for “mem=” can be simply placed as the value for “nodes=”.
  • The nodes file name for “num_numa nodes” now is “num_node_boards
  • The nodes file name for “numa_node” now is node_board_str
• Moab requires an x64-bit architecture for deployment or upgrade beginning with version 7.1.

Access 7.1.5 documentation
Access Moab Plugin Downloads

Version Advisories:

• TORQUE 2.5.7 or later is required for customers using Moab advanced GPGPU scheduling capabilities. See System Requirements section of the Readme for more Component Compatibility details
• Moab “torque” packages are compiled against libtorque.so.0. If this package does not exist on your system but libtorque.so.2 does, it is safe to create a symlink to get Moab to run.
• Moab “odbc” packages are compiled against libodbc.so.1. In order to run an “odbc” version of Moab you must have this library already installed on your system.
• Upgrading from Moab 5.4: The Moab 5.4 uninstaller does not remove its man pages. Administrators performing an upgrade from 5.4 to 6.0 must manually remove the man page files.

Moab Workload Manager 6.1 is a major release with significant new enhancements. We recommend that before deploying this major release on your production environment, you deploy and test the functionality for your organization on a test environment.

Access 6.1 documentation