Re: starcluster createimage

From: Ranjit Chacko <no email>
Date: Tue, 10 May 2011 16:30:34 -0400

Yes I did add it to a _at_sc security group. I did go ahead and ignore the
warning and everything worked fine. Thanks,

-Ranjit

On 5/10/11 5/10/11 4:11 PM, Justin Riley wrote:
> Hi Ranjit,
>
> Did you add the instance to a _at_sc-* group when creating the instance in
> the Amazon console? That would cause the warning you're getting. In any
> case if you're sure you did not launch with StarCluster you can safely
> ignore the warning. The warning will be completely removed in the next
> version as this limitation of not being able to use StarCluster-started
> instances is gone in the latest development code.
>
> The user id you need to use is the numerical account id.
>
> HTH,
>
> ~Justin
>
>
> On 05/10/2011 01:45 PM, Ranjit Chacko wrote:
>> I'm also having some trouble with the createimage command.
>>
>> I created an instance through the AWS console, made the changes to the
>> instance I wanted to save, and then tried the createimage command.
>>
>> First I got a warning:
>> WARNING - Creating an image from a StarCluster instance can lead to
>> problems when attempting to use the resulting image with StarCluster
>> later on
>>
>> cli.py:517 - WARNING - The recommended way to re-image a StarCluster AMI
>> is to launch a single instance using either ElasticFox, the EC2 command
>> line tools, or the AWS management console. Then login to the instance,
>> modify it, and use this command to create a new AMI from it.
>>
>> I believe this is what I did, so I'm not sure why I'm getting the
>> warning. Does this mean the initial AMI I want to rebundle can't be one
>> of the StarCluster AMI's?
>>
>> Then an ssh command fails apparently because it does not have the right
>> user id. What is the appropriate user id to use here? Is it the
>> canonical id, or the AWS account id?
>>
>> Thanks,
>>
>> -Ranjit
>>
>> On 5/10/11 5/10/11 12:11 PM, starcluster-request_at_mit.edu wrote:
>>> Message: 1
>>> Date: Tue, 10 May 2011 10:00:07 -0400
>>> From: Justin Riley<jtriley_at_MIT.EDU>
>>> Subject: Re: [StarCluster] starcluster createimage
>>> To: Neil Gong<neilz.gong_at_gmail.com>
>>> Cc: "starcluster_at_mit.edu"<starcluster_at_mit.edu>
>>> Message-ID:<754B77AD-2E9C-410E-9874-4D4D9CCF3022_at_mit.edu>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hi Neil,
>>>
>>> Make sure you have EC2_CERT and EC2_PRIVATE_KEY specified in your [aws info] section:
>>>
>>> [aws info]
>>> EC2_CERT = /path/to/cert-*.pem
>>> EC2_PRIVATE_KEY= /path/to/pk-*.pem
>>>
>>> Let me know if that helps,
>>>
>>> ~Justin
>>>
>>> On May 4, 2011, at 5:41 PM, Neil Gong wrote:
>>>
>>>> Dear Sir/Madam,
>>>>
>>>> My name is Neil Gong, a graduate student of EECS at UC Berkeley. I'm
>>>> using your tool StarCluster. I encountered a problem. When I first
>>>> used starcluster createimage, it created an image for me successfully,
>>>> but when I tried this the second time, I encountered a error:
>>>>
>>>> cli.py:1079 - ERROR - No certificate file (pem) file specified
>>>>
>>>>
>>>> Every other function is OK. I can start a cluster .
>>>>
>>>> Thanks
>>>> Neil
>>>> _______________________________________________
>>>> StarCluster mailing list
>>>> StarCluster_at_mit.edu
>>>> http://mailman.mit.edu/mailman/listinfo/starcluster
>>>
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> StarCluster mailing list
>>> StarCluster_at_mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/starcluster
>>>
>>>
>>> End of StarCluster Digest, Vol 21, Issue 3
>>> ******************************************
>> _______________________________________________
>> StarCluster mailing list
>> StarCluster_at_mit.edu
>> http://mailman.mit.edu/mailman/listinfo/starcluster
Received on Tue May 10 2011 - 16:30:39 EDT