The procedure that follows explains only the special requirements for installing Sun Grid Engine for use with Sun Cluster HA for Sun Grid Engine. For complete information about installing and configuring Sun Grid Engine, see your Sun Grid Engine documentation.
To enable Sun Grid Engine to run in a cluster, you must modify Sun Grid Engine to use a logical host name.
Before you begin, ensure that you have the host names of all hosts in the grid. Create a separate list of host names for each type of host in the grid:
Execution hosts
Administrative hosts
Submit hosts
Become superuser of the cluster node where you are installing Sun Grid Engine.
Install the Sun Grid Engine distribution files. You have to choose between the tar.gz format and the pkgadd format.
Follow the instructions outlined in How to Load the Distribution Files On a Workstation in the N1 Grid Engine 6 Installation Guide.
If you choose the pkgadd format, you need to make sure to install Patches for the Sun Grid Engine software on exactly the same node the Sun Grid Engine packages are registered on.
Set the SGE_ROOT environment variable to the directory for the root of Sun Grid Engine file system that you created in Preparing the Nodes and Disks.
# SGE_ROOT=sge-root-dir # export SGE_ROOT |
Go to the directory for the root of Sun Grid Engine file system.
# cd sge-root-dir |
Start the script that installs the Sun Grid Engine master host.
# ./install_qmaster |
Follow the prompts on screen to provide or confirm the following information:
The name of the Sun Grid Engine administrative user
The value of the SGE_ROOT environment variable
The TCP port number
The name of the Sun Grid Engine cell to be configured
The path to the spool directory
The setup for the correct file permissions
Details of your domain name service (DNS) domains
When you are asked whether you want to use classic spooling or Berkley DB, do not choose to use a Berkely DB spooling Server.
Either choose the classic spooling method, or choose Berkley DB with local spooling.
When you are prompted, specify the range of group IDs for Sun Grid Engine to use.
To ensure that you allocate enough group IDs, specify a range of approximately 100 group IDs, for example, 20000-20100.
Follow the prompts on screen to provide or confirm the following information:
The path to the spooling directory for the execution daemon
The email address of the user who should receive problem reports
Confirm the configuration parameters
When you are asked if you want to install the script that starts Sun Grid Engine at boot time, reply no.
You are asked if you want to install the script that starts Sun Grid Engine at boot time.
We can install the startup script that will start qmaster/scheduler at machine boot (y/n) [y] >> n |
To ensure that Sun Cluster HA for Sun Grid Engine can provide fault monitoring and automatic fault recovery, Sun Grid Engine must be started only by Sun Cluster.
Follow the prompts on screen to provide or confirm the following information:
Specify the list of execution, admin and submit hosts
Do not use a shadow host
Select a scheduler profile
Become superuser of a node in the cluster that will host Sun Grid Engine.
Create a failover resource group to contain the Sun Cluster HA for Sun Grid Engine resources.
Use the resource group that you identified when you answered the questions in Configuration Planning Questions.
# clresourcegroup create -p Pathprefix=sge-root-dir sge-rg |
Specifies a directory on a cluster file system that Sun Cluster HA for NFS uses to maintain administrative and status information. This directory must be the directory that you created for the root of the Sun Grid Engine file system in Preparing the Nodes and Disks.
Specifies that the resource group that you are creating is named sge-rg.
Add a resource for the Sun Grid Engine logical host name to the failover resource group that you created in Step 2.
# clreslogicalhostname create \ -g sge-rg \ -h hostlist \ sge-lh-rs |
Specifies that the logical host name resource is to be added to the failover resource group that you created in Step 2
Specifies a comma-separated list of host names that are to be made available by this logical host name resource
Specifies that the resource that you are creating is named sge-lh-rs