<div class="gmail_quote">On Wed, Nov 4, 2009 at 12:22 PM, Henning Sprang <span dir="ltr"><<a href="mailto:henning.sprang@gmail.com">henning.sprang@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Joel,<br></blockquote><div><br>Hi!<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
On Wed, Nov 4, 2009 at 10:26 AM, Joel Merrick <<a href="mailto:joel.merrick@gmail.com">joel.merrick@gmail.com</a>> wrote:<br>
> Exactly the same here... only with Chef[1], rather than Puppet<br>
><br>
> [1] <a href="http://www.opscode.com/chef" target="_blank">http://www.opscode.com/chef</a><br>
<br>
</div>Do you have some information on the differences(pros and cons) of<br>
managing configurations with FAI softupdate versus Chef?<br></blockquote><div><br>Well, the templating within Chef capability for a start.<br><br>It's extremely flexible. Plus as it's written in pure ruby, it's extensible (think reading in user information from ldap or SQL etc..)<br>
<br>I'm not entirely sure that you'd be able to achieve the flexibility of chef with FAI's softupdates, although my knowledge of softupdates is fairly limited I'm afraid. If you have any additional reading, feel free to send it my way :)<br clear="all">
</div></div><br><br>-- <br>$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'<br><br>