Using GridWay With Unicluster Express - Part I

Those folks who are closely following development of the Globus Toolkit software probably noticed that its most recent (4.2) release also includes GridWay metascheduler as one of Globus execution management components. This is very good news for the grid community (especially for organizations with more than one cluster), and the GridWay guys certainly deserve praise for their efforts. For any of the earlier (4.0.x) versions of the Toolkit GridWay must be downloaded and installed separately from the standard GT install. In this article I decided to describe steps necessary for GridWay installation on top of Unicluster Express 3.2 (UCE), which is based on GT 4.0.5. In the following, I will assume that UCE has been installed in its default location (/usr/local/unicluster). Before you start, make sure that you have recent version of (non-gnu) Java compiler installed on your system. You will also need a C compiler, which should be available from your linux distribution.

1. Download GridWay and unpack it in your scratch area. The current release of the software (5.4) is intended for GT 4.2 (which is not fully backwards compatible with 4.0.x releases), so I used the most recent stable release appropriate for GT 4.0.x series.

   $ wget http://www.gridway.org/software/files/gw-5.2.3.tar.gz
   $ tar zxvf gw-5.2.3.tar.gz
   

2. Configure your UCE build environment by sourcing the UCE setup file and regenerating the GT flavor information. On my 64-bit development machine, I used gcc64dbg:

   $ source /usr/local/unicluster/unicluster-user-env.sh
   $ gpt-build –nosrc gcc64dbg
   

3. Make sure that java compiler is in your path. I have used Sun’s JDK 6.0 that was installed in the /opt directory:

   $ export JAVA_HOME=/opt/jdk
   $ export PATH=$JAVA_HOME/bin:$PATH
   

   Note that Java part of the GridWay build does not use Ant.
4. Configure GridWay.

   $ cd gw-5.2.3
   $ ./configure --prefix=/opt/gw --with-docs --with-tests
   

   The generated makefile will have JAVA_HOME variable set to JRE shipped with UniCluster Express. Since GridWay relies on some java specific header files (e.g. jni.h), and since we are using external JDK, this needs to be corrected manually. One way to do this is to edit src/Makefile and to point JAVA_HOME to your JDK directory:

   $ vi src/Makefile 
   $ cat src/Makefile | grep "JAVA_HOME ="
   JAVA_HOME = /opt/jdk
   

5. Build and install software (make sure that your installation directory is writeable).

   $ make
   $ make install
   

   With any luck, your build and installation will complete without any issues. Before starting GridWay, however, there are few configuration details that need to be taken care off. I’ll discuss those in my next post.

Comments

[Mark]

Thanks for a great post. Very useful.
Mark