<?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: F5 acquires Acopia</title>
	<atom:link href="http://storagemojo.com/2007/08/06/f5-acquires-acopia/feed/" rel="self" type="application/rss+xml" />
	<link>http://storagemojo.com/2007/08/06/f5-acquires-acopia/</link>
	<description>Data storage info &#38; analysis</description>
	<pubDate>Fri, 08 Aug 2008 20:54:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Robert Pearson</title>
		<link>http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104750</link>
		<dc:creator>Robert Pearson</dc:creator>
		<pubDate>Wed, 08 Aug 2007 09:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104750</guid>
		<description>RE: Load balancers in general
Nice to have if you can get them. Nice to know when you need them
Every time I get in a "load balancer" discussion I'm reminded of the great, but short-lived, debate about whether a time division or statistical mux is the best way to go. Time division just came first. "Stat" muxes were always superior to time division.

So the question is, "Why are we screwing around with load_balancers when we need something better?" Load balancers came first? What comes next? When can I get it?

I've had to build my own for years. I never wanted to be in the "load balancer" software development, and certainly not in the software maintenance, business.
Where should load balancers operate? Do they communicate with each other? Is there an Open Standard?
Can I use Thin Provisioning as a load balancer?

I want this as a standard service handled by the (Storage? or App? or network? Other?) SLA.
Why don't disk drives talk to each other? We don't want them that smart?
Why don't disk drives have SSD and Flash in them for quick rebuilds?
Maybe all the engineers that could do this were on a bridge "too far" somewhere?</description>
		<content:encoded><![CDATA[<p>RE: Load balancers in general<br />
Nice to have if you can get them. Nice to know when you need them<br />
Every time I get in a &#8220;load balancer&#8221; discussion I&#8217;m reminded of the great, but short-lived, debate about whether a time division or statistical mux is the best way to go. Time division just came first. &#8220;Stat&#8221; muxes were always superior to time division.</p>
<p>So the question is, &#8220;Why are we screwing around with load_balancers when we need something better?&#8221; Load balancers came first? What comes next? When can I get it?</p>
<p>I&#8217;ve had to build my own for years. I never wanted to be in the &#8220;load balancer&#8221; software development, and certainly not in the software maintenance, business.<br />
Where should load balancers operate? Do they communicate with each other? Is there an Open Standard?<br />
Can I use Thin Provisioning as a load balancer?</p>
<p>I want this as a standard service handled by the (Storage? or App? or network? Other?) SLA.<br />
Why don&#8217;t disk drives talk to each other? We don&#8217;t want them that smart?<br />
Why don&#8217;t disk drives have SSD and Flash in them for quick rebuilds?<br />
Maybe all the engineers that could do this were on a bridge &#8220;too far&#8221; somewhere?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blake</title>
		<link>http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104353</link>
		<dc:creator>Blake</dc:creator>
		<pubDate>Tue, 07 Aug 2007 07:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104353</guid>
		<description>This is probably the best future Acopia could have had.  They were struggling to find a real home all alone.  With f5 leading with load balancers, it fits nicely into that market.  Good Stuff!</description>
		<content:encoded><![CDATA[<p>This is probably the best future Acopia could have had.  They were struggling to find a real home all alone.  With f5 leading with load balancers, it fits nicely into that market.  Good Stuff!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin Harris</title>
		<link>http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104336</link>
		<dc:creator>Robin Harris</dc:creator>
		<pubDate>Tue, 07 Aug 2007 06:27:03 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104336</guid>
		<description>Anarchist - I assume that is ironic -

I don't have an opinion about Rainfinity vs Acopia. I haven't looked at either of them enough. Hooking up with a $3.6 B market cap and a 40% growth rate can't hurt.

Max, I am unimpressed by Cisco's OEM only strategy for FC switches. I don't know what they have planned for Neopath, but at some point you have to engage with customers directly if you want to own the business. Networking guys generally don't get storage - look how Intransa has struggled - not to mention Cisco's weakness in storage.

Storage will never be part of Cisco's or F5's business. *Access* to storage is their business, but only if they go direct.

The low-intensity warfare between storage and servers in the datacenter shows no sign of ending. A crisp definition of the lines between the two is the best hope for a networking company to horn in on the massive storage revenue stream and margins.

If F5 markets it right, they could do very well. See networking guys comment above. 

I'm not bashing networking folks. The two markets are just different in ways that the networking mindset has difficulty discerning. The reverse is also true. Access, not persistence, is the key.

Robin</description>
		<content:encoded><![CDATA[<p>Anarchist - I assume that is ironic -</p>
<p>I don&#8217;t have an opinion about Rainfinity vs Acopia. I haven&#8217;t looked at either of them enough. Hooking up with a $3.6 B market cap and a 40% growth rate can&#8217;t hurt.</p>
<p>Max, I am unimpressed by Cisco&#8217;s OEM only strategy for FC switches. I don&#8217;t know what they have planned for Neopath, but at some point you have to engage with customers directly if you want to own the business. Networking guys generally don&#8217;t get storage - look how Intransa has struggled - not to mention Cisco&#8217;s weakness in storage.</p>
<p>Storage will never be part of Cisco&#8217;s or F5&#8217;s business. *Access* to storage is their business, but only if they go direct.</p>
<p>The low-intensity warfare between storage and servers in the datacenter shows no sign of ending. A crisp definition of the lines between the two is the best hope for a networking company to horn in on the massive storage revenue stream and margins.</p>
<p>If F5 markets it right, they could do very well. See networking guys comment above. </p>
<p>I&#8217;m not bashing networking folks. The two markets are just different in ways that the networking mindset has difficulty discerning. The reverse is also true. Access, not persistence, is the key.</p>
<p>Robin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104324</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Tue, 07 Aug 2007 05:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104324</guid>
		<description>With Cisco gobbling up Neopath, this is a smart move for F5.   These file virtualization appliances are essentially IP storage load balancers /traffic managers, and F5 always made a very good load balancer.

It'll be interesting to see how long it takes F5 to integrate it with it's main appliances.</description>
		<content:encoded><![CDATA[<p>With Cisco gobbling up Neopath, this is a smart move for F5.   These file virtualization appliances are essentially IP storage load balancers /traffic managers, and F5 always made a very good load balancer.</p>
<p>It&#8217;ll be interesting to see how long it takes F5 to integrate it with it&#8217;s main appliances.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the storage anarchist</title>
		<link>http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104290</link>
		<dc:creator>the storage anarchist</dc:creator>
		<pubDate>Tue, 07 Aug 2007 02:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/2007/08/06/f5-acquires-acopia/#comment-104290</guid>
		<description>Of course, the real question is: Does F5 make Acopia a stronger competitor to EMC's RainFinity, or not?

F5 who?</description>
		<content:encoded><![CDATA[<p>Of course, the real question is: Does F5 make Acopia a stronger competitor to EMC&#8217;s RainFinity, or not?</p>
<p>F5 who?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in -0.391 seconds -->
