- From: Tim Uckun <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: Puppet vs Chef
- Date: Thu, 14 Jan 2010 09:15:21 +1300
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VIJxA64jowo0/Qav44NN7tz42vUsV4VZXqxf79z+Wc/9Cpd9IA3wAcbpWQZ3Ocr6i4 O9X8VocbjQe110RZKtLMA82p0MkwCsSFt1ANWhIyMwfnPMGbWRRE7/uZKjsLmE6akpFM S1IEgAewXEAcQlVawUWXhor2nz0WuDGFQVIgs=
>
I recently added Ohai and Chef support to AutomateIT as well, so you
>
can use Chef resources and Ohai facts in your AutomateIT recipes if
>
you want. (Not sure what the status of merging that stuff is, I should
>
ping Igal)
Interesting because I did the same thing with facter and automateit.
It was pretty trivial of course.
My automateit setup ended up being very different than the "default"
setup but that's one of the great things about automateit being "just
ruby". You can use all the ruby goodness.
One thing you might want to do (if the licenses allow it) is to add
some of the text editing power of automateit to chef (or puppet) and
or to add some of the "bundles" or "packages" concepts to automateit.
IMHO that would be a pretty nice system. I think that's my next step
in playing with automateit. It would be nice to be able to share a
directory with somebody knowing it's fully self contained.
I read some of the comments on the blog entry and I think the
comparison between sysadmins and programmers are pretty valid. If you
are a ruby programmer you will probably find it frustrating to deal
with the puppet DSL eventually.
Archive powered by MHonArc 2.6.16.