<?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: Incremental deployment</title>
	<atom:link href="http://nutrun.com/weblog/incremental-deployment/feed/" rel="self" type="application/rss+xml" />
	<link>http://nutrun.com/weblog/incremental-deployment/</link>
	<description>nutrun</description>
	<lastBuildDate>Mon, 28 Jun 2010 07:35:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: George Malamidis</title>
		<link>http://nutrun.com/weblog/incremental-deployment/comment-page-1/#comment-1800</link>
		<dc:creator>George Malamidis</dc:creator>
		<pubDate>Mon, 04 Jan 2010 12:11:27 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=342#comment-1800</guid>
		<description>Hi Andy,

We use a third party DNS service that load balances between AWS regions and between the AWS / &quot;non-AWS&quot; servers. All requests go to one domain that gets delegated internally, at DNS level, so clients only have to deal with one DNS entry that never changes.</description>
		<content:encoded><![CDATA[<p>Hi Andy,</p>
<p>We use a third party DNS service that load balances between AWS regions and between the AWS / &#8220;non-AWS&#8221; servers. All requests go to one domain that gets delegated internally, at DNS level, so clients only have to deal with one DNS entry that never changes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Johnstone</title>
		<link>http://nutrun.com/weblog/incremental-deployment/comment-page-1/#comment-1792</link>
		<dc:creator>Andrew Johnstone</dc:creator>
		<pubDate>Sat, 02 Jan 2010 13:25:46 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=342#comment-1792</guid>
		<description>Hi,

I&#039;m curious to know how you handle high availability, in particular with your DNS and non AWS failover. In the event of complete failure at our current provider we can reconfigure all of our services within one hour onto EC2. However the biggest issue for us is redirecting DNS or redirecting traffic to the new servers. The clients that use our services are large corporates that cache DNS.

Cheers

Andy</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;m curious to know how you handle high availability, in particular with your DNS and non AWS failover. In the event of complete failure at our current provider we can reconfigure all of our services within one hour onto EC2. However the biggest issue for us is redirecting DNS or redirecting traffic to the new servers. The clients that use our services are large corporates that cache DNS.</p>
<p>Cheers</p>
<p>Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: volcane</title>
		<link>http://nutrun.com/weblog/incremental-deployment/comment-page-1/#comment-1753</link>
		<dc:creator>volcane</dc:creator>
		<pubDate>Tue, 22 Dec 2009 15:43:26 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=342#comment-1753</guid>
		<description>Here&#039;s something similar I came up with recently:

http://www.devco.net/archives/2009/11/06/test_driven_deployment_-_mcollective_puppet_cucumber.php</description>
		<content:encoded><![CDATA[<p>Here&#8217;s something similar I came up with recently:</p>
<p><a href="http://www.devco.net/archives/2009/11/06/test_driven_deployment_-_mcollective_puppet_cucumber.php" rel="nofollow">http://www.devco.net/archives/2009/11/06/test_driven_deployment_-_mcollective_puppet_cucumber.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Incremental deployment « nutrun -- Topsy.com</title>
		<link>http://nutrun.com/weblog/incremental-deployment/comment-page-1/#comment-1752</link>
		<dc:creator>Tweets that mention Incremental deployment « nutrun -- Topsy.com</dc:creator>
		<pubDate>Tue, 22 Dec 2009 15:03:38 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=342#comment-1752</guid>
		<description>[...] This post was mentioned on Twitter by Peter Waldschmidt, George Malamidis. George Malamidis said: Me on @pingles&#039;s and @andykent&#039;s critical, high availability system deployment strategy http://bit.ly/8ZJxIz [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Peter Waldschmidt, George Malamidis. George Malamidis said: Me on @pingles&#39;s and @andykent&#39;s critical, high availability system deployment strategy <a href="http://bit.ly/8ZJxIz" rel="nofollow">http://bit.ly/8ZJxIz</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmytro Shteflyuk</title>
		<link>http://nutrun.com/weblog/incremental-deployment/comment-page-1/#comment-1751</link>
		<dc:creator>Dmytro Shteflyuk</dc:creator>
		<pubDate>Tue, 22 Dec 2009 14:44:31 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=342#comment-1751</guid>
		<description>Why not use &lt;a href=&quot;http://weblog.jamisbuck.org/2007/7/23/capistrano-multistage&quot; rel=&quot;nofollow&quot;&gt;capistrano multistage&lt;/a&gt;?</description>
		<content:encoded><![CDATA[<p>Why not use <a href="http://weblog.jamisbuck.org/2007/7/23/capistrano-multistage" rel="nofollow">capistrano multistage</a>?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
