Show Children Hide Children FtsANoteOnVersions FtsClientCompatabilityMatrix FtsDbCodeGuide FtsDiagnosisScripts FtsFTM FtsMenu FtsRelease15 FtsRelease20 FtsRelease21 FtsServerDeployExampleTier1 FtsServerInstall21 FtsServiceDependencies FtsTier0Deployment FtsTutorial FtsUsefulCommands FtsVomsRoles FtsWikiPages TransferOperations
Main FTS Pages
Previous FTSes
All FTS Pages
Last Page Update

WLCG FTS Service Description

This page defines the installation, configuration and the procedures related to the WLCG FTS service.

This page documents the current FTS situation.

FTS Deployment

FTS Releases

The current FTS release is 2.1

Release Release Notes Install Guide Admin Guide ProceduresSorted descending
1.3 FtsRelease13 FtsServerInstall13 FtsServerAdmin13  
1.1.1 FtsRelease112 FtsServerInstall112 FtsServerAdmin112  
2.1 FtsRelease21 FtsServerInstall21 FtsServerAdmin20 FtsProcedures20
2.0 FtsRelease20 FtsServerInstall20 FtsServerAdmin20 FtsProcedures20
1.5 FtsRelease15 FtsServerInstall15 FtsServerAdmin15 FtsProcedures15
1.4 FtsRelease14 FtsServerInstall14 FtsServerAdmin14 FtsProcedures14

FTS Component Overview

There are four components to any of the FTS Service. Any one node can run any number of components.

FTS Web Service

This component allows users to submit FTS jobs and query their status. It is the only component that users interact with.

FTS Channel Agents

Each network channel, e.g CERN-RAL has a distinct daemon running transfers for it. The daemon is responsible for starting and controlling transfers on the associated network link.

These nodes run one daemon for every channel that the CERN-PROD FTS is responsible for. The channel agent daemons are spread over a number of nodes ~equally. The nodes also run one agent for every VO that the CERN-PROD FTS is responsible for; there are current 5 VOs. The VO agents are all run together on the same node.

FTS VO Agents

This component is responsible for VO-specific parts of the transfer (e.g. updating the replica catalog for a given VO or applying VO-specific retry policies in case of failed transfers). Each VO has a distinct VO agent daemon running for it.

FTS Monitor

This provides GridView monitoring feed into the WLCG monitoring system and a couple of modules for basic monitoring. It is intended that new monitoring modules can be dropped into this as needed (it's expects a basic apache server to be installed).


FTS PL/SQL code guidelines are described in FtsDbCodeGuide.

Maintainer: GavinMcCance, SteveTraylen

This topic: LCG > FtsWlcg
Topic revision: r28 - 2008-08-12 - AkosFrohner
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback