[galaxy-dev] Dynamically decide where a Galaxy tool runs

2013-07-12 Thread Saliya Ekanayake
Hi, I see in documentation that Galaxy tools may be configured to run on a cluster (http://wiki.galaxyproject.org/Admin/Config/Performance/Clusterhttp://wiki.galaxyproject.org/Admin/Config/Performance/Cluster#DRMAA). This is something our research group is interested in, but it's not possible to

Re: [galaxy-dev] Dynamically decide where a Galaxy tool runs

2013-07-12 Thread James Taylor
On Fri, Jul 12, 2013 at 2:42 PM, Saliya Ekanayake esal...@gmail.com wrote: Hi, I see in documentation that Galaxy tools may be configured to run on a cluster (http://wiki.galaxyproject.org/Admin/Config/Performance/Cluster). This is something our research group is interested in, but it's not

Re: [galaxy-dev] Dynamically decide where a Galaxy tool runs

2013-07-12 Thread Saliya Ekanayake
Thank you. I have two follow up questions. 1.) Is there a documentation on writing a deployer, so we can extend Galxy to deploy to a different system, say Amazon EC2 or Azure? 2.) Is it possible to show information about these destinations in the front end UI of Galaxy? Thank you, Saliya On

Re: [galaxy-dev] Dynamically decide where a Galaxy tool runs

2013-07-12 Thread Adam Brenner
This is something our research group is interested in, but it's not possible to specify which cluster the particular tool should run on ahead of time. Incorrect (at least to my knowledge). Using the new way jobs are handled within Galaxy via the XML[1] files you can send specific jobs to