Some work is already in progress for that. Please see
I don't believe it handles configuration of the cluster backend, but I'm
sure that would be a good addition to the project.
2015-08-05 10:02 GMT-05:00 Tiago Rodrigues Antao <t...@popgen.net>:
> On Tue, 4 Aug 2015 17:26:00 +0000
> "Kandalaft, Iyad" <iyad.kandal...@agr.gc.ca> wrote:
> > As a supplement to Oksana's original inquiry, we, at AAFC, couple
> > Galaxy to SGE and possibly a different grid engine in the future for
> > job scheduling. The old-fashioned way of doing that is to unify
> > storage path and UID/GID between the application server and cluster.
> I am starting to warm of the idea of making a small web interface that
> asks for a few configuration options:
> 1. type of grid engine
> 2. desired docker/galaxy flavour (RNA, exome, WGS, ...)
> 3. ... (e.g. intial admin user and password)
> and would pull Björn's relevant Dockerfile, patch it and generate a new
> one, tailored to the need of the user.
> I think it is impossible to have a set of dockerfiles for all the
> desired configurations (think analysis flavours times number of cluster
> types - for example).
> I will need to implement something like this very soon, and I would not
> mind to do it in a way that the community could reuse...
> So comments would be appreciated...
> 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:
> To search Galaxy mailing lists use the unified search at:
Center for Phage Technology
Rm 312A, BioBio
Texas A&M University
College Station, TX 77843
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:
To search Galaxy mailing lists use the unified search at: