2. RESTRICTIONS Software is confidential and copyrighted. Title to
--More--(11%)
Software and all associated intellectual property rights is retained by Sun
and/or its licensors. Except as specifically authorized in any Supplemental
License Terms, you may not make copies of Software, other than a single copy
of Software for archival purposes. Unless enforcement is prohibited by
applicable law, you may not modify, decompile, or reverse engineer Software.
You acknowledge that Software is not designed, licensed or intended for use
in the design, construction, operation or maintenance of any nuclear
facility. Sun disclaims any express or implied warranty of fitness for such
uses. No right, title or interest in or to any trademark, service mark,
logo or trade name of Sun or its licensors is granted under this Agreement.
3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90)
days from the date of purchase, as evidenced by a copy of the receipt, the
media on which Software is furnished (if any) will be free of defects in
materials and workmanship under normal use. Except for the foregoing,
Software is provided "AS IS". Your exclusive remedy and Sun's entire
liability under this limited warranty will be at Sun's option to replace
Software media or refund the fee paid for Software.
6. Termination. This Agreement is effective until terminated. You may
terminate this Agreement at any time by destroying all copies of Software.
This Agreement will terminate immediately without notice from Sun if you
fail to comply with any provision of this Agreement. Upon Termination, you
--More--(38%)
must destroy all copies of Software.
8. U.S. Government Restricted Rights. If Software is being acquired by or
on behalf of the U.S. Government or by a U.S. Government prime contractor or
subcontractor (at any tier), then the Government's rights in Software and
accompanying documentation will be only as set forth in this Agreement; this
is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of
Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD
acquisitions).
3. Termination. Either party may terminate this Agreement immediately
should any Grid Engine Software become, or in either party's opinion be
likely to become, the subject of a claim of infringement of a patent, trade
secret, copyright or other intellectual property right.
--More--(87%)
4. No support. Unless you have entered into a separate support agreement
with Sun, Sun is under no obligation to support the Software or to provide
to you any updates or error corrections (collectively referred to as
"Software Updates"). If Sun provides any Software Updates, whether pursuant
to a support agreement or otherwise, at its sole discretion, the Software
Updates will be considered part of the Software and subject to the terms of
this Agreement.
6. Open Source license. The Source Code version of the Original Code of
this software is available under the terms of the Sun Industry Standards
License version 1.2 and subsequent versions, which may be viewed at
.
7. Third Party Code. Some portions of Software are provided with notices
--More--(98%)
and/or licenses from other parties, which govern the use of those portions
and which are set forth in the 3rd party_licscopyrights file.
Do you agree with that license? (y/n) [n] >> y
- 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.
You are installing not as user >root
This will allow you to run Grid Engine only under your user id for testing
a limited functionality of Grid Engine.
Hit if this is ok or stop the installation with Ctrl-C >>
Checking $SGE_ROOT directory
----------------------------
The Grid Engine root directory is:
$SGE_ROOT = /appl/sge/ge6.2u2_1
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 [/appl/sge/ge6.2u2_1] >>
Your $SGE_ROOT directory: /appl/sge/ge6.2u2_1
Hit to continue >>
Grid Engine TCP/IP communication service
----------------------------------------
The port for sge_qmaster is currently set as service.
sge_qmaster service set to port 1536
Now you have the possibility to set/change the communication ports by using the
>shell environment< or you may configure it via a network service, configured
in local >/etc/service<, >NIS< or >NIS+<, adding an entry in the form
to your services database and make sure to use an unused port number.
How do you want to configure the Grid Engine communication ports?
Using the >shell environment<: [1]
Using a network service like >/etc/service<, >NIS/NIS+<: [2]
(default: 2) >>
Grid Engine TCP/IP service >sge_qmaster<
----------------------------------------
Using the service
sge_qmaster
for communication with Grid Engine.
Hit to continue >>
Grid Engine TCP/IP communication service
----------------------------------------
The port for sge_execd is currently set as service.
sge_execd service set to port 1537
Now you have the possibility to set/change the communication ports by using the
>shell environment< or you may configure it via a network service, configured
in local >/etc/service<, >NIS< or >NIS+<, adding an entry in the form
to your services database and make sure to use an unused port number.
How do you want to configure the Grid Engine communication ports?
Using the >shell environment<: [1]
Using a network service like >/etc/service<, >NIS/NIS+<: [2]
(default: 2) >>
Grid Engine TCP/IP communication service
-----------------------------------------
Using the service
sge_execd
for communication with Grid Engine.
Hit 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=
will be set for all further Grid Engine commands.
Enter cell name [default] >>
The "common" directory in cell >default< already exists!
Do you want to select another cell name? (y/n) [y] >> n
You can overwrite or delete this directory. If you choose overwrite
(YES option) only the "bootstrap" and "cluster_name" files will be deleted).
Delete (NO option) - will delete the whole directory!
Do you want to overwrite [y] or delete [n] the directory? (y/n) [y] >>
Specified cluster name >$SGE_CLUSTER_NAME=p1536< resulted in the following conflict!
Detected a presence of old RC scripts.
/etc/init.d/sgemaster.p1536
Specified cluster name >$SGE_CLUSTER_NAME=p1536< resulted in the following conflict!
Detected a presence of old RC scripts.
/etc/init.d/sgeexecd.p1536
Stop the installation (WARNING: selecting 'n' will remove the detected cluster) (y/n) [y] >> n
Deleting bootstrap and cluster_name files!
Using cell >default<.
Hit to continue >>
Unique cluster name
-------------------
The cluster name uniquely identifies a specific Sun Grid Engine cluster.
The cluster name must be unique throughout your organization. The name
is not related to the SGE cell.
The cluster name must start with a letter ([A-Za-z]), followed by letters,
digits ([0-9]), dashes (-) or underscores (_).
Enter new cluster name or hit
to use default [p1536] >>
Your $SGE_CLUSTER_NAME: p1536
Hit 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.
Your account on this host 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
[/appl/sge/ge6.2u2_1/default/spool/qmaster]
will be used as qmaster spool directory by default!
Do you want to select another qmaster spool directory (y/n) [n] >>
Windows Execution Host Support
------------------------------
Are you going to install Windows Execution Hosts? (y/n) [n] >>
Verifying and setting file permissions
--------------------------------------
You are not installing as user >root<
Can't set the file owner/group and permissions
Hit 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] >>
Ignoring domain name when comparing hostnames.
Hit to continue >>
Making directories
------------------
Hit 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
Berkeley Database spooling parameters
-------------------------------------
Enter the name of your Berkeley DB Spooling Server [x4150c] >> x4150d
Enter the database directory [/appl/sge/ge6.2u2_1/default/spooldb] >>
Dumping bootstrapping information
Initializing spooling database
Hit 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-20100] >>
Using >20000-20100< as gid range. Hit to continue >>
Grid Engine cluster configuration
---------------------------------
Please give the basic configuration parameters of your Grid Engine
installation:
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: [/appl/sge/ge6.2u2_1/default/spool] >>
Grid Engine cluster configuration (continued)
---------------------------------------------
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 /appl/sge/ge6.2u2_1/default/spool
administrator_mail
Do you want to change the configuration parameters (y/n) [n] >>
Creating local configuration
----------------------------
Creating >act_qmaster< file
Adding default complex attributes
Adding default parallel environments (PE)
Adding SGE default usersets
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 to continue >>
Hit to continue >>
Grid Engine qmaster startup
---------------------------
Starting qmaster daemon. Please wait ...
starting sge_qmaster
Hit 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 if the line is getting too long. Once you are finished
simply press 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] >>
Adding admin and submit hosts
-----------------------------
Please enter a blank seperated list of hosts.
Stop by entering . 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): x4150c x4150d x4150e x4150f x4150g x4150h x4150i x4150j x4150k x4150l x4150m x4150n x4150o x4150p x4150q
adminhost "x4150c" already exists
x4150c added to submit host list
x4150d added to administrative host list
x4150d added to submit host list
x4150e added to administrative host list
x4150e added to submit host list
x4150f added to administrative host list
x4150f added to submit host list
x4150g added to administrative host list
x4150g added to submit host list
x4150h added to administrative host list
x4150h added to submit host list
x4150i added to administrative host list
x4150i added to submit host list
x4150j added to administrative host list
x4150j added to submit host list
x4150k added to administrative host list
x4150k added to submit host list
x4150l added to administrative host list
x4150l added to submit host list
x4150m added to administrative host list
x4150m added to submit host list
x4150n added to administrative host list
x4150n added to submit host list
x4150o added to administrative host list
x4150o added to submit host list
x4150p added to administrative host list
x4150p added to submit host list
x4150q added to administrative host list
x4150q added to submit host list
Hit to continue >>
Adding admin and submit hosts
-----------------------------
Please enter a blank seperated list of hosts.
Stop by entering . 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 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 for adding and
for removing this host
Attention: This is not the shadow host installation
procedure.
You still have to install the shadow host separately
Do you want to add your shadow host(s) now? (y/n) [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 if the line is getting too long. Once you are finished
simply press 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] >>
Adding admin hosts
------------------
Please enter a blank seperated list of hosts.
Stop by entering . 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): x4150e
adminhost "x4150e" already exists
Hit to continue >>
Adding admin hosts
------------------
Please enter a blank seperated list of hosts.
Stop by entering . 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 to continue >>
Creating the default
queue and hostgroup
----------------------------------------------------------- added "@allhosts" to host group list
added "all.q" to cluster queue list
Hit to continue >>
Scheduler Tuning
----------------
The details on the different options are described in the manual.
Configurations
--------------
1) Normal
Fixed interval scheduling, report limited 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 preferred configuration and hit !
Default configuration is [1] >>
We're configuring the scheduler with >Normal< settings!
Do you agree? (y/n) [y] >>
changed scheduler configuration
Using Grid Engine
-----------------
You should now enter the command:
source /appl/sge/ge6.2u2_1/default/common/settings.csh
if you are a csh/tcsh user or
# . /appl/sge/ge6.2u2_1/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 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: /appl/sge/ge6.2u2_1/default/spool/qmaster/messages
Exec daemon: //messages
Grid Engine startup scripts
---------------------------
Grid Engine startup scripts can be found at:
/appl/sge/ge6.2u2_1/default/common/sgemaster (qmaster)
/appl/sge/ge6.2u2_1/default/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
Please hit >>
sge_qmaster successfully installed!
-bash-3.00$ ps -ef |grep sge
sgeadmin 3030 1 0 15:33 ? 00:00:00 /appl/sge/ge6.2u2_1/bin/lx24-amd64/sge_qmaster
