<?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: Thoughts From Interop Las Vegas 2009</title>
	<atom:link href="http://saaskatoon.deliveredinnovation.com/2009/05/29/thoughts-from-interop-las-vegas-2009/feed/" rel="self" type="application/rss+xml" />
	<link>http://saaskatoon.deliveredinnovation.com/2009/05/29/thoughts-from-interop-las-vegas-2009/</link>
	<description>SaaS, PaaS, and Cloud Computing</description>
	<lastBuildDate>Mon, 24 May 2010 21:01:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Peter Coffee, salesforce.com</title>
		<link>http://saaskatoon.deliveredinnovation.com/2009/05/29/thoughts-from-interop-las-vegas-2009/comment-page-1/#comment-54</link>
		<dc:creator>Peter Coffee, salesforce.com</dc:creator>
		<pubDate>Wed, 03 Jun 2009 20:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://saaskatoon.com/?p=311#comment-54</guid>
		<description>With no desire to be confrontational ;), I&#039;m not sure what it means to say that &quot;there is a weird tendency to use negative reinforcement as a means to enforce compliance.&quot;  I believe I made the points, during the Interop discussion, that

(i) a document that calls itself an SLA can define the denominator of the uptime fraction in any way it likes. By the time a vendor has excluded scheduled maintenance, or unscheduled maintenance with more than X hours&#039; advance notice (for example), an arbitrary number of 9s can be achieved without actually giving the customer what&#039;s needed in terms of actual availability.

(ii) actual availability, quantifiably displayed via public dashboards and with full disclosure of every service anomaly, is what should actually be compared among both cloud and on-premise alternatives.  If that means I&#039;m saying that &quot;saleforce.com’s numbers...speak for themselves,&quot; I guess I&#039;m also saying that nothing else can speak for them.  Everything else, it seems to me, is just hopes and artful representations.

Thanks for putting these key issues on the table: I agree, or at least I believe we agree, that at this point it&#039;s more important for cloud providers to join in combat against ignorance and FUD than it is for cloud providers to seek advantage over each other.  Achieving understanding of the cloud is Job One for all of us.

 - pc</description>
		<content:encoded><![CDATA[<p>With no desire to be confrontational ;), I&#8217;m not sure what it means to say that &#8220;there is a weird tendency to use negative reinforcement as a means to enforce compliance.&#8221;  I believe I made the points, during the Interop discussion, that</p>
<p>(i) a document that calls itself an SLA can define the denominator of the uptime fraction in any way it likes. By the time a vendor has excluded scheduled maintenance, or unscheduled maintenance with more than X hours&#8217; advance notice (for example), an arbitrary number of 9s can be achieved without actually giving the customer what&#8217;s needed in terms of actual availability.</p>
<p>(ii) actual availability, quantifiably displayed via public dashboards and with full disclosure of every service anomaly, is what should actually be compared among both cloud and on-premise alternatives.  If that means I&#8217;m saying that &#8220;saleforce.com’s numbers&#8230;speak for themselves,&#8221; I guess I&#8217;m also saying that nothing else can speak for them.  Everything else, it seems to me, is just hopes and artful representations.</p>
<p>Thanks for putting these key issues on the table: I agree, or at least I believe we agree, that at this point it&#8217;s more important for cloud providers to join in combat against ignorance and FUD than it is for cloud providers to seek advantage over each other.  Achieving understanding of the cloud is Job One for all of us.</p>
<p> &#8211; pc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deliveredinnovation</title>
		<link>http://saaskatoon.deliveredinnovation.com/2009/05/29/thoughts-from-interop-las-vegas-2009/comment-page-1/#comment-56</link>
		<dc:creator>deliveredinnovation</dc:creator>
		<pubDate>Tue, 02 Jun 2009 22:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://saaskatoon.com/?p=311#comment-56</guid>
		<description>Thanks for the sharp eye, Kevin.  Post updated...</description>
		<content:encoded><![CDATA[<p>Thanks for the sharp eye, Kevin.  Post updated&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Smith</title>
		<link>http://saaskatoon.deliveredinnovation.com/2009/05/29/thoughts-from-interop-las-vegas-2009/comment-page-1/#comment-55</link>
		<dc:creator>Kevin Smith</dc:creator>
		<pubDate>Tue, 02 Jun 2009 21:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://saaskatoon.com/?p=311#comment-55</guid>
		<description>Treb Ryan is at OpSource, not OpsWare.</description>
		<content:encoded><![CDATA[<p>Treb Ryan is at OpSource, not OpsWare.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Kaplan</title>
		<link>http://saaskatoon.deliveredinnovation.com/2009/05/29/thoughts-from-interop-las-vegas-2009/comment-page-1/#comment-57</link>
		<dc:creator>Jeff Kaplan</dc:creator>
		<pubDate>Fri, 29 May 2009 21:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://saaskatoon.com/?p=311#comment-57</guid>
		<description>Thanks for the positive feedback re: my session at Interop and the way I handled the questions from the audience. You&#039;ve also done a great job of capturing the tone of the event and the attitudes of the attendees.</description>
		<content:encoded><![CDATA[<p>Thanks for the positive feedback re: my session at Interop and the way I handled the questions from the audience. You&#8217;ve also done a great job of capturing the tone of the event and the attitudes of the attendees.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
