If you are using Microsoft Windows machines, after the installation, each user has to register their Windows password with N1 Grid Engine using the sgepasswd client application. (See Appendix B for more information.)
Log in to the execution host as root.
As you did for the master installation, either copy the installation files to a local installation directory sge-root or use a network installation directory.
If the $SGE_ROOT environment variable is not set, set it by typing:
# SGE_ROOT=sge-root; export SGE_ROOT
|
To confirm that you have set the $SGE_ROOT environment variable, type:
Change directory (cd) to the installation directory, sge-root.
Verify that the execution host has been declared on the administration host.
If you do not see the name of this execution host in the output of the qconf command, you will need to declare it as an administration host.
Start a new terminal session or window.
In that window, log into the master host.
Declare the execution host as an administration host, using the qconf command.
# qconf -ah quark
quark added to administrative host list
|
Log back out of the master host, and continue with the installation of the execution host.
Run the install_execd command.
If you are installing using the Certificate Security Protocol method described in Chapter 4, Installing the Increased Security Features, add the -csp option to the install_execd command.
This command starts the execution host installation procedure.
Welcome to the Grid Engine execution host installation
------------------------------------------------------
If you haven't installed the Grid Engine qmaster host yet, you must execute
this step (with >install_qmaster<) prior the execution host installation.
For a sucessful installation you need a running Grid Engine qmaster. It is
also neccessary that this host is an administrative host.
You can verify your current list of administrative hosts with
the command:
# qconf -sh
You can add an administrative host with the command:
# qconf -ah <hostname>
The execution host installation will take approximately 5 minutes.
Hit <RETURN> to continue >> |
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 <RETURN>
to use default [/opt/n1ge6] >>
Your $SGE_ROOT directory: /opt/n1ge6
Hit <RETURN> to continue >> |
Type the name of your cell.
The use of grid engine system cells is described in Cells.
Grid Engine cells
-----------------
Grid Engine supports multiple cells.
If you are not planning to run multiple Grid Engine clusters or if you don't
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=<your_cell_name>
will be set for all further Grid Engine commands.
Enter cell name [default] >> |
If you have decided to use cells, then type the cell names now.
If you have decided not to use cells, then press the Return key to continue.
Using cell >default<.
Hit <RETURN> to continue >> |
Press <RETURN> to continue.
The install script checks to see whether the admin user already exists.
If the admin user already exists, the script continues uninterrupted. If the admin user does not exist, the script shows the following screen where you must supply a password for the admin user. After the admin user is created, press the Return key to continue 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 <ENTER> to continue! |
Press the Return key to continue.
The script verifies that the execution host has been declared as an administration host.
Checking hostname resolving
---------------------------
This hostname is known at qmaster as an administrative host.
Hit <RETURN> to continue >> |
Specify whether you want to use a local spool directory.
For information on spooling, see Spool Directories Under the Root Directory.
Local execd spool directory configuration
-----------------------------------------
During the qmaster installation you've already entered a global
execd spool directory. This is used, if no local spool directory is configured.
Now you can configure a local spool directory for this host.
ATTENTION: The local spool directory doesn't have to be located on a local
drive. It is specific to the <local> host and can be located on network drives,
too. But for performance reasons, spooling to a local drive is recommended.
FOR WINDOWS USER: On Windows systems the local spool directory MUST be set
to a local harddisk directory.
Installing an execd without local spool directory makes the host unuseable.
Local spooling on local harddisk is mandatory for Windows systems.
Do you want to configure a local spool directory
for this host (y/n) [n] >> |
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 <RETURN> to continue >> |
If you do want a local spool directory, answer y.
In the following example, /var/tmp/spool is used as the local spool directory on host1. Choose any directory that meets the disk space requirements described in Disk Space Requirements.
Do you want to configure a local spool directory
for this host (y/n) [n] >> y
Please enter the local spool directory now! >> /var/tmp/spool
Using local execd spool directory [/var/tmp/spool]
Hit <RETURN> to continue >> |
Creating local configuration
----------------------------
sgeadmin@host1 modified "host1" in configuration list
Local configuration for host >host1n< created.
Hit <RETURN> to continue >> |
Specify whether you want execd to start automatically at boot time.
You might not want to install the startup script if you are installing a test cluster or you would rather start the daemon manually on reboot.
execd startup script
--------------------
We can install the startup script that will
start execd at machine boot (y/n) [y] >> y
Installing startup script /etc/rc2.d/S95sgeexecd
Hit <RETURN> to continue >> |
WINDOWS ONLY – Choose whether to display the GUI for Windows jobs.
An N1 Grid Engine Helper Service is included with the N1 Grid Engine 6.1 distribution. This service enables Windows jobs to display a GUI on the visible desktop of the execution host. The visible desktop is either the desktop of the user currently logged in on the execution host or the desktop of the next user who will log in. It is not the log in screen.
The Helper Service is a independent component loosely coupled with the execution daemon. The startup of the Helper Service is plugged in the Services dialog box in the Windows control panel. You can install only one Helper Service per host. There can be only one execution daemon installed per Helper Server.
The installation script asks during the installation of a execution host whether you want to see the GUI of Windows jobs.
SGE Windows Helper Service Installation
---------------------------------------
If you're going to run Windows job's using GUI support, you have
to install the Windows Helper Service
Do you want to install the Windows Helper Service? (y/n) [n] >> |
Start the execution daemon.
Grid Engine execution daemon startup
------------------------------------
Starting execution daemon. Please wait ...
starting sge_execd
Hit <RETURN> to continue >> |
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 host
it 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 screens of information will be displayed before the script exits. The commands that are noted in those screens are also documented in this chapter.
Create the environment variables for use with the grid engine software.
Note –
If no cell name was specified during installation, the value of cell is default.
If you are using a C shell, type the following command:
% source sge-root/cell/common/settings.csh
|
If you are using a Bourne shell or Korn shell, type the following command:
$ . sge-root/cell/common/settings.sh |
