Product SiteDocumentation Site

Red Hat Enterprise MRG 2

Grid Installation Guide

Installation information for the Grid component of Red Hat Enterprise MRG

Edition 1

Logo

Lana Brindley

Red Hat Engineering Content Services

Alison Young

Red Hat Engineering Content Services

Legal Notice

Copyright © 2011 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
All other trademarks are the property of their respective owners.


1801 Varsity Drive
 RaleighNC 27606-2072 USA
 Phone: +1 919 754 3700
 Phone: 888 733 4281
 Fax: +1 919 754 3701

Abstract
This book will show you how to download and install the MRG Grid component of the Red Hat Enterprise MRG distributed computing platform. For detailed information on the use of MRG Grid, see the MRG Grid User Guide.

Preface
1. Document Conventions
1.1. Typographic Conventions
1.2. Pull-quote Conventions
1.3. Notes and Warnings
2. Getting Help and Giving Feedback
2.1. Do You Need Help?
2.2. We Need Feedback!
1. Overview
2. MRG Grid Benefits and Features
3. MRG Grid Scale Requirements
4. Installing MRG Grid
4.1. Installing MRG Grid on Red Hat Enterprise Linux
4.2. Installing MRG Grid on Microsoft Windows
5. Getting Started with MRG Grid
6. More Information
A. Revision History

Preface

Red Hat Enterprise MRG
This book contains basic overview and installation information for the MRG Grid component of Red Hat Enterprise MRG. Red Hat Enterprise MRG is a high performance distributed computing platform consisting of three components:
  1. Messaging — Cross platform, high performance, reliable messaging using the Advanced Message Queuing Protocol (AMQP) standard.
  2. Realtime — Consistent low-latency and predictable response times for applications that require microsecond latency.
  3. Grid — Distributed High Throughput Computing (HTC) and High Performance Computing (HPC).
All three components of Red Hat Enterprise MRG are designed to be used as part of the platform, but can also be used separately.
MRG Grid
Grid computing allows organizations to fully utilize their computing resources to complete high-performance tasks. By monitoring all resources - rack-mounted clusters and general workstations - for availability, any spare computing power can be redirected towards other, more intensive tasks until it is explicitly required again. This allows a standard networked system to operate in a way that is similar to a supercomputer.
MRG Grid provides High Throughput and High Performance computing and enables enterprises to achieve higher peak computing capacity as well as improved infrastructure utilization by leveraging their existing technology to build high performance grids. MRG Grid provides a job queuing mechanism, scheduling policy, priority scheme, resource monitoring, and resource management. Users submit their jobs to MRG Grid, where they are placed into a queue. MRG Grid then chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion.
MRG Grid is based on the Condor Project developed within the University of Wisconsin-Madison. Condor also offers a comprehensive library of freely available documentation in its Manual.

1. Document Conventions

This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.

1.1. Typographic Conventions

Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
Press Enter to execute the command.
Press Ctrl+Alt+F2 to switch to the first virtual terminal. Press Ctrl+Alt+F1 to return to your X-Windows session.
The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mono-spaced bold. For example:
File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
Choose SystemPreferencesMouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
To insert a special character into a gedit file, choose ApplicationsAccessoriesCharacter Map from the main menu bar. Next, choose SearchFind… from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose EditPaste from the gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john@example.com.
The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home.
To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release.
Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
Publican is a DocBook publishing system.

1.2. Pull-quote Conventions

Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in mono-spaced roman and presented thus:
books        Desktop   documentation  drafts  mss    photos   stuff  svn
books_tests  Desktop1  downloads      images  notes  scripts  svgs
Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:
package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[]) 
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }
}

1.3. Notes and Warnings

Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.

Note

Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.

Important

Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.

Warning

Warnings should not be ignored. Ignoring warnings will most likely cause data loss.

2. Getting Help and Giving Feedback

2.1. Do You Need Help?

If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at http://access.redhat.com. Through the customer portal, you can:
  • search or browse through a knowledgebase of technical support articles about Red Hat products.
  • submit a support case to Red Hat Global Support Services (GSS).
  • access other product documentation.
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo. Click on the name of any mailing list to subscribe to that list or to access the list archives.

2.2. We Need Feedback!

If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product Red Hat Enterprise MRG.
When submitting a bug report, be sure to mention the manual's identifier: Grid_Installation_Guide
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.

Chapter 1. Overview

MRG Grid provides high throughput and high performance computing and enables enterprises to achieve higher peak computing capacity as well as higher IT utilization by leveraging their existing infrastructure and building high performance grids. High throughput computing (HTC) delivers large amounts of computing power over a sustained period of time (months or years), whereas high performance computing (HPC) delivers significant computing power over a short period of time (hours or days).
MRG Grid enables enterprises and research organizations to bring the power of distributed computing across their entire infrastructure to tackle the largest computational problems in a highly efficient and effective manner.

Chapter 2. MRG Grid Benefits and Features

Benefits
MRG Grid provides significant benefits and value for enterprises, including:
Power
MRG Grid can process the largest computational workloads, from massively parallel High Performance Computing jobs to long-running High Throughput Computing jobs
Peak Workload Handling
MRG Grid adds on-demand computational power for handling peak loads. This is achieved through capabilities such as cycle-stealing, scheduling, and the use of remote grids.
Flexibility
MRG Grid provides complete flexibility and can run high-burst or lengthy computations in both centralized and distributed grids. Jobs can be run on various platforms including Linux and Windows. Furthermore, MRG Grid can schedule virtualized environments and workloads for the utmost flexibility in utilizing infrastructure.
Powerful Management Tools
Managing MRG Grid is simplified by leveraging the Red Hat Enterprise MRG unified, browser-based management console. The Red Hat Enterprise MRG integrated management tools enable administrators to manage, configure, provision, deploy, and monitor their grid deployments using the same tools they use for MRG Messaging and MRG Realtime.
Features
MRG Grid provides a broad set of features across both High Throughput Computing and High Performance Computing, including:
Virtualization
Allows for submission of a virtual machine (VM) as a user job, supporting migration of the VM
Dedicated and Undedicated Node Management (Cycle-Stealing)
Allows for dedicated resources (clusters) to be augmented with otherwise undedicated (desktops) using flexible policies
Multiple Standards-Based APIs
The web service interface provides job submission and management functionality; the command line interface provides functionality that is highly scriptable, with consistent output
Security
Authentication using multiple mechanisms
Privacy provided by network encryption
Integrity of network traffic
Authorization through flexible configuration policies
Management Tools
Powerful browser-based management tools for managing daemons and machines, security, compute jobs, scalability settings, priorities, and more. Also provides sophisticated monitoring capabilities.
Workflow Management
The ability to specify job dependencies, via DAGMan, allows for construction and execution of complex workflows
Accounting
User and group resource utilization is tracked and accessible to administrators
ClassAds
A flexible language for policy and meta-data description
Policies
Flexible, customizable policies specified by jobs and resources via ClassAds
High Availability
The Negotiator and Collector, via the High Availability Daemon (HAD), and the Schedd, via Schedd Fail-over, can have their state replicated to allow for graceful fail-over upon service disruption
Compute On-Demand (COD)
The ability for a node or set of nodes to be claimed by a user in such a way that others may use the claimed nodes until the user needs them
Priority Based Scheduling
Priority scheduling is performed at the granularity of a user
Fair-share scheduling can be performed on groups of users
Priority management is controllable by administrators
Account Remapping
Allows for execution across administrative domains
Enhance security by using a restricted pool of users to run jobs on execute machines
Parallel Universe
Provides an extensible framework for running parallel - including Message Passing Interface (MPI) - jobs
Co-allocation of compute nodes is done automatically
Framework implementation for MPICH1, MPICH2, and LAM provided
Java Universe
Explicit support of jobs written in Java
Time Scheduling for Job Execution (Cron)
Allows a job or multiple jobs to be started at specific times, with customizable policy for failures such as missed deadlines
File Staging
Support for automatic file staging in the absence of a shared file system. Job input and online file streaming from submit to execute nodes using Chirp

Chapter 3. MRG Grid Scale Requirements

MRG Grid is designed for deployments of any scale, from fewer than a dozen nodes to tens of thousands of nodes.
The deployments described below are examples of scale sizes.
Small
An example small scale deployment is:
  • 64 nodes (each quad dual-core CPUs)
  • 5 concurrent grid users, accessing the grid at 1 page view per second (peak)
  • 10 job submitters, submitting 1 job per second concurrently (peak)
  • 10 job completions per minute (sustained), 3 years of job history (1 million jobs)
  • Ability to sustain peak rates for at least 5 minutes
Medium
An example medium scale deployment is:
  • 500 nodes (each quad dual-core CPUs)
  • 20 concurrent grid users, accessing the grid at 1 page view per second (peak)
  • 20 job submitters, submitting 2 jobs per second concurrently (peak)
  • 100 job completions per minute (sustained), 3 years of job history (10 million jobs)
  • Ability to sustain peak rates for at least 5 minutes
Large
A large-scale grid is defined as a grid supporting 5000 Execute Nodes, or a similar magnitude. There are several considerations when implementing a large scale grid. Red Hat, Inc currently recommends that customers configure large-scale MRG Grid installations in cooperation with a Solution Architect through Red Hat, Inc Consulting.

Chapter 4. Installing MRG Grid

In order to install MRG Grid you will need to have registered your system with Red Hat Network. This table lists the Red Hat Enterprise MRG channels available on Red Hat Network for MRG Grid.
Table 4.1. Red Hat Enterprise MRG Channels Available on Red Hat Network
Channel Name Operating System Architecture
Red Hat MRG Grid RHEL-5 Server 32-bit, 64-bit
Red Hat MRG Grid RHEL-6 Server 32-bit, 64-bit
Red Hat MRG Grid non-Linux 32-bit

