Specifically, the node had several EBS volumes attached/mounted, and elastic IP, and those ID’s are stored as node attributes on the existing node within chef-server.
I want to fire up a new EC2 instance, and have it take-over for the down node, and re-attach/mount the EBS volumes, and elastic IP.
With amazon instances being treated as disposable, should we treat nodes as disposable as well? Or is there a way to have a new server assume ownership of an existing node?
Right now, I’m copy/pasting the current run_list data from chef-server, and grabbing any/all attributes, with the assumption that my only option is to manually rebuild the node data within chef.
Since knife has 2 methods, “node delete” and “client delete”, one would think that simply deleting the client would let a new server register itself as an existing node, and would inherit that nodes existing run_list and attributes. Otherwise, what is the point of deleting a node without deleting the client or vice versa.
On Oct 17, 2011, at 12:30 PM, Haim Ashkenazi wrote:
On Mon, Oct 17, 2011 at 6:13 PM, Aaron Abramson firstname.lastname@example.org wrote:
I lost an EC2 instance over the weekend. Is there a proper method to replace it?
In the past, when I simply delete a client from chef, and bootstrap a client using the same node name, it registers itself, but wipes out the node run_list and attribute data.
Is there a way to bring up a new instance and assign it to be XYZ node and inherit the run_list & attributes?
Any reason why not specify the run_list in the bootstrap command (-r)? Do you have spacial attributes for each host or can you define them in a role?