That is what I was looking for. Thank you very much!
BRIDGER LARSON | Associate Build/Release Engineer | SirsiDynix
P: 801.223.5345 | email@example.com:firstname.lastname@example.org
www.sirsidynix.comhttp://www.sirsidynix.com/ | TOLL FREE: +1 800.284.3969
From: Ranjib Dey [mailto:email@example.com]
Sent: Friday, December 07, 2012 4:56 PM
Subject: [chef] Re: Re: Auto scaling with chef questions
unless explicitly mentioned (via the -N flag) chef client will register new node name as fqdn.
for the second question: no. chef does not delete the client and node automatically when you terminate the ec2 instance. but knife-ec2 address this.
On Fri, Dec 7, 2012 at 3:50 PM, Cassiano Leal <firstname.lastname@example.org:email@example.com> wrote:
I had been thinking about the very same thing for a while, but haven’t had the time to run some tests.
My guess so far is that every new machine that spins up will run chef-client, create a node and a client using the validator key and using the ec2-****** FQDN as client/node name. Have you tried running ‘hostname -f’ on an EC2 server?
On Friday, December 7, 2012 at 21:43, Bridger Larson wrote:
The company I am working for is moving to AWS. I want to be able to have Chef pre-installed on our application server AMI’s so when they start up they will be configured correctly.
If one AMI can create many servers, how does the Chef client give them different client names?
How does Chef know to remove them when the server is deleted?