<?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: Why do all deployment systems suck?</title>
	<atom:link href="http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/feed/" rel="self" type="application/rss+xml" />
	<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/</link>
	<description>Ramblings of a Cyclist Hacker</description>
	<lastBuildDate>Thu, 04 Mar 2010 03:39:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wakko.livejournal.com/</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3232</link>
		<dc:creator>wakko.livejournal.com/</dc:creator>
		<pubDate>Thu, 08 Oct 2009 00:13:21 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3232</guid>
		<description>I&#039;m a big proponent of using koji, rpm, and yum for app deployment, with puppet for config management and consistency assurance.  It&#039;s what we&#039;re using at $DAYJOB with around two dozen j2ee apps across ~1000 systems.

In general, where capistrano, maven, and others fail is providing integration with the sysadmins&#039; tools. Most of those tools try to recreate a dev-centric environment on every system, rather than promoting and enforcing reproducibility in any environment.

Plus, allowing rpm and yum to handle dependency resolution means that your code can have dependencies on packages provided by the distro without requiring your devs and sysadmins to document this multiple times in multiple locations.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a big proponent of using koji, rpm, and yum for app deployment, with puppet for config management and consistency assurance.  It&#8217;s what we&#8217;re using at $DAYJOB with around two dozen j2ee apps across ~1000 systems.</p>
<p>In general, where capistrano, maven, and others fail is providing integration with the sysadmins&#8217; tools. Most of those tools try to recreate a dev-centric environment on every system, rather than promoting and enforcing reproducibility in any environment.</p>
<p>Plus, allowing rpm and yum to handle dependency resolution means that your code can have dependencies on packages provided by the distro without requiring your devs and sysadmins to document this multiple times in multiple locations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emailtoid.net/i/b17cf6d9/&#8230;</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3231</link>
		<dc:creator>emailtoid.net/i/b17cf6d9/&#8230;</dc:creator>
		<pubDate>Wed, 07 Oct 2009 14:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3231</guid>
		<description>For Java application you can try to simply use maven with specific plugin.
Check this presentation:
http://www.slideshare.net/wakaleo/automated-deployment-with-maven-going-the-whole-nine-yards</description>
		<content:encoded><![CDATA[<p>For Java application you can try to simply use maven with specific plugin.<br />
Check this presentation:<br />
<a href="http://www.slideshare.net/wakaleo/automated-deployment-with-maven-going-the-whole-nine-yards" rel="nofollow">http://www.slideshare.net/wakaleo/automated-deployment-with-maven-going-the-whole-nine-yards</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3230</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Wed, 07 Oct 2009 13:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3230</guid>
		<description>&lt;a href=&quot;#comment-3226&quot; rel=&quot;nofollow&quot;&gt;@pwnguin.net/&lt;/a&gt;, &lt;a href=&quot;#comment-3227&quot; rel=&quot;nofollow&quot;&gt;@slashdotaccount&lt;/a&gt;: The problem with using Linux packages is that it presupposes that either all the developers are running Linux and can thus build the type of package you&#039;ve chosen (not true) or that you have some central, dedicated building resources (also not the case).  Otherwise, the route of building packages can work great.  It&#039;s just not appropriate here.</description>
		<content:encoded><![CDATA[<p><a href="#comment-3226" rel="nofollow">@pwnguin.net/</a>, <a href="#comment-3227" rel="nofollow">@slashdotaccount</a>: The problem with using Linux packages is that it presupposes that either all the developers are running Linux and can thus build the type of package you&#8217;ve chosen (not true) or that you have some central, dedicated building resources (also not the case).  Otherwise, the route of building packages can work great.  It&#8217;s just not appropriate here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3229</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Wed, 07 Oct 2009 13:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3229</guid>
		<description>&lt;a href=&quot;#comment-3225&quot; rel=&quot;nofollow&quot;&gt;@scottt.id.fedoraproject.org/&lt;/a&gt; I hadn&#039;t seen buildout, but it looks pretty tied to zope and plone and without any real notion of remote systems.</description>
		<content:encoded><![CDATA[<p><a href="#comment-3225" rel="nofollow">@scottt.id.fedoraproject.org/</a> I hadn&#8217;t seen buildout, but it looks pretty tied to zope and plone and without any real notion of remote systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3228</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Wed, 07 Oct 2009 13:50:42 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3228</guid>
		<description>&lt;a href=&quot;#comment-3223&quot; rel=&quot;nofollow&quot;&gt;@claimid.com/alikins&lt;/a&gt; Yeah, Fabric is the closest... unfortunately, still pretty far.  I sent a mail to their list to see if there&#039;s any chance of some of the things I&#039;m going to need being interesting to them.  We&#039;ll see what they say.  I mostly looked at Func as Seth suggested it but yeah, not there really right now.</description>
		<content:encoded><![CDATA[<p><a href="#comment-3223" rel="nofollow">@claimid.com/alikins</a> Yeah, Fabric is the closest&#8230; unfortunately, still pretty far.  I sent a mail to their list to see if there&#8217;s any chance of some of the things I&#8217;m going to need being interesting to them.  We&#8217;ll see what they say.  I mostly looked at Func as Seth suggested it but yeah, not there really right now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slashdotaccount</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3227</link>
		<dc:creator>slashdotaccount</dc:creator>
		<pubDate>Wed, 07 Oct 2009 09:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3227</guid>
		<description>What about apt or yum?</description>
		<content:encoded><![CDATA[<p>What about apt or yum?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pwnguin.net/</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3226</link>
		<dc:creator>pwnguin.net/</dc:creator>
		<pubDate>Wed, 07 Oct 2009 05:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3226</guid>
		<description>I&#039;m not sure what&#039;s wrong with cfengine / puppet for config management and just using .deb packages (or .rpm). At least in debian, it seems simple enough.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure what&#8217;s wrong with cfengine / puppet for config management and just using .deb packages (or .rpm). At least in debian, it seems simple enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scottt.id.fedoraproject.org/</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3225</link>
		<dc:creator>scottt.id.fedoraproject.org/</dc:creator>
		<pubDate>Wed, 07 Oct 2009 05:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3225</guid>
		<description>&lt;a href=&quot;//www.buildout.org/\&quot; rel=&quot;nofollow&quot;&gt;zc.buildout&lt;/a&gt; has quite a few &lt;a href=&quot;action=browse&amp;show=all&amp;c=512\&quot; rel=&quot;nofollow&quot;&gt;recipes&lt;/a&gt; for python programs. I&#039;ve never used it with jetty or Tomcat though.</description>
		<content:encoded><![CDATA[<p><a href="//www.buildout.org/\" rel="nofollow">zc.buildout</a> has quite a few <a href="action=browse&amp;show=all&amp;c=512\" rel="nofollow">recipes</a> for python programs. I&#8217;ve never used it with jetty or Tomcat though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: claimid.com/alikins</title>
		<link>http://velohacker.com/fedora-notes/why-do-all-deployment-systems-suck/comment-page-1/#comment-3223</link>
		<dc:creator>claimid.com/alikins</dc:creator>
		<pubDate>Wed, 07 Oct 2009 03:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://velohacker.com/?p=3973#comment-3223</guid>
		<description>I don&#039;t really think of Func as a deployment tool. Though I would like to eventually build a deployment/orchestration tool atop of it. That said, it looks like a Fabric is heading in the direction I was thinking of.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t really think of Func as a deployment tool. Though I would like to eventually build a deployment/orchestration tool atop of it. That said, it looks like a Fabric is heading in the direction I was thinking of.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