Important

Before you install Red Hat Enterprise MRG check that your hardware and operating system are supported. A complete list is available on the Red Hat Enterprise MRG Supported Hardware Page.

4.1. Installing MRG Grid on Red Hat Enterprise Linux

  1. Install the MRG Grid group using the yum command.
    # yum groupinstall "MRG Grid"
    
  2. You can check the installation location and that the components have been installed successfully by using the rpm -ql command with the name of the package you installed. For example:
    # rpm -ql condor
    /etc/condor
    /etc/condor/condor_config
    /usr/bin/condor
    ...
    [output truncated]
    

Note

If you find that yum is not installing all the dependencies you require, make sure that you have registered your system with Red Hat Network.

4.2. Installing MRG Grid on Microsoft Windows

  1. Navigate to the directory where the installation file has been saved. Double-click on the .msi file.
  2. Click Next to begin the installation.
  3. Read the End-User License Agreement. Check I accept the terms in the License Agreement and click Next to continue.
  4. Enter the IP configuration information for the installation. Click Next to continue.
  5. Enter your email configuration information for the installation. Click Next to continue.
  6. Enter the location of your Java installation. Click Next to continue.
  7. Enter the installation location. Click Next to continue.
  8. Click Install to complete the installation.
  9. Click Finish to exit the Setup Wizard.
  10. The Setup Wizard will prompt for the machine to be restarted.
    Remote configuration is enabled by default. After the restart, MRG Grid will attempt to connect to the remote configuration store to download the new configuration.

Note

The installer can also be run in unattended mode. Open the shell by selecting StartRun then typing in cmd. At the shell prompt, use a command like this:
> msiexec [options] condor-7.4.msi CONDOR_HOST="YOUR.CONDOR.HOST.IP" BROKER_HOST="YOUR.QMF.BROKER.IP" ADMIN_EMAIL="admin@your_domain.com" SMTP="mailserver.your_domain.com"

Chapter 5. Getting Started with MRG Grid

  1. It is advised that you review the local configuration file before starting MRG Grid. By default, this file is located at /etc/condor/config.d/00personal_condor.config.
  2. The default configuration sets up a Personal Condor. This is a specific configuration suited for individual users who do not have their own pool of machines. To find out more about Personal Condor, see the Condor Manual.
  3. To allow other machines to join your pool additional configuration must be done. Open the local configuration file in your preferred text editor and create/locate the ALLOW_WRITE option. Change this option to allow machines to join your pool and submit jobs. Any machine that you give write access to using the ALLOW_WRITE option should also be given read access using the ALLOW_READ option.
    ALLOW_WRITE = *.your.domain.com

    Warning

    The simplest option is to change the ALLOW_WRITE option to ALLOW_WRITE = *. However, this will allow anyone to submit jobs or add machines to your pool. This is a serious security risk and therefore not recommended.
  4. MRG Grid is usually run as a service. To start MRG Grid run the following command:
    # service condor start
    

Note

See Further Reading, for places to turn for help if you have trouble with installing MRG Grid.
For detailed configuration information, see the MRG Grid User Guide.

Chapter 6. More Information

Reporting Bugs
Follow these instructions to enter a bug report:
  1. You will need a Bugzilla account. You can create one at Create Bugzilla Account.
  2. Once you have a Bugzilla account, log in and click on Enter A New Bug Report.
  3. You will need to identify the product (Red Hat Enterprise MRG), the version (2.0), and whether the bug occurs in the software (component=grid) or in the documentation (component=Grid_Installation_Guide).
Further Reading
Red Hat Enterprise MRG and MRG Grid Product Information
MRG Grid User Guide and other Red Hat Enterprise MRG manuals
Condor Manual
Red Hat Knowledgebase

Revision History

Revision History
Revision 1-1Wed Sep 07 2011Alison Young
Prepared for publishing
Revision 1-0Thu Jun 23 2011Alison Young
Prepared for publishing
Revision 0.1-7Fri Jun 17 2011Alison Young
Rebuilt for docs stage
Revision 0.1-6Fri Jun 17 2011Alison Young
Minor scale updates
Revision 0.1-5Tue Jun 14 2011Alison Young
Minor updates
Revision 0.1-4Thu Jun 09 2011Alison Young
BZ#677495 - updated Windows Installation images
Revision 0.1-3Fri Jun 03 2011Alison Young
rebuilt as stage didn't update
Revision 0.1-2Thu Jun 02 2011Alison Young
BZ#677495 - Updates for 2.0
BZ#708789 - typo fix
BZ#708792 - typo fix
Revision 0.1-1Fri May 20 2011Alison Young
Minor xml updates
Revision 0.1-0Tue Feb 22 2011Alison Young
Fork from 1.3