Summary of data management meeting Monday, March 15th, 2004 16:00 Bat 2-R030
==============================================================================

Present: N.Brook, P.Charpentier, J.Closier, M.Frank, R.Graciani, 
         G.Kutznetsov, J.Saborido, A.Tsaragorotzev, R.Vizcaya

Workload Management System (Andrei, Ian, Vincent):
- Information service is installed on lbnts2 to serve
  status reports etc.
- Input data are accessible through the file catalog
- Agent was modified and executes a job being a collection 
  of modules.
- The production database must still be interfaced to produce
  proper JDL scripts for the job submission.
- Asynchronous updates of the file catalog and asynchronous data
  transfers must still be implemented.

Monitoring and accounting (Ricardo):
- Accounting must be integrated into DIRAC

Data Management tools & hardware (Joel/Andrei):
- Access to datasets stored in castor is possible from LCG2.
  Castor is a known storage element, the datasets produced in
  LCG2, which are stored in castor are also visible for
  regular batch/interactive jobs.
  Other storage systems must be tested.
- The AliEn file catalog has an interface, which allows to generate 
  POOL XML catalog slices.
- In order to implement catalog synchronization between LCG/EDG-RLS
  and AliEn a naming convention is required. Andrei suggests
  2 levels: /<configuration name>/<configuration version>/<logical file name>
  The first "real" physical file name is the name of the file in the 
  local storage element ie. on the Grid this will be the grid storage name.
- Andrei is now happy with the support of the Lxgate05 machine.

Production database/XML catalog/bookkeeping (Markus):
- Script to generate slices of the XML catalog needs better
  error reporting.
- Andrei will send the file catalog interface he expects
  to be provided by the bookkeeping database to Markus.
  Markus will implement the read-only part of this interface 
  for the existing bookkeeping database.
- The production database must be populated with proper workflows
  in order to test a real execution environment.

Dirac desktop (Gennady):
- Implementation based on SOAP done.
- The output XML job descriptions are not yet tested.

Minutes:
Markus Frank