« Grid Engine installation preparation
Setting up NFS »

Grid Engine installation installation

Fresh from a nice Memorial Day picnic lunch in Dolores Park, it feels like time to take a nap. But I’m going to install the Grid Engine instead! Here comes the installation part of the installation process.

Getting the Software

I downloaded the Grid Engine 6.0u8 common files and Mac OS X binaries linked from here and unpacked the contents of each into /usr/local/gridengine on both of my machines.

Then I set the $SGE_ROOT environment variables in the system-wide /etc/bashrc file, and added the binary directory to the standard $PATH:


export SGE_ROOT=/usr/local/gridengine
export PATH=$SGE_ROOT/bin/darwin:$PATH

and did a source /etc/bashrc to update my session’s environment variables.

Setting up the Master Host

Making sure I was in the $SGE_ROOT directory and in a sudo -s session, I ran this on good-old Astor:

./install_qmaster

I followed through some screens:

  • Admin user At the first screen, I said OK to use ebaskerv (my user account) as the admin user.
  • root directory The root directory was right.
  • TCP/IP services As requested, I added sge_qmaster to my /etc/services file, and in anticipation added one for sge_execd:
    sge_qmaster 781/tcp
    sge_execd 782/tcp
  • Cells Named my cell algore, as promised.
  • qmaster spool directory Default is fine: /usr/local/gridengine/algore/spool/qmaster
  • Windows Execution Host Support Are you going to install Windows Execution Hosts? Are you kidding me? At least, by Judas, the default is no.
  • File permissions I said no when asked if I had already verified and set file permissions. My guess is these would need fixing. I said yes at the next screen (please verify and set my permissions) and all looked hunky-dory (“Your file permissions were set”).
  • Hostname resolving method This asks if all my hosts are in one DNS domain. I’m going to cross my fingers and hope that the zeroconf pseudo-domain local. will work, and answer yes.
  • Making directories This seemed to go fine. (“Mrs. Crabapple and Principal Skinner were in the closet making directories, and I saw one of the directories, and the directory looked at me!”) RETURN!
  • Setup spooling I chose classic spooling, because I had this suspicion that BerkeleyDB wasn’t ever installed properly on my machine. I’m looking for simplicity, not performance. The spooling database seemed to be initialized properly on the next screen.
  • Group id range For some strange reason, the Grid Engine needs a range of UNIX group ids to assign dynamically to jobs. I’m pretty sure the example range 20000-20100 is free and large enough, so I’ll use that.
  • Cluster configuration First up: execd_spool_dir. The default seems fine. Then, administrator email: I gave it my email, but I don’t think email sending is even set up right on my machine, so it probably won’t work.
  • Creating local configuration This seemed to work…
  • qmaster/scheduler startup script Apparently, it knows how to set up a startup script. I’ll let it go ahead and try…wow! It put something in /Library/StartupItems! Clever girl.
  • qmaster and scheduler startup Started up successfully!
  • hosts This is easy: just two for now. astor.local. and darwin.local., maybe more later. (They misspelled “separated” in “Please enter a blank seperated list of hosts.”) This seemed to go correctly. I said no to a shadow host, partially because I like to live dangerously, and mostly because my grid consists of two computers. Then, the default queue and hostgroup were added: just astor.local.—maybe I have to add darwin.local. manually later.
  • Scheduler tuning Went with Normal.
  • Using gridengine Looks like they provide a nice script to set all the environment variables. So I replaced my old bashrc line with:
    . /usr/local/gridengine/algore/common/settings.sh
  • Messages FYI, messages logged to:
    /tmp/qmaster_messages
    /tmp/execd_messages
    /usr/local/gridengine/algore/spool/qmaster/messages
    [execd_spool_dir]/[hostname]/messages
    and startup scripts are at:
    /usr/local/gridengine/algore/common/sgemaster (qmaster and scheduler)
    /usr/local/gridengine/algore/common/sgeexecd (execd)
  • Almost done “Your Grid Engine qmaster installation is now completed” says the friendly screen. Now I get to start the execution host installation. Next post.

This entry was posted on Monday, May 29th, 2006 at 5:46 pm and is filed under GridSweeper. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply