Input

EDG schedule:

Currently EDG V 1.4.x

05/2003 EDG V2.0 released

09/2003 EDG V2.x - Final testbed release

Early 2004 Final EDG review

LCG-1 deployement schedule:

12/2002 - Draft recommendation from WG1 (Recommendation on middleware components)

01/2003 - Start of deployment

02/2003 - Final recommendation from WG1 (Middleware components chosen)

06/2003 - A working version of a LCG-1 based system deployed on ~10 centers

07/2003 - Start of LCG-1 service

09/2003 - An LCG-1 based production system available for the MC-production on 10-15 centers

LCG-1 Components as of 01/2003:

VDT 1.1.5:

Globus 2.0 + openssl security patch + new job manager.

ClassAds: 0.9.3

Condor: 6.4.3

Condor-G: 6.4.3

EDG Certificates 0.12-1

EDG CRL Update: 1.2.5-1

FTSH 0.0.9

MDS 2.2 + static GLUE schema

EDG mkgridmap

Perl--5.003Convert-ASN1-0.16 Filesys-DiskFree-0.06 IO-Socket-SSL-0.91 Net_SSLeay.pm-1.20 perl-ldap-0.26  

From EDG 1.3.0:

GDMP 3.2.5 ( to be migrated to 4.0)

Replica Catalogue Server ( to be migrated to RLS) edg-rc-server 3.1-1

Replica Manager staticedg-replica-manager 2.0.6

Replica Catalogue API /CLI staticReplicaCatalogue 3.2-3

Workload Management (informationindex-1.2.9-1, jobsubmission-[glue-aware], lbserver-1.2.14-1, locallogger-1.2.12-1, proxy-1.2.8-1, userinterface-1.2.15-1)

From DataTAG 1.0:

GLUE Information Providers

Edt-monitor

From PACMAN:

Python 1.5.2

Pacman 2.098

Deployement plans update ==> Ian Bird March 10, 2003

LVG-0 released:

• VDT 1.1.6 (Globus 2.2.3)
• EDG WP1, 2
• GLUE Schema, MDS, etc.

LCG-1 will be released by July 1

• Will be VDT 1.1.7 and EDG 2.0
• Delivered to LCG by EDG end of April
• This will include RLS and R-GMA as well as MDS
• Testing and certification process will be on LCG certification testbed

LCG-1 will be identical to EDG 2.0

LCG-1 Ramp-up schedule (from Ian Bird – GDB – March 10, 2003)

BaBarGrid Tentative Schedule

Software installation and maintenance at SLAC

• 03/2003 ---> 06/2003 Maintenance of current EDG installation (V 1.4.x),
• Investigate on possibility to install a beta version under RH 7.2  (Dave + Dominique)
• 06/2003 Installation of LCG-1 / EDG V2.0. At this point it will probably be necessary to continue to maintain V1.4.x until V2.0.x is stable enough
• 05/2003 ---> 12/2003 Maintenance of EDG V2.0.x

• 03/2003 Installation of VDT
• 03/2003 --> 09/2003 Evaluation of VDT only  - The goal is to answer the question:  "What can we do with a minimal Grid  toolkit  - Adil , John B (?) - Dominique

• Assesment of LCG-1
• 09/2003 Deployement of LCG-1 at SLAC as a service for the whole BaBar collaboration

Action Item: Check how BaBar can interact with LCG and EGEE (Dominique) What will be the starting point for EGEE ?

Open issues at SLAC (From Booker)

• How do we map certs to unix accounts?
• How do we keep the grid-mapfile up to date?
• Something may be in place by May 1st

• How do we monitor the software and keep it up to date?
• Slac has its own procedures not necessarily compatible with EDG software distribution system. SLAC would prefer something more modular. Wait until EDG V2.0 is available
• How do we track errors and resolve problems?

Inter-operability

• 06/2003 - 10/2003 Test inter-operability between LCG-1 and VDT only

• Now - Define a relevant set of things to test ???
• Apply to analysis test jobs

Installation elsewhere

• 04/2003 Include and test a second RB accessible by the BaBar VO ( in Italy)
• Define a strategy to manage 2 RB
• Would be good to keep one in production while upgrading the second one, but probably impractical as we are not the only users - Already in place at IC (1 month overlap) (Eleonora to discuss this in Bologna)
• EDG / LCG installation in the European sites will follow the official deployment schedule, BaBar will just make use of it
• FZK:
• Learning curve on EDG 1.4 : 04/2003 --> 6 or 9/2003  Preferably on a RH 7.2 version
• Then early experience on LCG-1 with an example analysis. 9/2003 --> 12/2003

BaBarGrid code development

• 03/2003 ---> 09/2003 Develop framework to run analysis jobs on Grid (EDG V1.4.x / LCG-1) - Match use cases to Grid implementation
• Develop BaBar user interface  (Janusz)
• Evaluation of GENIUS as a possible framework for the User Interface (Italy )
• Other interfaces  
• Develop simple BaBarGrid job monitoring - Explore what is available.
• RGMA/BOSS (Janusz)  Job output monitoring
• Other utilities
• 04/2003 ---> 09/2003 Develop framework to run analysis jobs on VDT
• 05/2003 ---> 12/2003
• Test of RLS independently from LCG-1 06/2003  - 
• 07/2003 - 10/2003 Define how to use RLS in an analysis environment 

Bookkeeping

• 03/2003 --> 09/2003 Work with bookkeeping group to define how BaBarGrid should be taken into account
• 10/2003 Bookkeeping included with BaBarGrid user interface

VSC

· 06/2003 -> 08/2003 VSC test and deployement

• Define a strategy to run VSC at SLAC and  interactions with other sites

Large scale tests

• 04/2003 - 12/2003 Run a full real analysis production in a BaBarGrid framework, mainly using the Karlsruhe environment. This will probably be based on LCG-1 (perhaps this is meaningless if EDG V2.0 is identical to LCG-1)
• A full analysis is something like 10000 jobs (~8 CPU hours) producing of the order of 200-500 GB n-tuple output

Open issues for large scale production

• How do we deal with skimming ?
• Where do we store output collections ?
• How do we make the book-keeping
• Should we transfer the output collections to all Tier-As ? To a single Tier-A ? Is it possible / preferable to keep the output collections in place and to run further jobs where the skims are located ?

SP Grid

• Setup configuration to run with edg 1.4.x -
• Investigate mixed configuration (RH 7.2, 6.2 7.3 issue) April
• EDG 2.0 May or June ....
• RPM (May) - CDB accessed from outside (test  within a week)
• Integrate other work from Ohio and Bristol  
• First test version : depends on EDG V2.0 => September  Something sent to integration team . Few beta sites try it.
• Production : end of 2003

General

• Need to define how to manage auxiliary data-files like PID tables and Tracking Efficiency
• Should it be part of the packaging system ?
• Should it be stored in SE ? In which form ?

SRB

• Need input from Adil and Wilko
• Evaluate SRB V2.0
• Find how to work RLS and SRB together 
• Does it bring something useful ?