- Creat sgeadmin user
- Extract Sun Grid Engine software (binary code) into a network installation directory (i.e. /opt/sge62, with NFS mount)
- Enable tcp/ip services
sge_qmaster 6444/tcp
sge_execd 6445/tcp
sge_execd 6445/tcp
- Set $SGE_ROOT (i.e. export SGE_ROOT=/opt/sge62)
- chown -R sgeadmin $SGE_ROOT
Install Sun Grid Engine execution host (logon as root on linux64-client1):
cd $SGE_ROOT
$SGE_ROOT/install_execd
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 sucessfull installation you need a running Grid Engine qmaster. It is
also neccesary 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
The execution host installation will take approximately 5 minutes.
Hit <RETURN> to continue >>
Checking $SGE_ROOT directory
----------------------------
The Grid Engine root directory is:
$SGE_ROOT = /opt/SGE
If this directory is not correct (e.g. it may contain an automounter
prefix) enter the correct path to this directory or hit
Your $SGE_ROOT directory: /opt/SGE
Hit <RETURN> to continue >>
Grid Engine cells
-----------------
Please enter cell name which you used for the qmaster
installation or press to use [default] >>
Using cell: >default<
Hit <RETURN> to continue >>
Grid Engine TCP/IP communication service
----------------------------------------
The port for sge_execd is currently set as service.
sge_execd service set to port 6445
Hit <RETURN> to continue >>
Checking hostname resolving
---------------------------
This hostname is known at qmaster as an administrative host.
Hit <RETURN> to continue >>
Execd spool directory configuration
-----------------------------------
You defined a global spool directory when you installed the master host.
You can use that directory for spooling jobs from this execution host
or you can define a different spool directory for this execution host.
ATTENTION: For most operating systems, the spool directory does not have to
be located on a local disk. The spool directory can be located on a
network-accessible drive. However, using a local spool directory provides
better performance.
FOR WINDOWS USERS: On Windows systems, the spool directory MUST be located
on a local disk. If you install an execution daemon on a Windows system
without a local spool directory, the execution host is unusable.
The spool directory is currently set to:
<</opt/SGE/default/spool/linux64-client1>>
Do you want to configure a different spool directory
for this host (y/n) [n] >> n
Creating local configuration
----------------------------
sgeadmin@linux64-client1 added "linux64-client1" to configuration list
Local configuration for host >linux64-client1< created.
Hit <RETURN> to continue >>
execd startup script
--------------------
We can install the startup script that will
start execd at machine boot (y/n) [y] >> y
execd startup script
--------------------
We can install the startup script that will
start execd at machine boot (y/n) [y] >> y
cp /opt/SGE/default/common/sgeexecd /etc/init.d/sgeexecd.my_test
/usr/lib/lsb/install_initd /etc/init.d/sgeexecd.my_test
Hit <RETURN> to continue >>
Grid Engine execution daemon startup
------------------------------------
Starting execution daemon. Please wait ...
starting sge_execd
Hit <RETURN> to continue >>
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 4 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] >> y
root@linux64-client1 modified "@allhosts" in host group list
root@linux64-client1 modified "all.q" in cluster queue list
Hit <RETURN> to continue >>
Using Grid Engine
-----------------
You should now enter the command:
source /opt/SGE/default/common/settings.csh
if you are a csh/tcsh user or
# . /opt/SGE/default/common/settings.sh
if you are a sh/ksh user.
This will set or expand the following environment variables:
- $SGE_ROOT (always necessary)
- $SGE_CELL (if you are using a cell other than >default<)
- $SGE_CLUSTER_NAME (always necessary)
- $SGE_QMASTER_PORT (if you haven't added the service >sge_qmaster<)
- $SGE_EXECD_PORT (if you haven't added the service >sge_execd<)
- $PATH/$path (to find the Grid Engine binaries)
- $MANPATH (to access the manual pages)
Hit <RETURN> to see where Grid Engine logs messages >>
Grid Engine messages
--------------------
Grid Engine messages can be found at:
/tmp/qmaster_messages (during qmaster startup)
/tmp/execd_messages (during execution daemon startup)
After startup the daemons log their messages in their spool directories.
Qmaster: /opt/SGE/default/spool/qmaster/messages
Exec daemon: //messages
Grid Engine startup scripts
---------------------------
Grid Engine startup scripts can be found at:
/opt/SGE/default/common/sgemaster (qmaster)
/opt/SGE/default/common/sgeexecd (execd)
Do you want to see previous screen about using Grid Engine again (y/n) [n] >> n
Your execution daemon installation is now completed.
[root@linux64-client1 ~]# ln -s /opt/SGE/default/common/settings.sh /etc/profile.d/sge.sh
[root@linux64-client1 ~]# ln -s /opt/SGE/default/common/settings.csh /etc/profile.d/sge.csh
No comments:
Post a Comment