[chef] Re: Re: Re: Re: How to handle the elastic_ip associate recipe to finish up smoothly?

[Hector Castro < >]

Hi everyone,

I dug into knife-ec2 this afternoon and was looking for a way to
associate an Elastic IP to a node created via knife-ec2.  That
eventually led me to KNIFE_EC2-67, now known as KNIFE-151.  It looks
like the leading pull request associated with this ticket is:

   https://github.com/opscode/knife-ec2/pull/88

Are we at a stage where we can mark the ticket as "Fix Provided" so
that it can make it to the next step in the code review process?

Thanks,

--
Hector


On Wed, Jul 11, 2012 at 5:36 PM, AJ Christensen 
<
 >
 wrote:
> Bryan,
>
> On 12 July 2012 09:26, Bryan McLellan 
> <
 >
>  wrote:
>> On Thu, Jul 5, 2012 at 8:29 PM, Scott M. Likens 
>> <
 >
>>  wrote:
>>> Unfortunately if you are not running chef-solo under (screen and/or tmux)
>>> your SSH connection will get interrupted once the new IP address is 
>>> attached
>>> to the instance.
>>>
>>> The only real way to make this better is to either do one of the 
>>> following:
>>>
>>> Run chef-client under screen/tmux on the server itself.   Likely modifying
>>> the bootstrap so it installs screen (and or tmux) and then runs 
>>> chef-client
>>> under that.
>>> Provision the servers first and then run knife bootstrap once the Elastic 
>>> IP
>>> address is attached.
>>>
>>> ec2-run-instances ami-.... then follow up with ec2-associate-addresses to
>>> the instance.
>>
>> It was proposed on KNIFE_EC2-67 [1] to add an option to knife-ec2 to
>> associate an address before beginning the bootstrap. Generally we try
>> to avoid adding ec2-tools features to knife-ec2 that aren't chef
>> specific, but it is simple and useful, so we weren't really sure where
>> to go with this at code review.
>>
>> The bigger question is, are we lacking a way to run cookbooks in a
>> such a way that will trigger chef to finish and then restart itself?
>> One other example would be updating chef using chef, then continuing
>> along. Thoughts?
>
> This seems simple enough to be affective. Perhaps the new forkable
> client + configurable retries would assist?
>
> --AJ
>
>>
>> --
>> Bryan McLellan | opscode | technical program manager, open source
>> (c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org
>>
>> [1] http://tickets.opscode.com/browse/KNIFE_EC2-67