Galaxy configuration for TESP #72
Conversation
|
I think you are hitting issues with vars precedence, see https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#understanding-variable-precedence |
group_vars/galaxyservers.yml
Outdated
| @@ -34,33 +34,19 @@ galaxy_job_config: | |||
| local_runner: | |||
| load: galaxy.jobs.runners.local:LocalJobRunner | |||
| workers: 4 | |||
| pulsar_tpv_runner: | |||
There was a problem hiding this comment.
I don't think, it's necessary to delete neither TPV runner nor TPV environment. You can just add new runner and environment for TESP and change only the default (line 50). This is global setting for all instances.
There was a problem hiding this comment.
I assume guys are doing this just for testing at the moment, we need to devise a plan how to set up different job_confs anyways...likely put in separate files?
There was a problem hiding this comment.
Well, we can separate job_config to default file in templates/galaxy/config/ and use the lookup-first_found:
"{{ lookup('first_found', ['templates/'+inventory_hostname+'/config/job_conf.yaml.j2', 'templates/
galaxy/config/job_conf.yaml.j2']) }}"
There was a problem hiding this comment.
alternative is to define csnt_galaxy_job_config I guess
|
try now with 5df8abb |
| @@ -206,7 +206,7 @@ galaxy_tmpclean_command: "{{ _galaxy_tmpclean_command[(ansible_os_family | lower | |||
| #galaxy_node_version: "XX.YY.Z" | |||
|
|
|||
| # Where to clone Galaxy from. Backwards compatibility with galaxy_git_repo | |||
| galaxy_repo: "{{ galaxy_git_repo | default('https://github.com/galaxyproject/galaxy.git') }}" | |||
| # galaxy_repo: "{{ galaxy_git_repo | default('https://github.com/galaxyproject/galaxy.git') }}" | |||
There was a problem hiding this comment.
please remove any modifications to this file
galaxy.yml
Outdated
| @@ -105,7 +105,7 @@ | |||
| - galaxyproject.tusd | |||
| - usegalaxy_eu.apptainer | |||
| - galaxyproject.galaxy | |||
| - usegalaxy_eu.tpv_auto_lint | |||
| # - usegalaxy_eu.tpv_auto_lint | |||
There was a problem hiding this comment.
you likely need to revert this now
No description provided.