Hi Kyeong,
Sorry you've run into this issue. This is happening because the
us-east-1 StarCluster AMI is hard-coded in the createvolume command in
StarCluster 0.91.2 and cannot be modified via the config or an option
to the createvolume command. The latest github code, however, allows
you to pass an --image-id flag that allows you to switch to another
AMI when creating new volumes. In general any Linux AMI should work in
theory provided it has the standard sfdisk/mkfs.ext3 commands that are
commonly available on most Linux distros. You can also change the mkfs
command used by the createvolume command via the --mkfs-cmd flag if
needed. If you're interested in testing the latest code please note
that you will need to shutdown all clusters previously launched using
the 0.91* release before using the development version. Also any
volumes created can only be used with the development version. Any
volumes created with the development version will be compatible with
the upcoming 0.92 release.
Hope that helps,
~Justin
On Wed, Jan 12, 2011 at 11:41 AM, Kyeong Soo (Joseph) Kim
<kyeongsoo.kim_at_gmail.com> wrote:
> Dear All,
> This is to report the said failure of "createvolume" in the eu-west zone.
> Per the starcluster documentation, I have set environment variable and
> configuration file as follows:
> * Environment variable
> EC2_URL=https://ec2.eu-west-1.amazonaws.com
> * Configuration file
> =============================================
> [aws_info]
> ...
> AWS_REGION_NAME = eu-west-1
> AWS_REGION_HOS = ec2.eu-west-1.amazonaws.com
> ...
>
> [cluster smallcluster]
> ...
> # AMI for cluster nodes.
> # US region
> # - The base i386 StarCluster AMI is ami-d1c42db8
> # - The base x86_64 StarCluster AMI is ami-a5c42dcc
> # EU region
> # - The base i386 StarCluster AMI is ami-a4d7fdd0
> # - The base x86_64 StarCluster AMI is ami-38d5ff4c
> NODE_IMAGE_ID = ami-a4d7fdd0
> NODE_INSTANCE_TYPE = m1.small
> ...
> =============================================
> Because the default AMIs suggested in the template (i.e., "ami-d1c42db8" and
> "ami-a5c42dcc") are not available in the eu-west region, I changed it to one
> available (based on "listpublic" command). Then, I got the following error
> when trying to create a volume:
> =============================================
> ~$ starcluster createvolume 30 eu-west-1a
> StarCluster - (http://web.mit.edu/starcluster)
> Software Tools for Academics and Researchers (STAR)
> Please submit bug reports to starcluster_at_mit.edu
> cli.py:1079 - ERROR - AMI ami-d1c42db8 does not exist
> =============================================
> It seems that the setting of NODE_IMAGE_ID has no impact on the AMI used for
> volume creation.
> With Regards,
> Joseph
> --
> Kyeong Soo (Joseph) Kim, Ph.D.
> Senior Lecturer in Networking
> Room 112, Digital Technium
> Multidisciplinary Nanotechnology Centre, College of Engineering
> Swansea University, Singleton Park, Swansea SA2 8PP, Wales UK
> TEL: +44 (0)1792 602024
> EMAIL: k.s.kim_at_swansea.ac.uk
> HOME: http://iat-hnrl.swan.ac.uk/ (group)
> http://iat-hnrl.swan.ac.uk/~kks/ (personal)
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
Received on Tue Feb 01 2011 - 13:25:10 EST