Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement kerberos, voms_proxy and rucio for dask workflows #831

Closed
Alputer opened this issue Sep 6, 2024 · 1 comment
Closed

Implement kerberos, voms_proxy and rucio for dask workflows #831

Alputer opened this issue Sep 6, 2024 · 1 comment
Assignees
@Alputer
Labels
workflow/dask

Comments

@Alputer
Copy link
Member

Alputer commented Sep 6, 2024

Currently, we do not create any resource related to kerberos, voms_proxy and rucio authentication mechanisms. Implementation should be relatively straightforward and we already have a reference inside reana-job-controller component for adding related resources, however, testing these mechanisms are not trivial locally which requires additional tricks and effort.
@Alputer Alputer self-assigned this Sep 6, 2024
@Alputer Alputer added this to Dask Sep 6, 2024
This was referenced Feb 10, 2025
Closed
Closed
Closed
@tiborsimko
Copy link
Member

todo: ‏We have only kerberos resource for the whole workflow. For VOMS and Rucio, it would be good to do the same, since for Dask-based workloads, we are looking only at the workflow top level whether Dask should be supported or not.
Please see the PR set that was necessary to introduce Kerberos for the whole workflow: reanahub/reana-workflow-engine-snakemake#44

@github-project-automation github-project-automation bot moved this from Ready for work to Done in Dask Feb 11, 2025
Alputer added a commit to Alputer/reana-commons that referenced this issue Feb 11, 2025
@Alputer
feat(openapi): support VOMS_proxy and Rucio under resources (reanahub…
54af92b 
…#483)

Following Dask integration into REANA, it became necessary for
Dask clusters to be aware of if VOMS_proxy or Rucio is needed
for the whole workflow. Parsing each step in reana.yaml
is not desirable, hence we add voms_proxy and rucio under
global resources definition.

Closes reanahub/reana#831
Alputer added a commit to Alputer/reana-commons that referenced this issue Feb 11, 2025
@Alputer
feat(openapi): add global voms_proxy & rucio fields to reana.yaml (re…
b91b2b4 
…anahub#483)

Following Dask integration into REANA, it became necessary for
Dask clusters to be aware of if VOMS_proxy or Rucio is needed
for the whole workflow. Parsing each step in reana.yaml
is not desirable, hence we add voms_proxy and rucio under
global resources definition.

Closes reanahub/reana#831
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Alputer Alputer

Labels
workflow/dask
Projects
Dask
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tiborsimko @Alputer