<?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: Thinking Aloud on Clouds</title>
	<atom:link href="http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Fri, 20 Nov 2009 20:00:49 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lydia Leong</title>
		<link>http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/comment-page-1/#comment-76</link>
		<dc:creator>Lydia Leong</dc:creator>
		<pubDate>Wed, 10 Dec 2008 20:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/#comment-76</guid>
		<description>OVF looks like it&#039;s the emerging standard for VM portability. It goes beyond the individual virtual disk image formats (AMI, VMDK, VHD, etc.) to specify an environment. Portability is inherent to a lot of VMware&#039;s vCloud concepts, and is a necessary enabler for the commodities market you&#039;re thinking about. Of course, what vendor is going to voluntarily commoditize? Every vendor is likely going to want to do its own special sauce, limiting ready portability.</description>
		<content:encoded><![CDATA[<p>OVF looks like it&#8217;s the emerging standard for VM portability. It goes beyond the individual virtual disk image formats (AMI, VMDK, VHD, etc.) to specify an environment. Portability is inherent to a lot of VMware&#8217;s vCloud concepts, and is a necessary enabler for the commodities market you&#8217;re thinking about. Of course, what vendor is going to voluntarily commoditize? Every vendor is likely going to want to do its own special sauce, limiting ready portability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron Haight</title>
		<link>http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/comment-page-1/#comment-61</link>
		<dc:creator>Cameron Haight</dc:creator>
		<pubDate>Fri, 21 Nov 2008 22:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/#comment-61</guid>
		<description>Thank you Lori!  I like the term &quot;CAM&quot; - but maybe I can make it CAMeron!  ;-)  Seriously, you raise some good points on pricing both in terms of the model plus how value added services may be taken into account.  It will be an interesting market to watch develop!  Thanks again for taking the time to comment!</description>
		<content:encoded><![CDATA[<p>Thank you Lori!  I like the term &#8220;CAM&#8221; &#8211; but maybe I can make it CAMeron!  <img src='http://blogs.gartner.com/cameron_haight/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />   Seriously, you raise some good points on pricing both in terms of the model plus how value added services may be taken into account.  It will be an interesting market to watch develop!  Thanks again for taking the time to comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lori MacVittie</title>
		<link>http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/comment-page-1/#comment-38</link>
		<dc:creator>Lori MacVittie</dc:creator>
		<pubDate>Fri, 21 Nov 2008 14:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/cameron_haight/2008/11/21/thinking-aloud-on-clouds/#comment-38</guid>
		<description>Cameron, 

Interesting thoughts, especially on the cataloging and BAM style visibility into the cloud. Perhaps you should coin that phrase now, CAM (Cloud Activity Monitoring), before someone else nabs the opportunity. :-) 

Pricing seems to be a sticking point for cloud computing, as well, because it depends on the &lt;a href=&quot;http://devcentral.f5.com/weblogs/macvittie/archive/2008/11/20/as-a-service-the-many-faces-of-the-cloud.aspx&quot; rel=&quot;nofollow&quot;&gt;model of the cloud&lt;/a&gt;. If you&#039;re leasing infrastructure as a service, then it makes sense to charge per GHz and RAM, while if the cloud is primarily about object storage then charging on a per GB per month basis is probably more appropriate. Similarly, if you are a Platform as a Service provider, you might want to charge based on a combination of GHz/RAM/Bandwidth/Database access. 

The possibility of value-added services like app acceleration, optimization, application security, etc... also provides an interesting pricing model for vendors, and plays well into your concept of an uber registry in which not only core capabilities/SLAs might be stored, but what additional options are available for performance-minded customers. 

Interesting thoughts in general. This is definitely an emerging market with a lot of potential. 

Lori</description>
		<content:encoded><![CDATA[<p>Cameron, </p>
<p>Interesting thoughts, especially on the cataloging and BAM style visibility into the cloud. Perhaps you should coin that phrase now, CAM (Cloud Activity Monitoring), before someone else nabs the opportunity. <img src='http://blogs.gartner.com/cameron_haight/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  </p>
<p>Pricing seems to be a sticking point for cloud computing, as well, because it depends on the <a href="http://devcentral.f5.com/weblogs/macvittie/archive/2008/11/20/as-a-service-the-many-faces-of-the-cloud.aspx" rel="nofollow">model of the cloud</a>. If you&#8217;re leasing infrastructure as a service, then it makes sense to charge per GHz and RAM, while if the cloud is primarily about object storage then charging on a per GB per month basis is probably more appropriate. Similarly, if you are a Platform as a Service provider, you might want to charge based on a combination of GHz/RAM/Bandwidth/Database access. </p>
<p>The possibility of value-added services like app acceleration, optimization, application security, etc&#8230; also provides an interesting pricing model for vendors, and plays well into your concept of an uber registry in which not only core capabilities/SLAs might be stored, but what additional options are available for performance-minded customers. </p>
<p>Interesting thoughts in general. This is definitely an emerging market with a lot of potential. </p>
<p>Lori</p>
]]></content:encoded>
	</item>
</channel>
</rss>
