On Fri, Nov 2, 2012 at 9:53 AM, Oleksandr Moskalenko <o...@hpc.ufl.edu> wrote:
> The dynamic runner is alive and well thanks to the continuous work of the
> author John Chilton and others. For instance, yesterday John committed code
> to galaxy-central that propagates tracebacks from the dynamic job runner's
> job rules script to the logs and also allows us to raise explicit exceptions
> from the job rules script thus making it possible to fail a job and print an
> arbitrary message in the job history's error message as well as making it
> much easier to debug the job rules.
> John's information is right on spot. I can also share my rules script with
> you. I've completely switched our production instance to the dynamic runner.
> It allows me to set the resource requests based on datasets (blast query at
> the moment, but I'm getting to the point of using the database as well),
> resources allocated to the user's group or a secondary group and so on as we
> well as check internal ACLs for tool usage restrictions and such and send
> jobs to specific queues or compute nodes as necessary.
> I think your goals will inevitably bring you to the dynamic runner and it's
> not a bad thing.
Please, could you share your rules related to blast. I would love to
take a look at them.
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: