<?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: Fault Tolerance: Diamond in the Rough</title>
	<atom:link href="http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/</link>
	<description>Virtualization, Cloud Computing, Technology of Business &#38; Business of Technology</description>
	<lastBuildDate>Fri, 12 Mar 2010 05:02:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Convergence of Private Clouds Presentation &#124; latoga labs</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-540</link>
		<dc:creator>Convergence of Private Clouds Presentation &#124; latoga labs</dc:creator>
		<pubDate>Wed, 29 Jul 2009 18:14:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-540</guid>
		<description>[...] Fault Tolerance: Diamond in the Rough with links to additional FT [...]</description>
		<content:encoded><![CDATA[<p>[...] Fault Tolerance: Diamond in the Rough with links to additional FT [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Bond</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-502</link>
		<dc:creator>Nick Bond</dc:creator>
		<pubDate>Wed, 08 Jul 2009 12:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-502</guid>
		<description>Interuptions to service to a sub-set of your users is different to application downtime, at least in my mind.

Any modern online application that cannot handle the interuption of a connection etc. is poorly architected.

I would suggest that you would have to use both (or just load balancing) for true full availability. Geographic seperation of servers is essential to maintain systems running in case of a catastrophic failure (fire, aircraft strike etc). Therefore global load balancing would be needed, I suspect running FT across multiple locations would be fraught with problems (if not impossible)?

Nick</description>
		<content:encoded><![CDATA[<p>Interuptions to service to a sub-set of your users is different to application downtime, at least in my mind.</p>
<p>Any modern online application that cannot handle the interuption of a connection etc. is poorly architected.</p>
<p>I would suggest that you would have to use both (or just load balancing) for true full availability. Geographic seperation of servers is essential to maintain systems running in case of a catastrophic failure (fire, aircraft strike etc). Therefore global load balancing would be needed, I suspect running FT across multiple locations would be fraught with problems (if not impossible)?</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: latoga</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-499</link>
		<dc:creator>latoga</dc:creator>
		<pubDate>Tue, 07 Jul 2009 15:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-499</guid>
		<description>The use cases for Load Balancing versus Fault Tolerance are very different Nick.  Typically, you wouldn&#039;t use both.  As I described, if your application requires zero downtime the additional resources you are using is the price of that zero downtime and load balancing can not guarantee zero downtime.  This zero downtime requirement is typically for applications that are critical to a businesses operations.  The whole point here is that FT makes zero downtime cost a lot less than it did previously!</description>
		<content:encoded><![CDATA[<p>The use cases for Load Balancing versus Fault Tolerance are very different Nick.  Typically, you wouldn&#8217;t use both.  As I described, if your application requires zero downtime the additional resources you are using is the price of that zero downtime and load balancing can not guarantee zero downtime.  This zero downtime requirement is typically for applications that are critical to a businesses operations.  The whole point here is that FT makes zero downtime cost a lot less than it did previously!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: latoga</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-498</link>
		<dc:creator>latoga</dc:creator>
		<pubDate>Tue, 07 Jul 2009 15:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-498</guid>
		<description>This is a great point John, I hadn&#039;t considered the option of turning on FT just for a busy peak period for an application.  Many of my clients are considering building dedicated environments targeted for internal users who require higher availability (i.e., SRM enabled clusters, FT specific sub-clusters).  The ability to vMotion a VM to a FT cluster and turn it on for a month when it is really needed allows an IT organization to be more responsive to the needs of their customers.  

Now, to enable this for self service and include a way to calculate a charge for this via vCenter ChargeBack!  :-)</description>
		<content:encoded><![CDATA[<p>This is a great point John, I hadn&#8217;t considered the option of turning on FT just for a busy peak period for an application.  Many of my clients are considering building dedicated environments targeted for internal users who require higher availability (i.e., SRM enabled clusters, FT specific sub-clusters).  The ability to vMotion a VM to a FT cluster and turn it on for a month when it is really needed allows an IT organization to be more responsive to the needs of their customers.  </p>
<p>Now, to enable this for self service and include a way to calculate a charge for this via vCenter ChargeBack!  <img src='http://www.latogalabs.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: latoga</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-497</link>
		<dc:creator>latoga</dc:creator>
		<pubDate>Tue, 07 Jul 2009 15:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-497</guid>
		<description>Thanks for sharing your script William.  Great addition to be able to manage FT from the command line!</description>
		<content:encoded><![CDATA[<p>Thanks for sharing your script William.  Great addition to be able to manage FT from the command line!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Bond</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-495</link>
		<dc:creator>Nick Bond</dc:creator>
		<pubDate>Tue, 07 Jul 2009 10:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-495</guid>
		<description>Nice feature, but surely the cost (in terms of resource) are too high?

It must be more practical to run two instances of the application (which is in effect what you are doing with FT), and actually use them by adding a load balancer into the infrastructure. Particularly if you need to then scale the application, two running instances with FT means four lots of resource...

Load balancing especially makes sense when you can use a Virtual Appliance version.

Nick</description>
		<content:encoded><![CDATA[<p>Nice feature, but surely the cost (in terms of resource) are too high?</p>
<p>It must be more practical to run two instances of the application (which is in effect what you are doing with FT), and actually use them by adding a load balancer into the infrastructure. Particularly if you need to then scale the application, two running instances with FT means four lots of resource&#8230;</p>
<p>Load balancing especially makes sense when you can use a Virtual Appliance version.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Troyer</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-493</link>
		<dc:creator>John Troyer</dc:creator>
		<pubDate>Tue, 07 Jul 2009 05:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-493</guid>
		<description>What expanded my consciousness during our &lt;a href=&quot;http://blogs.vmware.com/vmtn/2009/07/vmware-studio-2-beta-vapps-community-roundtable-podcast-54.html&quot; rel=&quot;nofollow&quot;&gt;podcast with the FT team&lt;/a&gt; was the notion that FT was so easy to use that you could even just turn it on for a few weeks during the holiday or end of the quarter rush and then turn it off again later. 

The fact that FT &lt;i&gt;isn&#039;t&lt;/i&gt; a multi-million dollar solution and instead is a feature that can be turned on with a flick of the mouse really opens up the use cases -- could be quite a game-changing tool in your toolbox.</description>
		<content:encoded><![CDATA[<p>What expanded my consciousness during our <a href="http://blogs.vmware.com/vmtn/2009/07/vmware-studio-2-beta-vapps-community-roundtable-podcast-54.html" rel="nofollow">podcast with the FT team</a> was the notion that FT was so easy to use that you could even just turn it on for a few weeks during the holiday or end of the quarter rush and then turn it off again later. </p>
<p>The fact that FT <i>isn&#8217;t</i> a multi-million dollar solution and instead is a feature that can be turned on with a flick of the mouse really opens up the use cases &#8212; could be quite a game-changing tool in your toolbox.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Lam</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-492</link>
		<dc:creator>William Lam</dc:creator>
		<pubDate>Tue, 07 Jul 2009 04:22:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-492</guid>
		<description>This is another good link to add to the resources for FT: http://www.yellow-bricks.com/2009/07/01/ftcli-pl-vmware-fault-tolerant-managment/</description>
		<content:encoded><![CDATA[<p>This is another good link to add to the resources for FT: <a href="http://www.yellow-bricks.com/2009/07/01/ftcli-pl-vmware-fault-tolerant-managment/" rel="nofollow">http://www.yellow-bricks.com/2009/07/01/ftcli-pl-vmware-fault-tolerant-managment/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware Announces vSphere 4 Cloud OS &#124; latoga labs</title>
		<link>http://www.latogalabs.com/2009/07/fault-tolerance-diamond-in-the-rough/comment-page-1/#comment-491</link>
		<dc:creator>VMware Announces vSphere 4 Cloud OS &#124; latoga labs</dc:creator>
		<pubDate>Tue, 07 Jul 2009 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=709#comment-491</guid>
		<description>[...] Fault Tolerance and the hidden revolution this provides [...]</description>
		<content:encoded><![CDATA[<p>[...] Fault Tolerance and the hidden revolution this provides [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
