Current FTS planning

1. Current FTS planning Gavin McCance & Paolo Badino ATLAS DDM session 14 September 2006

2. Plans: current • Support • Support of CERN FTS instance and expert support for T1 instances • Patches and fixes as required • Inter-site export support to debug problems • Next user-visible features • Delegation in FTS • Requires earlier deployment of new client version (to ensure backwards compatibility) • Schema to support the new features • Planned for certification end September • SRM v2.2 support • Both SRM v2.2 and SRM v1.1 supported • Cleaner error classes and messages • Cleaner SRM interactions • Planned for certification end October ATLAS DDM meeting

3. Plans: next • Better transfer service monitoring is then the highest development priority • We will not achieve the agreed WLCG service availability targets without this • We have a reasonable set of internal alarms and procedures to check for problems on the FTS daemons or hardware • These need to be exposed to the tier-1 sites running FTS • However, the current overall service takes an unsustainable amount of ‘expert’ effort to debug inter-site problems • Improved SAM tests • SAM team already working on this • Properly exposing the FTS view of the transfers • Automatic reporting of rates / failure rates (per site / per VO) • Alarms to CIC-on-duty and sites if channels go bad • Top-3 things that are broken on your SRM ATLAS DDM meeting

4. Plans: after • Next things • Optimized SRM interaction: split preparation from transfer • Pre-staging support • Notification of finished jobs (so you don’t have to poll) • Catalog plug-ins • LFC in particular • Examine current FTS deployment model • (it doesn’t fit so well for all VOs) • Improve FTS discovery model (“where do I send my job?”) • Better service controls • Make it easier to run and debug problems • Work to support an open-source database is starting ATLAS DDM meeting