Skip to content

Connect proTES to a TES backend at the DE Node #126

Open

Description

@uniqueg

Why?

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.

How?

  1. Pick the backend: the BIH TESK or the BIH Funnel, whichever accepts proTES' calls. The egress probes of Ask node operators to run the probe nvflare-wes-testbed#3 show which of them run tasks for an LS Login user.
  2. Agree with the Node's operators how proTES authenticates there: proTES calls its backends with its own client credentials token (chore: configure proTES for ELIXIR On-Cloud #31), so the backend must accept proTES' client (an allow-list of clients, as for the FI TESK in Connect proTES to the FI TESK with its service token #111), or proTES exchanges the user's token per backend (feat: exchange user tokens per TES backend protes#501, nice to have). Record the claims the backend checks, without tokens.
  3. 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).
  4. Check that a task submitted to proTES as an ECP_CLN member can run on it, and that the Cloud Registry lists it.
  5. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ecp-wp4: M4.4ELIXIR Compute Platform WP4 milestone/deliverable this issue contributes topriority: highHigh prioritystatus: triageHas not been triaged by admintype: deploymentworkload: hoursLikely takes hours to resolve

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions