Please enter JAVA_HOME or press enter [/usr/jdk/latest] >>
Please enter additional JVM arguments (optional, default is [-Xmx256m]) >> Using the following JMX MBean server settings.
libjvm_path >/usr/jdk/latest/jre/lib/amd64/server/libjvm.so< Additional JVM arguments >-Xmx256m<
Do you want to use these data (y/n) [y] >>
Hit <RETURN> to continue >>
Step 10
Creating local configuration ---
sgeadmin@shadow1 modified "shadow1" in configuration list Local configuration for host >shadow1< created.
Hit <RETURN> to continue >> Step 11
shadow startup script ---
Do you want to start shadowd automatically at machine boot?
NOTE: If you select "n" SMF will be not used at all! (y/n) [y] >> y
Hit <RETURN> to continue >>
Step 12
Starting sge_shadowd on host shadow1 Shadowhost installation completed!
How to Install Execution Hosts
The execution host installation procedure creates the appropriate directory hierarchy required by sge_execd, and starts the sge_execd daemon on the execution host. This section describes how to install execution hosts interactively from the command line. You can automate the installation of execution of multiple hosts by using the
procedure described in Automating the Installation Process. Before You Begin
Before installing an execution host, you first need to install the master server as described in How to Install the Master Host and share the common directory.
Caution: If you the fail to share the $SGE_ROOT/$SGE_CELL/common directory, you will not able to install execution hosts on nodes other than the qmaster host.
How to Install Execution Hosts
■ You might have to install additional software on your computer. See Microsoft Services for UNIX and Microsoft Subsystem for UNIX-based Applications. ■ See the steps described in How to Install a CSP-Secured System - Steps 6a, 6b and
6c.
■ After the installation, each user has to register their Windows password with Grid Engine using the sgepasswd client application. See User Management on Windows Hosts for more information.
Steps
1. Log in to the execution host as root.
2. As you did for the master installation, either copy the installation files to a local installation directorysge-rootor use a network installation directory.
3. If the $SGE_ROOT environment variable is not set, set it by typing: # SGE_ROOT=<path_to_install/unpacked_directory>; export SGE_ROOT To confirm that you have set the $SGE_ROOT environment variable, type: # echo $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. ■ If you do not see the name of this execution host in the output of the qconf
-sh 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.
6. Type the install_execd command, adding the -csp flag if you are installing using the Certificate Security Protocol method described in Installing the Increased Security Features. This command starts the execution host installation procedure. For a complete installation example, see Example Execution Host Installation. # ./inst_sge -x
Welcome to the Grid Engine execution host installation --- .
. .
The execution host installation will take approximately 5 minutes. Note: For Windows only, You must satisfy several prerequisites before you can install Grid Engine execution hosts with Windows operating systems.
How to Install Execution Hosts
Hit <RETURN> to continue >>
7. Verify the $SGE_ROOT directory setting. In the example shown in lines 27 through 41 of the Example Execution Host Installation, the value of $SGE_ROOT is
/scratch2/myusername/sge62.
8. Type the name of your cell or accept the default cell name. See lines 042 through 076 of the Example Execution Host Installation. The use of Grid Engine system cells is described in Cells.
■ 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.
9. The install script checks to see what ports have been defined for the execution daemon. See lines 077 through 085 of the Example Execution Host Installation. If no ports have been defined, you will be asked to define them.
10. 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.
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!
11. Verify the execution host has been declared as an administration host. See lines 086 through 092 of the Example Execution Host Installation.
12. Specify whether you want to use a local spool directory. See lines 093 through 122 of the Example Execution Host Installation. For information on spooling, see Spool Directories under the Root Directory.
■ If you do not want a local spool directory, answer n.
■ If you do want a local spool directory, answer y. In the example,
/tmp/dom/execs is used as the local spool directory on domain.com. Choose any directory that meets the disk space requirements described in Disk Space Requirements.
13. Specify whether you want execd to start automatically at boot time. See lines 123 through 131 of the Example Execution Host Installation. 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.
14. WINDOWS ONLY - Choose whether to display the GUI for Windows jobs. See lines 132 through 163 of the Example Execution Host Installation. A Grid Engine Helper Service is included with the Grid Engine 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