<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Hacking Culture for Continuous Delivery</title>
	<atom:link href="http://devops.com/2012/11/08/hacking-culture-for-continuous-delivery/feed/" rel="self" type="application/rss+xml" />
	<link>http://devops.com/2012/11/08/hacking-culture-for-continuous-delivery/</link>
	<description>Finishing what agile development started</description>
	<lastBuildDate>Wed, 24 Apr 2013 12:41:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: developers</title>
		<link>http://devops.com/2012/11/08/hacking-culture-for-continuous-delivery/#comment-261</link>
		<dc:creator><![CDATA[developers]]></dc:creator>
		<pubDate>Mon, 19 Nov 2012 10:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://devops.com/?p=338#comment-261</guid>
		<description><![CDATA[Infrastructure as Code. This is the most important entry point, providing full-stack automation. Commodity hardware can be used with this approach, as reliability is provided in the software stack. Datacenters must have APIs; you can’t rely on humans to take action. All services including things like DNS have to follow this model. Infrastructure becomes a product, and the app dev team is the customer. Stackify enables agile &lt;a href=&quot;http://www.stackify.com/&quot; rel=&quot;nofollow&quot;&gt;developers&lt;/a&gt; to provide agile support by giving developers production access to their applications, servers, and databases to improve their ability to do application support and troubleshooting.]]></description>
		<content:encoded><![CDATA[<p>Infrastructure as Code. This is the most important entry point, providing full-stack automation. Commodity hardware can be used with this approach, as reliability is provided in the software stack. Datacenters must have APIs; you can’t rely on humans to take action. All services including things like DNS have to follow this model. Infrastructure becomes a product, and the app dev team is the customer. Stackify enables agile <a href="http://www.stackify.com/" rel="nofollow">developers</a> to provide agile support by giving developers production access to their applications, servers, and databases to improve their ability to do application support and troubleshooting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bawigga</title>
		<link>http://devops.com/2012/11/08/hacking-culture-for-continuous-delivery/#comment-204</link>
		<dc:creator><![CDATA[bawigga]]></dc:creator>
		<pubDate>Sun, 11 Nov 2012 19:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://devops.com/?p=338#comment-204</guid>
		<description><![CDATA[&quot;Common Attributes of Web Scale Cultures ... You must also design for failure, and this is where a lot of teams struggle.&quot;

What does it mean to design for failure? Just touching on the face that you should write pretty defensive code?]]></description>
		<content:encoded><![CDATA[<p>&#8220;Common Attributes of Web Scale Cultures &#8230; You must also design for failure, and this is where a lot of teams struggle.&#8221;</p>
<p>What does it mean to design for failure? Just touching on the face that you should write pretty defensive code?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gil Hoffer</title>
		<link>http://devops.com/2012/11/08/hacking-culture-for-continuous-delivery/#comment-196</link>
		<dc:creator><![CDATA[Gil Hoffer]]></dc:creator>
		<pubDate>Fri, 09 Nov 2012 09:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://devops.com/?p=338#comment-196</guid>
		<description><![CDATA[Great post! I relate deeply to all the points mentioned in it.
While I agree probably the greatest challenge is a cultural one - taking an org with distinct dev, ops, and test groups with existing practices, prejudices and tradition, and make everyone switch their line of thought to continuous delivery is not a simple battle.

Unfortunately though, even if everyone in the organization is aligned towards continuous delivery - it is still pretty hard to achieve (as not every aspect of the infrastructure is controlled by an API, and it requires a massive effort from the organization). We need to be able to * completely* abstract the application from the underlying infrastructure - similarly to what hypervisors do between physical servers and operating systems.

I work for Ravello Systems, where we try to achieve just that - supplying a new universal platform which abstracts (existing and new) applications from the underlying cloud (all aspects - compute, network and storage). You can check us out at &lt;a href=&quot;http://bitly.com/Te5KRZ&quot; rel=&quot;nofollow&quot;&gt;http://bitly.com/Te5KRZ&lt;/a&gt;]]></description>
		<content:encoded><![CDATA[<p>Great post! I relate deeply to all the points mentioned in it.<br />
While I agree probably the greatest challenge is a cultural one &#8211; taking an org with distinct dev, ops, and test groups with existing practices, prejudices and tradition, and make everyone switch their line of thought to continuous delivery is not a simple battle.</p>
<p>Unfortunately though, even if everyone in the organization is aligned towards continuous delivery &#8211; it is still pretty hard to achieve (as not every aspect of the infrastructure is controlled by an API, and it requires a massive effort from the organization). We need to be able to * completely* abstract the application from the underlying infrastructure &#8211; similarly to what hypervisors do between physical servers and operating systems.</p>
<p>I work for Ravello Systems, where we try to achieve just that &#8211; supplying a new universal platform which abstracts (existing and new) applications from the underlying cloud (all aspects &#8211; compute, network and storage). You can check us out at <a href="http://bitly.com/Te5KRZ" rel="nofollow">http://bitly.com/Te5KRZ</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
