<?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: VMware: Top of todays requirements list</title>
	<atom:link href="http://blog.nigelpoulton.com/vmware-top-of-todays-requirements-list/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nigelpoulton.com/vmware-top-of-todays-requirements-list/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
	<description>with nigel poulton</description>
	<lastBuildDate>Thu, 09 Feb 2012 07:49:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Maria</title>
		<link>http://blog.nigelpoulton.com/vmware-top-of-todays-requirements-list/comment-page-1/#comment-1828</link>
		<dc:creator>Maria</dc:creator>
		<pubDate>Thu, 09 Feb 2012 05:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nigelpoulton.com/?p=837#comment-1828</guid>
		<description>No. I think it just means pnoerrmafce for your randomly accessed blocks will continue to kick arse, but your sequential I/O to same VMFS volume would continue to be slowed down because of the interruption of random I/O at the VMware level.  A Compellent storage architect would be more qualified to answer, but the slowdown that Scott is talking about is at VMware level and independent of the type of storage.</description>
		<content:encoded><![CDATA[<p>No. I think it just means pnoerrmafce for your randomly accessed blocks will continue to kick arse, but your sequential I/O to same VMFS volume would continue to be slowed down because of the interruption of random I/O at the VMware level.  A Compellent storage architect would be more qualified to answer, but the slowdown that Scott is talking about is at VMware level and independent of the type of storage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Poulton</title>
		<link>http://blog.nigelpoulton.com/vmware-top-of-todays-requirements-list/comment-page-1/#comment-819</link>
		<dc:creator>Nigel Poulton</dc:creator>
		<pubDate>Mon, 26 Jul 2010 15:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nigelpoulton.com/?p=837#comment-819</guid>
		<description>John,

Thanks for your comments and I totally agree.  I suppose my comments should have been more along the lines of &quot;when announcing new products and rev&#039;s of existing products......&quot;.  Key is that when making announcements focus should be less on improved feeds and speeds improvements and more on integration with products and services higher up the stack.

Thanks for your comments.

Fatima,

I think we&#039;re on the same page. Integration higher layers in the stack is the key, Im just suggesting that VMware seems to have the momentum at the moment. 

I also agree that the vendors ignore the other hypervisors at their own peril. Personally I can only see the other hypervisors start to catch-up with VMware (Hyper-V especiallly).

Nigel</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Thanks for your comments and I totally agree.  I suppose my comments should have been more along the lines of &#8220;when announcing new products and rev&#8217;s of existing products&#8230;&#8230;&#8221;.  Key is that when making announcements focus should be less on improved feeds and speeds improvements and more on integration with products and services higher up the stack.</p>
<p>Thanks for your comments.</p>
<p>Fatima,</p>
<p>I think we&#8217;re on the same page. Integration higher layers in the stack is the key, Im just suggesting that VMware seems to have the momentum at the moment. </p>
<p>I also agree that the vendors ignore the other hypervisors at their own peril. Personally I can only see the other hypervisors start to catch-up with VMware (Hyper-V especiallly).</p>
<p>Nigel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fatima Stoneknuckle</title>
		<link>http://blog.nigelpoulton.com/vmware-top-of-todays-requirements-list/comment-page-1/#comment-818</link>
		<dc:creator>Fatima Stoneknuckle</dc:creator>
		<pubDate>Mon, 26 Jul 2010 14:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nigelpoulton.com/?p=837#comment-818</guid>
		<description>&lt;p&gt;Good points Nigel.&#160; Indeed, storage vendors should, and have always needed to, keep their eye on the portions of the IT stack above them, especially those with momentum.&#160; To round out the perspective, however, would be the point that&#160;there are significant numbers of&#160;IT customers who are leary of VMware hegemony and pricing, and of becoming too dependent upon them.&#160; As such, they are cautious about adopting any or too many&#160;of VMware&#039;s SW functionality&#160;outside of the hypervisor level where VMware has taken on management functions.&#160;&#160; And, they may very well seek to diversify at the hypervisor level as well, by adopting Xen, Hyper-V, or KVM in some environments.&#160;&#160; This only suggests that storage vendors cannot afford to&#160;neglect these other virtualization platforms&#160;either.&#160;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Good points Nigel.&nbsp; Indeed, storage vendors should, and have always needed to, keep their eye on the portions of the IT stack above them, especially those with momentum.&nbsp; To round out the perspective, however, would be the point that&nbsp;there are significant numbers of&nbsp;IT customers who are leary of VMware hegemony and pricing, and of becoming too dependent upon them.&nbsp; As such, they are cautious about adopting any or too many&nbsp;of VMware&#39;s SW functionality&nbsp;outside of the hypervisor level where VMware has taken on management functions.&nbsp;&nbsp; And, they may very well seek to diversify at the hypervisor level as well, by adopting Xen, Hyper-V, or KVM in some environments.&nbsp;&nbsp; This only suggests that storage vendors cannot afford to&nbsp;neglect these other virtualization platforms&nbsp;either.&nbsp;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Troyer</title>
		<link>http://blog.nigelpoulton.com/vmware-top-of-todays-requirements-list/comment-page-1/#comment-813</link>
		<dc:creator>John Troyer</dc:creator>
		<pubDate>Fri, 23 Jul 2010 19:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nigelpoulton.com/?p=837#comment-813</guid>
		<description>&lt;p&gt;One good thing is that VAAI integration is, for most vendors, a firmware upgrade. Let&#039;s not trivialize the effort required to implement the new software, but it does mean that integration can be delivered in a mortal timeframe and can often work with the current generation of gear.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>One good thing is that VAAI integration is, for most vendors, a firmware upgrade. Let&#39;s not trivialize the effort required to implement the new software, but it does mean that integration can be delivered in a mortal timeframe and can often work with the current generation of gear.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

