<?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: Cloudkick takes &#8220;Best in Show&#8221; at Under the Radar</title>
	<atom:link href="http://alex.polvi.net/2009/04/26/cloudkick-takes-best-in-show-at-under-the-radar/feed/" rel="self" type="application/rss+xml" />
	<link>http://alex.polvi.net/2009/04/26/cloudkick-takes-best-in-show-at-under-the-radar/</link>
	<description>let's do this!!</description>
	<lastBuildDate>Mon, 27 Apr 2009 17:32:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: cshields</title>
		<link>http://alex.polvi.net/2009/04/26/cloudkick-takes-best-in-show-at-under-the-radar/comment-page-1/#comment-163076</link>
		<dc:creator>cshields</dc:creator>
		<pubDate>Mon, 27 Apr 2009 17:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://alex.polvi.net/?p=343#comment-163076</guid>
		<description>Good job, Alex!  I&#039;ve said this briefly before, but a huge opportunity for you will lie the HPC market.  As much as I personally think that HPC needs are opposite those of the typical &quot;cloud&quot; user, the fact of the matter is that researchers read about it in the magazines, they think they need it, and so HPC sites are testing the waters to cater to their needs.  

What does this mean?  You will have a dozen major cloud providers across the existing major HPC sites, and many of those resources will be offered up to a variety of users via the Teragrid (or the upcoming Teragrid XD).  Quite a few of us already have our own testbed cloud clusters.

The short of this is that you have a fresh new target market of users who will be doing cloud computing with a dynamic pool of providers.  There&#039;s no better way to manage that scenario then with what I&#039;ve seen you demonstrate.

Now, it may be rather difficult to just pull in a handful of dynamic providers.  But it should be something to keep on your radar.  I&#039;ll pass this along to the people on our team working on the cloud cluster, maybe they have additional input (you remember Joe? He&#039;s one of them).  Nobody knows quite how it will play in the HPC world and on the Teragrid so it is all speculation at this point.  Technically, you can bet on it being eucalyptus / nimbus based.

Cheers!</description>
		<content:encoded><![CDATA[<p>Good job, Alex!  I&#8217;ve said this briefly before, but a huge opportunity for you will lie the HPC market.  As much as I personally think that HPC needs are opposite those of the typical &#8220;cloud&#8221; user, the fact of the matter is that researchers read about it in the magazines, they think they need it, and so HPC sites are testing the waters to cater to their needs.  </p>
<p>What does this mean?  You will have a dozen major cloud providers across the existing major HPC sites, and many of those resources will be offered up to a variety of users via the Teragrid (or the upcoming Teragrid XD).  Quite a few of us already have our own testbed cloud clusters.</p>
<p>The short of this is that you have a fresh new target market of users who will be doing cloud computing with a dynamic pool of providers.  There&#8217;s no better way to manage that scenario then with what I&#8217;ve seen you demonstrate.</p>
<p>Now, it may be rather difficult to just pull in a handful of dynamic providers.  But it should be something to keep on your radar.  I&#8217;ll pass this along to the people on our team working on the cloud cluster, maybe they have additional input (you remember Joe? He&#8217;s one of them).  Nobody knows quite how it will play in the HPC world and on the Teragrid so it is all speculation at this point.  Technically, you can bet on it being eucalyptus / nimbus based.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
