<?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"
	>
<channel>
	<title>Comments on: The enterprise and open-source storage</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/storage-soup/the-enterprise-and-open-source-storage/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/storage-soup/the-enterprise-and-open-source-storage/</link>
	<description>A SearchStorage.com blog.</description>
	<pubDate>Sat, 28 Nov 2009 10:56:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jesse</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/the-enterprise-and-open-source-storage/#comment-7175</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Tue, 01 Jul 2008 03:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/06/25/the-enterprise-and-open-source-storage/#comment-7175</guid>
		<description>Centerra - largely a "cheap" storage solution supported by a comprehensive software package.  It's a great option for archival and would probably be suitable for a high-bandwidth archiving application if it was capable of...well, higher bandwidth.

Support and resiliency - that's a great way to put it.  You might be able to put together a solution that is resilient through multiple Raid levels.  (ID Software Raid-5 striped across hardware Raid-5 or something equally complex) but you're still the one getting the page at 4am when the system jumps the shark.

Personally I'd pay big money *NOT* to be the one getting the page at 4am.  Especially if it's someone else's money.  :)

I prefer the casual email the following morning from EMC stating - "A drive went bad, we fixed it, no host impact."</description>
		<content:encoded><![CDATA[<p>Centerra - largely a &#8220;cheap&#8221; storage solution supported by a comprehensive software package.  It&#8217;s a great option for archival and would probably be suitable for a high-bandwidth archiving application if it was capable of&#8230;well, higher bandwidth.</p>
<p>Support and resiliency - that&#8217;s a great way to put it.  You might be able to put together a solution that is resilient through multiple Raid levels.  (ID Software Raid-5 striped across hardware Raid-5 or something equally complex) but you&#8217;re still the one getting the page at 4am when the system jumps the shark.</p>
<p>Personally I&#8217;d pay big money *NOT* to be the one getting the page at 4am.  Especially if it&#8217;s someone else&#8217;s money.  <img src='http://itknowledgeexchange.techtarget.com/storage-soup/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
I prefer the casual email the following morning from EMC stating - &#8220;A drive went bad, we fixed it, no host impact.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Chalmers</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/the-enterprise-and-open-source-storage/#comment-7174</link>
		<dc:creator>Steve Chalmers</dc:creator>
		<pubDate>Tue, 01 Jul 2008 00:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/06/25/the-enterprise-and-open-source-storage/#comment-7174</guid>
		<description>Sitting in an obscure corner of the Gates building on the Stanford campus is a computer motherboard and some disks in an enclosure made of Legos.  It's protected in a display case, of course.  That was Google's first computer.

Up 101 in Mountain View in the computer museum is a rack, with flimsy sheet metal trays to which computer motherboards (and disks) are attached.  That's Google's first cluster.

I work in the storage business, and have never set foot at Google.  Best we can tell, nearly all of Google's business today is run off of huge clusters of client motherboards + client disks, attached to trays descended from what's in the computer museum.  If a tray fails, the software works around it by rerouting work to one of the trays with a duplicate of its data.

Compared to that solution, the Tyan motherboard, external SATA controller, InfiniBand, and probably premium SATA disks would seem gold plated.  And most importantly in financial services where milliseconds matter, those enterprise array controllers don't add their millisecond (or yes, these days, even a tenth of a millisecond) to the latency of an I/O.

Oh, and the Thumper would cost far more than the Tyan homebrew.  Still vastly less than a DMX or competitor.

From the point of view of preserving my job, those kinds of solutions scare me.  But the software cost of developing them is quite high, and having a person on site with both skills and parts to repair is also expensive.  So for now I sleep at night.</description>
		<content:encoded><![CDATA[<p>Sitting in an obscure corner of the Gates building on the Stanford campus is a computer motherboard and some disks in an enclosure made of Legos.  It&#8217;s protected in a display case, of course.  That was Google&#8217;s first computer.</p>
<p>Up 101 in Mountain View in the computer museum is a rack, with flimsy sheet metal trays to which computer motherboards (and disks) are attached.  That&#8217;s Google&#8217;s first cluster.</p>
<p>I work in the storage business, and have never set foot at Google.  Best we can tell, nearly all of Google&#8217;s business today is run off of huge clusters of client motherboards + client disks, attached to trays descended from what&#8217;s in the computer museum.  If a tray fails, the software works around it by rerouting work to one of the trays with a duplicate of its data.</p>
<p>Compared to that solution, the Tyan motherboard, external SATA controller, InfiniBand, and probably premium SATA disks would seem gold plated.  And most importantly in financial services where milliseconds matter, those enterprise array controllers don&#8217;t add their millisecond (or yes, these days, even a tenth of a millisecond) to the latency of an I/O.</p>
<p>Oh, and the Thumper would cost far more than the Tyan homebrew.  Still vastly less than a DMX or competitor.</p>
<p>From the point of view of preserving my job, those kinds of solutions scare me.  But the software cost of developing them is quite high, and having a person on site with both skills and parts to repair is also expensive.  So for now I sleep at night.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Lewis</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/the-enterprise-and-open-source-storage/#comment-7173</link>
		<dc:creator>Karl Lewis</dc:creator>
		<pubDate>Thu, 26 Jun 2008 19:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/06/25/the-enterprise-and-open-source-storage/#comment-7173</guid>
		<description>SUN's acquisition of Lustre has the potential to make them the risin star (pun intended) of scalable, commodity storage.  Combining Lustre's ability to scale performance across nodes with ZFS' immense scalability and rich feature set adds up to a rich product set.  I've heard people refer to this mythical combination as "the death-knell of enterprise storage vendors".  Being able to use cost-effective Thumpers as storage bricks and combine them in interesting, automated ways will certainly make users think twice about their next storage purchase.  But, who knows if this product combination will ever exist?</description>
		<content:encoded><![CDATA[<p>SUN&#8217;s acquisition of Lustre has the potential to make them the risin star (pun intended) of scalable, commodity storage.  Combining Lustre&#8217;s ability to scale performance across nodes with ZFS&#8217; immense scalability and rich feature set adds up to a rich product set.  I&#8217;ve heard people refer to this mythical combination as &#8220;the death-knell of enterprise storage vendors&#8221;.  Being able to use cost-effective Thumpers as storage bricks and combine them in interesting, automated ways will certainly make users think twice about their next storage purchase.  But, who knows if this product combination will ever exist?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carter George</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/the-enterprise-and-open-source-storage/#comment-7172</link>
		<dc:creator>Carter George</dc:creator>
		<pubDate>Thu, 26 Jun 2008 04:39:42 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/06/25/the-enterprise-and-open-source-storage/#comment-7172</guid>
		<description>Sun's Thumper is a perfectly good feature-rich Unix file system.   There are others like it, but combined with Sun's strong and reasonably-priced  Thumper hardware, it's an all around good middle-of-the-road storage solution.  What's amazing to me is the positive spin on ZFS - it's just a well-featured single node Unix file system.    Better than the free ones you get with Linux, but it's not clustered, not distributed, does not have a global namespace to stitch together "bricks" of commodity storage in to a unified fault tolerant whole.    It's none of those things.
What will be far more challenging to the existing enterprise status quo is that the big boys are all bringing out scalable commodity storage offeringsof their own, ones that will undermine the margins of their own high-end Enterprise storage platforms.  EMC has announced Hulk and Maui, and is even shipping Hulk, if not the more elusive Maui.   IBM is readying XIV.   HP has announced their CFS-based Extreme Data Storage built on Proliant blades.    There are your top three technology vendors, period, launching scalable, commodity based storage platforms.   It's one thing for Ibrix, Isilon, Panasas, and PolyServe to bring those things to market - it's another when it's HP, IBM, and EMC.     So the landscape is changing, and the relentless drive to commodity price points that wiped out the Enterprise Server 5 years ago is indeed about to start on storage.</description>
		<content:encoded><![CDATA[<p>Sun&#8217;s Thumper is a perfectly good feature-rich Unix file system.   There are others like it, but combined with Sun&#8217;s strong and reasonably-priced  Thumper hardware, it&#8217;s an all around good middle-of-the-road storage solution.  What&#8217;s amazing to me is the positive spin on ZFS - it&#8217;s just a well-featured single node Unix file system.    Better than the free ones you get with Linux, but it&#8217;s not clustered, not distributed, does not have a global namespace to stitch together &#8220;bricks&#8221; of commodity storage in to a unified fault tolerant whole.    It&#8217;s none of those things.<br />
What will be far more challenging to the existing enterprise status quo is that the big boys are all bringing out scalable commodity storage offeringsof their own, ones that will undermine the margins of their own high-end Enterprise storage platforms.  EMC has announced Hulk and Maui, and is even shipping Hulk, if not the more elusive Maui.   IBM is readying XIV.   HP has announced their CFS-based Extreme Data Storage built on Proliant blades.    There are your top three technology vendors, period, launching scalable, commodity based storage platforms.   It&#8217;s one thing for Ibrix, Isilon, Panasas, and PolyServe to bring those things to market - it&#8217;s another when it&#8217;s HP, IBM, and EMC.     So the landscape is changing, and the relentless drive to commodity price points that wiped out the Enterprise Server 5 years ago is indeed about to start on storage.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->