[chef] Re: Re: Re: aws autoscaling and chef cleanup

[Sam Darwin < >]

Thanks for all the great replies!!

Morgan: that is checking for terminated instances in AWS, but they may
completely vanish from AWS (not even shows as 'terminated' anymore)
and not necessarily get processed, unless the script is run often?
Cassiano: very cool about knife not having to be setup.
Thom:  SNS , SQS, looks like the way to go
Alex:  Nuvole has an implementation for that
Brian:  has an implementation for Nuvole
each step further it seems...   will look into these suggestions.


On Fri, May 17, 2013 at 8:52 PM, Brian Hatfield 
<
 >
 wrote:
> Based upon that Nuvole Computing article, I wrote this:
>
> https://github.com/bmhatfield/chef-deregistration-manager
>
> Might be useful.
>
>
> On Fri, May 17, 2013 at 1:49 PM, Alex Corley 
> <
 >
>  wrote:
>>
>>
>> http://www.nuvolecomputing.com/2012/07/02/chef-node-de-registration-for-autoscaling-groups/
>>
>> (Not my article)
>>
>> This is not a self-cleanup, requires a backend workflow/process, but it
>> can be expanded in any number of ways.
>>
>> - alex
>>
>>
>> On 05/17/2013 11:43 AM, Sam Darwin wrote:
>>>
>>>
>>> If using AWS auto-scaling + Chef, the final step of instance cleanup
>>> seems to
>>> be slightly unclear.
>>>
>>> One solution is to run a script in /etc/rc0.d which is called on
>>> shutdown.
>>> "knife node delete".    This requires knife to be configured and working
>>> on the
>>> instance, which is a (minor) pain.    This method will also fail for an
>>> abrupt
>>> machine crash.
>>>
>>> Another solution is to have a script which queries chef server for
>>> instances
>>> that haven't checked in for a while, and removes those.   That would
>>> require
>>> having chef-client running very often or as a daemon.
>>>
>>> I wonder what the security implications would be of adding functionality
>>> into
>>> chef-client:
>>>
>>> chef-client --remove-self-from-server
>>>
>>> Some people have posted about a script which checks for terminated
>>> instances
>>> and removes them.   this sounds like the best way.    Perhaps they mean
>>> to
>>> query AWS first, and then make changes to chef-server.    now to figure
>>> out
>>> how...
>>>
>>
>>
>> --
>> Alex Corley | Software as a Service Engineer
>> Zenoss, Inc. | Transforming IT Operations
>> 
 
>>  | Skype: acorley_zenoss | Github: anthroprose
>
>