gLite 3.x / SL(C)4

16 October 2006

See SLC4 planning wiki

9 October 2006

See Joint Operations minutes and meetings for a discussion of SL(C)4 support.

3 October 2006

Dear all, since the port of gLite into ETICS and to SLC4 is now our (ETICS) first priority, I would like to keep you informed of the progress so that the necessary actions canbe taken.

Most external dependencies required for SLC4 have been registered into the system and the first gLite base components have been ported (about 10% of the total). The work has been done manually so far to verify the validity of the new build information schema, but a script to register automatically gLite components into ETICS is available (not yet publicly, sorry, need a bit more testing to make it reasonably error-free). This should speed up the process. The goal is to port all gLite components into the ETICS system by the and of October, which automatically means that they will be built on SLC3 (ia32) and SLC4 (ia32 and x86_64). In theory also builds on Debian and ia64 should be possible although the builds system on those systems has not been completely tested. Components are ported by subsystem with priority given to those required to have the UI and WN ready first. In any case components are built as they are available. I will notify the EMT as each subsystem is ported and what problems have been found if any. At some point active debugging of the developers will be necessary.

Full FTS Services

This is assumed to mean stable transfers corresponding to the full matrix required by the different VOs at rates that satisfy those in the megatable (see attachment below).

A more complete definition:

Production quality transfers on all Tx-Ty channels at 2008 rates, including recovery.
Production level monitoring, tools for debugging problems, full integration into standard operations & support.