|
N1 패키지는 아래 사이트에서 다운로드 하면됨
http://www.sun.com/software/solaris/get.jsp
http://www.sun.com/software/gridware/
Part 4/4 of N1
Grid Engine 6 Update 8, English
에 리눅스용 패키지가 들어있다.
Part 2/4 of N1
Grid Engine 6 Update 8, English
Gemm 패키지가 들어있다.
install_qmaster
를 실행하고 모든 호스트들에게
/usr/N1/* 의 모든 파일을 복사해준다.
그런후에 install_execd
를 실행하여 실행 서버로 등록한다.
[root@모든서버들]# mkdir /usr/N1
[root@server n1ge6_0u8]# mkdir
/usr/N1/swc
[root@server n1ge6_0u8]# mkdir
/usr/N1/gemm
[root@모든서버들
n1ge6_0u8]# ls
gemm-2.2-169.mapp n1ge-6_0u8-bin-linux24-i586.tar.gz
n1ge-6_0u8-common.tar.gz swc-linux_2.2.3.tar.gz
gemm-2.2-169.tar n1ge-6_0u8-bin-linux24-x64.tar.gz
n1ge-6_0u8-doc.tar.gz n1ge-6_0u8-arco.tar.gz
[root@모든서버들 n1ge6_0u8]#
tar zxf n1ge-6_0u8-bin-linux24-i586.tar.gz -C
/usr/N1
[root@모든서버들 n1ge6_0u8]# tar zxf
n1ge-6_0u8-common.tar.gz -C /usr/N1
[root@모든서버들 n1ge6_0u8]# tar zxf
n1ge-6_0u8-doc.tar.gz -C /usr/N1
[root@server n1ge6_0u8]# tar zxf swc-linux_2.2.3.tar.gz -C /usr/N1/swc
[root@server n1ge6_0u8]# tar xf
gemm-2.2-169.tar -C /usr/N1/gemm
[root@모든서버들]#
ls
3rd_party/ catman/
doc/ gemm/
inst_sge* install_qmaster* man/ pvm/
swc/ utilbin/
bin/ ckpt/
examples/ include/ install_execd*
lib/
mpi/ qmon/ util/
[root@localhost
swc]# ls
SUNWjato-2.1.2-20040514.i386.rpm
SUNWmcosx-2.2.3-1.i386.rpm license.txt
SUNWmcon-2.2.3-1.i386.rpm
SUNWmctag-2.2.3-1.i386.rpm setup*
SUNWmconr-2.2.3-1.i386.rpm
SUNWtcatu-4.0.5-2.i386.rpm
sun-javahelp-2.0_01-fcs.i586.rpm
SUNWmcos-2.2.3-1.i386.rpm
j2sdk-1_4_2_06-linux-i586.rpm
[root@localhost
gemm]# ls
base-mgmt-grid-2.2-6.i386.pkg menu-config-gemm.xml
scripts/
base-mgmt-grid-2.2-6.noarch.rpm mgmtStation/
struts-config-gemm.xml
base-mgmt-grid-2.2-6.sparc.pkg module-config.xml
validation-gemm.xml
[root@모든서버들]# cat
/etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1
localhost.localdomain localhost
10.10.10.138
file001 ß
실행서버 & 쉐도우 서버
10.10.10.139
file002 ß
실행서버
10.10.10.11
server ß
마스터 서버 & 실행서버
10.10.10.50
spoolserver ß
스플링서버 (작업에 대한 데이터베이스
가지고 있는 서버)
The
requirements for the Berkeley DB spooling host are similar to the
requirements for
the master
host:
_ The host must be a stable platform.
_ The host must not be excessively busy with other processing.
_ At least 60 – 120 Mbytes of unused main
memory must be available to run the grid
engine 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 GByte
or more of
unused main memory may be required and two CPUs may be
beneficial.
_ (Optional) A separate spooling host must
be installed before the master host.
_ (Optional) The directory, sge-root, should be installed locally, to cut down on
network traffic.
[root@file001 ~]# uname -n
file001
[root@file002 ~]# uname -n
file002
[root@server ~]# uname -n
server
[root@spoolserver ~]# uname -n
spoolserver
[root@모든서버들]#
cd /usr/N1/
[root@모든 서버들]# vi /etc/services
#SGE
sge_qmaster 536/tcp
sge_execd
537/tcp
[root@모든서버들]# useradd -d /usr/N1 sgeadmin
[root@server
N1]# ls -ld /usr/N1
drwxr-xr-x 18 sgeadmin
sgeadmin 4096 Aug 3 13:20 /usr/N1
[root@server N1]# chown -R sgeadmin.sgeadmin /usr/N1
[root@server N1]# export
SGE_ROOT=/usr/N1
[root@server N1]# export SGE_CELL=hoho
Cells
You can set up the grid engine system as a single cluster or as a collection
of loosely
coupled clusters called cells. The SGE_CELL environment variable indicates
the cluster
being 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.
[root@server N1]# ./install_qmaster
Welcome to the Grid Engine installation
---------------------------------------
Grid Engine qmaster host installation
-------------------------------------
Before you continue with the installation please read these hints:
- 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 <RETURN> to continue >>
Grid Engine admin user account
------------------------------
The current directory
/usr/N1
is owned by user
sgeadmin
If user >root< does not have write permissions in this directory on
*all*
of the machines where Grid Engine will be installed (NFS partitions not
exported for user >root< with read/write permissions) it is recommended
to
install Grid Engine that all spool files will be created under the user id
of user >sgeadmin<.
IMPORTANT NOTE: The daemons still have to be started by user >root<.
Do you want to install Grid Engine as admin user
>sgeadmin< (y/n) [y] >> y
Installing Grid Engine as admin user >sgeadmin<
Hit <RETURN> to continue >>
Checking $SGE_ROOT directory
----------------------------
The Grid Engine root directory is:
$SGE_ROOT = /usr/N1
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 [/usr/N1] >>
Your $SGE_ROOT directory: /usr/N1
Hit <RETURN> to continue >>
Grid Engine TCP/IP service >sge_qmaster<
----------------------------------------
Using the service
sge_qmaster
for communication with Grid Engine.
Hit <RETURN> to continue >>
Grid Engine TCP/IP service >sge_execd<
--------------------------------------
Using the service
sge_execd
for communication with Grid Engine.
Hit <RETURN> to continue >>
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 [hoho]
>>
Using cell >hoho<.
Hit <RETURN> to continue >>
Grid Engine qmaster spool directory
-----------------------------------
The qmaster spool directory is the place where the qmaster daemon stores
the configuration and the state of the queuing system.
The admin user >sgeadmin< must have
read/write access
to the qmaster spool directory.
If you will install shadow master hosts or if you want to be able to start
the qmaster daemon on other hosts (see the
corresponding section in the
Grid 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
[/usr/N1/hoho/spool/qmaster]
will be used as qmaster spool directory by default!
Do you want to select another qmaster
spool directory (y/n) [n] >> n
Windows Execution Host Support
------------------------------
Are you going to install Windows Execution Hosts?
(y/n) [n] >> n
Verifying and setting file permissions
--------------------------------------
Did you install this version with >pkgadd< or
did you already
verify and set the file permissions of your
distribution (y/n) [y] >> n
Verifying and setting file permissions
--------------------------------------
We may now verify and set the file permissions of your Grid Engine
distribution.
This may be useful since due to unpacking and copying of your distribution
your 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_party<
Verifying and setting file permissions and owner in >bin<
Verifying and setting file permissions and owner in >ckpt<
Verifying and setting file permissions and owner in >examples<
Verifying and setting file permissions and owner in >inst_sge<
Verifying and setting file permissions and owner in >install_execd<
Verifying and setting file permissions and owner in >install_qmaster<
Verifying and setting file permissions and owner in >lib<
Verifying and setting file permissions and owner in >mpi<
Verifying and setting file permissions and owner in >pvm<
Verifying and setting file permissions and owner in >qmon<
Verifying and setting file permissions and owner in >util<
Verifying and setting file permissions and owner in >utilbin<
Verifying and setting file permissions and owner in >catman<
Verifying and setting file permissions and owner in >doc<
Verifying and setting file permissions and owner in >include<
Verifying and setting file permissions and owner in >man<
Your file permissions were set
Hit <RETURN> to continue >>
Select default Grid Engine hostname resolving method
----------------------------------------------------
Are all hosts of your cluster in one DNS domain? If this is
the case the hostnames
>hostA< and
>hostA.foo.com<
would be treated as equal, because the DNS domain name >foo.com<
is ignored when comparing hostnames.
Are all hosts of your cluster in a single DNS
domain (y/n) [y] >> y
Ignoring domainname when comparing hostnames.
Hit <RETURN> to continue >>
Making directories
------------------
creating directory: hoho
creating directory: hoho/common
creating directory: /usr/N1/hoho/spool/qmaster
creating directory: /usr/N1/hoho/spool/qmaster/job_scripts
Hit <RETURN> to continue >>
Setup spooling
--------------
Your SGE binaries are compiled to link the spooling libraries
during runtime (dynamically). So you can choose between Berkeley DB
spooling and Classic spooling method.
Please choose a spooling method (berkeleydb|classic) [berkeleydb]
>>
The Berkeley DB spooling method provides two configurations!
Local spooling:
The Berkeley DB spools into a local directory on this host (qmaster host)
This setup is faster, but you can't setup a shadow master host
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 more
failsafe, but results in a clear potential security hole. RPC communication
(as used by Berkeley DB) can be easily compromised. Please only use this
alternative if your site is secure or if you are not concerned about
security. Check the installation guide for further advice on how to achieve
failsafety without compromising security.
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 <RETURN>
@@@@@@ 이 화면이 나오면 스플링 서버를 위한 몇가지 추가 작업이 있다.
추후 쉐도우마스터 설정을 위해서 스플링
서버를 설정하는 것이다.
먼저 다른 터미널 창을 띄어서 스풀링 서버로 사용될 서버에 접속한다.
그런후 스풀링 서버에 아래의 작업을
수행한후 계속 진행한다.
]# ssh
spoolserver
[root@spoolserver ~]# cd n1ge6_0u8/
[root@spoolserver
n1ge6_0u8]# ls
gemm-2.2-169.mapp n1ge-6_0u8-bin-linux24-i586.tar.gz
n1ge-6_0u8-common.tar.gz swc-linux_2.2.3.tar.gz
gemm-2.2-169.tar n1ge-6_0u8-bin-linux24-x64.tar.gz
n1ge-6_0u8-doc.tar.gz
[root@spoolserver
n1ge6_0u8]# alias ls='ls -F --color=tty'
[root@spoolserver n1ge6_0u8]# tar zxf n1ge-6_0u8-bin-linux24-i586.tar.gz
-C /usr/N1
[root@spoolserver n1ge6_0u8]# tar zxf n1ge-6_0u8-common.tar.gz -C /usr/N1
[root@spoolserver n1ge6_0u8]# tar zxf n1ge-6_0u8-doc.tar.gz -C /usr/N1
[root@spoolserver
n1ge6_0u8]# vi /etc/services
#SGE
sge_qmaster 536/tcp
sge_execd 537/tcp
[root@spoolserver
n1ge6_0u8]# useradd -d /usr/N1 sgeadmin
[root@spoolserver n1ge6_0u8]# chown
-R sgeadmin.sgeadmin /usr/N1
[root@spoolserver
n1ge6_0u8]# export SGE_ROOT=/usr/N1
[root@spoolserver
n1ge6_0u8]# export SGE_CELL=hoho
[root@spoolserver
n1ge6_0u8]# cd $SGE_ROOT
[root@spoolserver N1]# pwd
/usr/N1
[root@spoolserver N1]# ./inst_sge -db
Grid Engine admin user account
------------------------------
The current directory
/usr/N1
is owned by user
sgeadmin
If user >root< does not have write permissions in this directory on
*all*
of the machines where Grid Engine will be installed (NFS partitions not
exported for user >root< with read/write permissions) it is recommended
to
install Grid Engine that all spool files will be created under the user id
of user >sgeadmin<.
IMPORTANT NOTE: The daemons still have to be started by user >root<.
Do you want to install Grid Engine as admin user
>sgeadmin< (y/n) [y] >> y
Installing Grid Engine as admin user >sgeadmin<
Hit <RETURN> to continue >>
Checking $SGE_ROOT directory
----------------------------
The Grid Engine root directory is:
$SGE_ROOT = /usr/N1
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 [/usr/N1] >>
Your $SGE_ROOT directory: /usr/N1
Hit <RETURN> to continue >>
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 [hoho]
>>
Using cell >hoho<.
Hit <RETURN> to continue >>
creating directory: hoho
creating directory: hoho/common
Setup spooling
--------------
Select default Grid Engine hostname resolving method
----------------------------------------------------
Are all hosts of your cluster in one DNS domain? If this is
the case the hostnames
>hostA< and
>hostA.foo.com<
would be treated as equal, because the DNS domain name >foo.com<
is ignored when comparing hostnames.
Are all hosts of your cluster in a single DNS
domain (y/n) [y] >> y
Ignoring domainname when comparing hostnames.
Hit <RETURN> to continue >>
Berkeley Database spooling parameters
-------------------------------------
You are going to install a RPC Client/Server machanism!
In this case, qmaster will
contact a RPC server running on a separate server machine.
If you want to use the SGE shadowd, you have to use
the
RPC Client/Server mechanism.
Enter database server name or
hit <RETURN> to use default [spoolserver] >>
Enter the database directory
or hit <RETURN> to use default [/usr/N1/hoho/spooldb] >>
creating directory: /usr/N1/hoho/spooldb
Now we have to startup the rc script
>/usr/N1/hoho/common/sgebdb<
on the RPC server machine
If you already have a configured Berkeley DB Spooling Server,
you have to restart the Database with the rc script
now and continue with >NO<
Shall the installation script try to start the
RPC server? (y/n) [y] >>y
Starting rpc server on host spoolserver!
The Berkeley DB has been started with these parameters:
Spooling Server Name: spoolserver
DB Spooling Directory: /usr/N1/hoho/spooldb
Please remember these values, during Qmaster
installation
you will be asked for! Hit <RETURN> to continue!
The Berkeley DB installation is completed now!
berkeleydb startup script
-------------------------
We can install the startup script that will
start berkeleydb at
machine boot (y/n) [y] >> y
cp /usr/N1/hoho/common/sgebdb /etc/init.d/sgebdb
/usr/lib/lsb/install_initd /etc/init.d/sgebdb
Hit <RETURN> to continue >>
If you are using a Berkely DB Server, please add
the bdb_checkpoint.sh
script to your crontab. This script is used for
transaction
checkpointing and cleanup in SGE installations with
a
Berkeley DB RPC Server. You will find this script in:
/usr/N1/util/
It must be added to the crontab of the user (sgeadmin), who runs the
berkeley_db_svc on the server host.
e.g. * * * * * <full path to scripts> <sge-root
dir> <sge-cell> <bdb-dir>
@ 확인
[root@spoolserver N1]# crontab
-e
* * * * * sgeadmin /usr/N1/util/bdb_checkpoint.sh
/usr/N1 hoho /usr/N1/hoho/spooldb
[root@spoolserver
cron.d]# cat /var/spool/cron/root
* * * * * sgeadmin /usr/N1/util/bdb_checkpoint.sh
/usr/N1 hoho /usr/N1/hoho/spooldb
[root@spoolserver
N1]# ps axf | grep berkeley
12970 pts/2 S+ 0:00
\_ grep berkeley
12907 pts/2 S 0:00
/usr/N1/utilbin/lx24-x86/berkeley_db_svc -L /usr/N1/hoho/spooldb/bdb_messages
-h /usr/N1/hoho spooldb
[root@spoolserver
N1]# rpcinfo -p
프로그램 버전 원형 포트
100000 2 tcp
111 portmapper
100000 2 udp
111 portmapper
351457 4002 tcp
32777
[root@spoolserver
N1]# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local
Address
Foreign
Address
State PID/Program name
tcp
0 0
0.0.0.0:32777
0.0.0.0:*
LISTEN 12907/berkeley_db_s
tcp
0 0
0.0.0.0:111
0.0.0.0:*
LISTEN 4812/portmap
[root@spoolserver N1]# vi /etc/exports
[root@spoolserver hoho]# cat
/etc/exports
/usr/N1/hoho/spooldb *(rw,no_root_squash)
[root@spoolserver N1]# /etc/init.d/nfs
restart
NFS mountd를 종료 중입니다:
[실패]
NFS 데몬을 종료 중입니다:
[실패]
NFS quota를 종료 중입니다:
[실패]
NFS 서비스를 종료 중입니다:
[ 확인 ]
NFS 서비스를 시작하고 있습니다:
[ 확인 ]
NFS 쿼터를 시작하고 있습니다:
[ 확인 ]
NFS 데몬을 시작함:
[ 확인 ]
NFS mountd를 시작하고 있습니다:
[ 확인 ]
[root@spoolserver
N1]# exportfs
/usr/N1/hoho/spooldb
<world>
@@@@@@ 여기까지 spoolserver 에서의 설정이다.
이제는 spoolserver
설정때문에 잠시 멈춘 설치하고 있는 서버로 넘어간후 rpc 통신을 위한(버클리db 는 rpc 통신을
한다. 역시 썬에서 만든 티가 난다. ㅋㅋ) portmap 데몬을 구동한후 계속 설치한다.
[root@server
~]# /etc/init.d/portmap start
[root@server ~]# rpcinfo
-p
program vers proto port
100000 2
tcp 111 portmapper
100000 2
udp 111 portmapper
아래 화면에서 멈춰있을 것이다.
------------------------------------------------------------------------------------
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 <RETURN>
------------------------------------------------------------------------------------
엔터 키를 눌러 다음 설치로 넘어간다.
Berkeley Database spooling parameters
-------------------------------------
Please enter the name of your Berkeley DB Spooling Server! >> spoolserver
Please enter the Database Directory now!
Default: [/usr/N1/hoho/spooldb] >>
Dumping bootstrapping information
Initializing spooling database
Hit <RETURN> to continue >>
Grid Engine group id range
--------------------------
When jobs are started under the control of Grid Engine an additional group id
is set on platforms which do not support jobs. This is done to provide
maximum
control for Grid Engine jobs.
This additional UNIX group id range must be unused group id's
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 id's which will be assigned
dynamically for jobs.
The range must be big enough to provide enough numbers for the maximum number
of Grid Engine jobs running at a single moment on a single host. E.g. a range
like >20000-20100< means, that Grid Engine will use the group ids from
20000-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-20200
Using >20000-20200< as gid range. Hit
<RETURN> to continue >>
Grid Engine cluster configuration
---------------------------------
Please give the basic configuration parameters of your Grid Engine
installation:
<execd_spool_dir>
The pathname of the spool directory of the execution hosts. User >sgeadmin<
must have the right to create this directory and to write into it.
Default: [/usr/N1/hoho/spool] >>
Grid Engine cluster configuration (continued)
---------------------------------------------
<administrator_mail>
The email address of the administrator to whom problem reports are sent.
It's is recommended to configure this parameter. You may use >none<
if you do not wish to receive administrator mail.
Please enter an email address in the form >user@foo.com<.
Default: [none] >>
The following parameters for the cluster configuration were configured:
execd_spool_dir
/usr/N1/hoho/spool
administrator_mail
none
Do you want to change the configuration
parameters (y/n) [n] >> n
Creating local configuration
----------------------------
Creating >act_qmaster< file
Adding default complex attributes
Reading in
complex attributes.
Adding default parallel environments (PE)
Reading in
parallel environments:
PE "make".
Adding SGE default usersets
Reading 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
file
Creating >sgemaster< script
Creating >sgeexecd< script
Creating settings files for >.profile/.cshrc<
Hit <RETURN> to continue >>
qmaster/scheduler startup script
--------------------------------
We can install the startup script that will
start qmaster/scheduler
at machine boot (y/n) [y] >> y
cp /usr/N1/hoho/common/sgemaster /etc/init.d/sgemaster
/usr/lib/lsb/install_initd /etc/init.d/sgemaster
Hit <RETURN> to continue >>
Grid Engine qmaster and scheduler startup
-----------------------------------------
Starting qmaster and scheduler daemon. Please wait
...
starting sge_qmaster
starting sge_schedd
Hit <RETURN> to continue >>
Adding Grid Engine hosts
------------------------
Please now add the list of hosts, where you will later install your execution
daemons. These hosts will be also added as valid submit hosts.
Please enter a blank separated list of your execution hosts. You may
press <RETURN> if the line is getting too long. Once you are finished
simply press <RETURN> without entering a name.
You also may prepare a file with the hostnames of the machines where you plan
to install Grid Engine. This may be convenient if you are installing Grid
Engine 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 <RETURN>. You may repeat this step until you are
entering an empty list. You will see messages from Grid Engine
when the hosts are added.
Host(s): file001 file002 server
file001 added to administrative host list
file001 added to submit host list
file002 added to administrative host list
file002 added to submit host list
adminhost "server" already exists
server added to submit host list
Hit <RETURN> to continue >>
Adding admin and submit hosts
-----------------------------
Please enter a blank seperated list of hosts.
Stop by entering <RETURN>. You may repeat this step until you are
entering an empty list. You will see messages from Grid Engine
when the hosts are added.
Host(s):
Finished adding hosts. Hit <RETURN> to continue >>
If you want to use a shadow host, it is recommended to add this host
to the list of administrative hosts.
If you are not sure, it is also possible to add or remove hosts after the
installation with <qconf -ah hostname> for
adding and <qconf -dh hostname>
for removing this host
Attention: This is not the shadow host installationprocedure.
You still have to install the shadow host separately
Do you want to add your shadow host(s) now? (y/n)
[y] >> y
Adding Grid Engine shadow hosts
-------------------------------
Please now add the list of hosts, where you will later install your shadow
daemon.
Please enter a blank separated list of your execution hosts. You may
press <RETURN> if the line is getting too long. Once you are finished
simply press <RETURN> without entering a name.
You also may prepare a file with the hostnames of the machines where you plan
to install Grid Engine. This may be convenient if you are installing Grid
Engine on many hosts.
Do you want to use a file which contains the list
of hosts (y/n) [n] >> n
Adding admin hosts
------------------
Please enter a blank seperated list of hosts.
Stop by entering <RETURN>. You may repeat this step until you are
entering an empty list. You will see messages from Grid Engine
when the hosts are added.
Host(s): file001
adminhost "file001" already exists
Hit <RETURN> to continue >>
Adding admin hosts
------------------
Please enter a blank seperated list of hosts.
Stop by entering <RETURN>. You may repeat this step until you are
entering an empty list. You will see messages from Grid Engine
when the hosts are added.
Host(s):
Finished adding hosts. Hit <RETURN> to continue >>
Creating the default <all.q> queue and <allhosts> hostgroup
-----------------------------------------------------------
root@server added "@allhosts"
to host group list
root@server added "all.q"
to cluster queue list
Hit <RETURN> to continue >>
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) Max
Immediate Scheduling,
report no scheduling information,
actual load
Enter the number of your prefered configuration and
hit <RETURN>!
Default configuration is [1] >>
We're configuring the scheduler with >Normal< settings!
Do you agree? (y/n) [y] >> y
changed scheduler configuration
Using Grid Engine
-----------------
You should now enter the command:
source /usr/N1/hoho/common/settings.csh
if you are a csh/tcsh user or
# . /usr/N1/hoho/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_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: /usr/N1/hoho/spool/qmaster/messages
Exec daemon: <execd_spool_dir>/<hostname>/messages
Grid Engine startup scripts
---------------------------
Grid Engine startup scripts can be found at:
/usr/N1/hoho/common/sgemaster (qmaster
and scheduler)
/usr/N1/hoho/common/sgeexecd (execd)
Do you want to see previous screen about using Grid Engine again (y/n) [n]
>>
Your Grid Engine qmaster installation is now
completed
------------------------------------------------------
Please now login to all hosts where you want to run an execution daemon
and start the execution host installation procedure.
If you want to run an execution daemon on this host, please do not forget
to make the execution host installation in this host as well.
All execution hosts must be administrative hosts during the installation.
All hosts which you added to the list of administrative hosts during this
installation procedure can now be installed.
You may verify your administrative hosts with the command
# qconf -sh
and you may add new administrative hosts with the command
# qconf -ah <hostname>
Please hit <RETURN> >>
sge_qmaster successfully installed!
[root@server N1]# scp -r /usr/N1/ file001:/usr
[root@server N1]# scp -r
/usr/N1/ file002:/usr
[root@server N1]# scp -r /usr/N1/hoho/common/*
spoolserver:/usr/N1/hoho/common
@ 확인
@ 마스터 서버 설정 확인
[root@server N1]# ps axf
15037 ?
Ss 0:00
portmap
15816 ? Sl 0:00 /usr/N1/bin/lx24-x86/sge_qmaster
15836 ? Sl 0:00 /usr/N1/bin/lx24-x86/sge_schedd
[root@server
N1]# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local
Address
Foreign
Address
State PID/Program name
tcp
0 0
0.0.0.0:111
0.0.0.0:*
LISTEN
15037/portmap
tcp
0 0
0.0.0.0:536
0.0.0.0:*
LISTEN 15816/sge_qmaster
[root@server N1]#
rpcinfo -p
program vers proto port
100000 2
tcp 111 portmapper
100000 2
udp 111 portmapper
@ 스풀링 서버 설정 확인
[root@spoolserver common]# ps axf |grep berkeley
15717 pts/2 S+ 0:00
\_ grep berkeley
12907 pts/2 S 0:00
/usr/N1/utilbin/lx24-x86/berkeley_db_svc -L /usr/N1/hoho/spooldb/bdb_messages
-h /usr/N1/hoho spooldb
[root@spoolserver
common]# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local
Address
Foreign
Address
State PID/Program name
tcp
0 0 0.0.0.0:32777
0.0.0.0:*
LISTEN 12907/berkeley_db_s
tcp
0 0
0.0.0.0:111
0.0.0.0:*
LISTEN 4812/portmap
[root@spoolserver
common]# rpcinfo -p
프로그램 버전 원형 포트
100000 2 tcp
111 portmapper
100000 2 udp
111 portmapper
351457 4002 tcp
32777
@@ 추가 작업
1. act_qmaster 파일에는 qmaster (마스터 서버) 호스트 네임이 등록되어
있다.
이것은 sge_qmaster 데몬이
뜰수 있는 곳의 서버를 지정하는 곳이다.
위에서 server 로 지정하였으므로 server 라는 호스트 명이 들어가 있을것이다.
또한 이 파일을 참조하여 실행데몬들이 마스터에 접속한다.
마스터서버가 갑자기 죽는다면 쉐도우 마스터가 마스터 서버의 작업 내용들을 이어 받아야 하므로
쉐도우
서버는 이 파일을 자신의 호스트 네임으로 수정하고 sge_qmaster,
sge_shced 데몬을 띄운다.
그러면 실행노드들의 파일도 변경이 되어 쉐도우 서버로 접속을 해야하지만 실행노드들의 파일은 수동으로 고쳐줘야한다.
그러므로 /usr/N1/hoho/common 디렉토리를 공유하여 사용한다. 스풀링 서버 디렉토리
공유하는 식으로..
여기서는 스풀링 서버의 common 디렉토리를 공유하여 사용하면 되겠다.
2. /usr/N1/hoho/spooldb 디렉토리는 작업에 대한 정보 데이터베이스 파일들이 들어있다. 쉐도우 서버로 사용할 서버들 및 마스터 서버에서는 이 디렉토리를
공유해야한다.
위에서 스플링서버 설정할때 /usr/N1/hoho/spooldb 디렉토리를 공유했다.
마스터 서버 및 쉐도우서버들은 #] mount
-t nfs spoolserver:/usr/N1/hoho/spooldb
/usr/N1/hoho/spooldb 를 사용하여 로컬로 nfs 마운트
하여야한다.
3. 라이브러리 등록
설치 스크립트 마지막부분에 source
/usr/N1/hoho/common/settings.csh 이렇게 하라고 되어 있지만 잘안된다
아래 처럼
등록해준다.
모든 서버]# ]# cat /etc/ld.so.conf
/usr/N1/lib/lx24-x86
[root@server
common]# ls -l
total 56
-rw-r--r-- 1 sgeadmin
sgeadmin
8 Aug 4 12:05
act_qmaster
-r--r--r-- 1 sgeadmin sgeadmin 338 Aug 3 18:44 bootstrap
-rw-r--r-- 1 sgeadmin
sgeadmin 748
Aug 3 18:44
qtask
-rw-r--r-- 1 sgeadmin
sgeadmin 725
Aug 3 18:44
settings.csh
-rw-r--r-- 1 sgeadmin
sgeadmin 676
Aug 3 18:44
settings.sh
-rw-r--r-- 1 sgeadmin
sgeadmin 356
Aug 3 18:44
sge_aliases
-rw-r--r-- 1 sgeadmin
sgeadmin 918
Aug 3 18:44
sge_request
-rwxr-xr-x 1 sgeadmin
sgeadmin 7219 Aug 3 18:44 sgeexecd
-rwxr-xr-x 1 sgeadmin
sgeadmin 14160 Aug 3 18:44 sgemaster
[root@server common]# cat act_qmaster
server
[root@server common]# scp *
spoolserver:/usr/N1/hoho/common
root@spoolserver's password:
accounting
100% 33KB 32.9KB/s 00:00
act_qmaster
100% 7 0.0KB/s 00:00
bootstrap 100%
338 0.3KB/s 00:00
qtask 100%
748 0.7KB/s 00:00
settings.csh 100%
725 0.7KB/s 00:00
settings.sh 100%
676 0.7KB/s 00:00
sge_aliases 100%
356 0.4KB/s 00:00
sge_request 100%
918 0.9KB/s 00:00
sgeexecd 100%
7219 7.1KB/s 00:00
sgemaster 100%
14KB 13.8KB/s 00:00
[root@spoolserver common]# pwd
/usr/N1/hoho/common
[root@spoolserver common]# ls
-l
합계 96
-rw-r--r-- 1
root root 33732 8월 4 12:06
accounting
-rw-r--r-- 1 root
root 7 8월 4 12:06
act_qmaster
-r--r--r-- 1 root
root 338 8월
4 12:06
bootstrap
-rw-r--r-- 1 root
root 748 8월
4 12:06 qtask
-rw-r--r-- 1 root
root 725 8월
4 12:06 settings.csh
-rw-r--r-- 1 root
root 676 8월
4 12:06 settings.sh
-rw-r--r-- 1 root
root 356 8월
4 12:06 sge_aliases
-rw-r--r-- 1 root
root 918 8월
4 12:06 sge_request
-rwxr-xr-x 1 sgeadmin
sgeadmin 6197 8월 3 18:21
sgebdb
-rwxr-xr-x 1 root
root 7219 8월
4 12:06 sgeexecd
-rwxr-xr-x 1 root
root 14160 8월 4 12:06 sgemaster
[root@spoolserver common]# chown sgeadmin. *
[root@spoolserver
common]# vi /etc/exports
[root@spoolserver common]# cat /etc/exports
/usr/N1/hoho/spooldb *(rw,no_root_squash)
/usr/N1/hoho/common *(rw,no_root_squash)
[root@spoolserver
common]# /etc/init.d/nfs restart
NFS mountd를 종료 중입니다:
[ 확인
]
NFS 데몬을 종료 중입니다:
[ 확인 ]
NFS quota를 종료 중입니다:
[ 확인 ]
NFS 서비스를 종료 중입니다:
[ 확인 ]
NFS 서비스를 시작하고 있습니다:
[ 확인 ]
NFS 쿼터를 시작하고 있습니다:
[ 확인 ]
NFS 데몬을 시작함:
[ 확인 ]
NFS mountd를 시작하고 있습니다:
[ 확인 ]
[root@spoolserver
common]# exportfs
[ 확인
]
/usr/N1/hoho/spooldb
<world>
/usr/N1/hoho/common
<world>
모든 서버에서 ./install_execd 를 실행하여 실행데몬 설정을 한후...
모든 서버에서 spoolserver
가 공유하고 있는 디렉토리들을 마운트한다.
[root@모든 서버 common]# mount -t nfs
spoolserver:/usr/N1/hoho/common/ /usr/N1/hoho/common/
마스터 서버 및 쉐도우 마스터 서버로 설정할
서버에서는 아래처럼 스풀디렉토리도 공유한다.
[root@마스터서버
및 쉐도우마스터서버들 common]# mount -t nfs spoolserver:/usr/N1/hoho/spooldb/
/usr/N1/hoho/spooldb/
# ] 참고.
qmon 실행하기 위해서는 아래의 패키지가 설치되어 있어야한다.
=============================================================================
Package Arch
Version
Repository
Size
=============================================================================
Installing:
openmotif21
i386
2.1.30-14
base
996 k
Installing
for dependencies:
xorg-x11-deprecated-libs i386
6.8.2-37.FC4.49.2.1
updates-released 88
k
|