n1 grid engine 6 installation guide

8/7/2019 N1 Grid Engine 6 Installation Guide

1/136

N1 Grid Engine 6 Installation Guide

Sun Microsystems, Inc.4150 Network CircleSanta Clara, CA 95054U.S.A.

Part No: 817611820June 2005


2/136

Copyright 2005 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.

This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. Nopart of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S.and other countries, exclusively licensed through X/Open Company, Ltd.

Sun, N1, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, N1 and Solaris are trademarks or registered trademarks of SunMicrosystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks ofSPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by SunMicrosystems, Inc.

The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges thepioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds anon-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Suns licensees who implement OPEN LOOK GUIsand otherwise comply with Suns written license agreements.

U.S. Government Rights Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement andapplicable provisions of the FAR and its supplements.

DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, AREDISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2005 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. Tous droits rservs.

Ce produit ou document est protg par un copyright et distribu avec des licences qui en restreignent lutilisation, la copie, la distribution, et ladcompilation. Aucune partie de ce produit ou document ne peut tre reproduite sous aucune forme, par quelque moyen que ce soit, sanslautorisation pralable et crite de Sun et de ses bailleurs de licence, sil y en a. Le logiciel dtenu par des tiers, et qui comprend la technologie relativeaux polices de caractres, est protg par un copyright et licenci par des fournisseurs de Sun.

Des parties de ce produit pourront tre drives du systme Berkeley BSD licencis par lUniversit de Californie. UNIX est une marque dpose auxEtats-Unis et dans dautres pays et licencie exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, docs.sun.com, AnswerBook, AnswerBook2, et Solaris sont des mardques de fabrique ou des marques dposes,de Sun Microsystems, Inc. aux Etats-Unis et dans dautres pays. Toutes les marques SPARC sont utilises sous licence et sont des marques de fabriqueou des marques dposes de SPARC International, Inc. aux Etats-Unis et dans dautres pays. Les produits portant les marques SPARC sont bass surune architecture dveloppe par Sun Microsystems, Inc.

Linterface dutilisation graphique OPEN LOOK et Sun a t dveloppe par Sun Microsystems, Inc. pour ses utilisateurs et licencis. Sun reconnatles efforts de pionniers de Xerox pour la recherche et le dveloppement du concept des interfaces dutilisation visuelle ou graphique pour lindustriede linformatique. Sun dtient une licence non exclusive de Xerox sur linterface dutilisation graphique Xerox, cette licence couvrant galement leslicencis de Sun qui mettent en place linterface dutilisation graphique OPEN LOOK et qui en outre se conforment aux licences crites de Sun.

CETTE PUBLICATION EST FOURNIE EN LETAT ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, NEST ACCORDEE, Y COMPRIS DESGARANTIES CONCERNANT LA VALEUR MARCHANDE, LAPTITUDE DE LA PUBLICATION A REPONDRE A UNE UTILISATIONPARTICULIERE, OU LE FAIT QUELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE GARANTIE NESAPPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU.

050701@12762


3/136

Contents

Preface 7

1 Before You Install the Software 11

Plan the Installation 11

Decisions That You Must Make 11

Gather the Necessary Information 12

Loading the Distribution Files On a Workstation 23

M How to Load the Distribution Files On a Workstation 23

2 Installing the Grid Engine Software Interactively 27

Interactive Installation Overview 28

Performing an Installation 28M How to Install the Master Host 28

M How to Install Execution Hosts 42

Registering Administration Hosts 47

Registering Submit Hosts 48

M How to Install the Berkeley DB Spooling Server 48

3 Automating the Installation Process 53

Using the inst_sge Utility and a Configuration Template 53

M How to Use the inst_sge Utility to Automate the Installation Process 53

4 Installing the Increased Security Features 59

Why Install the Increased Security Features? 59

Additional Setup Required 60

3


4/136

M How to Install a CSP-Secured System 60

M How to Generate Certificates and Private Keys for Users 64

M How to Renew Certificates 65Checking Certificates 65

5 Upgrading from a Previous Release of Grid Engine Software 69

About Upgrading the Software 69

M How to Upgrade the Software 69

6 Verifying the Installation 83

Verifying the Installation 83

M How to Verify That the Daemons Are Running on the Master Host 83

M How to Verify That the Daemons Are Running on the Execution Hosts 84

M How to Run Simple Commands 85

M How to Submit Test Jobs 86

7 Removing the Grid Engine Software 89

Removing the Software Interactively 89

M How to Remove the Software Interactively 89

Removing the Software Using the inst_sge Utility and a ConfigurationTemplate 90

M How to Remove the Software Interactively 90

8 Installing the Accounting and Reporting Console 93

Setting Up the Database Software 93

Set up the PostgreSQL Database Software 93

M How to Start the Database Server 93

M How to Set Up a PostgreSQL Database 96

M How to Set Up an Oracle Database 96

Install the Accounting and Reporting Software 97

M How to Set Up dbWriter 97

M How to Install Sun Web Console 103

M How to Install the Accounting and Reporting Console 104M How to Add Authorized ARCo Users 107

4 N1 Grid Engine 6 Installation Guide June 2005


5/136

A Microsoft Services For UNIX 109

Overview 109

Unsupported N1GE Functionality 110System Requirements 110

Services for UNIX Installation 110

Post SFU Installation Tasks 118

Troubleshooting SFU 119

B User Management For N1GE on Windows Hosts 121

Overview 121

Managing Users on Windows Hosts 121

Windows User Example 122

UNIX User Management 122Using N1GE in a Microsoft Windows Environment 123

Registering Windows Domain User Passwords 123

C Other N1GE Installation Issues 125

Checking Linux Motif Libraries 125

M Installing Linux Motif Libraries 125

Installing N1GE on a System with IPMP 126

What is IP Multipathing? 126

Issues between IPMP and Grid Engine 126

Installing the Grid Engine Master Node With IPMP 127Installing a Grid Engine on an Execution Host With IPMP 128

Enabling Administrative and Submit Hosts with IPMP 128

Glossary 129

Index 133

5


6/136



7/136

Preface

The N1 Grid Engine 6 Installation Guide describes the procedures for installing and

upgrading the N1 Grid Engine 6 software.

This version of the manual supports Grid Engine 6 Update 4.

Who Should Use This BookThis manual is for engineers and system administrators, who need to install the N1Grid Engine 6 software. Installation of the N1 Grid Engine 6 software should be doneby someone who is familiar with the administration of the platform on which the

software is installed.

Before You Read This BookWhile this book contains a complete glossary, if you are new to N1 Grid Engine 6software, you should familiarize yourself with the concepts that are discussed inChapter 1, Introduction to the N1 Grid Engine 6 Software, in N1 Grid Engine 6 UsersGuide.

7


8/136

How This Book Is OrganizedChapter 1 describes each of decisions you must make in the planning process, andhow to extract the installation files from CD-ROM.

Chapter 2 describes the procedure for installing the software manually.

Chapter 3 describes the files and commands necessary to automate your installations.

Chapter 4 describes the procedure for installing CSP-based encryption.

Chapter 5 describes the upgrade procedure.

Chapter 6 describes how you can ensure that the software is installed correctly.

Chapter 7 describes the procedure to remove the software from your systems.

Chapter 8 describes the procedure for installing the optional accounting and reportingmodule.

Chapter 9, explains the functions of the DBWriter in detail.

Appendix A, explains how to prepare a Windows system for installation of N1GE6 byinstalling Microsofts Services for UNIX.

Appendix B, describes some installation corner cases.

Glossary is a list of product-specific words and phrases and their definitions.

Related BooksOther books in the N1 Grid Engine 6 software documentation collection include:

I N1 Grid Engine 6 Users GuideI N1 Grid Engine 6 Administration GuideI N1 Grid Engine 6 Release Notes



9/136

Accessing Sun Documentation OnlineThe docs.sun.comSM Web site enables you to access Sun technical documentationonline. You can browse the docs.sun.com archive or search for a specific book title orsubject. The URL is http://docs.sun.com.

Ordering Sun Documentation

Sun Microsystems offers select product documentation in print. For a list ofdocuments and how to order them, see Buy printed documentation athttp://docs.sun.com.

Typographic ConventionsThe following table describes the typographic changes that are used in this book.

TABLE P1 Typographic Conventions

Typeface or Symbol Meaning Example

AaBbCc123 The names of commands, files, anddirectories, and onscreen computeroutput

Edit your .login file.

Use ls -a to list all files.

machine_name% you have

mail.

AaBbCc123 What you type, contrasted with onscreencomputer output

machine_name% su

Password:

AaBbCc123 Command-line placeholder: replace witha real name or value

To delete a file, type rmfilename.

AaBbCc123 Book titles, new terms, or terms to beemphasized

Read Chapter 6 in Users Guide.

These are called class options.

You must be root to do this.

9
http://docs.sun.com/http://docs.sun.com/http://docs.sun.com/http://docs.sun.com/http://docs.sun.com/http://docs.sun.com/


10/136

Shell Prompts in Command ExamplesThe following table shows the default system prompt and superuser prompt for the Cshell, Bourne shell, and Korn shell.

TABLE P2 Shell Prompts

Shell Prompt

C shell prompt machine_name%

C shell superuser prompt machine_name#

Bourne shell and Korn shell prompt $

Bourne shell and Korn shell superuser prompt #



11/136

CHAPTER 1

Before You Install the Software

This chapter describes the steps that need to be taken before you install the N1 Grid

Engine 6 software (grid engine software).

This chapter includes the following topics:

I Plan the Installation on page 11I Loading the Distribution Files On a Workstation on page 23

Plan the InstallationWhether you have installed previous versions of the grid engine software or this isyour first time, you will need to do some planning before you extract and install the

software. This section describes the decisions you must make, and, wherever possible,gives you criteria on which you can base your decisions.

Decisions That You Must MakeYou must make several decisions before you can plan the installation:

I Decide whether your system of networked computer hosts that run N1 GridEngine 6 software (grid engine system) is to be a single cluster or a collection ofsub-clusters, called cells. Cells allow you to install separate instances of the gridengine software but share the binary files across those instances.

I

Select the machines that are to be grid engine system hosts. Determine the hosttype of each machine: master host, shadow master host, administration host, submit host,execution host, or a combination.

I Ensure that all users of the grid engine system have the same user names on allsubmit and execution hosts.

11


12/136

Note Hosts running Windows as operating system cannot have the host type

master host or shadow master host.

I Decide how to order grid engine software directories. For example, you couldorganize directories as a complete tree on each workstation, or you couldcross-mount directories, or you could set up a partial directory tree on someworkstations. You must also decide where to locate each grid engine softwareinstallation directory, sge-root.

I Decide on the sites queue structure.

I Determine whether to define network services as an NIS file or as local to eachworkstation in /etc/services.

I Use the information in this chapter to gather the information necessary to complete

the installation worksheet.

Gather the Necessary InformationBefore you install the grid engine software, you must plan how to achieve the resultsthat fit your environment. This section helps you make the decisions that affect the restof the procedure. Write down your installation plan in a table similar to the followingexample.

Parameter Value

sge-root directory

Cell name

Administrative user

sge_qmaster port number

sge_execd port number

Master host

Shadow master hosts

Execution hosts

Administration hosts

Submit hosts

Group ID range for jobs



13/136

Parameter Value

Spooling mechanism (Berkeley DB or Classic

spooling)

Berkeley DB server host (the master oranother host)

Berkeley DB spooling directory on thedatabase server

Scheduler tuning profile (Normal, High, Max)

Installation method (interactive, secure,automated, or upgrade)

If you are going to install N1GE 6 on aWindows system, acquire and installMicrosoft Services For UNIX. See Appendix A

for more information.

If you are going to install N1GE 6 on aWindows system, create the required CSPcertificates before installing N1GE. See thesection called How to Install a CSP-securedSystem in Chapter 4 for information aboutCSP certificates.

Check the Other Installations Appendix forapplicability.

Disk Space Requirements

The grid engine software directory tree has the following fixed disk spacerequirements:

I 40 Mbytes for the installation files (including documentation) without any binaries

I Between 10 and 15 Mbytes for each set of binaries

The ideal disk space for grid engine system spool directories is as follows:

I 10-200 Mbytes for the master host spool directoriesI 10-200 Mbytes for the Berkeley DB spool directories

Note The spool directories of the master host and of the execution hosts areconfigurable and need not reside under the default location, sge-root.

Chapter 1 Before You Install the Software 13


14/136

Note You must satisfy several Windows-specific prerequisites before you can install

N1GE on hosts running Windows as operating system. It might be necessary to installadditional software on your computer which might require additional disk space. (SeeAppendix A).

sge-root Installation Directory

Create a directory into which you will load the contents of the distribution media. Thisdirectory is called the root directory, or sge-root. When the grid engine system isrunning, this directory stores the current cluster configuration and all other data thatmust be spooled to disk.

Note It is not a requirement that spool areas reside under sge-root. Actually thislocation may be avoided for efficiency reasons.

Use a valid path name for the directory that is network accessible on all hosts. Forexample, if the file system is mounted using automounter, set sge-root to /usr/N1GE6,not to /tmp_mnt/usr/N1GE6. Throughout this document, the sge-root variable isused to refer to the installation directory.

sge-root is the top level of the grid engine software directory tree. Each grid enginesystem component in a cell needs read access to the sge-root/cell/common directory, onstartup. When grid engine software is installed as a single cluster, the value of cell isdefault.

For ease of installation and administration, this directory should be readable on allhosts on which you intend to run the grid engine software installation procedure. Forexample, you can select a directory available across a network file system, such asNFS. If you choose to select file systems that are local to the hosts, you must copy theinstallation directory to each host before you start the installation procedure for theparticular machine. See File Access Permissions on page 16 for a description ofrequired permissions.

Directory Organization

When determining the directory organization, you must decide the following:

I The directory organization (for example, whether you will install a completesoftware tree on each workstation, directories cross-mounted, or a partial directorytree on some workstations, and so on)

I Where to locate each root directory, sge-root



15/136

Note Because changing the installation directory or the spool directories requires a

new installation of the system, use extra care to select a suitable installation directoryup front. Note that all important information from a previous installation can bepreserved.

By default, the installation procedure installs the grid engine software, manuals, spoolareas, and the configuration files in a directory hierarchy under the installationdirectory (see Figure 11). If you accept this default behavior, you should install orselect a directory with the access permissions that are described in File AccessPermissions on page 16.

You can select the spool areas to put in other locations during the primary installation.See Configuring Queues in N1 Grid Engine 6 Administration Guide for instructions.

FIGURE 11 Sample Directory Hierarchy



16/136

Cells

You can set up the grid engine system as a single cluster or as a collection of looselycoupled clusters called cells. The SGE_CELL environment variable indicates the clusterbeing referenced. When the grid engine system is installed as a single cluster,$SGE_CELL is not set, and the value default is assumed for the cell value.

User Names

In order for the grid engine system to verify that users submitting jobs havepermission to submit them on the desired execution hosts, users names must beidentical on the submit and execution hosts involved. You may therefore have tochange user names on some machines, because grid engine system users map directlyto system user accounts.

Note User names on the master host are not relevant for permission checking. Theseuser names do not have to match or even exist.

Installation Accounts

You can install the grid engine software either as the root user or as an unprivilegeduser (for example, your own user account). However, if you install the softwarelogged in as an unprivileged user, the installation allows only that user to run gridengine system jobs. Access is denied to all other accounts. Installing the softwarelogged in as the root account resolves this restriction. However, root permission isrequired for the complete installation procedure. Also, if you install as an unprivileged

user, you are not allowed to use the qrsh, qtcsh, qmake commands, nor can you runtightly integrated parallel jobs.

