Hi Dannon,

Yes, this is what I was thinking about. The reason is that at the moment the SGE cluster is managed separately. Also we are likely to migrate to a different cluster infrastructure (probably LSF) and I thought that if I set up a master node on AWS I could than "only" have to change the cluster part.

The idea is that if the user metadata is stored on the AWS master node and his/her files on S3 than it would be relatively easy to just "swap" the cluster that is providing the "raw muscle". But I don't have a good understanding of the galaxy architecture and the documentation seems a bit sparse. So any advice on this is most welcome.

-Nick

On Tue, May 28, 2013 at 3:58 PM, Dannon Baker <dannon.baker@gmail.com> wrote:

Hi Nick,

Not sure I completely understand what you're trying to do here. So, you want to have a galaxy head node on AWS that dispatches jobs to a non-AWS private SGE cluster?

-Dannon

On Thu, May 16, 2013 at 12:18 PM, Nikolay N. <nikolay12@gmail.com> wrote:

Hi,

I was contemplating setting up a galaxy master node on a aws instance but executing the workflows on an internal SGE cluster. I am not yet very familiar with galaxy so wanted to ask whether this is feasible (i.e. the API would support it). Any advice/recommendation is most welcome.

many thanks,
Nick

___________________________________________________________
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/