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

["Steven Murawski" < >]

                                        You can also use a custom bootstrap template.  The template is the what controls how Chef is installed and registered.  You could strip out the install part and just use the file transfer and registration process parts of the install template from the bootstrap.

Steve

Steven Murawski

Community Software Development Engineer @ Chef

Microsoft MVP - PowerShell
http://stevenmurawski.com

On 7/15/2015 9:18:25 AM, Nico Kadel-Garcia < > wrote:

The node needs it's private keys generated, and the server needs to register the public keys for the node, for "chef-client" to ever work for that node. You can manually create an artificial node in chef-server. I've seen this used to auto populate DNS tables and monitoring for non-chef enabled hosts, but it's confusing.

Nico Kadel-Garcia
Email:
Sent from iPhone

> On Jul 12, 2015, at 12:09, "o haya" < > wrote:
>
> 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
>
>