[chef] Re: Re: "Just" register a Chef node ?

[o haya < >]

Hi Andrew (and Noah, from the earlier response),

Thanks!  I didn't realize that it already checks for the presence of 
chef-client (should've tested it myself, and will now).

Jim

--------------------------------------------
On Sun, 7/12/15, Andrew Brown 
<
 >
 wrote:

 Subject: [chef] Re: "Just" register a Chef node ?
 To: "o haya" 
<
 >,
 
"
 "
 
<
 >
 Cc: 
"
 "
 
<
 >
 Date: Sunday, July 12, 2015, 12:24 PM
 
 Hello Jim,
 
 You could prevent knife from
 installing the client by using the
 '--bootstrap-install-command' option, though keep in
 mind that it already checks if /usr/bin/chef-client
 ‎exists, and won't re-install if that check
 succeeds.
 
 Cheers,
 Andrew
 
 Sent
 from my BlackBerry 10 smartphone on the Rogers network.
   Original Message
 From: o haya
 Sent: Sunday, July 12, 2015 12:09 PM
 To: 

 
 Reply To: 

 
 Cc: 

 
 Subject: [chef] "Just" register a
 Chef node ?
 
 
 Hi,
 
 Assuming
 the machine already:
 
 - Has
 the Chef client software installed
 - Has
 client.pem removed
 - Has client.rb with
 "node_name" being empty
 
 Does Chef provide a way/tool to remotely cause
 that machine to be registered as a Chef node (initiated from
 a centralized machine)?
 
 This would be for both Windows-based and Linux
 (CENTOS-/Redhat-) based machines.
 
 I know that we can do "knife
 bootstrap", but in our case, we don't want to push
 the Chef client software to the node machines, but rather
 want to pre-provision the node machines with the Chef client
 software and just be able to cause the node machines to
 register as Chef nodes.  Something like having a
 "knife bootstrap", but where the bootstrap process
 would not include pushing the Chef client software to the
 node machine(s), would be perfect.
 
 Thanks,
 Jim