[chef] Re: Re: Re: Possibilities for node_name in Chef client configuration

[Noah Kantrowitz < >]

On Jun 9, 2014, at 12:26 PM, Jeff Blaine 
<
 >
 wrote:

> Thanks Noah and Adam.
> 
>> Set node_name to what you want in /etc/chef/client.rb.
> 
> Well yeah, that's what I'm trying to do :)
> 
> What I've learned is that chef-client has not gathered ohai
> data before it loads this config file, so ohai['fqdn'] is
> not available for munging in client.rb as such:
> 
>    node_name ohai['fqdn'].downcase.gsub('domain.com', '')
> 
> Not a big deal there. We already use the chef-client cookbook
> and can do the munging there in our wrapper for it.
> 
> Is the node name used as any sort of *input data* for that node's
> client key generation?
> 
> If so, obviously renaming our node objects is going to require
> rekeying everything.

Yes, the node name is used as the API client username as well. Unfortunately 
fixing this is kind of a pain, but you can make a little script using 
chef-api or pychef to do the bulk of the copying work.

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail