An alternative approach (which, granted, has not been publicized much yet) is to use http://bioCloudCentral.org and start your instance via that portal. I just tested it and and instance with Galaxy configured and running was up in about 5 minutes. When filling out the form, you may want to choose the Galaxy AMI (vs. the default CloudBioLinux one - which will also work) by clicking on the Advanced Options and choosing Galaxy Cloud AMI from the drop down menu).

Enis

On Sat, May 19, 2012 at 6:34 AM, Diana Cox-Foster <dxc12@psu.edu> wrote:

Hi, I am finding that the run time on the public galaxy is exceptionally long, with job submitted yesterday still waiting to start.

Given that I need to have analyses performed more quickly, I have tried to use Galaxy on the Cloud. Is this the following still the current version of cloudman to use?

Current AMI:

AMI: ami-da58aab3

Name: 861460482541/galaxy-cloudman-2011-03-22
I have set up instances for this version and have waited for over an hour for them to load, with multiple attempts to get the websites to open. All status indicators say that the instance is running.

Any insight welcomed--- thanks--- Diana

**********************************
Diana Cox-Foster, Professor
office: 536 ASI Bldg

MAIL:
501 ASI Bldg
Department of Entomology
Penn State University
University Park, PA, USA 16802

email: dxc12@psu.edu
office phone: 814-865-1022
dept. phone: 814-865-1895

___________________________________________________________
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org. Please keep all replies on the list by
using "reply all" in your mail client. For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

http://lists.bx.psu.edu/