BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//CERN//INDICO//EN
BEGIN:VEVENT
SUMMARY:DM Cluster Meeting
DTSTART;VALUE=DATE-TIME:20050316T090000Z
DTEND;VALUE=DATE-TIME:20050316T100000Z
DTSTAMP;VALUE=DATE-TIME:20130522T144920Z
UID:indico-event-a051763@cern.ch
DESCRIPTION:Regular Cluster Meeting\n\n- CVS Usage\n- Documentation topics
 \n- MAPS\n- AOB\n\nhttp://indico.cern.ch/conferenceDisplay.py?confId=a0517
 63
LOCATION:CERN 513-1-23
URL:http://indico.cern.ch/conferenceDisplay.py?confId=a051763
END:VEVENT
BEGIN:VEVENT
SUMMARY:DM Cluster Meeting
DTSTART;VALUE=DATE-TIME:20050323T090000Z
DTEND;VALUE=DATE-TIME:20050323T100000Z
DTSTAMP;VALUE=DATE-TIME:20130522T144920Z
UID:indico-event-a051877@cern.ch
DESCRIPTION:Weekly Data Management Cluster Meeting\n\n- Baseline Services 
 (Erwin or Frederic invited)\n- Presentations \n   Frederic asked for the f
 ollowing\n  I would need some slides for a presentation in Barcelona At th
 e \n  beginning of April. Could I ask you (or your people) to have a \n  d
 ozen of technical slides explaining how\n   -) Catalog is working (incl. A
 CL)\n   -) gLite I/O is working\n   -) how gLite I/O uses catalogs\, FAS\,
  SRM\, ...\n\n  The level of technicalities should be at the level of Gavi
 n's slides for Lyon.\n\nAOB\n\nhttp://indico.cern.ch/conferenceDisplay.py?
 confId=a051877
LOCATION:CERN 513-1-23
URL:http://indico.cern.ch/conferenceDisplay.py?confId=a051877
END:VEVENT
BEGIN:VEVENT
SUMMARY:DM Cluster Meeting
DTSTART;VALUE=DATE-TIME:20050330T080000Z
DTEND;VALUE=DATE-TIME:20050330T090000Z
DTSTAMP;VALUE=DATE-TIME:20130522T144920Z
UID:indico-event-a051975@cern.ch
DESCRIPTION:Networking information needed for Transfer\n\nhttp://indico.ce
 rn.ch/conferenceDisplay.py?confId=a051975
LOCATION:CERN 513-1-23
URL:http://indico.cern.ch/conferenceDisplay.py?confId=a051975
END:VEVENT
BEGIN:VEVENT
SUMMARY:DM group meeting
DTSTART;VALUE=DATE-TIME:20060504T083000Z
DTEND;VALUE=DATE-TIME:20060504T103000Z
DTSTAMP;VALUE=DATE-TIME:20130522T144920Z
UID:indico-event-a062288@cern.ch
DESCRIPTION:http://indico.cern.ch/conferenceDisplay.py?confId=a062288
LOCATION:CERN 28-R-006
URL:http://indico.cern.ch/conferenceDisplay.py?confId=a062288
END:VEVENT
BEGIN:VEVENT
SUMMARY:Data Management Cluster Meeting
DTSTART;VALUE=DATE-TIME:20060512T083000Z
DTEND;VALUE=DATE-TIME:20060512T103000Z
DTSTAMP;VALUE=DATE-TIME:20130522T144920Z
UID:indico-event-a062379@cern.ch
DESCRIPTION:Agenda:\n\nOutstanding testing: GFAL\, lcg_utils\, DPM\, LFC\n
 -> Verify that with recent changes for build system\,\n   DPM/LFC still pr
 oduce good builds on LCG build system\n-> Fixes from Jiri for GFAL\, lcg_u
 tils\n-> Forthcoming fixes for DPM dpm_abortreq() and dpm_abortfiles()\n->
  GridFTP2\n\nWork for: GFAL\n-> SRMv2 (going on now)\n-> thread safety\n->
  allow (complete) rootd interface to GFAL\n\nWork for: lcg_utils\n-> threa
 d safety\n-> retries\, using different file replicas\n-> support for multi
 ple LFC replicas\n\nxrootd:\n-> produce a DPM aware xrootd\n\nWork for: LF
 C / DPM\n-> backup of database(s) (inparticular the namespace db)\n\nLFC D
 eployment\n-> What's the status / any problems?\n\nx86-64 bit support:\n->
  implies a change to VDT-1.3 (essentialy to globus 4\, non WS only)\n-> so
 me work/checking for eveything that touches globus\n-> anything else?\n\nA
 OB\n\nhttp://indico.cern.ch/conferenceDisplay.py?confId=a062379
LOCATION:CERN 28-R-006
URL:http://indico.cern.ch/conferenceDisplay.py?confId=a062379
END:VEVENT
BEGIN:VEVENT
SUMMARY:DM Group Meeting
DTSTART;VALUE=DATE-TIME:20060609T120000Z
DTEND;VALUE=DATE-TIME:20060609T140000Z
DTSTAMP;VALUE=DATE-TIME:20130522T144920Z
UID:indico-event-a062700@cern.ch
DESCRIPTION:** Agenda **\n\n+ Review of current position with respect to t
 he workplan\n * Where are we with respect to what was written?\n * How doe
 s the workplan need to be changed? (Following dicussions also\n   relevant
 : Keep this as open item that will evolve during the discussions)\n\n+ Sup
 port for lcg_utils\n * What should be the relative priority\n * Who suppor
 ts?\n\n+ Impact of arrival of SRM v2.2 on work done or being done on GFAL\
 n * Is the devleopment plan for the GFAL changes clear?\n\n+ Planning for 
 work on DPM and DPM's SRM to support SRM v2.2\n * What commitments do we h
 ave to the SRM group (e.g. time at which providers     \n   should have SR
 M with first few 2.2 methods available)\n * Can we/should we fullfil those
  commitments given current priorities?\n * What should our own timetable b
 e for SRM v2.2 deveopment and who will\n   work on it?\n\n+ AOB\n\nhttp://
 indico.cern.ch/conferenceDisplay.py?confId=a062700
LOCATION:CERN 28-R-028
URL:http://indico.cern.ch/conferenceDisplay.py?confId=a062700
END:VEVENT
END:VCALENDAR