Show Children Hide Children

Main FTS Pages
FtsRelease22
Install
Configuration
Administration
Procedures
Operations
Development
Previous FTSes
FtsRelease21
FtsRelease21
All FTS Pages
FtsWikiPages
Last Page Update
OliverKeeble
2015-09-08

FTS2 IS NOW OBSOLETE PLEASE SEE FTS3 FOR THE LATEST VERSION!!!

File Transfer Service

shadow_logo_huge.png

Current version

The current version of the FTS software, including all documentation: FtsRelease21.

For updates please refer to DMFtsPatchStatus

The next release is FtsRelease22 with the documentation:

Bug and problem reporting

  • All operational problems with the FTS service should be submitted via the GGUS portal.

  • All software problems should be submitted and are tracked in savannah.cern.ch.

  • If you don't know whether the problem is an operational or a software issue, submit it via the GGUS portal.

Software requirements tracking

The current prioritized list of software improvements requested by the EGEE VOs and tracked by the Technical Coordination Group on the JRA1 workplan:

FTS Overview

There are four components to any of the FTS Service. Any one node can run any number of components (although this has not been tested in full production).

FTS Web service ("FTS")

This component allows users to submit FTS jobs and query their status. It is the only component that users interact with. It runs as a Tomcat web-application (Java based). The node also has a local BDII with a GIP publishing the necessary information about this FTS server (the site BDII should configured to pull this information).

Referred to throughout a node type FTS.

fts-webservice-deployment.png

FTS agents ("FTA")

These are the back-end agents that do the work of the service. Each agent runs as a distinct daemon, and you may have as many agents daemons running on a node as it can support. There are two main type (channel and VO agent) which may be mixed across nodes as necessary.

Referred to throughout a node type FTA.

FTS agents: channel agent

Each network channel, (e.g. "transfers from CERN to RAL") has a distinct daemon running transfers for it. The daemon is responsible for starting and controlling transfers on the associated network link. When a transfer is started, a controlling process for that transfer is (double) forked from the controlling agent.

There should be one agent daemon for every channel that the FTS has defined, each managing a different channel.

Since they produce a large number of forked processes, the channel agent daemons are generally spread over a number of agent nodes ~equally.

fts-agent-deployment.png

FTS agents: VO agents

Each VO served by the FTS service has a distinct VO agent daemon running for it. This performs house-keeping tasks for that VO. There should be one VO agent daemon for every VO that will use the FTS service.

The VO agents consume very little resources and can be put freely on any agent node in the cluster.

FTS Monitor ("FTM")

This provides an Apache httpd server which serves monitoring data to a variety of clients. Most of the served data is statically produced by (frequently running) cron-script or daemons (rather than CGI-based).

It currently provides a GridView monitoring feed into the WLCG monitoring system and a couple of modules for basic service monitoring. It is intended that new monitoring modules can be dropped in as needed.

Referred to throughout a node type FTM.

Other links

Operational notes

The current status of the CERN-PROD service is described in TransferOperations.

FTS testing


Last edit: OliverKeeble on 2015-09-08 - 15:12
Number of topics: 1

Maintainer: RosaGarciaRioja

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng fts-agent-deployment.png r1 manage 145.3 K 2009-05-07 - 16:49 AkosFrohner  
PNGpng fts-webservice-deployment.png r1 manage 99.0 K 2009-05-07 - 16:49 AkosFrohner  
PNGpng shadow_logo_huge.png r1 manage 31.5 K 2006-10-10 - 14:04 PaoloBadino fts logo
Edit | Attach | Watch | Print version | History: r42 < r41 < r40 < r39 < r38 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r42 - 2015-09-08 - OliverKeeble
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback