<?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: Smoke-and-mirrors and cloud software</title>
	<atom:link href="http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/feed/" rel="self" type="application/rss+xml" />
	<link>http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/</link>
	<description>the business of Internet infrastructure, cloud computing, and data centers</description>
	<lastBuildDate>Mon, 13 Feb 2012 04:46:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Mark</title>
		<link>http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/#comment-1969</link>
		<dc:creator><![CDATA[Mark]]></dc:creator>
		<pubDate>Sun, 17 Jan 2010 10:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/#comment-1969</guid>
		<description><![CDATA[Found your blog on Google and was so glad i did. That was a warming read. I have a small question.Is it OK if i send you an email???...]]></description>
		<content:encoded><![CDATA[<p>Found your blog on Google and was so glad i did. That was a warming read. I have a small question.Is it OK if i send you an email???&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weekly Web Nuggets #55 : Code Monkey Labs</title>
		<link>http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/#comment-1459</link>
		<dc:creator><![CDATA[Weekly Web Nuggets #55 : Code Monkey Labs]]></dc:creator>
		<pubDate>Sun, 15 Mar 2009 03:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/#comment-1459</guid>
		<description><![CDATA[[...] Pick of the week: Smoke-and-Mirrors and Cloud Software [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Pick of the week: Smoke-and-Mirrors and Cloud Software [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Langley</title>
		<link>http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/#comment-1445</link>
		<dc:creator><![CDATA[Kent Langley]]></dc:creator>
		<pubDate>Tue, 10 Mar 2009 01:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://cloudpundit.com/2009/03/09/smoke-and-mirrors-and-cloud-software/#comment-1445</guid>
		<description><![CDATA[A few months ago I wrote the following definitions and proclaimed that if some service does not posses these features then, in my opinion, it’s not cloud computing.

    * Scalability - The ability of a computing system to grow relatively easily in response to increased demand
    * Elasticity - The ability of a system to dynamically acquire or release compute resources on-demand
    * Highly Available - Systems designed such that the loss of any one component of a system will not result in system failure.  No single points of failure (SPOF)

I still feel exactly the same way...

I posted a longer version of this on my own blog (blog.nscaled.com), it was too long to paste here.  In summary though, I commented on the combination of Fabric Mgmt and PaaS by some vendors.  In further thought, that kind of leads to what seems to already be happening with a merger what what some call PaaS and IaaS.  But, there are some road blocks (like proprietary API&#039;s).

Cheers..

-Kent]]></description>
		<content:encoded><![CDATA[<p>A few months ago I wrote the following definitions and proclaimed that if some service does not posses these features then, in my opinion, it’s not cloud computing.</p>
<p>    * Scalability &#8211; The ability of a computing system to grow relatively easily in response to increased demand<br />
    * Elasticity &#8211; The ability of a system to dynamically acquire or release compute resources on-demand<br />
    * Highly Available &#8211; Systems designed such that the loss of any one component of a system will not result in system failure.  No single points of failure (SPOF)</p>
<p>I still feel exactly the same way&#8230;</p>
<p>I posted a longer version of this on my own blog (blog.nscaled.com), it was too long to paste here.  In summary though, I commented on the combination of Fabric Mgmt and PaaS by some vendors.  In further thought, that kind of leads to what seems to already be happening with a merger what what some call PaaS and IaaS.  But, there are some road blocks (like proprietary API&#8217;s).</p>
<p>Cheers..</p>
<p>-Kent</p>
]]></content:encoded>
	</item>
</channel>
</rss>

