Re: Error running custom AMI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
FYI, I meant to say "ebsimage/s3image" commands instead of the
deprecated "createimage" command...old habits die hard :D
~Justin
On 12/31/2011 03:33 PM, Justin Riley wrote:
> Hi Paolo,
>
> StarCluster comes with a set of base 32bit/64bit AMIs as you've
> seen/used. These AMIs are tuned for use with StarCluster and any
> AMI you wish to use with StarCluster must be configured similarly
> in order to be used with StarCluster.
>
> The two most important requirements are:
>
> 1. root ssh logins must be permitted (this is what's currently
> causing your "Garbage Packet" error in your logs...) 2. NFS must be
> installed and the NFS start-up script in /etc/init.d must be linked
> to /etc/init.d/nfs
>
> StarCluster also expects that /opt/sge6-fresh contains a binary
> build of SGE/OGS in order to configure SGE/OGS at runtime. You can
> disable SGE/OGS support by setting disable_queue=True in your
> cluster templates if you do not require SGE/OGS and would like to
> skip this requirement.
>
> You can see all of the gory details involved with building a
> StarCluster AMI in the AMI "Cookbooks" in the StarCluster wiki:
>
> https://github.com/jtriley/StarCluster/wiki
>
> The majority of the steps in the guides are related to installing
> custom ATLAS/numpy/scipy/OpenMPI/etc which you can skip if you do
> not require.
>
> With that said, the recommended way to create a custom AMI for use
> with StarCluster is to launch a single instance of one of the
> StarCluster AMIs, configure to your liking, and then use
> StarCluster's 'createimage' command to build your custom AMI:
>
> http://web.mit.edu/stardev/cluster/docs/latest/manual/create_new_ami.html
>
> This approach avoids having to fiddle anything but your packages
> and customizations and lets StarCluster do the rest.
>
> ~Justin
>
>
> On 10/10/2011 08:20 AM, Paolo Di Tommaso wrote:
>> Dear StarCluster Team,
>
>> I'm evaluating your tool.
>
>> I had no problem starting a small cluster with the default
>> configuration. But when I tried to use a custom AMI (no more than
>> a Basic 64-bit Amazon Linux AMI, with few other custom tools). I
>> get the error message below.
>
>> Is there any special configuration in order to use custom AMI
>> images?
>
>> By the way your tool is amazing!
>
>> Thank you,
>
>> Paolo Di Tommaso Software Engineer Comparative Bioinformatics
>> Group Centre de Regulacio Genomica (CRG) Dr. Aiguader, 88 08003
>> Barcelona, Spain
>
>
>
> _______________________________________________ StarCluster mailing
> list StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAk7/cfoACgkQ4llAkMfDcrkL+ACePRVPVXxdwejsGBZ+tIVap1B1
EwoAnjD7LlN7n1/dhI/kSgwhAoHVzODW
=p3vq
-----END PGP SIGNATURE-----
Received on Sat Dec 31 2011 - 15:35:10 EST
This archive was generated by
hypermail 2.3.0.