Hi Brad,
On Tue, Jan 24, 2012 at 9:22 PM, Brad Chapman chapm...@50mail.com wrote:
Greg;
I'm almost positive I originally started the instance via
BioCloudCentral, and I always use Large. I've been exclusively using
BioCloudCentral for a few weeks now.
I hadn't noticed this issue until
Thanks Enis.
You are correct, that I'm restarting a cluster.
Would it be possible for the user to enter their zone on the form? Or
could CloudMan detect a problem, shutdown and try a different zone?
(probably infeasible).
Thanks again,
Greg
On Tue, Jan 24, 2012 at 9:08 AM, Enis Afgan
Both are feasible (and on the todo list) so lets just hope they get done
sooner rather than later... Your comments help push it higher up on the
list.
On Tue, Jan 24, 2012 at 3:29 PM, mailing list margeem...@gmail.com wrote:
Thanks Enis.
You are correct, that I'm restarting a cluster.
Enis and Greg;
This sounds like the availability zone issue. I am assuming you are
restarting the same cluster (i.e., using the same name) and the instance
that gets created may be created in a zone different from the one that
the
volume from the previous instantiation of the
Hi Brad,
I'm almost positive I originally started the instance via
BioCloudCentral, and I always use Large. I've been exclusively using
BioCloudCentral for a few weeks now.
I hadn't noticed this issue until yesterday. I can definitely do
whatever you need if you want to dig into the issue
Hi Greg,
This sounds like the availability zone issue. I am assuming you are
restarting the same cluster (i.e., using the same name) and the instance
that gets created may be created in a zone different from the one that the
volume from the previous instantiation of the cluster was in.
Greg;
I'm almost positive I originally started the instance via
BioCloudCentral, and I always use Large. I've been exclusively using
BioCloudCentral for a few weeks now.
I hadn't noticed this issue until yesterday. I can definitely do
whatever you need if you want to dig into the issue
7 matches
Mail list logo