Note If you decide to install grid engine as an unprivileged user, you must set thesge_commd port number higher than or equal to 1024.

File Access Permissions

If you install the software logged in as root, you might have a problem con figuringroot read/write access for all hosts on a shared file system. Therefore, you might haveproblems putting sge-root onto a network-wide file system.

You can force grid engine software to run all grid engine system components througha non-root administrative user account (called sgeadmin, for example). With thissetup, you need only read/write access to the shared sge-root file system for thisparticular user.



17/136

The installation procedure asks whether files should be created and owned by anadministrative user account. If you answer Yes and provide a valid user name, filesare created by this user. Otherwise, the user name under which you run theinstallation procedure is used. It is recommended that you create an administrativeuser, and answer Yes to this question.

Make sure in all cases that the account used for file handling on all hosts hasread/write access to the sge-root directory. Also, the installation procedure assumesthat the host from which you access the grid engine software distribution media canwrite to the sge-root directory.

Note The name of the root user on Windows hosts depends on the system languageof the Windows operating system. It is even possible to change the name of the rootuser. The default name for many languages is the name Administrator.

Network Services

Determine whether your sites network services are defined in an NIS database or inan /etc/services file that is local to each workstation. If your site uses NIS, findout the host name of your NIS server is so that you can add entries to the NISservices map.

The grid engine system services are sge_execd and sge_qmaster. To add theservices to your NIS map, choose reserved, unused port numbers. The followingexamples show sge_qmaster and sge_execd entries.

sge_qmaster 536/tcp

sge_execd 537/tcp

Master Host

The master host controls the grid engine system. This host runs the master daemonsge_qmaster, and the scheduling daemon, sge_schedd.

The master host must comply with the following requirements:

I The host must be a stable platform.

I The host must not be excessively busy with other processing.

I At least 60 120 Mbytes of unused main memory must be available to run the gridengine system daemons. For very large clusters that include many hundreds or

thousands of hosts and tens of thousands of jobs in the system at any time, 1 GByteor more of unused main memory might be required and two CPUs might bebeneficial.

I The master host must be installed before shadow master execution, administration,or submit hosts.



18/136

I (Optional) The grid engine software directory, sge-root, should be installed locally,to cut down on network traffic.

Note Windows hosts cannot act as master hosts.

Shadow Master Hosts

These hosts back up the functionality of sge_qmaster in case the master host or themaster daemon fails. To be a shadow master host, a machine must have the followingcharacteristics:

I It must run sge_shadowd.

I It must share sge_qmaster status, job information, and queue configuration

information that is logged to disk. In particular, the shadow master hosts needread/write root or administration user access to the sge_qmaster spool directoryand to the sge-root/cell/common directory.

I The sge-root/cell/common/shadow_masters file must contain a line defining thehost as a shadow master host.

Note If no cell name is specified during installation, the value of cell is default.

The shadow master host facility is activated for a host as soon as these conditions aremet. You do not need to restart the grid engine system daemons to make a host into ashadow master host.


Spool Directories Under the Root Directory

During the installation of the master host, you must specify the location of a spoolingdirectory. This directory is used to spool jobs from execution hosts that do not have alocal spooling directory.

I On the master host, spool directories are maintained under qmaster-spool-dir. Thelocation of qmaster-spool-dir is defined during the master host installation process.

The default value of qmaster-spool-dir is sge-root/cell/spool/qmaster.I On each execution host, a spool directory called execd-spool-dir is defined during

the execution host installation processes. The default value of execd-spool-dir issge-root/cell/spool/exec-host. You will get better performance from executionhosts with local spooling directories than from execution hosts that have NFS



19/136

mounted the master hosts spooling directory.

Note If no cell name is specified during installation, the value of cell is default.

You do not need to export these directories to other machines. However, exporting theentire sge-root tree and making it write-accessible for the master host and all executablehosts makes administration easier.

Choosing Between Classic Spooling and DatabaseSpooling

During the installation, you are given the option to choose between classic spooling

and Berkeley DB spooling server. If you choose Berkeley DB spooling, you are thengiven the option to spool to a local directory or to a separate host, known as aBerkeley DB spooling server.

While classic spooling is an option, you should see better performance using aBerkeley DB spooling server. Part of this performance increase is because the masterhost can make non-blocking writes to the database, but has to make blocking writes tothe text file used by classic spooling. Other factors that may influence your decisionare file format and data integrity. There is a greater level of data integrity when youwrite to the Berkeley DB, rather than to a text file. However, a text file stores data in aformat that humans can read and edit. Normally, you do not need to read these files,but the spooling directory contains the messages from the system daemons, which canbe useful during debugging.

Database Server and Spooling Host

The master host can store its configuration and state to a Berkeley DB spoolingdatabase. The spooling database can be installed on the master server or on a separatehost. When the Berkeley DB spools into a local directory on the master host, theperformance is better, but if you want to set up a shadow master host, you need to usea separate Berkeley DB spooling server (host). In this case, you have to choose a hostwith a configured RPC service. The master host connects through RPC to the BerkeleyDB.

Note Using a shadow master host is more reliable, but using a separate Berkeley DB

spooling host results in a potential security hole. RPC communication as used by theBerkeley DB can be easily compromised. Only use this alternative if your site is secureand if users can be trusted to access the Berkeley DB spooling host by means ofTCP/IP communication.



20/136

If you choose to use Berkeley DB spooling without a shadow master, you don t needto set up a separate spooling server. Likewise, if you choose not to use Berkeley DBspooling, you can set up a shadow master host without setting up a separate spoolingserver.

Once you determine whether you need a separate spooling server, you will also needto determine the location for the spooling directory. The spooling directory must belocal to the spooling server. A default value for the location of the spooling directory isrecommended during installation but this default value is not suitable when the fileserver is different from the master host.

The requirements for the Berkeley DB spooling host are similar to the requirements forthe master host:

I The host must be a stable platform.

I The host must not be excessively busy with other processing.

I At least 60 120 Mbytes of unused main memory must be available to run the gridengine system daemons. For very large clusters that include many hundreds orthousands of hosts and tens of thousands of jobs in the system at any time, 1 GByteor more of unused main memory may be required and two CPUs may bebeneficial.

I (Optional) A separate spooling host must be installed before the master host.

I (Optional) The directory, sge-root, should be installed locally, to cut down onnetwork traffic.

Execution Hosts

Execution hosts run the jobs that users submit to the grid engine system. An executionhost must first be set up as an administration host. You run an installation script oneach execution host.

Group IDs

You need to provide a range of IDs that will be assigned dynamically for jobs. Therange must be big enough to provide enough numbers for the maximum number ofgrid engine system jobs running at a single moment on a single host.

A group ID is assigned to each grid engine system job to monitor the resourceutilization of the job. Each job will be assigned a unique ID during the time it isrunning. For example, a range of 20000-20100 allows 100 jobs to run concurrently on asingle host. You can change the group ID range for your cluster configuration at anytime, but the values in the UNIX group ID range must be unused on your system.



21/136

Administration Hosts

Operators and managers of the grid engine system use administration hosts toperform administrative tasks such as reconfiguring queues or adding grid enginesystem users.

The master host installation script automatically makes the master host anadministration host. During the master host installation process, you can add otheradministration hosts. You can also manually add administration hosts on the masterhost at any time after installation.

Submit Hosts

Jobs can be submitted and controlled from submit hosts. The master host installationscript automatically makes the master host a submit host.

Cluster Queues

The installation procedure creates a default cluster queue structure, which is suitablefor getting acquainted with the system. The default queue can be removed afterinstallation.

Note No matter what directory is used for the installation of the software, theadministrator can change most settings that were created by the installationprocedure. This change can be made while the system is running.

There are several factors you need to consider when determining a queue structure.

I Whether you need cluster queues for sequential, interactive, parallel, and other jobtypes

I Which queue instances to put on which execution hosts

I How many job slots are needed in each queue

For more detailed information on administering cluster queues, see ConfiguringQueues in N1 Grid Engine 6 Administration Guide.

Scheduler ProfilesYou can choose from three scheduler profiles during the installation process: normal,high, and max. You can use these predefined profiles as a starting point for gridengine tuning.



22/136

Using these profiles, you can optimize the scheduler for one or more of the following:

I The amount of information about a scheduling run

I The load adjustment during a scheduling runI Interval scheduling (the default) or immediate scheduling

You can choose from three scheduler profiles:

I normal This profile uses load adaptation, and interval scheduling, and reportsall the information that the scheduler gathers during the dispatch cycle. Thisprofile is the starting point for most grids. Use this profile if your highest priority isgathering and reporting information about a scheduling run.

I high This profile is more appropriate for a large cluster, where throughput ismore important than gathering and reporting all the information from thescheduler. This profile also uses interval scheduling. Use this profile if you want toget better performance at the cost of getting less information about yourscheduling runs.

I max This profile disables all information gathering and reporting, enablesimmediate scheduling, and disables load adaptation. Immediate scheduling is veryuseful for sites with high throughput and very short running jobs. The advantageof immediate scheduling decreases as run time of the jobs increases. This profilecan be used in clusters of any size where only throughput is important andeverything else is a lower priority.

For more information on how to configure scheduling, see Administering theScheduler in N1 Grid Engine 6 Administration Guide.

Installation Method

Several methods are available for installing the grid engine software:I InteractiveI Interactive, with increased securityI Automated, using the inst_sge script and a configuration fileI Upgrade

To decide which installation method you should use, consider the following factors.

I Do you already have the grid engine software installed and running?

If so, youll probably want to upgrade. The upgrade process is described inChapter 5.

If not, the master host installation is only done once, so the master host is typicallyinstalled interactively, as described in Chapter 2.

I Do you need to install just a few execution hosts?

If so, then you will probably want to install them interactively, as described inChapter 2.

I Do you need to install a large number of execution hosts?



23/136

If so, then you might want to perform automated installation, using the inst_sgescript and a configuration file. This process is described in Using the inst_sgeUtility and a Configuration Template on page 53.

I Do you require your grid to use encryption?

If so, you have to perform an interactive installation with increased security. Thisprocess is described in Chapter 4.

Check the Other Installation Issues Appendix

If you are installing N1GE on a Linux system or on a system with IPMP, see the OtherInstallation Issues appendix for some important information.

Loading the Distribution Files On aWorkstationGrid Engine is distributed on CD-ROM, and through electronic download. Forinformation on how to access CD-ROMs, ask your system administrator or refer toyour local system documentation. The CD-ROM distribution contains a directorynamed N1_Grid_Engine_6u4. The product distribution is in this directory, in bothtar.gz format and the pkgadd format. The pkgadd format is provided for theSolaris Operating System (Solaris OS). For all supported operating systems, thesoftware is distributed in tar.gz format.

M How to Load the Distribution Files On aWorkstationEnsure that the file systems and directories that are to contain the grid engine softwaredistribution and the spool and configuration files are set up properly by setting theaccess permissions as defined in File Access Permissions on page 16.

1. Provide access to the distribution media.

I If you downloaded the software, rather than getting it on CD-ROM, just

unzip the five files into a directory. This directory must be located on a filesystem that has at least 350 MBytes free space.

2. Log in to a system, preferably a system that has a direct connection to a fileserver.

Before YouBegin

Steps



24/136

3. Create the installation directory as described in sge-root Installation Directoryon page 14.

# mkdir /opt/n1ge6

In these instructions, the installation directory is abbreviated as sge-root.

4. Install the binaries for all binary architectures that are to be used by any of yourmaster, execution, and submit hosts in your grid engine system cluster.

I The pkgadd Method

The pkgadd format is provided for the Solaris Operating System. To facilitateremote installation, the pkgadd directories are also provided in zip files.

You can install the following packages:

I SUNWsgeec Architecture independent files

I SUNWsgeed Documentation

I SUNWsgee Solaris (SPARC platform) 32-bit binaries for Solaris 7, Solaris8, and Solaris 9 Operating Systems

I SUNWsgeex Solaris (SPARC platform) 64-bit binaries for Solaris 7, Solaris8, and Solaris 9 Operating Systems

I SUNWsgeei Solaris (x86 platform) binaries for Solaris 8 and Solaris 9Operating Systems

I SUNWsgeeax - Solaris (x64 platform) binaries for Solaris 10 OperatingSystem

I SUNWsgeea - Accounting and Reporting Console (ARCo) packages for theSolaris and Linux Operating systems.

As you type the following commands, you must be prepared to respond toscript questions about your base directory, sge-root and the administrative user.

The script requests the choices you made during the planning steps of thisinstallation. See Decisions That You Must Make on page 11.

At the command prompt, type the following commands, responding to thescript questions.

# cd cdrom_mount_point/N1_Grid_Engine_6u4# pkgadd -d ./Common/Packages/SUNWsgeec# pkgadd -d ./Docs/Packages/SUNWsgeed# pkgadd -d ./Solaris_sparc/Packages/SUNWsgee (This is optional; at least one

binary set is required)# pkgadd -d ./Solaris_sparc/Packages/SUNWsgeex (This is optional; at least one

binary set is required)# pkgadd -d ./Solaris_x86/Packages/SUNWsgeei (This is optional; at least one

binary set is required)# pkgadd -d ./Solaris_x64/Packages/SUNWsgeeax (This is optional; at least one

binary set is required)

I The tar Method

For all supported operating systems, the software is distributed in tar.gzformat.



25/136

The following table contains files that you will need to install, regardless ofwhat platform you are on.

File Description

Common/tar/n1ge-6_0u4-common.tar.gz Architecture independent files

Docs/tar/n1ge-6_0u4-doc.tar.gz Release notes, installation guide, userguide and administration guide

The tar files that contain platform-specific binaries use the naming conventionof n1ge-6_0u4-bin-architecture.tar.gz. The following table lists theplatform-specific binaries. You need to install the file for each platform that youneed to support. Note that each platform has its own directory underN1_Grid_Engine_6u4.

Platform-Specific File Platform

Solaris_sparc/tar/n1ge-6_0u4-bin-solaris.tar.gz Solaris (SPARC platform)32-bit binaries for Solaris7, Solaris 8, and Solaris 9Operating Systems

Solaris_sparc/tar/n1ge-6_0u4-bin-solaris-sparcv9.tar.gz Solaris (SPARC platform)64-bit binaries for Solaris7, Solaris 8, and Solaris 9Operating Systems

Solaris_x86/tar/n1ge-6_0u4-bin-solaris-i586.tar.gz Solaris (x86 platform)binaries for Solaris 8, and

Solaris 9 OperatingSystems

Solaris_x64/tar/n1ge-6_0u4-bin-solaris-x64.tar.gz Solaris (x64 platform)64-bit binaries for Solaris10

Gemm/tar/n1ge-6_0u4-gemm.tar.gz Grid Engine ManagementModule, to be installedwith SCS 2.2.1.

Windows/tar/n1ge-6_0u4-bin-win32-x86.tar.gz Microsoft Windows (x86platform 32-bit binariesfor Windows 2000, XPand Windows Server 2003

Linux24_i586/tar/n1ge-6_0u4-bin-linux24-i586.tar.gz Linux (x86 platform)binaries for the 2.4 kernel



26/136

Linux24_amd64/tar/n1ge-6_0u4-bin-linux24-amd64.tar.gz Linux (AMD platform)binaries for the 2.4 kernel

MacOSX/tar/n1ge-6_0u4-bin-darwin.tar.gz Apple Mac OS/X

HPUX11/tar/n1ge-6_0u4-bin-hp11.tar.gz Hewlitt Packard HP-UX11

Aix51/tar/n1ge-6_0u4-bin-irix65.tar.gz SGI Irix 6.5

Aix43/tar/n1ge-6_0u4-bin-aix51.tar.gz IBM AIX 5.1

Irix65/tar/n1ge-6_0u4-bin-aix43.tar.gz IBM AIX 4.3

Type the following commands at the command prompt. In the example, basediris the abbreviation for the full directory,cdrom_mount_point/N1_Grid_Engine_6u4.

% su# cd sge-root# gzip -dc basedir/Common/tar/n1ge-6_0u4-common.tar.gz | tar xvpf -# gzip -dc basedir/Docs/tar/n1ge-6_0u4-doc.tar.gz | tar xvpf -# gzip -dc basedir/Solaris_sparc/tar/n1ge-6_0u4-bin-solsparc32.tar.gz | tar xvpf -# gzip -dc basedir/Solaris_sparc/tar/n1ge-6_0u4-bin-solsparc64.tar.gz | tar xvpf -# SGE_ROOT=sge-root; export SGE_ROOT

# util/setfileperm.sh $SGE_ROOT



27/136

CHAPTER 2

Installing the Grid Engine SoftwareInteractively

This chapter discusses the steps that you must take to manually install the grid engine

software. Please note that this chapter does not cover the upgrade process or theinstallation of the Accounting and Reporting Module, ARCo. Those processes arecovered in subsequent chapters.

Note The instructions in this chapter assume that you are installing the software on acomputer running the Solaris Operating System. Any difference in functionalitycreated by other operating system architecture that grid engine software runs on isdocumented in files starting with the string arc_depend_ in the sge-root/docdirectory. The remainder of the file name indicates the operating system architecturesto which the comments in the files apply, as in the arc_depend_irix.asc file.

Also note that there are several prerequisites that you must satisfy for Windowssystems before you can install N1GE6 (see Appendix A).

This chapter discusses the following topics:

I Interactive Installation Overview on page 28I Performing an Installation on page 28

27


28/136

Interactive Installation Overview

Note The instructions in this section are for a fresh grid engine system only. Forinstructions on how to install a new system with additional security protection, seeChapter 4. For instructions on how to upgrade an existing installation of an earlierversion of grid engine software, see Chapter 5.

Full installation includes the following tasks:

I Running an installation script on the master host and on every execution host inthe grid engine system

I Registering information about administration hosts and submit hosts

Performing an InstallationThis section includes instructions for performing the following tasks:

I How to Install the Master Host on page 28I How to Install Execution Hosts on page 42I Registering Administration Hosts on page 47I

Registering Submit Hosts on page 48I How to Install the Berkeley DB Spooling Server on page 48

The following sections describe how to install all the components of the grid enginesystem, including the master, execution, administration, and submit hosts. If you needto install the system with enhanced security, see Chapter 4 before you continueinstallation.

M How to Install the Master HostThe master installation procedure creates the appropriate directory hierarchy requiredby sge_qmaster and sge_schedd. The procedure starts up the grid engine system

daemons, sge_qmaster and sge_schedd, on the master host. The master host isalso registered as a host with administrative and submit permission. The installationprocedure creates a default configuration for the system on which it is run. Theinstallation script queries the system for the type of operating system. The script thenmakes meaningful settings based on this information.



29/136

If, at any time during the installation, you think something went wrong, you can quitthe installation procedure and restart it.

If you have decided to use an administrative user, as described in User Nameson page 16, you should create that user now. This procedure assumes that you havealready extracted the grid engine software, as described in Loading the DistributionFiles On a Workstation on page 23.


1. Log in to the master host as root.

2. Ensure that you have set the $SGE_ROOT environment variable by typing:

# echo $SGE_ROOT

I If the $SGE_ROOT environment variable is not set, set it now, by typing:

# SGE_ROOT=sge-root; export SGE_ROOT

3. Change to the installation directory.

I If the directory where the installation files reside is visible from the masterhost, change directories (cd) to the installation directory sge-root, and thenproceed to Step 4.

I If the directory is not visible and cannot be made visible, do the following:

a. Create a local installation directory, sge-root, on the master host.

b. Copy the installation files to the local installation directory sge-root acrossthe network (for example, by using ftp or rcp).

c. Change directories (cd) to the local sge-root directory.

4. Type the install_qmaster command, adding the -csp flag if you areinstalling using the Certificate Security Protocol method described in Chapter 4.

This command starts the master host installation procedure. You are asked severalquestions, and you might be required to run some administrative actions.

% ./install_qmasterWelcome to the Grid Engine installation

---------------------------------------

Grid Engine qmaster host installation

-------------------------------------

Before you continue with the installation please read these hints:

Before YouBegin

Steps

Chapter 2 Installing the Grid Engine Software Interactively 29


30/136

- Your terminal window should have a size of at least

80x24 characters

- The INTR character is often bound to the key Ctrl-C.The term >Ctrl-C< is used during the installation if you

have the possibility to abort the installation

The qmaster installation procedure will take approximately 5-10 minutes.

Hit to continue >>

5. Choose an administrative account owner.

Choosing Grid Engine admin user account

---------------------------------------

You may install Grid Engine that all files are created with the user id of an

unprivileged user.

This will make it possible to install and run Grid Engine in directories

where user >root< has no permissions to create and write files and directories.

- Grid Engine still has to be started by user >rootroot< (y/n) [y] >> y

Choosing a Grid Engine admin user name

--------------------------------------

Please enter a valid user name >> sgeadmin

Installing Grid Engine as admin user >sgeadmin>

6. Verify the sge-root directory setting.

In the following example, the value of sge-root is /opt/n1ge6.

Checking $SGE_ROOT directory

----------------------------

The Grid Engine root directory is:

$SGE_ROOT = /opt/n1ge6

If this directory is not correct (e.g. it may contain an automounter

prefix) enter the correct path to this directory or hit

to use default [/opt/n1ge6] >>

Your $SGE_ROOT directory: /opt/n1ge6

Hit to continue >>



31/136

7. Set up the TCP/IP services for the grid engine software.

a. You will be notified if the TCP/IP services have not been configured.

Grid Engine TCP/IP service >sge_qmastersge_qmaster< available in your >/etc/services< file

or in your NIS/NIS+ database.

You may add this service now to your services database or choose a port number

It is recommended to add the service now. If you are using NIS/NIS+ you should

add the service at your NIS/NIS+ server and not to the local >/etc/services

b. Start a new terminal session or window to add the information/etc/services file or your NIS maps.

c. Add the correct ports to the /etc/services file or your NIS services map, asdescribed in Network Services on page 17.

The following example shows how you might edit your /etc/services file.

...

sge_qmaster 536/tcp

sge_execd 537/tcp

Note In this example, the entries for both sge_qmaster and sge_execd areadded to /etc/services. Subsequent steps in this example assume that bothentries have been made.

Save your changes.

d. Return to the window where the installation script is running.

Please add the service now or press to go to entering a port number >

Press . You will see the following output:

sge_qmaster 536

Service >sge_qmaster< is now available.

Hit to continue >>

Grid Engine TCP/IP service >sge_execd>

8. Enter the name of your cell.

The use of grid engine system cells is described in Cells on page 16.

Grid Engine cells

-----------------

Grid Engine supports multiple cells.

If you are not planning to run multiple Grid Engine clusters or if you dont

know yet what is a Grid Engine cell it is safe to keep the default cell name

default

If you want to install multiple cells you can enter a cell name now.

The environment variable

$SGE_CELL=

will be set for all further Grid Engine commands.

Enter cell name [default] >>

I If you have decided to use cells, then enter the cell name now.

I If you have decided not to use cells, then press to continue.

Using cell >default>

Press to continue.

9. Specify a spool directory.

For guidelines on disk space requirements for the spool directory, see Disk SpaceRequirements on page 13. For information on where spool directory is installed,see Spool Directories Under the Root Directory on page 18.

Grid Engine qmaster spool directory

-----------------------------------

The qmaster spool directory is the place where the qmaster daemon storesthe configuration and the state of the queuing system.

The admin user >sgeadmin< must have read/write access

to the qmaster spool directory.



33/136

If you will install shadow master hosts or if you want to be able to startthe qmaster daemon on other hosts (see the corresponding sectionin theGrid Engine Installation and Administration Manual for details) the account

on the shadow master hosts also needs read/write access to this directory.

The following directory

[/opt/n1ge6/default/spool/qmaster]

will be used as qmaster spool directory by default!

Do you want to select another qmaster spool directory (y/n) [n] >>

I If you want to accept the default spool directory, press to continue.

I If you do not want to accept the default spool directory, then answer y.

In the following example the /my/spool directory is specified as the master

host spool directory.Do you want to select another qmaster spool directory (y/n) [n] >> y

Please enter a qmaster spool directory now! >>/my/spool

10. The next question concerns Windows-based execution hosts. If you do not planto use Windows support answer no. If you want windows support answer yes.

If you answer yes, you will be asked some Windows-specific questions further onin the installation process. These questions will be marked as WINDOWS ONLY.

Windows Execution Host Support------------------------------

Are you going to install Windows Execution Hosts? (y/n) [n]

11. WINDOWS ONLY If you are going to use Windows Domain users, answer Yes.SSL certificates will be created before daemon startup. If you answer: No, nocertificates will be created. For Domain users, after the daemon startup, you willbe asked for the Windows Administrator name (specified later in thisinstallation process.)

Windows Domain User Access--------------------------

Do you want to use Windows Domain Users (answer: y)

or are you going to use local Windows Users (answer: n) (y/n) [y] >>

12. Verify or set the correct file permissions. If you used pkgadd or you know thatthe file permissions are correct, you should answer yes. Answering no will direct

the script to set the permissions for you as shown in the next step.Verifying and setting file permissions--------------------------------------

Did you install this version with >pkgadd< or did you already



34/136

verify and set the file permissions of your distribution (y/n) [y] >> y

13. WINDOWS ONLY Set the correct file permissions. If you specified that you

wanted Windows Execution Host support in the previous question, you shouldlet the script set the file permissions for you. You do this by answering no to thefollowing question.

Verifying and setting file permissions--------------------------------------

Did you install this version with >pkgadd< or did you alreadyverify and set the file permissions of your distribution (y/n) [y] >>

In some cases, e.g. the binaries are stored on a NTFS or other filesystem which provideadditional file permissions, the UNIX file permissions can be wrong. In this case we wo

advise to verfiy and to set the file permissions (enter: n) (y/n) [n] >>n

Verifying and setting file permissions

--------------------------------------

We may now verify and set the file permissions of your Grid Enginedistribution.

This may be useful since due to unpacking and copying of your distributionyour files may be unaccessible to other users.

We will set the permissions of directories and binaries to

755 - that means executable are accessible for the world

and for ordinary files to

644 - that means readable for the world

Do you want to verify and set your file permissions (y/n) [y] >> y

Verifying and setting file permissions and owner in >3rd_partybinckptexamplesinstall_execdinstall_qmastermpipvmqmonutilutilbincatmandocmaninst_sgebinlibutilbin>

14. Specify whether all of your grid engine system hosts are located in a single DNSdomain.

Select default Grid Engine hostname resolving method----------------------------------------------------

Are all hosts of your cluster in one DNS domain? If this isthe case the hostnames

>hostA< and >hostA.foo.comfoo.com>

I If all of your grid engine system hosts are located in a single DNS domain,then answer y.

Are all hosts of your cluster in a single DNS domain (y/n) [y] >> y

Ignoring domainname when comparing hostnames.

Hit to continue >>

I If all of your grid engine system hosts are not located in a single DNSdomain, then answer n.

Are all hosts of your cluster in a single DNS domain (y/n) [y] >> n

The domainname is not ignored when comparing hostnames.

Hit to continue >>

Default domain for hostnames----------------------------

Sometimes the primary hostname of machines returns the short hostnamewithout a domain suffix like >foo.com/etc/hosts< file oryour NIS configuration it is usually safe to define a default domainbecause it is only used if your execution hosts return the short hostnameas their primary name.

If your execution hosts reside in more than one domain, the default domainparameter must be set on all execution hosts individually.

Do you want to configure a default domain (y/n) [y] >>

Press to continue.



36/136

a. If you want to specify a default domain, then answer y.

In the following example, sun.com is specified as the default domain.

Do you want to configure a default domain (y/n) [y] >> y

Please enter your default domain >> sun.com

Using >sun.com< as default domain. Hit to continue >>

b. If you do not want to specify a default domain, then answer n.

In the following example, sun.com is specified as the default domain.

Do you want to configure a default domain (y/n) [y] >> n

15. Press to continue.

Making directories

------------------

creating directory: default/commoncreating directory: /opt/n1ge6/default/spool/qmastercreating directory: /opt/n1ge6/default/spool/qmaster/job_scripts

Hit to continue >>

16. Specify whether you want to use classic spooling or Berkeley DB.

For more information on how to determine the type of spooling mechanism youwant, please see Choosing Between Classic Spooling and Database Spoolingon page 19.

Setup spooling--------------Your SGE binaries are compiled to link the spooling libraries

during runtime (dynamically). So you can choose between Berkeley DBspooling and Classic spooling method.

Please choose a spooling method (berkeleydb|classic) [berkeleydb] >>

I If you want to specify Berkeley DB spooling, press to continue.


The Berkeley DB spooling method provides two configurations!

1) Local spooling:The Berkeley DB spools into a local directory on this host (qmaster host)This setup is faster, but you cant setup a shadow master host

2) Berkeley DB Spooling Server:If you want to setup a shadow master host, you need to use

Berkeley DB Spooling Server!In this case you have to choose a host with a configured RPC service.The qmaster host connects via RPC to the Berkeley DB. This setup is morefailsafe, but results in a clear potential security hole. RPC communication(as used by Berkeley DB) can be easily compromised. Please only use thisalternative if your site is secure or if you are not concerned about



37/136

security. Check the installation guide for further advice on how to achievefailsafety without compromising security.

Do you want to use a Berkeley DB Spooling Server? (y/n) [n] >>

I If you want to use a Berkeley DB spooling server, enter y.

Do you want to use a Berkeley DB Spooling Server? (y/n) [n] >> y

Berkeley DB Setup

-----------------Please, log in to your Berkeley DB spooling host and execute "inst_sge -db"Please do not continue, before the Berkeley DB installation with

"inst_sge -db" is completed, continue with

Note Do not press until you have completed the Berkeley DB

installation on the spooling server.

a. Start a new terminal session or window.

b. Log in to the spooling server.

c. Install the software, as described in How to Install the Berkeley DBSpooling Server on page 48.

d. After you have installed the software on the spooling server, return tothe master installation window, and press to continue.

e. Enter the name of the spooling server.

In the following example, vector is the host name of the spoolingserver.

Berkeley Database spooling parameters-------------------------------------

Please enter the name of your Berkeley DB Spooling Server! >> vector

f. Enter the name of the spooling directory.

In the following example, /opt/n1ge6/default/spooldb is thespooling directory.

Please enter the Database Directory now!

Default: [/opt/n1ge6/default/spooldb] >>

Dumping bootstrapping informationInitializing spooling database

Hit to continue >>



38/136

I If you do not want to use a Berkeley DB spooling server, enter n.

Do you want to use a Berkeley DB Spooling Server? (y/n) [n] >> n

Hit to continue >>


Please enter the Database Directory now, even if you want to spool locallyit is necessary to enter this Database Directory.

Default: [/opt/n1ge6/default/spool/spooldb] >>

Specify an alternate directory, or press to continue.

creating directory: /opt/n1ge6/default/spool/spooldbDumping bootstrapping informationInitializing spooling database

Hit to continue >>

I If you want to specify classic spooling, then enter classic.

Please choose a spooling method (berkeleydb|classic) [berkeleydb] >> classic

Dumping bootstrapping informationInitializing spooling database

Hit to continue >>

17. Enter a group ID range

For more information, see Group IDs on page 20.

Grid Engine group id range

--------------------------

When jobs are started under the control of Grid Engine an additional group idis set on platforms which do not support jobs. This is done to provide maximumcontrol for Grid Engine jobs.

This additional UNIX group id range must be unused group ids in your system.Each job will be assigned a unique id during the time it is running.Therefore you need to provide a range of ids which will be assigneddynamically for jobs.

The range must be big enough to provide enough numbers for the maximum numberof Grid Engine jobs running at a single moment on a single host. E.g. a rangelike >20000-20100< means, that Grid Engine will use the group ids from20000-20100 and provides a range for 100 Grid Engine jobs at the same time

on a single host.

You can change at any time the group id range in your cluster configuration.

Please enter a range >> 20000-20100



39/136

Using >20000-20100< as gid range. Hit to continue >>

18. Verify the spooling directory for the execution daemon.

For information on spooling, see Spool Directories Under the Root Directoryon page 18.

Grid Engine cluster configuration---------------------------------

Please give the basic configuration parameters of your Grid Engineinstallation:

The pathname of the spool directory of the execution hosts. User >sgeadmin>

19. Enter the email address of the user who should receive problem reports.

In this example, the user who will receive problem report is [email protected].

Grid Engine cluster configuration (continued)---------------------------------------------

The email address of the administrator to whom problem reports are sent.

Its is recommended to configure this parameter. You may use >[email protected]> [email protected]

20. WINDOWS-ONLY At this point, if you specified that you wanted Windowssupport, you are asked to create CSP certificates. You should read the sectioncalled How to Install a CSP-secured System in Chapter 4 for informationabout CSP certificates before you go on.

21. Verify the configuration parameters.

The following parameters for the cluster configuration were configured:

execd_spool_dir /opt/n1ge6/default/spooladministrator_mail [email protected]

Do you want to change the configuration parameters (y/n) [n] >> n

Creating local configuration----------------------------Creating >act_qmaster< file

Adding default complex attributes



40/136

Reading in complex attributes. Adding default parallel environments (PE)Reading in parallel environments:

PE "make". Adding SGE default usersetsReading in usersets:

Userset "deadlineusers".Userset "defaultdepartment".

Adding >sge_aliases< path aliases file Adding >qtask< qtcsh sample default request file Adding >sge_request< default submit options fileCreating >sgemaster< scriptCreating >sgeexecd< scriptCreating settings files for >.profile/.cshrc>

22. Specify whether you want the daemons to start when the system is booted.

qmaster/scheduler startup script--------------------------------

We can install the startup script that willstart qmaster/scheduler at machine boot (y/n) [y] >> y

Installing startup script /etc/rc2.d/S95sgemaster

Hit to continue >>

...

23. WINDOWS-ONLY Add the Windows Administrator name to the SGEmanager list.

Windows Administrator Name

--------------------------

For a later execution host installation it is recommended to add theWindows Administrator name to the SGE manager list

Please, enter the Windows Administrator name [Default: Administrator] >>

24. Identify the hosts that you will later install as execution hosts.

Adding Grid Engine hosts------------------------

Please now add the list of hosts, where you will later install your executiondaemons. These hosts will be also added as valid submit hosts.

Please enter a blank separated list of your execution hosts. You maypress if the line is getting too long. Once you are finishedsimply press without entering a name.

You also may prepare a file with the hostnames of the machines where you plan



41/136

to install Grid Engine. This may be convenient if you are installing GridEngine on many hosts.

Do you want to use a file which contains the list of hosts (y/n) [n] >> n

Adding admin and submit hosts-----------------------------

Please enter a blank seperated list of hosts.

Stop by entering . You may repeat this step until you areentering an empty list. You will see messages from Grid Enginewhen the hosts are added.

Host(s): host1 host2 host3 host4

host1 added to administrative host listhost1 added to submit host listhost2 added to administrative host listhost2 added to submit host listhost3 added to administrative host listhost3 added to submit host listhost4 added to administrative host listhost4 added to submit host listHit to continue >>

Creating the default queue and hostgroup-----------------------------------------------------------

root@vector added "@allhosts" to host group listroot@vector added "all.q" to cluster queue list

Hit to continue >>

25. Select a scheduler profile.For information on how to determine which profile you should use, see SchedulerProfiles on page 21.

Scheduler Tuning----------------

The details on the different options are described in the manual.

Configurations--------------1) Normal

Fixed interval scheduling, report scheduling information,actual + assumed load

2) High Fixed interval scheduling, report limited scheduling information,actual load

3) MaxScheduling on demand, report no scheduling information,



42/136

actual load

Enter the number of your prefered configuration and hit !

Default configuration is [1] >>

Once you answer this question, the installation process is complete. Several screensof information will be displayed before the script exits. The commands that arenoted in those screens are also documented in this chapter.

26. Create the environment variables for use with the grid engine software.

Note If no cell name was specified during installation, the value of cell isdefault.

I If you are using a C shell, type the following command:

% source sge-root/cell/common/settings.csh

I If you are using a Bourne shell or Korn shell, type the following command:

$ . sge-root/cell/common/settings.sh

For details on how you can verify that the execution host has been set up correctly, seeHow to Verify That the Daemons Are Running on the Master Host on page 83.

M How to Install Execution Hosts

The execution host installation procedure creates the appropriate directory hierarchyrequired by sge_execd, and starts the sge_execd daemon on the execution host.This section describes how to install execution hosts interactively from the commandline. You can automate the installation of execution of multiple hosts by using theprocedure described in Chapter 3.

Before installing an execution host, you first need to have installed the master serveras described in How to Install the Master Host on page 28.

You must satisfy several prerequisites before you can install N1GE execution hostswith Windows operating systems. It might be necessary to install additional softwareon your computer. (See Appendix A.)

If you use the Domain User Concept on your Microsoft Windows machines then notethat there are additional installation steps necessary before you can continue with theexecution host installation. Follow the steps described in the section "How to Install aCSP-Secured System" -Steps 6a, 6b and 6c.using N1 GE 6 in this environment, seeAppendix B.

See Also

Before YouBegin



43/136

Note If you use the Domain User Concept on your Microsoft Windows machines

then note that after installation, each user has to register their Windows passwordwith N1GE using the sgepasswd client application. (See Appendix B for moreinformation.)

1. Log in to the execution host as root.

2. As you did for the master installation, either copy the installation files to a localinstallation directory sge-root or use a network installation directory.


# echo $SGE_ROOT

I

If the $SGE_ROOT environment variable is not set, set it now, by typing:# SGE_ROOT=sge-root; export SGE_ROOT

4. Change directory (cd) to the installation directory, sge-root.

5. Verify that the execution host has been declared on the administration host.

# qconf -sh

I If you do not see the name of this execution host in the output of the qconfcommand, you will need to declare it as an administration host.

a. Start a new terminal session or window.

b. In that window, log into the master host.

c. Declare the execution host as an administration host, using the qconfcommand.

# qconf -ah quarkquark added to administrative host list

d. Log back out of the master host, and continue with the installation of theexecution host.

6. Run the install_execd command.

If you are installing using the Certificate Security Protocol method described inChapter 4, add the -csp option to the install_execd command.

% ./install_execd

This command starts the execution host installation procedure.

Welcome to the Grid Engine execution host installation------------------------------------------------------

Steps



44/136

If you havent installed the Grid Engine qmaster host yet, you must executethis step (with >install_qmaster>



Checking $SGE_ROOT directory----------------------------



If this directory is not correct (e.g. it may contain an automounterprefix) enter the correct path to this directory or hit to use default [/opt/n1ge6] >>


Hit to continue >>

8. Enter the name of your cell(s).


Grid Engine cells-----------------


If you are not planning to run multiple Grid Engine clusters or if you dontknow yet what is a Grid Engine cell it is safe to keep the default cell name

default





45/136

$SGE_CELL=



I If you have decided to use cells, then enter the cell names now.

I If you have decided not to use cells, then press to continue.

Using cell >default>

Press to continue.

9. The install script checks to see if the admin user already exists. If the admin useralready exists, the script continues uninterrupted. If the admin user does notexist, the script shows the following screen where you must supply asked for a

password for the admin user. After the admin user is created, press Enter tocontinue with the installation.

Local Admin User----------------

The local admin user sgeadmin, does not exist!The script tries to create the admin user.

Please enter a password for your admin user >>

Creating admin user sgeadmin, now ...

Admin user created, hit to continue!

10. Press to continue.

The script verifies that the execution host has been declared as an administrationhost.

Checking hostname resolving---------------------------

This hostname is known at qmaster as an administrative host.

Hit to continue >>

11. Specify whether you want to use a local spool directory.

For information on spooling, see Spool Directories Under the Root Directoryon page 18.

Local execd spool directory configuration

-----------------------------------------

During the qmaster installation youve already entered a globalexecd spool directory. This is used, if no local spool directory is configured.

Now you can enter a local spool directory for this host.



46/136

Do you want to configure a local spool directory

for this host (y/n) [n] >>

I If you do not want a local spool directory, answer n.

Do you want to configure a local spool directory

for this host (y/n) [n] >> n

Creating local configuration----------------------------sgeadmin@host1 modified "host1" in configuration list

Local configuration for host >host1< created.

Hit to continue >>

I If you do want a local spool directory, answer y.

In the following example, /var/tmp/spool is used as the local spool directoryon host1. Choose any directory that meets the disk space requirementsdescribed in Disk Space Requirements on page 13.

Do you want to configure a local spool directoryfor this host (y/n) [n] >> y

Please enter the local spool directory now! >> /var/tmp/spoolUsing local execd spool directory [/var/tmp/spool]

Hit to continue >>

Creating local configuration----------------------------sgeadmin@host1 modified "host1" in configuration list

Local configuration for host >host1n< created.

Hit to continue >>

12. Specify whether you want execd to start automatically at boot time.

You may not wish to install the startup script if you are installing a test cluster oryou decide youd rather start the daemon manually on reboot.

execd startup script--------------------

We can install the startup script that willstart execd at machine boot (y/n) [y] >> y

Installing startup script /etc/rc2.d/S95sgeexecd

Hit to continue >>

Grid Engine execution daemon startup------------------------------------

Starting execution daemon. Please wait ...



47/136

starting sge_execd

Hit to continue >>

13. Specify a queue for this host.

Adding a queue for this host----------------------------

We can now add a queue instance for this host:

- it is added to the >allhosts< hostgroup- the queue provides 1 slot(s) for jobs in all queues

referencing the >allhosts< hostgroup

You do not need to add this host now, but before running jobs on this hostit must be added to at least one queue.

Do you want to add a default queue instance for this host (y/n) [y] >>Once you answer this question, the installation process is complete. Several screensof information will be displayed before the script exits. The commands that arenoted in those screens are also documented in this chapter.


Note If no cell name was specified during installation, the value of cell isdefault.





For details on how you can verify that the execution host has been set up correctly, seeHow to Verify That the Daemons Are Running on the Execution Hosts on page 84.

Registering Administration HostsThe master host is implicitly allowed to run administrative tasks and to submit,monitor, and delete jobs. The master host does not require any kind of additionalinstallation as administration. By contrast, pure administration hosts do requireregistration.

See Also



48/136

Note You can also install execution hosts by using the QMON graphical user interface.

For information on how to complete this task using QMON, see ConfiguringAdministration Hosts With QMON in N1 Grid Engine 6 Administration Guide.

From the master host, using the grid engine system administrative account (forexample, the sgeadmin account), type the following command.

% qconf -ah admin_host_name[,...]

Registering Submit Hosts

Note You can also install execution hosts by using the QMON graphical user interface.For information on how to complete this task using QMON, see Configuring SubmitHosts With QMON in N1 Grid Engine 6 Administration Guide.

From the master host, using the grid engine system administrative account (forexample, the sgeadmin account), type the following command.

% qconf -as submit_host_name[,...]

Refer to About Hosts and Daemons in N1 Grid Engine 6 Administration Guide formore details and other means to configure the different host types.

M How to Install the Berkeley DB Spooling ServerThe installation procedure installs the grid engine software necessary for Berkeley DBspooling.

The grid engine software must be loaded onto a local file system. For details on howto extract the files, see How to Load the Distribution Files On a Workstationon page 23.

1. Log in to the spooling server host as root.


# echo $SGE_ROOT

I If the $SGE_ROOT environment variable is not set, set it now, by typing:

# SGE_ROOT=sge-root; export SGE_ROOT

Before YouBegin

Steps



49/136

3. Change to the installation directory.

# cd $SGE_ROOT

4. Type the inst_sge command with the -db option.

# sge-root/inst_sge -db

This command starts the spooling server installation procedure. You are askedseveral questions. If you think something went wrong, you can quit the installationprocedure and restart it at any time.

5. Choose an administrative account owner.

Choosing Grid Engine admin user account---------------------------------------

You may install Grid Engine that all files are created with the user id of anunprivileged user.

This will make it possible to install and run Grid Engine in directorieswhere user >root< has no permissions to create and write files and directories.

- Grid Engine still has to be started by user >rootroot< (y/n) [y] >> y

Choosing a Grid Engine admin user name--------------------------------------

Please enter a valid user name >> sgeadminInstalling Grid Engine as admin user >sgeadmin>



Checking $SGE_ROOT directory----------------------------



If this directory is not correct (e.g. it may contain an automounterprefix) enter the correct path to this directory or hit to use default [/opt/n1ge6] >>


Hit to continue >>

7. Enter the name of your cell.



50/136


Grid Engine cells

-----------------


If you are not planning to run multiple Grid Engine clusters or if you dontknow yet what is a Grid Engine cell it is safe to keep the default cell name

default



$SGE_CELL=



8. Select Berkeley DB spooling.

Setup spooling--------------Your SGE binaries are compiled to link the spooling librariesduring runtime (dynamically). So you can choose between Berkeley DBspooling and Classic spooling method.


9. Verify your host name.

In this example, the installation script is being run on host2.


You are going to install a RPC Client/Server machanism!In this case, qmaster willcontact a RPC server running on a separate server machine.If you want to use the SGE shadowd, you have to use theRPC Client/Server mechanism.

Enter database server name or

hit to use default [host2] >>

10. Enter the directory path of your spooling directory.

You may need to change this path if this directory is NFS mounted, or if you don t

have write permissions to this directory.Enter the database directoryor hit to use default [/opt/n1ge6/default//spooldb] >>

creating directory: /opt/n1ge6/default//spooldb



51/136

11. Start the RPC server.

Now we have to startup the rc script

>/opt/n1ge6/default/common/sgebdbNO> yStarting rpc server on host host2!The Berkeley DB has been started with these parameters:

Spooling Server Name: host2DB Spooling Directory: /opt/n1ge6/default//spooldb

Please remember these values, during Qmaster installation

you will be asked for! Hit to continue!

12. Specify whether you want Berkeley DB service to start automatically at boottime.

Berkeley DB startup script--------------------------

We can install the startup script that

Grid Engine is started at machine boot (y/n) [y] >> y

Once you answer this question, the installation process is complete.


Note If no cell name was specified during installation, the value of cell is

default.







52/136



53/136

CHAPTER 3

Automating the Installation Process

This chapter describes how the software installation process for grid engine software

can be automated. Currently, you may only perform this procedure as theadministrative user. If you attempt to use this procedure running as the root user, theprocedure will fail.

Using the inst_sge Utility and aConfiguration TemplateThe inst_sge utility is a general-purpose script that can be used on any host toinstall locally as a master, administration, execution, submit or shadow master host.

You can use this utility in interactive mode to supplant any of the commands thatwere described in Chapter 2. In addition, the inst_sge utility can be used incombination with a configuration file to automate system installation.

Note When the inst_sge utility is used in combination with a configuration file toautomate system installation, the user will receive no feedback from the system.However, a log file is created in th

n1 grid engine 6 installation guide

Documents