[chef] Re: removing autoscaled-down nodes from chef server?

[John Martinez < >]

We have a shutdown init script that does two basic things:

knife node delete <itself>

knife client delete <itself>

Works great. 

Our AWS environments are very ephemeral, so we don't really care to worry about reboots and those kinds of things. :-)

-john

On Oct 18, 2012, at 9:17 AM, Denis Haskin < "> > wrote:

Looking for input on how to handle this: we use AWS's autoscaling to dynamically manage the number of front-end nodes against traffic, but we configure and provision the nodes with chef, so they do get registered with our chef server.

However, when the AWS autoscaling takes nodes down as traffic declines, they don't get de-registered from the chef server, so we're accumulating lots of invalid entries in our chef server.  Makes using the chef search facility sub-optimal (e.g. run a knife ssh command against a set of nodes that you've identified by search, but a lot of them aren't there any more so it takes a long time as the ssh requests time out, etc).

Suggestions on how to handle this?  I believe (and am checking) that nodes get an orderly shutdown when autoscaling decides they're not needed any more, so I guess I can hook into something there (these are ubuntu).  Is that the best approach?

Thanks,

--

Denis Haskin