<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: What VMware did next&#8230;?</title>
	<atom:link href="http://www.rtfm-ed.co.uk/2009/05/19/what-vmware-did-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rtfm-ed.co.uk/2009/05/19/what-vmware-did-next/</link>
	<description>Beyond the Manual, with Mike Laverick (VCI, VCP, CCI, CCEA, MCT, MCSE)</description>
	<lastBuildDate>Tue, 07 Feb 2012 21:25:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Simon Bramfitt</title>
		<link>http://www.rtfm-ed.co.uk/2009/05/19/what-vmware-did-next/comment-page-1/#comment-35041</link>
		<dc:creator>Simon Bramfitt</dc:creator>
		<pubDate>Wed, 20 May 2009 16:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.rtfm-ed.co.uk/?p=1256#comment-35041</guid>
		<description>Very well put Mike, I&#039;d just offer one more thought.  

A couple of years back the notion of VMware offering ESX free of charge was unthinkable (to VMware anyway).  Now anyone that does not offer a free Type I hypervisor won&#039;t get a seat at the table.  And so we move on to discussing the need for vendors to offer vmotion and HA capabilities free of charge.  In another 12 months or less this discussion point will be closed and anyone who does offer these capabilities free of charge will again be denied a seat at the table, and the focus will be on critical differentiating factors at the management and scalability layer. There will come a point when the give-aways will stop and vendors will establish more readily comparable pricing models, but I suspect it will be a while before we get there.</description>
		<content:encoded><![CDATA[<p>Very well put Mike, I&#8217;d just offer one more thought.  </p>
<p>A couple of years back the notion of VMware offering ESX free of charge was unthinkable (to VMware anyway).  Now anyone that does not offer a free Type I hypervisor won&#8217;t get a seat at the table.  And so we move on to discussing the need for vendors to offer vmotion and HA capabilities free of charge.  In another 12 months or less this discussion point will be closed and anyone who does offer these capabilities free of charge will again be denied a seat at the table, and the focus will be on critical differentiating factors at the management and scalability layer. There will come a point when the give-aways will stop and vendors will establish more readily comparable pricing models, but I suspect it will be a while before we get there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rynardt Spies</title>
		<link>http://www.rtfm-ed.co.uk/2009/05/19/what-vmware-did-next/comment-page-1/#comment-35036</link>
		<dc:creator>Rynardt Spies</dc:creator>
		<pubDate>Wed, 20 May 2009 09:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.rtfm-ed.co.uk/?p=1256#comment-35036</guid>
		<description>I completely agree. And as for VMotion being a critical part of the package, I simply can&#039;t see how it can be dismissed as just a nice to have tool. I guess those who dismiss VMotion as &quot;Nice to Have&quot; simply don&#039;t work in enterprise environments where a single change request can take days to be reviewed let alone approved. The ability to move VMs from one physical box to another certainly makes life in enterprise IT bearable.

Just to get a simple change through to fix or enhance something on a physical host can be tough enough. Imagine doing the same change request but having to include &quot;The following 15 systems will be unavailable...&quot; in the impact clause of a change request? That kite is not going to fly mate!
My view, charge for VMotion. It saves a lot of time in the long run, and in this world time=$$money$$. Why complain about forking out some $$$ in the first instance if it’s going to save you money in the long term? Or, of course you can opt to go with MS and save the cash on licensing only to lose more cash on techie salaries and SLA breaches. It’s up to you.</description>
		<content:encoded><![CDATA[<p>I completely agree. And as for VMotion being a critical part of the package, I simply can&#8217;t see how it can be dismissed as just a nice to have tool. I guess those who dismiss VMotion as &#8220;Nice to Have&#8221; simply don&#8217;t work in enterprise environments where a single change request can take days to be reviewed let alone approved. The ability to move VMs from one physical box to another certainly makes life in enterprise IT bearable.</p>
<p>Just to get a simple change through to fix or enhance something on a physical host can be tough enough. Imagine doing the same change request but having to include &#8220;The following 15 systems will be unavailable&#8230;&#8221; in the impact clause of a change request? That kite is not going to fly mate!<br />
My view, charge for VMotion. It saves a lot of time in the long run, and in this world time=$$money$$. Why complain about forking out some $$$ in the first instance if it’s going to save you money in the long term? Or, of course you can opt to go with MS and save the cash on licensing only to lose more cash on techie salaries and SLA breaches. It’s up to you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

