gLite 3.0.0 Release Notes

What is in gLite-3.0.0?


Who can upgrade?

Upgrades are supported from LCG-2.7.0. If you upgrade from gLite-1.5.0 upgrades might work for the components that are in common, however this has not been tested and it might be advisable to reinstall instead.

Why two workload management systems?

Since many applications haven't migrated all their production systems to the gLite WLM we have to keep the LCG RBs and CEs operating.

gLite CE or LCG CE?

All larger sites should deploy both CEs to ensure that the majority of resources is available from both worlds.

If you are running two CEs please take care to avoid collisions of pool account mapping. This is typically achieved either by allocating separate pool account ranges to each CE or by allowing them to share a gridmapdir.

Since the gLite WLMS can utilize LCG-CEs, smaller sites should stay with the LCG CE to allow access to their resources and data that is stored at their site.

The project will make an announcement when this preference will change.


gLiteWMS/LB or LCG-RB?

Since the work load manager end user APIs differ for these services you have to get an agreement with you local user community which node type they prefer.
Large sites should try to add at least on gLite WMS/LB node to the set of RBs that they are operating.

User Documentation

The team around Andrea Sciaba is currently working on an updated version of the LCG user guide. The document is currently a live document and users should come back frequently to get updated versions. You can find the document here:

As soon the document has stabilized we will publish in addition a version in html.

The above document can be used as an introduction and manual for the system, for those who need very detailed information on individual gLite components you can find links here:

For the FTS additional material is available here:

More in depth material for the gLite WLM is available from:

Links to additional LCG components can be found in the draft of the LCG User Guide.

Pointers to documentation on the components of this release are being compiled here

where you can find additional useful information.

Installing the release

Please use the 'Generic Installation and Configuration Guide' that you can find here for installation details.

For upgrade instructions refer to the 'Introduction to the Manual Upgrade Procedure' that you can find here.

There is a lot of useful node-specific information there which you should take note of. Note that yaim has been renamed to glite-yaim and relocated to /opt/glite. Many metapackages have been similarly renamed. Full details are in the above mentioned guides.

The configuration guides for native configuration via the gLite configuration management scripts will be updated during the next few days and can be found in 'gLite v3.0 Advanced Installation and Configuration Guide' and 'Generic gLite v3.0 VO Configuration Guide' here. This is relevant for those who run the gLite workload management services and VOMS and intend to avoid the YAIM wrappers.


The upgrade from lcg-2.7 to gLite-3.0 is described and has been tested. The upgrade from gLite-1.5 to 3.0 has not been tested and can't be seen as an upgrade because several components that have been in 1.5 are no longer part of the release bundle. Sites and projects that depend on these will be supported individually and should contact the deployment team via

Notes and known issues

Other issues to remain aware of

Between LCG-2_7_0 and gLite 3.0 MySQL has been upgraded from 4.0 to 4.1. There has been a change in the password encryption, please keep this in mind. This is handled by YAIM, but it might be good to know anyway.

Pointers to documentation on the components of this release are being compiled here

New Features

Before we start, this is not meant to be a complete list of all new features, but to highlight the most important changes.

Additional useful documentation

Additional useful documentation can be found

Several HowTos including one on configuration for MPI can be found at the gocwiki page:

The main page

includes links to other regional wiki's with useful additional material.