Hi All,
Pete asked me to chair the xrootd meeting while he is gone.
The next meeting on xrootd development, testing, deployment and monitoring
will be Tuesday, 12 October, 2004 at 10:15 CA, 19:15 Europe and 18:15 UK.
The location at SLAC is SCS conference room B.
The connection info for this meeting is:
phone: +1-510-665-5437
passcode: 4465
Agenda:
o New development/features
o status of posix-compatible client
o xrdcp
o "XTNetAdmin" interface (probably needs a new name)
o proxy support
o server side monitoring - Jacek
o client side monitoring support
o asynchronous I/O
o unsolicited requests
o administrative interface - Jacek/Artem
o bytes/read printout as file is closed?
o updates needed by Castor people
o latest fixes - Fabrizio, Andy
o progress on the problem list
o testing asynchronous mode
o Sites
o Example configurations
o getting rid of feature in BaBar KanAccess.cfg that allows "localroot"
to be specified there
o SLAC
o turning off non-xrootd log rotation for olbd - Andy/Bill
o olb03/olb04/kanolb-a renaming (arrghh!)
o Cornell
o Padova - Fulvio/Guglielmo
o problems reported by Antonio:
http://babar-hn.slac.stanford.edu:5090/HyperNews/get/KanSOS/393.html
o What are plans in Padova?
o CNAF
o problems
o olbd crash
o xrootd on SAN servers?
o RAL - Chris/Manny
o new disk space?
o import of skims
o rpm structure (libstdc++, config files)
o cleaning up classic Kanga data
o moving to latest version and cleanup of config files?
o In2p3 - Jean-Yves
o problems with new versions?
o cleanup of config files (including BaBar KanAccess.cfg file if
need be)
o access statistics
o FZK
o cleaning up classic Kanga data
o plans?
o ganglia/monitoring of kanNNN servers at SLAC - Yemi
o adding back xrootd metrics
o metrics for staging?
o monitoring of scratch area, etc.
o monitoring of xrootd versions and alarms when they fail the "Sesame
Street test" (Should be possible after yesterday's restart)
o monitoring of total BaBar data (/store/PR, /store/SP, /store/SPskims,
/store/PRskims, /store/users, /store/awg), #files and data volume
o Updates to presentation
o renaming of servers during/after shutdown (arrghh!)
o alarms?
o monitoring of #file descriptors/TCP connections, etc.
o xrootd procedures
o restart of servers (deployment of new versions)
o problems with particular data servers
o adding a new server
I have almost certainly forgotten some things, so please feel free to bring
anything important up during the meeting.
Cheers,
Wilko
|