galaxyproject / galaxyproject/galaxy

BYOC usecase - feature request

Open
#16,596 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.9k
Forks
1.2k
Avg merge
2d 16h
Merged PRs (30d)
169

Description

**Describe the bug**
For the BYOC and in the case of the actual end-user (read e.g. researcher) to be able to add his own HPC cluster to submit jobs to via Galaxy (e.g. via the ARC runner which is ongoing in development) it would be convenient that the user himself can add his X number of compute resources that he can use.

The current functionality in the user_preferences_extra_config.yml is not sufficient to do this. One could have a single text type and the user could add *one* compute resource, but that is not flexible a-la:

```
distributed_arc_compute:
description: Use distributed ARC compute resources
inputs:
- name: remote_arc_resources
label: Add your remote resource url
type: text
required: False
```

What instead would be useful is to have something like the Address filed is currently, where there is a "+" button that the user can press on multiple times to add several addresses.

Furthermore, from this list, I would like that the user could select one of them to be used as a default compute resource. Or let TPV select one for him.

**Screenshots**
Example of what is possible today - but is too limited
![Screenshot 2023-08-25 at 15 47 39](https://github.com/galaxyproject/galaxy/assets/22190352/06eced00-aa13-4ecd-939c-2944ac155277)

**Additional context**
This is in the context of the ARC runner which is in development, and the ESG project. Can surely also be useful not only for the ARC runner, but in general for the BYOC use-case of the ESG.

Contributor guide

Open the contributing guide

Research direction

Start with user_preferences_extra_config.yml and trace how the existing Address field supports adding multiple values. Then inspect the ARC runner and TPV entry points to understand how a selected default resource is consumed. Done means users can add multiple remote ARC resources and choose a default, or have TPV select one.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, yaml
Domain
backend, hpc
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.