Hi,
I was able to put the installation of a new chef client on a shell script
to be executed after a new system installation. Now, what I want is that
the first time this client/node runs it already has a run_list setup. Is it
possible?
Thanks
Kelly
yes you can do it either by
- pre creating the node using
knife node create
, make sure the name of
the node is either fqdn or the value of -N [while boot strapping] or the
node_name param in /etc/chef/client.rb
- make a json file which contains the run list and invoke the first chef
run in your node with -j argument, -j /etc/chef/bootstrap/first-boot.json
this is the way standard knife boot strap works
regards
ranjib
On Thu, Dec 29, 2011 at 3by:42 PM, Kelly Goedert kelly.goedert@gmail.comwrote:
Hi,
I was able to put the installation of a new chef client on a shell script
to be executed after a new system installation. Now, what I want is that
the first time this client/node runs it already has a run_list setup. Is it
possible?
Thanks
Kelly
Kelly,
You might want to peruse the Opscode Chef training materials to better understand where to go next. You can request access to them here: http://info.opscode.com/opentraining
Good luck,
Peter
On Dec 29, 2011, at 5:41 AM, Ranjib Dey wrote:
yes you can do it either by
- pre creating the node using
knife node create
, make sure the name of the node is either fqdn or the value of -N [while boot strapping] or the node_name param in /etc/chef/client.rb
- make a json file which contains the run list and invoke the first chef run in your node with -j argument, -j /etc/chef/bootstrap/first-boot.json
this is the way standard knife boot strap works
regards
ranjib
On Thu, Dec 29, 2011 at 3by:42 PM, Kelly Goedert kelly.goedert@gmail.com wrote:
Hi,
I was able to put the installation of a new chef client on a shell script to be executed after a new system installation. Now, what I want is that the first time this client/node runs it already has a run_list setup. Is it possible?
Thanks
Kelly
--
Peter Burkholder | Sr. System Administrator (consultant)
AARP | Digital Strategy & Operations | 601 E Street NW | Washington, DC 20049
pburkholder@aarp.org | aim: peterbtech | w: 202-434-3530 | c: 202-344-7129
For optimal efficiency, I check email at 2-hour intervals during the workday
(except when on-call). Please use IM or phone to contact me for urgent matters