TWiki> EGEE Web>SA3>EGEEReleases>Glite31WNPPS (revision 16)EditAttachPDF

Release notes for the gLite 3.1 WN for SL4 as provided to PPS

These notes describe the initial release to PPS of the gLite 3.1 WN for SL4

What's the difference between this and other releases for SL4?

A previous SL4 release has been made to PPS, composed of the gLite 3.0 / SL3 binaries.

The main differences are that in this release...

  • The binaries have been natively built on SL4
  • The codebase is gLite 3.1, not gLite 3.0 (in practise the changes here are small)
  • There are updated dependencies, most notably
    • VDT1.6 which provides GT4
    • Java 1.5
  • There is updated configuration based on yaim 3.1
  • Many obsolete components have been removed

Upgrade from the 'SL3 binaries on SL4' has not been tested.

This release has been tested only on 32 bit. Nevertheless, feedback on attempts at 64 bit installation are welcomed.


You will have to install a java 1.5 rpm first. Get this from sun

Please use the following repository to install

Important note: the previously communicated repository has been obsoleted

obsoleted repository:

The following meta-packages are available

  • glite-WN
  • glite-TORQUE_client

Note that installation via yaim for this version is not (yet) supported, please use native package management tools (yum is strongly recommended).

To use yum, create glite.repo in /etc/yum.repos.d with the following contents (please note that this information has changed since the original release)

name=gLite 3.1 Worker Node

name=Torque clients 


You will have to reference a jpackage repository too (for example in jpackage.repo);

name=JPackage 1.7, generic

name=JPackage 5, generic

More information on java and jpackage with gLite 3.1 can be found here

Then you can do

yum install glite-WN glite-TORQUE_client


The Trash.EGEEYAIM configuration for gLite 3.1 doesn't differ from the 3.0.1 from the configuration point of view. All configuration files used with Trash.EGEEYAIM 3.0.1 should be compatible with the Trash.EGEEYAIM 3.1.0 The yaim 3.1 is currently in finalization state and there is still a list of known problems and imperfections we are fixing. There are several modifications between yaim 3.0.1 and 3.1:

  • the configure_node, install_node and run_function are obsoleted although they are still located in the "/opt/glite/yaim/scripts" directory, please do not use them The configuration will very probably fail. All these commands will be removed in the next release. Their functionality has been replaced by new command yaim which has been introduced in yaim 3.0.1 and in yaim version 3.1 it became the only way to configure gLite middleware using yaim.
  • changes in the yaim packaging. Yaim 3.1 has a modular structure (glite-yaim-core, glite-yaim-clients) in contrary to the monolithic distribution of yaim 3.0.1 (glite-yaim package)
  • added service and node based configuration
The detailed documentation for yaim 3.1 is currently prepared and will be accessible soon from the : yaim 3.1 page.

Please configure your WN as follows

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n glite-WN 

Or with the torque client

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n glite-WN -n TORQUE_client

Tarball release

Have a look at this page

Known issues

There is a bug in glite-yaim-3.0.1-x which causes its failure when a new format of GLOBUS_TCP_PORT_RANGE (needed for the new globus) is used. This happens when the site normally running on gLite 3.0 installs SL4 WNs and the same site-info.def file is used for both configurations. In this case the fails with following output:
Executing config_glite_ce
Skipping file vo-list.cfg.xml
Skipping file glite-rgma-servicetool-externalServices.cfg.xml
Traceback (most recent call last):
 File "/opt/glite/yaim/functions/../libexec/", line 504, in ?
   environ['condor.HIGHPORT'] =\
IndexError: list index out of range
gLite configuration script has returned nonzero return code
/opt/glite/yaim/bin/../scripts/configure_node: line 18:
/ No such file or directory
gLite configuration script has returned nonzero return code
/opt/glite/yaim/bin/../scripts/configure_node: line 18:
/ No such file or directory
gLite configuration script has returned nonzero return code
Executing config_gip

The only currently known workaround is to use two site-info.def files. One with the new format of the GLOBUS_TCP_PORT_RANGE for SLC4 worker nodes and one with the old format for the rest of the site. New format:


old format:


Information system

Ensure that your subcluster is advertised as GLITE-3_1_0

GlueHostApplicationSoftwareRunTimeEnvironment: GLITE-3_1_0

You can use yaim's CE_RUNTIMEENV parameter for this.

Please also advertise your system architecture (currently unsupported in yaim).

-- JuhaHerrala - 16 May 2007

Edit | Attach | Watch | Print version | History: r20 | r18 < r17 < r16 < r15 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r16 - 2007-06-14 - unknown
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback