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

[Jesse Campbell < >]

the knife ec2 plugin has a --purge option for the knife ec2 vm delete command.
I'm thinking to copy that work and add it to the knive vsphere
command... rackspace could do it too.
Alternatively, deleting an instance could be a script that calls knife
<rack> vm delete, then knife client delete, then knife node delete.

Not sure which is better, adding it to the plugin, or deleting from a 
script...
-Jesse

On Fri, Mar 9, 2012 at 10:43, Brad Knowles 
<
 >
 wrote:
> On Mar 9, 2012, at 8:43 AM, Rob Guttman wrote:
>
>> 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.
>
> Same deal for Rackspace.  You want to delete the node, the client, and you 
> want to delete the Rackspace instance as well.  We also clean up our 
> auto-registered DNS entries, and our ssh "known_hosts" files.
>
> That's a lot of stuff to have to remember to clean up every time you delete 
> a node.
> ;-(
>
> --
> Brad Knowles 
> <
 >
> SAGE Level IV, Chef Level 0.0.1
>