I would like to run the Galaxy framework on server A, while performing all
of the jobs on server B using ssh.
Looking at the documentation here:
seems like it should be possible. However, the documentation states that
the cli runner requires, at a minimum, two parameters, one for the shell
(which I'm selecting SecureShell) and a Job plugin. I'm not sure what this
should be since the ones available are Torque, Slurm, and SlurmTorque and
I'm not running any of these. Can anyone give me any hints? My current
job_conf.xml looks like this:
<!-- <plugin id="local" type="runner"
<plugin id="cli" type="runner"
<destination id="cli_default" runner="cli">
As an alternative, in a tool xml I tried directly sshing between the
<command> tags e.g.:
<command>ssh galaxy@serverB 'sh $__tool_directory__/runTool.sh --verbose
> $output 2>&1' </command>
This appears to work. Is it possible to "inject" this ssh command into tool
execution in Galaxy?
I was looking to do this to avoid having to install a scheduler like SGE or
using Pulsar. Any suggestions would be greatly appreciated.
Our production Galaxy server has been running smoothly on a single
multicore box with Red Hat 6.7. As this box gets older and older, it is
in now time to replace it.
At the same time, we are also considering switching the operating system
to CentOS 7. Has anyone switched a production installation from Red Hat
to CentOS ?
'Galaxy Main' is running on CentOS, isn't-it?
I am also interested in plain numbers: how many of you are using Red
Hat, how many CentOS and which version for your production server. I
will probably need such numbers to convince our IT department.
There is no need to reply to the mailing list, just reply to me
(hrh(a)fmi.ch) and if I get enough I will then collate and anonymize all
the data and post back. Maybe we can even add such information to the
Thank you very much for your help
Hans-Rudolf Hotz, PhD
Friedrich Miescher Institute for Biomedical Research