- EOS WebDAV push issue root#1373 (ATLAS don't use push mode except for cloud storage R&D)
- All ATLAS T1 dCache tape endpoints works fine with SRM+HTTP using FTS devel-next
- StoRM tape endpoint doesn't work with SRM+HTTP GGUS:149954
- today this seems to work - what was changed?
- StoRM poor WebDAV performance & efficiency GGUS:150181
- today it looks OK (but tested only with less concurrent connections)
- DPM EPEL testing with fixes for LCGDM-2953 (close called twice -> thread fd mismatch / race)
- FTS Pilot with streaming enabled (failing TPC can fallback to streaming)
- Davix with curl backend release plans?
- FTS servers including devel-next still use neon/0.0.29
- we should use "final" software for our (stress) test
- ? Implementation / configuration status ?
- ATLAS production infrastructure TPC status
- Enabled sites grafana monitoring (7 days)
- GGUS for three remaining T1 with a production endpoint but without HTTP-TPC as primary protocol
- disccussion with RAL to enable a production end point for ECHO
- transfer volume for last 30 days
- 42% SRM
- 31% davs
- 26% gsiftp
- 1% xroot
- storage site preferred TPC protocol
- 38x WebDAV (21x DPM, 12x dCache, 1x Dynafed(?), 1x EOS, 1x StoRM, 2x XRootD)
- 32x SRM+GridFTP (2x DPM, 18x dCache, 12x StoRM)
- 19x GridFTP (8x DPM, 1x dCache, 2x ECHO, 8x XRootD)