Show Children Hide Children

FTS Changes from FTS 1.5 to FTS 2.0

Deployment Changes

YAIM Parameters

VOAgents with Yaim

VOAGENT_PYTHON is now VOAGENT.

This might work... sed 's/VOAGENT_PYTHON/VOAGENT/g'

FTA_MACHINES="ONE"
FTA_AGENTS_ONE="ATLAS ALICE"
FTA_ATLAS="VOAGENT_PYTHON"
FTA_ALICE="VOAGENT_PYTHON"
FTA_TYPEDEFAULT_VOAGENT_PYTHON_ACTIONS_RETRYMODULE="smarter_retry"
FTA_ATLAS_ACTIONS_ENABLEUNKNOWNSOURCE="true"

FTA_MACHINES="ONE"
FTA_AGENTS_ONE="ATLAS ALICE"
FTA_ATLAS="VOAGENT"
FTA_ALICE="VOAGENT"
FTA_TYPEDEFAULT_VOAGENT_ACTIONS_RETRYMODULE="smarter_retry"
FTA_ATLAS_ACTIONS_ENABLEUNKNOWNSOURCE="true"

YAIM target

The configuration targets are FTS2 and FTA2 instead of FTS and FTA, respectively.

This is a workaround due to the fact the both FTS 1.5 and FTS 2.0 configuration scripts need to be maintained on the same (glite 3.0) branch of the single YAIM RPM.

Running the wrong target will lead to a strange configuration...

Internal Changes

• Major improvements to the DB model to reduce DB load
• Fixes and cleanup of transfer-url-copy-component
  • N.B. this means the transfer-url-copy per-transfer logs are now in a different and (hopefully?) clearer format.
• Much more monitoring information now stored in the DB schema
  • Hopefully no longer any need to parse the logfile to get this information out
• Transfers exec rather than fork now which should result in better memory usage and less page copying.
• Possibility to examine detailed state of failed transfers (as admin) - memory mapped file reader.

Functional Changes

• Client proxy delegation supported in client and server
• Cleaner categorization of error messages
• glite-transfer-channel-audit command shows audit log of changes made to a channel
• glite-transfer-channel-list -x shows extra information about the channel
• glite-transfer-channel-set -m "Because I want to" expects you to say why you made the relevant channel change
• glite-transfer-channel-setvolimit allows you to set transfer caps per VO.
• glite-transfer-getroles -u allows you to explicitly ask for the privileges given to a specified user.
• SRM 2.2 beta support
• [... finish full list of changes]

Client compatibility

The 1.5 and 2.0 clients and servers servers binaries are fully backwards compatible.

See FtsClientCompatabilityMatrix for more details.

In particular, the existing FTS 1.5 client (from the gLite 3.0.2 update 5, UI version 3.0.6-0, released 11 October 2006) is compatible with the FTS 2.0 server (i.e. the server will run fine in this legacy mode). Note the additional number of reported states below - in order to work properly with an FTS 2.0 server, you will need to make the minimal changes described below to your application to support these additional states.

API change: the number of states in the exposed state machine has been increased:

• The Pending state is now Ready (Pending is now an intermediate state).
• The Done terminal state is now Finished. (Done is now an intermediate state which no-ops to Finished very quickly).
• There is an additional terminal state FinishedDirty.

to achieve maximum compatibility, clients are requested to make the minimum following changes:

• Where you check for "Pending", check for "Pending" || "Ready"
• Where you check for "Done", check for "Done" || "Finished"
• Where you check for "Failed", check for "Failed" || "FinishedDirty"

this means your application will be compatible with the states reported by both FTS 1.5 and by FTS 2.0.

FtsStateMachine20 describes the state machine and transitions in more detail.

FtsRelease20SpaceTokenCompatibility describes a short note about space tokens for SRM 2.2 and which version of the client and server you will need.

Upgrade path

1. Users are requested to make the above minimal changes to their application to support the new states. This will allow your software using the existing FTS 1.5 client to work fine with FTS 2.0 servers. DONE, by all experiments

2. Upgrade to the new client version in the latest FTS 2.0 gLite release (gLite 3.0.2 update 24 released 14 May 2007). This client is compatible with both the FTS 1.5 and FTS 2.0 servers, and with existing options in your application code, will run in legacy mode.

3. Drop the proxy password option (-p in glite-transfer-submit) when submitting to an FTS 2.0 server and the FTS 2.0 client will switch to using the new proxy delegation mode.

-- GavinMcCance - 15 June 2007