proTES¶
proTES is a gateway for GA4GH TES services. It receives task requests, applies middleware (plugins) and forwards each task to one of the TES services that it knows.
Role in the deployment¶
proTES sits in front of the Nodes' TES services: clients send their tasks to proTES, and proTES distributes them to the Nodes. It can read the verified TES services of a Cloud Registry, so that a new Node is used once it is registered and verified; the ELIXIR On-Cloud's proTES lists its TES services in its configuration instead (see below). Register a proTES that you deploy in the Cloud Registry like any other TES service, and end every upgrade or change of it by updating its entry, or checking that sync did (see After a deployment or an upgrade).
Docs¶
- proTES docs
- Deployment (Helm chart)
- Configuration, including the discovery of TES services in a Cloud Registry
- Plugins
In the ELIXIR On-Cloud¶
As of November 2026:
| What | Value |
|---|---|
| Address | https://protes.rahtiapp.fi/, TES API at /ga4gh/tes/v1 |
| Version | proTES 0.6.0 |
| Access | LS Login access tokens of members of the group ECP_CLN:EOC-Compute, issued to a client that it accepts, such as Krini's (see Researchers) |
| TES services | the TESK of the Finnish Node, listed in its configuration |
| Discovery in the Cloud Registry | off |
A Node's TES service is added to the configuration when its admins ask for
it and the service requires LS Login tokens (see Get added behind the
gateway).
The service info of proTES (GET /ga4gh/tes/v1/service-info) lists the TES
services that it uses. The rest of its configuration, such as its plugins
and how it authenticates at its TES services, is tracked in
generic-issues#31.