General discussion about Chef

[chef] Chef-client as a cron, or as a service, which cookbook?


Chronological Thread 
  • From: Tim Diggins < >
  • To:
  • Subject: [chef] Chef-client as a cron, or as a service, which cookbook?
  • Date: Sat, 9 Apr 2011 07:42:04 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=mMgVJw+oCwksNxwqc3720fQcna8JTbjzVCP8+As6czpCNVrkBy9l0R+QjOdC5pSV20 1YH5IauT/KM0DL90pG7E3EVvfnAZ1tvQIl9+/Y/rNYzZQA+EftvdFWJdojlNYFA0Olf3 pe3Dho9NZdUonybklxupJkkOh7qXsrvlDZpvE=
Hi -

I've got several functioning chef-provisioned and deployed systems/applications, and am only now getting round to worrying about automatic updates/deployment. (Up to now have been running knife ssh "sudo chef client" as needed).

The most obvious thing (and lightweight) that I can do is to add to one of my recipes a cron resource to sudo chef-client every 30 minutes. However I notice that there's a chef-client cookbook with recipe for running it as service.

Is there a strong reason for running chef-client as a service rather than a cron? The chef-client cookbook's README encourages me to delete the validation before installing chef-client. Why would I want to do that? 

There's also a client_service recipe within the chef cookbook as well.

Options, options. Any pointers?


thanks

Tim


--
------------------------------------------------------

Tim Diggins
http://red56.co.uk


Archive powered by MHonArc 2.6.16.

§