<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: VMware ESX 5</title>
	<atom:link href="http://vinf.net/2009/08/07/vmware-esx-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://vinf.net/2009/08/07/vmware-esx-5/</link>
	<description>My ramblings on the stuff that holds it all together</description>
	<lastBuildDate>Tue, 14 Feb 2012 12:29:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Omid Boloori</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-4369</link>
		<dc:creator><![CDATA[Omid Boloori]]></dc:creator>
		<pubDate>Sat, 14 May 2011 04:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-4369</guid>
		<description><![CDATA[I&#039;d like to see StorageDRS as a feature in ESXi 5. We&#039;re all now seeing storage tiering being offered by EMC and NetApp; it&#039;d be nice to integrate StorageDRS  into these pools to take advantage of faster disk (when needed).]]></description>
		<content:encoded><![CDATA[<p>I&#8217;d like to see StorageDRS as a feature in ESXi 5. We&#8217;re all now seeing storage tiering being offered by EMC and NetApp; it&#8217;d be nice to integrate StorageDRS  into these pools to take advantage of faster disk (when needed).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raj M</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-4046</link>
		<dc:creator><![CDATA[Raj M]]></dc:creator>
		<pubDate>Tue, 12 Apr 2011 14:36:24 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-4046</guid>
		<description><![CDATA[IS there any API released for ESX 5.. if not does anybody have some idea about it....]]></description>
		<content:encoded><![CDATA[<p>IS there any API released for ESX 5.. if not does anybody have some idea about it&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Where Next for VMware Workstation? &#171; Virtualization, Windows, Infrastructure and all that &#8220;stuff&#8221; in-between</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-1766</link>
		<dc:creator><![CDATA[Where Next for VMware Workstation? &#171; Virtualization, Windows, Infrastructure and all that &#8220;stuff&#8221; in-between]]></dc:creator>
		<pubDate>Wed, 28 Apr 2010 10:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-1766</guid>
		<description><![CDATA[[...] slightly wider in scope, If it were also back-ported and integrated into future versions of the vSphere product line you have a very powerful back-end server product – VMware talk of the software mainframe, this is [...]]]></description>
		<content:encoded><![CDATA[<p>[...] slightly wider in scope, If it were also back-ported and integrated into future versions of the vSphere product line you have a very powerful back-end server product – VMware talk of the software mainframe, this is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vinf</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-1375</link>
		<dc:creator><![CDATA[vinf]]></dc:creator>
		<pubDate>Tue, 12 Jan 2010 11:44:31 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-1375</guid>
		<description><![CDATA[Thanks - yeah it would be very cool - PXE boot the OS into RAM on a blade and I could envision a single central console with pools of ESXi hosts with the ability to apply configs to each.]]></description>
		<content:encoded><![CDATA[<p>Thanks &#8211; yeah it would be very cool &#8211; PXE boot the OS into RAM on a blade and I could envision a single central console with pools of ESXi hosts with the ability to apply configs to each.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gandalfk7</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-1372</link>
		<dc:creator><![CDATA[gandalfk7]]></dc:creator>
		<pubDate>Mon, 11 Jan 2010 22:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-1372</guid>
		<description><![CDATA[I was just thinking of stateless nodes this morning installing a 4i, in large environments it would be very interesting. 
A &quot;simple&quot; drop drop-in-the-rack &amp; go.

I like the idea.

btw, interesting blog.

Matteo]]></description>
		<content:encoded><![CDATA[<p>I was just thinking of stateless nodes this morning installing a 4i, in large environments it would be very interesting.<br />
A &#8220;simple&#8221; drop drop-in-the-rack &amp; go.</p>
<p>I like the idea.</p>
<p>btw, interesting blog.</p>
<p>Matteo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: It&#8217;s voting time.. &#171; Virtualization, Windows, Infrastructure and all that &#8220;stuff&#8221; in-between</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-1362</link>
		<dc:creator><![CDATA[It&#8217;s voting time.. &#171; Virtualization, Windows, Infrastructure and all that &#8220;stuff&#8221; in-between]]></dc:creator>
		<pubDate>Mon, 04 Jan 2010 22:04:45 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-1362</guid>
		<description><![CDATA[[...] VMware ESX 5 – what would you like to see [...]]]></description>
		<content:encoded><![CDATA[<p>[...] VMware ESX 5 – what would you like to see [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DaSein</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-1056</link>
		<dc:creator><![CDATA[DaSein]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 18:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-1056</guid>
		<description><![CDATA[Hardware passthough to support hardhare natively.  Asterisk PBX in ESX would be nice.]]></description>
		<content:encoded><![CDATA[<p>Hardware passthough to support hardhare natively.  Asterisk PBX in ESX would be nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-1053</link>
		<dc:creator><![CDATA[Kent]]></dc:creator>
		<pubDate>Mon, 10 Aug 2009 18:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-1053</guid>
		<description><![CDATA[I was actually thinking along the same lines as you with host replication, but I was going to go a step further.  For the branch office deployments, I am thinking of a &quot;fault tolerant&quot; host solution where all VMs and the service console mgmt is built for fault tolerance.  The VMs would be kept in sync with the storage replication between the two hosts.  The host configuration would be kept in sync with host profiles between the two boxes, and each location would be a single point of installation administration, i.e. one would not have separately configure / maintain each box.

The second idea is transparent storage sharing similar to the transparent page sharing idea where identical storage is deduplicated by the host on any storage.  Think NetApp ASIS built-into the host itself and storage independent.]]></description>
		<content:encoded><![CDATA[<p>I was actually thinking along the same lines as you with host replication, but I was going to go a step further.  For the branch office deployments, I am thinking of a &#8220;fault tolerant&#8221; host solution where all VMs and the service console mgmt is built for fault tolerance.  The VMs would be kept in sync with the storage replication between the two hosts.  The host configuration would be kept in sync with host profiles between the two boxes, and each location would be a single point of installation administration, i.e. one would not have separately configure / maintain each box.</p>
<p>The second idea is transparent storage sharing similar to the transparent page sharing idea where identical storage is deduplicated by the host on any storage.  Think NetApp ASIS built-into the host itself and storage independent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://vinf.net/2009/08/07/vmware-esx-5/#comment-1043</link>
		<dc:creator><![CDATA[William]]></dc:creator>
		<pubDate>Fri, 07 Aug 2009 23:02:50 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/08/07/vmware-esx-5/#comment-1043</guid>
		<description><![CDATA[IO DRS will definitely be in the next relesae (Will be previewed @ VMworld 09).

I think with the hot add vCPU/vMemory, this can potentially be integrated with DRS + SLA tools like AppSpeed + CapacityIQ to dynamically hot-add resources such as extra vCPUs and vMemory for a given workload and remove them when not needed. That would be a pretty neat feature but also complicated one to solve. Would be interesting to see

--William]]></description>
		<content:encoded><![CDATA[<p>IO DRS will definitely be in the next relesae (Will be previewed @ VMworld 09).</p>
<p>I think with the hot add vCPU/vMemory, this can potentially be integrated with DRS + SLA tools like AppSpeed + CapacityIQ to dynamically hot-add resources such as extra vCPUs and vMemory for a given workload and remove them when not needed. That would be a pretty neat feature but also complicated one to solve. Would be interesting to see</p>
<p>&#8211;William</p>
]]></content:encoded>
	</item>
</channel>
</rss>

