- From: Joshua Timberman <
>
- To:
- Subject: [chef] Re: Re: Re: renaming a node
- Date: Fri, 2 Apr 2010 11:46:34 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello!
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.
- --
Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
iEYEARECAAYFAku2LXoACgkQO97WSdVpzT0uEgCggCPKY+3J5KBR7qrL8wfJsg9n
H2wAn117YMUvf91HcMIY1LH5Ky6BQfWs
=KJbK
-----END PGP SIGNATURE-----
Archive powered by MHonArc 2.6.16.