On Jul 31, 2013, at 2:22 PM, Ben Gift wrote:
> I'm setting up Galaxy and Torque with my cluster and I was wondering if I
> could set it up so that nodes could be assigned for a whole history. This way
> I can re-run histories on certain nodes for benchmarking runtimes.
>
> It seems that the closest I can get with the built in functionality is
> specifying nodes on a per-tool basis, which is good but it would be painful
> to have to specify this for each tool I use in a pipeline each time.
>
> So how difficult would it be for me to add this feature, and which files
> should I start with in the code base? Or have I misunderstood and this is
> actually built in?
Hi Ben,
This can be accomplished by writing a dynamic job destination plugin. The
documentation for that feature can be found here:
http://wiki.galaxyproject.org/Admin/Config/Jobs#Dynamic_Destination_Mapping
--nate
>
> Thanks
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> http://lists.bx.psu.edu/
>
> To search Galaxy mailing lists use the unified search at:
> http://galaxyproject.org/search/mailinglists/
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
