Jump to content Australia-English
HP.com Australia home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com Australia home
Technologies  >  Grid  >  Globus

Globus Toolkit on XC Clusters

» 

Large Enterprise Business

» Products
» IT Strategy & Architecture
» Solutions
» Technologies
» Energy Efficiency
» Support & Drivers
» Promotions
» Media Center & Library
» Newsletter
» Success stories
What’s haunting your data center?
Define your datacenter infrastructure
Content starts here

XC Clusters overview

On XC Clusters, the Globus software need only be installed and configured on one node. The chosen node must have access to the external network (see Globus on Multi-homed hosts) and the ability to submit jobs into the LSF batch system. If the head node satisfies these requirements, it is the ideal choice. However, any login node is good alternative.

Once a suitable installation node has been selected, it is recommended that one obtain a new virtual IP address and corresponding hostname specifically for globus (e.g., "xcglobus.dom.ain"). While not required, this will make it possible to relocate the globus services to another node or set up a failover plan.


Java™ on XC Clusters

XC Clusters include the GNU Compiler for Java. Globus can not use this. It requires the Sun Java J2SE 1.4.2 SDK (or greater). Select and install the appropriate J2SE, set the $JAVA_HOME environment variable accordingly and put $JAVA_HOME/bin at the front of $PATH. For XC clusters built on the Opteron™ platform, we were successful with the J2SE 1.5.0 for Linux/AMD64.

MySQL® on XC Clusters

Before building, GT4 requires that a JDBC compliant database be present on the host system. XC Clusters come configured with the MySQL database which satisfies this requirement. However, the version of MySQL delivered on the XC is different from that which Globus used, so the ODBC connecter software they supply will not build on the XC. Instead, please obtain, build and install the following software packages on the XC before installing GT4.
  • iODBC version 3.52.3
        # ./configure --prefix=${INST_DIR} \
             --with-iodbc-inidir=${INST_DIR}/etc \
             --disable-gtktest --with-pthreads \
             --disable-gui
        # make
        # make install
    
  • unixODBC version 2.2.11
        # ./configure --prefix=${INST_DIR}
        # make
        # make install
    
  • MySQL ODBC Connector version 3.51.12.
        # ./configure --prefix=${INST_DIR} \
             --with-iodbc=${INST_DIR} \
             --with-unixODBC=${INST_DIR} \
             --with-odbc-ini=${INST_DIR}/etc \
             --enable-thread-safe --disable-gui
        # make
        # make install
    

Getting started

»  Contact HP
»  HP Grid Consulting Services

Globus Toolkit         feedback form

»  Send questions or feedback on the Globus Toolkit for HP platforms

Grid computing

»  HP grid computing
»  HP Labs grid technical reports
»  Computational and data grids
»  HP Collaboration and Competency Network
»  Globus Alliance
»  Globus Toolkit

HP platforms

»  HP Unified Cluster Portfolio
»  Linux
»  HP-UX 11i
»  XC Clusters
»  HP Integrity servers
»  HP Tru64 UNIX®

Configuring and building GT4

With the database software and J2SE in place, it is time to configure and build the Globus Toolkit. Follow the instructions in the GT4 Admin Guide. On XC Clusters, we tested with the following environment variables and configuration options:
    $ GLOBUS_MYSQL_PATH=/usr
    $ export GLOBUS_MYSQL_PATH
    $ ODBCINIDIR=${INST_DIR}
    $ ./configure \
         --prefix=$GLOBUS_LOCATION \
         --enable-wsgram-lsf --enable-rls \
         --with-iodbc=${INST_DIR} \
         --with-mysql-libs=$GLOBUS_MYSQL_PATH/lib64/mysql \
         --with-mysql-includes=$GLOBUS_MYSQL_PATH/include/mysql \
         --with-odbc-ini=$ODBCINIDIR
Note that, the "--with-mysql-libs" should use the "lib64" directory on 64-bit platforms and "lib" on 32-bit systems.

Configuring MySQL

With Globus built and installed, the MySQL database can be configured according to the instructions at the globus web site. For testing, we used the following MySQL commands to create a database user named "globus" with password "globusdb":
   # mysql
   mysql> use mysql;
   mysql> grant all on lrc1000.* to globus@localhost
   mysql>    identified by 'globusdb';
   mysql> grant all on rli1000.* to globus@localhost
   mysql>    identified by 'globusdb';
   mysql> SHOW GRANTS for globus@localhost;
   mysql> UPDATE mysql.user SET Password = OLD_PASSWORD('globusdb')
   mysql>    WHERE Host = 'localhost' AND User = 'globus';
   mysql> FLUSH PRIVILEGES;

Then edit "$GLOBUS_LOCATION/etc/globus-rls-server.conf" and change "db_user" to "globus", "db_pwd" to "globusdb" and "odbcini" to "${INST_DIR}/etc/odbc.ini". Finally create the "odbc.ini" file as detailed in the GT4 Admin Guide.

Configuring the XC Firewall

The last step for installing GT4 on XC Clusters is to poke holes in the XC firewall to enable the various Globus services to be accessed from the external network. Use the XC openipport(8) command to do this. For example:
   # echo "GT2 Gatekeeper"
   # openipport --port 2119 --protocol tcp --interface External
   #
   # echo "GT4 WS Core container"
   # openipport --port 8443 --protocol tcp --interface External

The GridFTP server is a little more complicated since an entire range of ports must be opened for data connections. In this case, a sequence of openipport commands may be given or, provided the administrator understands XC networking, a single iptables(8) command may be used. For example:

   # echo "GridFTP"
   # openipport --port 2811 --protocol tcp --interface External
   #
   # echo "GridFTP data"
   # openipport --port 40000 --protocol tcp --interface External
   # openipport --port 40001 --protocol tcp --interface External
   # openipport --port 40002 --protocol tcp --interface External
   # [...]
   # openipport --port 40100 --protocol tcp --interface External
   #
   # echo "GridFTP data using iptables"
   # iptables -I RH-Firewall-1-INPUT -i external_interface \
   #     -p tcp -m tcp --dport 40000:40100 --j ACCEPT
Also, be sure to set GLOBUS_TCP_PORT_RANGE=40000,40100 in "env" section of GridFTP "/etc/xinetd.d" services file so that it knows to restrict data transfers to these ports.

Other XC notes

And for job submission, since sudo(8) is already installed, just add users of the GRAM service to the existing "/etc/sudoers" file.
About PDF files: The PDF files on this site can be read online or printed using Adobe® Acrobat® Reader. If you do not have this software on your system, you may download it from Adobe's website. 
Printable version
Privacy statement Using this site means you accept its terms
© 2008 Hewlett-Packard Development Company, L.P.