80 likes | 107 Views
Updates on FTS production status, software improvements, deployment schedule, and status of SRM interaction tests for CERN and T1 sites. Includes details on FTS 2.0, deployment progress, certification, compliance, and pending issues resolved.
E N D
FTS status Paolo Tedesco GSSD meeting - 12 April 2007
FTS production status • CERN and all T1 sites using FTS 1.5 • (from gLite release 3.0) • > 6 PB exported from T0 since start of SC4 • FTS infrastructure runs well • CERN and T1 sites ~ understand the software • Most problems ironed out last year • Remainder of the problems understood with experiments and we have a plan to address them • Still problems with ‘overall transfer service’ • We’ve started to systematically follow-up SRM problems detected by FTS
FTS 2.0: what • Based on feedback from Amsterdam workshop • Certificate delegation • Security issue: No more MyProxy passphrase in the job • Improved monitoring capabilities • This is critical for the reliability of the ‘overall transfer service’ • Alpha SRM 2.2 support – see later… • Better database model • Improved performance and scalability • Better administration tools • Make it easier to run the service • Placeholders for the future functionality • To minimize the service impact of future upgrades
FTS 2.0: schedule • FTS 2.0 currently deployed on pilot service@CERN • In testing since December: running dteam tests to stress-test it • This is the ‘uncertified’ code • Open pilot to experiments to verify full backwards compatibility with experiment code • Tested OK with Atlas, others happening now • Release subject to successful verification • Deployment at CERN T0 scheduled in April 2007 • RAL are running ‘pre-production’ in parallel • Roll-out to T1 sites a month after that • We expect at least one update will be needed to the April version
FTS - SRM 2.2 interaction tests • Purpose: test FTS interaction with existing SRM implementations to verify FTS's expectations are met: • Conformity to specification • handling of bad / unexpected values • Required parameters • source file size obtained from srmStatusOfGetRequest or from srmLs • Possibility to clean-up • srmAbortRequest / srmRm
Tests procedure • Set of transfers using a list of endpoint definitions • DPM • CASTOR • DCACHE • STORM • Analyse logs and soap messages • Current status updated athttps://twiki.cern.ch/twiki/bin/view/EGEE/FTSSRMValidationStatus
Current situation • SRM compliance issues solved • STORM: FILETYPE_DIRECTORY in srmLs operations • CASTOR: LINK in srmLs, no file size in srmStatusOfGetRequest operations • Pending issues • STORM: "This SRM put request contained nothing to process" • CASTOR: “putDone without a put”
Summary • Major new release • Delegation • Alpha SRM 2.2 support • Performance and usability • Better monitoring of transfers • Schedule: April at CERN, May at T1s • SRM 2.2 / FTS integration testing on track • Many issues resolved in last few months