Re: Bug in Starcluster / paramiko

From: Justin Riley <no email>
Date: Tue, 03 Jan 2012 17:25:02 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Paul,

I noticed in your crash report you're using the Amazon Linux AMI which
is not compatible with StarCluster. You instead need to use one of the
StarCluster supported AMIs. You can obtain a list of available
StarCluster AMIs using the 'listpublic' command:

$ starcluster listpublic

To see AMIs in other regions:

$ starcluster -r us-west-1 listpublic

You will need to specify one of these AMI ids in your config file.

You can also customize the StarCluster AMI for your needs:

http://web.mit.edu/stardev/cluster/docs/latest/manual/create_new_ami.html

Hope that helps,

~Justin



On 01/03/2012 05:17 PM, Paul Koerbitz wrote:
> Dear Starcluster Team,
>
> it looks like I stumbled upon a bug in Starcluster / paramiko. I
> was just trying to set up my first cluster, so it is also possible
> that I did something wrong. Please find the bug report attached.
>
> I am running Ubuntu 10.04 amd64 with python 2.6 running under
> virtualenv. Please let me know if you need any more information.
>
> kind regards Paul

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8DgD4ACgkQ4llAkMfDcrnUygCdHTEqKB1f+AE0m3jfXhieeyWy
xcQAnAmH/ybf41EyabxDvM2wmIGc1T8a
=x/YX
-----END PGP SIGNATURE-----
Received on Tue Jan 03 2012 - 17:25:05 EST