- From: Daniel DeLeo <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: renaming a node
- Date: Fri, 2 Apr 2010 11:01:33 -0700
Ohai!
Your FQDN doesn't need to resolve via DNS. Even just 'localdomain'
will get the job done.
Dan DeLeo
On Fri, Apr 2, 2010 at 10:54 AM, John Merrells
<
>
wrote:
>
>
On Apr 2, 2010, at 10:46 AM, Joshua Timberman wrote:
>
>
On Apr 2, 2010, at 11:42 AM, John Merrells wrote:
>
>
The other thing I don't grok yet is the relationship between the client
>
name,
>
>
the node name, and the hostname. When chef client registers itself it
>
creates
>
>
a client and a node with the hostname for their name and creates a
>
certificate
>
>
for the client.... but.... if i change the hostname of the machine is it
>
going to
>
>
break the authentication of the client using the client certificate? Hmm...
>
>
thinking out load really.
>
>
>
Chef uses the "node_name" value for the "client_name" when it registers the
>
new client with the API.
>
>
By default, the "node_name" comes from the FQDN as detected by ohai (via
>
hostname -f). You can override this setting in the client.rb by setting
>
node_name explicitly:
>
>
% grep node_name /etc/chef/client.rb
>
node_name "web1prod.example.com"
>
>
This isn't easily managable or scalable but for a one-off system it's okay.
>
>
Thanks.
>
I think that only helps me if I know what the hostname is going to be before
>
chef-client runs for the first time. Currently, as a quirk of the hosting
>
provider API the machine doesn't know that. I should probably push on that.
>
btw - does chef require that the hostname be resolvable? Or does it just
>
have to look like a fqdn?
>
John
>
--
>
John Merrells
>
http://johnmerrells.com
>
+1.415.244.5808
>
>
>
>
>
>
Archive powered by MHonArc 2.6.16.