You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Connect proTES to a TES backend at the DE Node #126
The M4.4 chain test (#44) needs tasks that run through the proTES gateway on the backends of at least two Nodes. So far proTES is to use only the FI TESK (#111). The DE Node (BIH) runs a TESK (2.0.0, requires LS Login tokens) and a Funnel, both reachable from outside, so one of them can be the second backend. Part of M4.4.
Add the backend to proTES' backends with the matching auth setting and run proTES' integration check against it (a task that completes, one that fails, one cancelled).
Check that a task submitted to proTES as an ECP_CLN member can run on it, and that the Cloud Registry lists it.
Record the configuration here (no secrets), and the rollback: remove the backend from proTES' backends.
Acceptance criteria
Tasks sent to proTES run on a TES backend at a second Node (besides FI) with tokens; the integration check passes.
The configuration is recorded.
Dependencies:#31 (proTES client credentials), the Node operators' configuration; see also #111.
Activity