<?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: 6 things we need to know from VMware</title>
	<atom:link href="http://gigaom.com/2012/08/24/6-things-we-need-to-know-from-vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/08/24/6-things-we-need-to-know-from-vmware/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 02:04:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Keith Townsend</title>
		<link>http://gigaom.com/2012/08/24/6-things-we-need-to-know-from-vmware/#comment-942393</link>
		<dc:creator><![CDATA[Keith Townsend]]></dc:creator>
		<pubDate>Sun, 26 Aug 2012 01:10:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=555304#comment-942393</guid>
		<description><![CDATA[Reblogged this on &lt;a href=&quot;http://virtualizedgeek.com/2012/08/25/1015/&quot; rel=&quot;nofollow&quot;&gt;Virtualized Geek&lt;/a&gt; and commented: 
Great set of questions.  I&#039;d also like to know why stick with VMware long term?  2013 will be the year the Hypervisor will become a commodity.  Why not look to open source and Microsoft to take care of all of my hypervisor and cloud management needs.  I believe VMware needs to move quickly into communicating what they are and why we need to continue to lock our virtualization and cloud workloads into their ecosystem when there will be good enough solutions available by the later part of 2013. ]]></description>
		<content:encoded><![CDATA[<p>Reblogged this on <a href="http://virtualizedgeek.com/2012/08/25/1015/" rel="nofollow">Virtualized Geek</a> and commented:<br />
Great set of questions.  I&#8217;d also like to know why stick with VMware long term?  2013 will be the year the Hypervisor will become a commodity.  Why not look to open source and Microsoft to take care of all of my hypervisor and cloud management needs.  I believe VMware needs to move quickly into communicating what they are and why we need to continue to lock our virtualization and cloud workloads into their ecosystem when there will be good enough solutions available by the later part of 2013. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sinclair Schuller</title>
		<link>http://gigaom.com/2012/08/24/6-things-we-need-to-know-from-vmware/#comment-937159</link>
		<dc:creator><![CDATA[Sinclair Schuller]]></dc:creator>
		<pubDate>Fri, 24 Aug 2012 16:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=555304#comment-937159</guid>
		<description><![CDATA[An even deeper question they should address regarding CloudFoundry is how are they going to balance offering a CloudFoundry PaaS (literally as a service) and sell a product, both of which will compete with CloudFoundry ecosystem partners, while keeping their ecosystem in tact. It seems like they&#039;ve created quite a &quot;rock and a hard place&quot; with this ecosystem strategy.

Traditionally, you don&#039;t see open source/ecosystem plays have this sort of tension so early, if at all. If it&#039;s &quot;faux-pen source&quot; like CloudFoundry is (or like Red Hat), it&#039;s awkward to give commercial incentive to partners that you&#039;ll ultimately compete with. Everyone needs to remember that although CF is &quot;open&quot;, it&#039;s still VMware&#039;s cloud play. Then the question becomes: what makes CF different than proprietary PaaS plays? In fact, doesn&#039;t it make CF even more complicated than a proprietary play? We faced this question at Apprenda and decided that we a) wanted to be a commercial play b) focus our &quot;open&quot; efforts on helping customers avoid infrastructure lock-in and c) never offering a pay-for PaaS service since it&#039;s impossible to be &quot;an arms dealer to both sides of the war but participate only on one side&quot;]]></description>
		<content:encoded><![CDATA[<p>An even deeper question they should address regarding CloudFoundry is how are they going to balance offering a CloudFoundry PaaS (literally as a service) and sell a product, both of which will compete with CloudFoundry ecosystem partners, while keeping their ecosystem in tact. It seems like they&#8217;ve created quite a &#8220;rock and a hard place&#8221; with this ecosystem strategy.</p>
<p>Traditionally, you don&#8217;t see open source/ecosystem plays have this sort of tension so early, if at all. If it&#8217;s &#8220;faux-pen source&#8221; like CloudFoundry is (or like Red Hat), it&#8217;s awkward to give commercial incentive to partners that you&#8217;ll ultimately compete with. Everyone needs to remember that although CF is &#8220;open&#8221;, it&#8217;s still VMware&#8217;s cloud play. Then the question becomes: what makes CF different than proprietary PaaS plays? In fact, doesn&#8217;t it make CF even more complicated than a proprietary play? We faced this question at Apprenda and decided that we a) wanted to be a commercial play b) focus our &#8220;open&#8221; efforts on helping customers avoid infrastructure lock-in and c) never offering a pay-for PaaS service since it&#8217;s impossible to be &#8220;an arms dealer to both sides of the war but participate only on one side&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
