- From: Andrew Brown <
>
- To: o haya <
>, "
" <
>
- Cc: "
" <
>
- Subject: [chef] Re: "Just" register a Chef node ?
- Date: Sun, 12 Jul 2015 16:24:02 +0000
- Accept-language: en-US, en-CA
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
- [chef] "Just" register a Chef node ?, o haya, 07/12/2015
- [chef] Re: "Just" register a Chef node ?, Noah Kantrowitz, 07/12/2015
- [chef] Re: "Just" register a Chef node ?, Andrew Brown, 07/12/2015
- [chef] Re: "Just" register a Chef node ?, Tracy Phillips, 07/13/2015
- [chef] Re: "Just" register a Chef node ?, Nico Kadel-Garcia, 07/15/2015
- [chef] RE: "Just" register a Chef node ?, Benzinger, Dennis, 07/15/2015
Archive powered by MHonArc 2.6.16.