Hi All
I implemented a chef service.
The service itself installs ruby and chef-solo and it provides easy to
use classes to run recipes on the cluster that could be used by other services.
I still has some limitations as I only tested in rackspace, the
implementation for RHEL based distros is still partly missing, and it only
accepts cookbooks by url (does not fetch them from the central repo yet).
Nonetheless it might be interesting to someone else.
My question is:
- I got a sense from the puppet issue that another direction was
decided in terms of provisioning (e.g., not making chef or puppet common
services but part of a provisioning abstraction). Did I misunderstand? is it
still worth attaching the patch to the chef issue?
Cheers
David Alves
