<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Providers on cd ~</title><link>https://www.rottenbytes.info/tags/providers/</link><description>Recent content in Providers on cd ~</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Mar 2011 22:16:44 +0000</lastBuildDate><atom:link href="https://www.rottenbytes.info/tags/providers/index.xml" rel="self" type="application/rss+xml"/><item><title>Generic use of chef providers in mcollective</title><link>https://www.rottenbytes.info/2011/03/11/generic-use-of-chef-providers-in-mcollective/</link><pubDate>Fri, 11 Mar 2011 22:16:44 +0000</pubDate><guid>https://www.rottenbytes.info/2011/03/11/generic-use-of-chef-providers-in-mcollective/</guid><description>&lt;p&gt;&lt;img class="alignleft size-full wp-image-62" title="eth0" src="http://www.rottenbytes.info/wp-content/uploads/2009/02/eth0.jpg" alt="eth0" width="80" height="103" /&gt;This post follows my &lt;a href="http://www.rottenbytes.info/?p=404"&gt;previous&lt;/a&gt; one, dealing with the reuse of chef providers of chef in mcollective. In the comments Adam Jacob had &lt;a href="http://www.rottenbytes.info/?p=404#comment-1405"&gt;an interesting word&lt;/a&gt; and when I wrote my second agent, to manage package I saw it would be a piece of cake to write a really generic agent, due to the nature of chef resource (and the way to invoke them)&lt;/p&gt;</description></item></channel></rss>