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 instance
> 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 versa.
> 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: