It depends. Why do you want to do it? When you start chef-client via cron’s @reboot directive, as mentioned by Konstantin, you may knock out your chef-server, if e.g. you are rebooting a couple of nodes (like after a power outage…). It looks like you either want to run chef using the regular chef-client init.d/runit setup with a splay (see https://github.com/opscode-cookbooks/chef-client) or implicitly when deploying new instances (and apply a gate to limit the number of parallel request). When my nodes reboot e.g. due to kernel upgrades, they usually don’t need an extra/immediate chef run… That’s why I’m curious about your scenario. best regards Roland |
Archive powered by MHonArc 2.6.16.