The middleware summary at the meeting today was in my opinion not very clear so here is the information in a more structured way.
Feel free to get the information directly from the GDB presentations which you will find here:
EMI release status: http://indico.cern.ch/materialDisplay.py?contribId=1&sessionId=1&materialId=1&confId=106643
gLite 3.1/3.2 update: http://indico.cern.ch/materialDisplay.py?contribId=1&sessionId=1&materialId=slides&confId=106643
The EMI release.
The first release is called “Kebnekaise” and the release manager is Cristina Aiftimiei. The release is apparently at candidate 3 stage (RC3) which means that the rpm, src.rpm, tar.gz files etc. are produced and being verified such that deployment tests are starting. Markus Schulz took issue with this statement in the meeting as many components are not successfully building in the build system. Apparently the RC3 is 60% of components building.
EMI-1 will now include gLite-Cluster. Work has started on the EMI-UI and WN 32-bit and is almost complete for 64-bit. A tarball release of the UI/WN will be made available after the EMI-1 release IF it is still requested.
EMI releases are being tracked here: https://savannah.cern.ch/task/?group=emi-releases.
If you want an overview of what is EMI and how is it going to work then see this talk from the February GDB: http://indico.cern.ch/materialDisplay.py?contribId=4&sessionId=1&materialId=slides&confId=106641. It includes information on EMI-1 and the roadmap.
The release from EMI is taken by EGI and formed (validated; tested in staged-rollout and integrated with other products) into a Unified Middleware Distribution (UMD) as explained in this talk: http://indico.cern.ch/materialDisplay.py?contribId=7&sessionId=1&materialId=1&confId=106641 . For the first run through of the UMD process a 3 month period is expected but components can come through earlier than that. If we urgently need an update/patched version of something we can (and may) take a release directly from the developers (for example for glexec/ARGUS).
In terms of the status and updates for the gLite middleware....
The 3.2 release will be fully supported until October 2011. Security updates (vulnerability fixes) will be done until April 2012.
The WMS will not be back ported in to gLite 3.2.
CREAM 1.6.5 contains an urgent update for LHCb.
Glite-cluster is available.
Before EMI-1 there will be a new patched version of Torque; a UI update to fix known issues and a patch update for the FTS.
These remain fully supported in 3.1: lcg-CE; WMS; FTS; FTA; FTM
These are now security fixes only for: UI; WN;VOMS; DPM; LFC
The lcg-CE can now be configured to work with glite-cluster. A twiki is being prepared to cover deployment scenarios.
[While glite-CLUSTER can publish information about clusters and subclusters it should not publish UniqueIDs which are already published by another node such as lcg-CE or creamCE. For instance since version 3.1.46 the lcg-CE can be configured in 'cluster mode' which will prevent it from publishing its own cluster/subcluster IDs and allow the glite-CLUSTER node to be used to do that].
Before EMI-1 there will be a WMS update (now); DPM/LFC patches to fix VOMS memory leak; FTS patches.
An overall summary of component support for gLite 3.1 and 3.2 can be found here: http://glite.cern.ch/support_calendar
Discussion has started for the end of updates to the LCG-CE – probably September 2011 – and security fixes end of 2011 or April 2012.
I hope that this is a clearer now!