Question: Configuring Pulsar Failed
gravatar for yuedeji
19 days ago by
yuedeji10 wrote:

We are trying to move Galaxy jobs run on a remote HPC cluster and return the results back. Pulsar seems to be a good fit. Our current solution is moving Galaxy jobs to a Pulsar server, and then let Pulsar push jobs to a HPC cluster.

Galaxy Server --1--> Pulsar Server --2--> HPC Cluster

However, we failed to make it work at the step 1. We successfully installed both Galaxy and Pulsar, but we failed to make the connect. The configurations are listed below. Could someone tell us where did we configure incorrectly? Really appreciate it!

On Galaxy side, the job_conf.xml file is 1 2 <job_conf> 3 <plugins> 4 <plugin id="local" type="runner" load=""/> 5 <plugin id="pulsar" type="runner" load=""/> 6 </plugins> 7 <handlers> 8 <handler id="main"/> 9 </handlers> 10 <destinations default="local"> 11 <destination id="local" runner="local"/> 12 <destination id="remote_cluster" runner="pulsar"> 13 <param id="url"></param> 14 <param id="private_token">abc</param> 15 </destination> 16 </destinations> 17 <tools> 18 <tool id="msconvert" destination="remote_cluster"/> 19 <tool id="bed_to_bigBed" destination="remote_cluster"/> 20 <tool id="proteinpilot" destination="remote_cluster"/> 21 </tools> 22 </job_conf>

On Pulsar side, the server.ini file is [server:main] use = egg:Paste#http port = 8913 host = localhost ssl_pem = host.pem ...

app.yml is private_key: abc

ADD COMMENTlink modified 18 days ago by Jennifer Hillman Jackson24k • written 19 days ago by yuedeji10
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 71 users visited in the last hour