[chef] Re: Re: Handling "deleted" servers on chef

[Rob Guttman < >]

One tip for ec2 users: you may also need/want to delete the chef *client*(i.e., not just the node) from the chef server.

The reason is that ec2 reuses private ip addresses which (at least in my case) are what get used as the client id when knife bootstrapping a node.  Therefore, you can get a client id collision if a new ec2 instance reuses a private ip address the chef server has seen before.

- Rob

On Mar 9, 2012, at 8:45 AM, Leonardo Gamas wrote:

I had a similar script triggered by a Nagios host state change. When the machine went down Nagios would figure out and execute the script.

2012/3/9 jorge espada < "> >

Hi Chefs,

I was wondering how some of you are handling deleted servers (bare metal or VMs) which means nodes for the chef server. 

For instance, if for some reason I suddenly kill 20 of my VMs/servers I need to do some kind of housekeeping on chef-server, which in my case, a dumb script does it.

Thoughts?

Thanks

Jorge E. Espada

--

Leonardo Gamas
Software Engineer
T +55 (71) 3494-3514
C +55 (75) 8134-7440
" target="_blank">
www.jusbrasil.com.br