Overview of the gLite Data Transfer interfaces

gLite File Transfer/Placement Service (FTS/FPS) Documentation

A job (request) submitted to the FTS/FPS service can be in one of the following list of states:

Submitted: The job is submitted, accepted and waiting for channel allocation.
Pending: The job is allocated to a channel and transfers are ready to start. For the FPS, an additional step for logical file names resolution (to SURLs) has been successfully performed.
Active: At least one of the transfers in the job has started.
Done: All transfers were successful. For the FPS, an additional step for catalog update (new replicas registration) is required.
Failed: At least one of the transfers in the job has failed.
Hold: Some transfers inside the job have failed even after retried and were put on hold, waiting for action by a service manager.
Canceling: Cancel was requested for this job. Finished transfers are kept, non-started ones go to canceled immediately, and job waits for on-going tranfers to finish (or aborts them where supported).
Canceled: Result of a cancel request on the job - and after Canceling.
Finished: This is a FPS only state. All registrations of replicas in the catalog were successful.
FinishedDirty: This is a FPS only state. Some of the replica registrations in the catalog have failed.

A file transfer inside a job submitted to the FTS/FPS service can be in one of the following list of states:

Submitted: The file transfer is submitted, accepted and waiting for channel allocation.
Pending: The file transfer has been allocated to a channel and is waiting to start.
Active: The file transfer is ongoing.
Done: The file transfer has finished successfully.
Failed: The file transfer has failed with an unrecoverable error (even after retrying - if that was the case).
Waiting: The file transfer has failed, but with a recoverable error, so the service will retry.
Hold: There were too many retry failures. File transfer waits for action from service manager.
Canceling: Cancel was requested for this file transfer. Next step will either actually aborting the transfer (if supported) or waiting until it is finished.
Canceled: The file transfer has been canceled.
CatalogFailed: This is a FPS only state. Either resolution of a replica from a logical file name or replica registration has failed.
Finished: This is a FPS only state. The transfer is finished (including replica registration).

There are in total 5 different roles that a user can have and acumulate on the service:

Admin: administrator of the service. Can perform any operation, including submitting jobs.
Channel Manager: manages a single channel. Can perform any operation involving the same channel information (query and update) and requests linked to the same channel (query and update/cancel).
VO Manager: manages a single VO. Can perform any operation involving requests linked to the same VO (query and update/cancel). Can also query information about channels.
Submitter User: regular user with additional capability to submit jobs.
Regular User: managers its own job, including query and canceling it.
Vetoed User: has been vetoed in the service. Cannot perform any operation.

Matching roles and operations on the service, one gets: