<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Puppet works hard to make sure nodes are in compliance</title>
	<atom:link href="http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/</link>
	<description>a system administrators mutterings</description>
	<lastBuildDate>Fri, 10 Feb 2012 18:12:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John Arundel</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-1010</link>
		<dc:creator>John Arundel</dc:creator>
		<pubDate>Wed, 13 Jan 2010 13:35:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-1010</guid>
		<description>Puppet vs Chef is a debate which seems to provoke strong reactions (on both sides). Whatever the history betwen the developers, it&#039;s the technical merits of each tool which will weigh most with people choosing their configuration management tool.

I&#039;ve written a summary of the respective merits (in my opinion, of course) of Puppet and Chef here:

http://bitfieldconsulting.com/puppet-vs-chef</description>
		<content:encoded><![CDATA[<p>Puppet vs Chef is a debate which seems to provoke strong reactions (on both sides). Whatever the history betwen the developers, it&#8217;s the technical merits of each tool which will weigh most with people choosing their configuration management tool.</p>
<p>I&#8217;ve written a summary of the respective merits (in my opinion, of course) of Puppet and Chef here:</p>
<p><a href="http://bitfieldconsulting.com/puppet-vs-chef" rel="nofollow">http://bitfieldconsulting.com/puppet-vs-chef</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan McLellan</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-1003</link>
		<dc:creator>Bryan McLellan</dc:creator>
		<pubDate>Tue, 24 Nov 2009 10:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-1003</guid>
		<description>&quot;Before watching it, you should know that Chef was written by a long-time Puppet user who never contributed much back to Puppet, ...&quot;

This is not true. I&#039;m not sure what name to place on the course of events that has led anyone to believe this. Whatever would convey it, disappointing is a word I would associate. 

Theres a telling trail of crumbs here:
http://projects.reductivelabs.com/issues/1010</description>
		<content:encoded><![CDATA[<p>&#8220;Before watching it, you should know that Chef was written by a long-time Puppet user who never contributed much back to Puppet, &#8230;&#8221;</p>
<p>This is not true. I&#8217;m not sure what name to place on the course of events that has led anyone to believe this. Whatever would convey it, disappointing is a word I would associate. </p>
<p>Theres a telling trail of crumbs here:<br />
<a href="http://projects.reductivelabs.com/issues/1010" rel="nofollow">http://projects.reductivelabs.com/issues/1010</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Sharp</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-989</link>
		<dc:creator>Chuck Sharp</dc:creator>
		<pubDate>Mon, 31 Aug 2009 19:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-989</guid>
		<description>Another simple way to check text file line terminations (what a horrible troubleshooting time-waster) is the file command. Here&#039;s how it looks:

$ echo -e &#039;test\ntest\n&#039; &gt; testme
$ file testme
testme: ASCII text
$ unix2dos testme
unix2dos: converting file testme to DOS format ...
$ file testme
testme: ASCII text, with CRLF line terminators</description>
		<content:encoded><![CDATA[<p>Another simple way to check text file line terminations (what a horrible troubleshooting time-waster) is the file command. Here&#8217;s how it looks:</p>
<p>$ echo -e &#8216;test\ntest\n&#8217; &gt; testme<br />
$ file testme<br />
testme: ASCII text<br />
$ unix2dos testme<br />
unix2dos: converting file testme to DOS format &#8230;<br />
$ file testme<br />
testme: ASCII text, with CRLF line terminators</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Anderson</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-958</link>
		<dc:creator>Nick Anderson</dc:creator>
		<pubDate>Tue, 25 Aug 2009 14:12:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-958</guid>
		<description>Thanks for the comment Mark.

You learn something new every day. I had never used od before, it will be a handy tool to add to my collection.

If someone wants a short rundown on the tool see this article http://www.linuxjournal.com/article/1326</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Mark.</p>
<p>You learn something new every day. I had never used od before, it will be a handy tool to add to my collection.</p>
<p>If someone wants a short rundown on the tool see this article <a href="http://www.linuxjournal.com/article/1326" rel="nofollow">http://www.linuxjournal.com/article/1326</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Carey</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-957</link>
		<dc:creator>Mark Carey</dc:creator>
		<pubDate>Tue, 25 Aug 2009 05:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-957</guid>
		<description>As you&#039;ve seen there are other things than bad line endings that can happen when using &quot;bad&quot; windows editors on files that will be parsed in various linux daemons.  The most notorious I&#039;ve encountered is where garbage meta characters are added to the first line of a php file.  This causes php to fail to parse the file and returns an obscure error.  Unfortunately vi/vim does not show the meta chars.  This is where a quick check in a tool like od is handy.</description>
		<content:encoded><![CDATA[<p>As you&#8217;ve seen there are other things than bad line endings that can happen when using &#8220;bad&#8221; windows editors on files that will be parsed in various linux daemons.  The most notorious I&#8217;ve encountered is where garbage meta characters are added to the first line of a php file.  This causes php to fail to parse the file and returns an obscure error.  Unfortunately vi/vim does not show the meta chars.  This is where a quick check in a tool like od is handy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Anderson</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-926</link>
		<dc:creator>Nick Anderson</dc:creator>
		<pubDate>Tue, 04 Aug 2009 01:18:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-926</guid>
		<description>Indeed I am aware that notepad is horrible. I was just surprised because I did not see any ^M characters on any of the lines.</description>
		<content:encoded><![CDATA[<p>Indeed I am aware that notepad is horrible. I was just surprised because I did not see any ^M characters on any of the lines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zed</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-925</link>
		<dc:creator>Zed</dc:creator>
		<pubDate>Tue, 04 Aug 2009 01:09:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-925</guid>
		<description>FYI, notepad is the worst editor ever (use notepad2, notepad++ or even wordpad).

The issue you were seeing is because of notepad&#039;s poor handling of end of lines.</description>
		<content:encoded><![CDATA[<p>FYI, notepad is the worst editor ever (use notepad2, notepad++ or even wordpad).</p>
<p>The issue you were seeing is because of notepad&#8217;s poor handling of end of lines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Anderson</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-921</link>
		<dc:creator>Nick Anderson</dc:creator>
		<pubDate>Fri, 31 Jul 2009 14:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-921</guid>
		<description>Thanks for the link, that sounds interesting. Im all for being able to re-use knowledge and Im sure that learning Chef would help with ruby things in the future but Im more of a python kind of guy. There are definitely some things with puppet that could improve but personally I am not nervous about some old code that was written when Luke was still learning Ruby. Everyone has that, there are deployments that I did in the past that still work well but I cringe at the thought of doing it that way again. I suppose to me its a good sign, the developers skills are improving and they are critiquing their own code.</description>
		<content:encoded><![CDATA[<p>Thanks for the link, that sounds interesting. Im all for being able to re-use knowledge and Im sure that learning Chef would help with ruby things in the future but Im more of a python kind of guy. There are definitely some things with puppet that could improve but personally I am not nervous about some old code that was written when Luke was still learning Ruby. Everyone has that, there are deployments that I did in the past that still work well but I cringe at the thought of doing it that way again. I suppose to me its a good sign, the developers skills are improving and they are critiquing their own code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Ellison</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-920</link>
		<dc:creator>Justin Ellison</dc:creator>
		<pubDate>Fri, 31 Jul 2009 13:42:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-920</guid>
		<description>This webcast was an interesting watch: http://www.ducea.com/2009/06/30/osbridge-configuration-management-panel/.  BCFG2, Chef, Puppet, and CFEngine were all present for a panel discussion.  Before watching it, you should know that Chef was written by a long-time Puppet user who never contributed much back to Puppet, so there&#039;s some &quot;tension&quot; there.

At one point, the panel speaker asks, who comprises the majority of your user base?  Sysadmins was the answer for Puppet, and Devs was the answer for Chef.  One point for Puppet.  Google uses Puppet, which is another point for Puppet.  

However, the author of Puppet talks about how there&#039;s code in there that is still around from when he didn&#039;t know Ruby so well, which makes me a bit nervous.  Looking at some of my perl programs from when I was first learning it makes me shudder.

The one thing that I think is a huge positive is that Chef makes you learn a bit of Ruby to do the configuration.  Puppet has it&#039;s own DSL, but you can&#039;t use that knowledge anyplace else except for within Puppet.  What you learn about Chef&#039;s &quot;language&quot;, you can use later for scripts, Rails, whatever.

In the end, I think I&#039;ll go with Puppet, but I hope that the author has his eyes open and incorporates some of the things that Chef does well into future releases.

Good discussion!</description>
		<content:encoded><![CDATA[<p>This webcast was an interesting watch: <a href="http://www.ducea.com/2009/06/30/osbridge-configuration-management-panel/" rel="nofollow">http://www.ducea.com/2009/06/30/osbridge-configuration-management-panel/</a>.  BCFG2, Chef, Puppet, and CFEngine were all present for a panel discussion.  Before watching it, you should know that Chef was written by a long-time Puppet user who never contributed much back to Puppet, so there&#8217;s some &#8220;tension&#8221; there.</p>
<p>At one point, the panel speaker asks, who comprises the majority of your user base?  Sysadmins was the answer for Puppet, and Devs was the answer for Chef.  One point for Puppet.  Google uses Puppet, which is another point for Puppet.  </p>
<p>However, the author of Puppet talks about how there&#8217;s code in there that is still around from when he didn&#8217;t know Ruby so well, which makes me a bit nervous.  Looking at some of my perl programs from when I was first learning it makes me shudder.</p>
<p>The one thing that I think is a huge positive is that Chef makes you learn a bit of Ruby to do the configuration.  Puppet has it&#8217;s own DSL, but you can&#8217;t use that knowledge anyplace else except for within Puppet.  What you learn about Chef&#8217;s &#8220;language&#8221;, you can use later for scripts, Rails, whatever.</p>
<p>In the end, I think I&#8217;ll go with Puppet, but I hope that the author has his eyes open and incorporates some of the things that Chef does well into future releases.</p>
<p>Good discussion!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Anderson</title>
		<link>http://www.cmdln.org/2009/07/29/puppet-works-hard-to-make-sure-nodes-are-in-compliance/comment-page-1/#comment-918</link>
		<dc:creator>Nick Anderson</dc:creator>
		<pubDate>Fri, 31 Jul 2009 05:48:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.cmdln.org/?p=425#comment-918</guid>
		<description>Chef looks nice. However for my environment I think the knowledge of requiring ruby knowledge would not go over well. I&#039;m still drawn to bcfg2 but for now I just can&#039;t seem to get over the xml based configs. I&#039;d love to see a good writeup on chef though if you have done anything. I have a feeling that Chef would be a better fit where you have more developer types taking care of systems but maybe thats just a mis-conception on my part.</description>
		<content:encoded><![CDATA[<p>Chef looks nice. However for my environment I think the knowledge of requiring ruby knowledge would not go over well. I&#8217;m still drawn to bcfg2 but for now I just can&#8217;t seem to get over the xml based configs. I&#8217;d love to see a good writeup on chef though if you have done anything. I have a feeling that Chef would be a better fit where you have more developer types taking care of systems but maybe thats just a mis-conception on my part.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

