To be clear: your cluster is running in us-east-1d? Did you specify that with
AVAILABILITY_ZONE = us-east-1d
In the cluster section of your config?
On Jan 27, 2013, at 8:34 PM, "Brian Osborne" <bosborne11_at_verizon.net<mailto:bosborne11_at_verizon.net>> wrote:
Yes, the EBS I'm trying to use is available in us-east-1d and I specify "AWS_REGION_NAME = us-east-1" in my .starcluster/config.
On Jan 27, 2013, at 4:28 PM, "MacMullan, Hugh" <hughmac_at_wharton.upenn.edu<mailto:hughmac_at_wharton.upenn.edu>> wrote:
Is it in the same Availability Zone (us-east-1[abc] as the cluster that is trying to mount it?
Yes you can use any volume, however created, assuming the OS can mount it (it has a file system, etc)
That's all I got! :)
On Jan 27, 2013, at 3:43 PM, "Brian Osborne" <bosborne11_at_verizon.net<mailto:bosborne11_at_verizon.net>> wrote:
I've created an EBS in us-east-1d that I can attach, detach, mount and mount on various EC2 instances. I can see that it's "available" in console.aws.amazon.com<http://console.aws.amazon.com
>. But when I try to use it in a cluster I see:
Validating cluster template settings...
!!! ERROR - volume vol-2a717454 does not exist
Here's some excerpts from my config:
AWS_REGION_NAME = us-east-1
VOLUMES = bio
VOLUME_ID = vol-2a717454
MOUNT_PATH = /bio
On the other hand I can use "createvolume". I guess I have 2 questions:
- can I use the EBS I've created by hand?
- if not, what's the best way of getting the content of my EBS into the volume I create using "createvolume"?
StarCluster mailing list
Received on Sun Jan 27 2013 - 21:17:24 EST