The ec2 instance is your personal instance that you have complete control over
for customization, you don't have a personal quota, nobody else will be waiting
in line to run jobs, etc.
The server at main.g2.bx.psu.edu is our public galaxy instance that we provide
and administer, but because it's a public service we do have quotas and
sometimes processing queues, and so on.
Regarding data security, here's the relevant snippet from the public galaxy
"""This is a free, public, internet accessible resource. Data transfer and data
storage are not encrypted. If there are restrictions on the way your research
data can be stored and used, please consult your local institutional review
board or the project PI before uploading it to any public site, including this
Galaxy server. If you have protected data, large data storage requirements, or
short deadlines you are encouraged to setup your own local Galaxy instance or
run Galaxy on the cloud."""
Lastly, for aws, you don't *have* to terminate the ec2 instance and start it
back up when you want to use it, but remember that for every hour of use Amazon
does bill you. If you aren't running any jobs on the instance, it would make
sense to terminate it and start it back up when you want it again.
On Dec 20, 2012, at 1:52 PM, "Sun, Wenping [USA]" <sun_wenp...@bah.com> wrote:
> When I use main.g2.bx.psu.edu to access the galaxy, I did see the ec2
> instance initiated from my aws console. Why this happen and what this
> instance doing?
> Meantime, what is the data security on main.g2.bx.psu.edu?
> If I use aws instance for the data works, do I have to terminate the ec2
> instances/cluster and then launch the instance every time?
> Thank you,
> -----Original Message-----
> From: Dannon Baker [mailto:dannonba...@me.com]
> Sent: Thursday, December 20, 2012 1:43 PM
> To: Sun, Wenping [USA]
> Cc: galaxy-u...@bx.psu.edu
> Subject: Re: [External] Re: [galaxy-user] galaxy cloudman login and aws
> Ahh, ok. If you want to work exclusively on main and don't have the need for
> a cloud instance, just terminate (and permanently delete, if desired) cloud
> instances through the cloudman interface and keep using main.g2.bx.psu.edu.
> On Dec 20, 2012, at 1:41 PM, "Sun, Wenping [USA]" <sun_wenp...@bah.com> wrote:
>> Thanks and my question is--
>> How to shutting down the cloud if working on main.g2.bx.psu.edu?
>> -----Original Message-----
>> From: Dannon Baker [mailto:dannonba...@me.com]
>> Sent: Thursday, December 20, 2012 1:38 PM
>> To: Sun, Wenping [USA]
>> Cc: galaxy-u...@bx.psu.edu
>> Subject: [External] Re: [galaxy-user] galaxy cloudman login and aws
>> It looks like you've worked on both the public galaxy site we provide
>> (main.g2.bx.psu.edu) and your own cloud instance. Data on the public
>> instance won't be automatically migrated to the cloud instance and vice
>> All work done on the cloud site will remain there and persist after
>> termination and restart of that cloud cluster. Work on main.g2.bx.psu.edu
>> is completely separate and will remain there.
>> On Dec 20, 2012, at 12:44 PM, "Sun, Wenping [USA]" <sun_wenp...@bah.com>
>>> Dear galaxy members,
>>> I have question on galaxy running on cloud with the issue of authorization
>>> I have launched aws galaxy cloudman instances to work with, shutting
>>> down the cluster afterwards. Then the 2nd time here are the steps
>>> that I did-
>>> 1. Launch the galaxy at cloudlaunch site
>>> 2. Register and then log in
>>> 3. Worked with data uploading and processing (the login information
>>> can see from pull-down menu), as well as the data history
>>> 4. Go to aws console to check, find the instance is running
>>> 5. Copy the dns site followed by /cloud to check the cluster nodes,
>>> click "access galaxy" button there
>>> 6. On the galaxy window choose user login
>>> 7. And here is the window I have - I cannot login and no history data
>>> My question:
>>> it seems that the two galaxy access is not the same. I rather to use the
>>> site from cloudlaunch site if it is preferred. However, I still have to go
>>> to the instance DNS site for shutting down the instance/cluster to avoid
>>> aws unnecessary charge. And, if I need to add cluster nodes, I still need
>>> to go to the DNS site.
>>> What is the appropriate procedure I need to follow to retain the data
>>> history and log in between two accesses, especially while shutting down and
>>> I really appreciate your inputs and helps!
>>> Kind regards,
>>> 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:
>>> To manage your subscriptions to this and other Galaxy lists, please
>>> use the interface at:
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:
To manage your subscriptions to this and other Galaxy lists,
please use the interface at: