FTS Changes from 1.4 to 1.5

This page describes the changes from FTS version 1.4 to 1.5. It complements the 1.5 Release Notes available on the gLite home page.

Functional changes

The 1.5 release is mostly a maintenance release of 1.4.1 with bugfixes and some internal refactoring to support the future introduction of new features.

SRM copy support

The problems with SRM copy have now been fixed. The performance of SRM copy should be better.

Improved retry logic

The default retry logic is now improved. The FTS should handle the "file exists, cannot write" case better now. The retry policy is now a plugin python script that can be configured per VO.

Deployment changes

The deployment model of the FTS components is the same.

YAIM support

The configuration has been changed to YAIM for better integration with LCG.

FTS info provider

The YAIM configuration also configures an FTS info provider in order to register the FTS service endpoints and the managed channel into the information system.

Upgrading

The upgrade procedure is described in FtsServerUpgrade14to15. There are some RPM / apt issues with the upgrade that you should take care with (with external dependencies). The upgrade involves both a DB schema upgrade and a configuration file change (to YAIM format); there is no automatic migration script.

If you are still running 1.1.2 or 1.3, we recommend a clean install (see FtsServerInstall15).

Client compatibility

Neither the web-services API nor the CLI has changed.

An additional CLI tool is provided: glite-transfer-discovery to query the EGEE.BDII for channel endpoints information. It uses the information published by the FTS info provider

Known Issues

The improved retry logic doesn't yet evaluate srmcopy error messages, therefore the recovery rate for srmcopy channels is low.