<?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: Building a House in the Cloud &#8211; Cloudcenters vs. Infrastructure Web Services</title>
	<atom:link href="http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/</link>
	<description>&#34;Control in the Cloud™&#34;</description>
	<lastBuildDate>Thu, 11 Mar 2010 15:49:38 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: villa stone</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-2076</link>
		<dc:creator>villa stone</dc:creator>
		<pubDate>Fri, 04 Sep 2009 09:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-2076</guid>
		<description>Most cloudcenters are going to pre-bundle an entire datacenter for your usage, but follow a utility charge model just like that of AWS. Much like a &#039;general contractor&#039; in Michael&#039;s example you still only use the materials and subcontractors that you decide when building your house. It just happens that they are already pre-bundled and designed to work together, so there is much less work on your part. 

For a large house, you&#039;ll use it all. For a smaller house, maybe only pick and choose what you need



Read more: http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/#ixzz0Q87uopUM</description>
		<content:encoded><![CDATA[<p>Most cloudcenters are going to pre-bundle an entire datacenter for your usage, but follow a utility charge model just like that of AWS. Much like a &#8216;general contractor&#8217; in Michael&#8217;s example you still only use the materials and subcontractors that you decide when building your house. It just happens that they are already pre-bundled and designed to work together, so there is much less work on your part. </p>
<p>For a large house, you&#8217;ll use it all. For a smaller house, maybe only pick and choose what you need</p>
<p>Read more: <a href="http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/#ixzz0Q87uopUM" rel="nofollow">http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/#ixzz0Q87uopUM</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rational Survivability &#187; Private Clouds: Your Definition Sucks</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-1980</link>
		<dc:creator>Rational Survivability &#187; Private Clouds: Your Definition Sucks</dc:creator>
		<pubDate>Thu, 30 Jul 2009 23:24:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-1980</guid>
		<description>[...] are too narrow end exculpatory in definition when you consider that you are omitting solutions like GoGrid&#8217;s CloudCenter concepts &#8212; extending your datacenter via VPN onto a cloud IaaS provider whose infrastructure [...]</description>
		<content:encoded><![CDATA[<p>[...] are too narrow end exculpatory in definition when you consider that you are omitting solutions like GoGrid&#8217;s CloudCenter concepts &#8212; extending your datacenter via VPN onto a cloud IaaS provider whose infrastructure [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: randybias</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-1536</link>
		<dc:creator>randybias</dc:creator>
		<pubDate>Thu, 16 Apr 2009 05:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-1536</guid>
		<description>Shannon, 
 
  You can also program elastic scalability using GoGrid API functionality just like Amazon&#039;s EC2.  In fact, our partner, RightScale currently supports this kind of scalability on both GoGrid and Amazon. 
 
 
--Randy </description>
		<content:encoded><![CDATA[<p>Shannon, </p>
<p>  You can also program elastic scalability using GoGrid API functionality just like Amazon&#039;s EC2.  In fact, our partner, RightScale currently supports this kind of scalability on both GoGrid and Amazon. </p>
<p>&#8211;Randy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shannon Clark</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-1535</link>
		<dc:creator>Shannon Clark</dc:creator>
		<pubDate>Thu, 16 Apr 2009 04:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-1535</guid>
		<description>A question - how does GoGrid compare to Amazon&#039;s API driven ability to (if admittedly you program this) to provision additional capacity as your systems detect the need (i.e. as usage spikes over certain levels your systems could via API calls provision additional servers - and likewise turn off instances when the usage spike passes)? 
 
As I think about scaling via utilizing the cloud I see a few distinct &amp; different dimensions: 
 
Compute capacity (i.e. resolving requests &amp; service as user increase in numbers and frequency of use) 
 
Storage capacity - an issue if your specific application has storage needs on a per-user basis 
 
Bandwidth - again highly application dependent but often needs to also scale with growth (and can in some cases grow quite large &amp; pricy quickly) 
 
Shannon </description>
		<content:encoded><![CDATA[<p>A question &#8211; how does GoGrid compare to Amazon&#039;s API driven ability to (if admittedly you program this) to provision additional capacity as your systems detect the need (i.e. as usage spikes over certain levels your systems could via API calls provision additional servers &#8211; and likewise turn off instances when the usage spike passes)? </p>
<p>As I think about scaling via utilizing the cloud I see a few distinct &amp; different dimensions: </p>
<p>Compute capacity (i.e. resolving requests &amp; service as user increase in numbers and frequency of use) </p>
<p>Storage capacity &#8211; an issue if your specific application has storage needs on a per-user basis </p>
<p>Bandwidth &#8211; again highly application dependent but often needs to also scale with growth (and can in some cases grow quite large &amp; pricy quickly) </p>
<p>Shannon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virtual, Cloud, Datacenters? &#124; neoTactics</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-1525</link>
		<dc:creator>Virtual, Cloud, Datacenters? &#124; neoTactics</dc:creator>
		<pubDate>Mon, 13 Apr 2009 18:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-1525</guid>
		<description>[...] An emerging trend pioneered by GoGrid and also pre-announced by RackSpace Cloud is the &#8220;cloudcenter&#8220;, a datacenter-in-the-sky.  Cloudcenters are an intermediate step between no virtualization [...]</description>
		<content:encoded><![CDATA[<p>[...] An emerging trend pioneered by GoGrid and also pre-announced by RackSpace Cloud is the &#8220;cloudcenter&#8220;, a datacenter-in-the-sky.  Cloudcenters are an intermediate step between no virtualization [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: randybias</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-1234</link>
		<dc:creator>randybias</dc:creator>
		<pubDate>Thu, 12 Feb 2009 23:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-1234</guid>
		<description>Doug, thanks for your question.  Cloudcenters are a type of IaaS.  We discovered the distinction while trying to understand why our service looked so different from other IaaS platforms, specifically AWS.  I strongly recommend reading my early posting (&lt;a href=&quot;http://blog.gogrid.com/2009/01/08/cloudcenters-are-datacenters-in-the-sky/)&quot; target=&quot;_blank&quot;&gt;http://blog.gogrid.com/2009/01/08/cloudcenters-ar...&lt;/a&gt; which goes into some detail on cloudcenters. 
 
I am not aware of any significant blockers to your requirements using GoGrid as it is very much a standard cloud infrastructure.  Perhaps the primary issue is that VDI is another virtualization technology.  Generally speaking you cannot deploy virtualization inside another virtualized system; however, it would be possible to use our CloudConnect offering to deploy VDI on dedicated servers (ServePath) or colocated servers (ColoServe) that were attached to your GoGrid cloud offering. 
 
FYI, larger virtual machine sizes were quietly deployed today and are available now on GoGrid.  We&#039;ll have a full press release on Tuesday.  The new larger virtual machine sizes have 2+ cores.  </description>
		<content:encoded><![CDATA[<p>Doug, thanks for your question.  Cloudcenters are a type of IaaS.  We discovered the distinction while trying to understand why our service looked so different from other IaaS platforms, specifically AWS.  I strongly recommend reading my early posting (<a href="http://blog.gogrid.com/2009/01/08/cloudcenters-are-datacenters-in-the-sky/)" target="_blank"></a><a href="http://blog.gogrid.com/2009/01/08/cloudcenters-ar.." rel="nofollow">http://blog.gogrid.com/2009/01/08/cloudcenters-ar..</a>. which goes into some detail on cloudcenters. </p>
<p>I am not aware of any significant blockers to your requirements using GoGrid as it is very much a standard cloud infrastructure.  Perhaps the primary issue is that VDI is another virtualization technology.  Generally speaking you cannot deploy virtualization inside another virtualized system; however, it would be possible to use our CloudConnect offering to deploy VDI on dedicated servers (ServePath) or colocated servers (ColoServe) that were attached to your GoGrid cloud offering. </p>
<p>FYI, larger virtual machine sizes were quietly deployed today and are available now on GoGrid.  We&#039;ll have a full press release on Tuesday.  The new larger virtual machine sizes have 2+ cores.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Ford</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-1231</link>
		<dc:creator>Doug Ford</dc:creator>
		<pubDate>Thu, 12 Feb 2009 22:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-1231</guid>
		<description>Great post. I admitedly breezed through it, but I was eager to learn more about your Cloud Center idea. I think the name is fantastic. The first question that comes to my mind is &quot;how is the cloud center different from Infrastructure-as-a-Service (IaaS)?&quot; Maybe they&#039;re are the same with two different names? If so, I like Cloud Center a lot better than IaaS! I am interested because I have been searching for an IaaS vendor to partner with rather than building out our own IaaS environment. So far, I&#039;ve been disappointed at the countless limitations on cloud providers that limit memory, CPU, and disk. Not to mention the deficiencies in backup and recovery. The customers I want to put in the cloud are going to need Terminal Server(s), VDI server(s), Application Server(s), SQL Server(s), Exchange Server(s), and File Server(s). All of these servers will require a minimum of 4GB of RAM and most will require 2+ CPU&#039;s. Is your vision of Cloud Center to support a complete infrastructure with configurations that make sense in the world of small businesses?  
 </description>
		<content:encoded><![CDATA[<p>Great post. I admitedly breezed through it, but I was eager to learn more about your Cloud Center idea. I think the name is fantastic. The first question that comes to my mind is &quot;how is the cloud center different from Infrastructure-as-a-Service (IaaS)?&quot; Maybe they&#039;re are the same with two different names? If so, I like Cloud Center a lot better than IaaS! I am interested because I have been searching for an IaaS vendor to partner with rather than building out our own IaaS environment. So far, I&#039;ve been disappointed at the countless limitations on cloud providers that limit memory, CPU, and disk. Not to mention the deficiencies in backup and recovery. The customers I want to put in the cloud are going to need Terminal Server(s), VDI server(s), Application Server(s), SQL Server(s), Exchange Server(s), and File Server(s). All of these servers will require a minimum of 4GB of RAM and most will require 2+ CPU&#039;s. Is your vision of Cloud Center to support a complete infrastructure with configurations that make sense in the world of small businesses?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clinton Fein</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-980</link>
		<dc:creator>Clinton Fein</dc:creator>
		<pubDate>Sat, 17 Jan 2009 00:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-980</guid>
		<description>I think you hit the nail on the head. 
 
Having turned to your service in a crunch recently, the obvious focus on user experience made all the difference in the world.  
 
The UI was elegantly simple, intuitive, and free of any distraction, and the functionality well executed. It was exactly what we needed, hoped for and got. I have already recommended you guys to people in my network on that basis alone.  
 
The fact of the matter is I watched an engineer fly through your sign up and set up at the speed of light, and the fact that he could do it, and that the experience was so predictable, is a testament to designing the appropriate interface for the correct target. 
 
Environments that are familiar to system admins and IT operations folk are only part of the equation. I&#039;m frequently amazed at how often user experience is ignored when it comes to content administrators, let alone engineers or system administrators. However, the fact that you&#039;re not only engaging in this thought process, but already implementing accordingly, is a key differentiator. 
 
Good luck. </description>
		<content:encoded><![CDATA[<p>I think you hit the nail on the head. </p>
<p>Having turned to your service in a crunch recently, the obvious focus on user experience made all the difference in the world.  </p>
<p>The UI was elegantly simple, intuitive, and free of any distraction, and the functionality well executed. It was exactly what we needed, hoped for and got. I have already recommended you guys to people in my network on that basis alone.  </p>
<p>The fact of the matter is I watched an engineer fly through your sign up and set up at the speed of light, and the fact that he could do it, and that the experience was so predictable, is a testament to designing the appropriate interface for the correct target. </p>
<p>Environments that are familiar to system admins and IT operations folk are only part of the equation. I&#039;m frequently amazed at how often user experience is ignored when it comes to content administrators, let alone engineers or system administrators. However, the fact that you&#039;re not only engaging in this thought process, but already implementing accordingly, is a key differentiator. </p>
<p>Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sheehan</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-978</link>
		<dc:creator>Michael Sheehan</dc:creator>
		<pubDate>Thu, 15 Jan 2009 18:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-978</guid>
		<description>Good catch! I guess I should fire my copy editor (that would be me). Thanks for pointing that out! </description>
		<content:encoded><![CDATA[<p>Good catch! I guess I should fire my copy editor (that would be me). Thanks for pointing that out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris S</title>
		<link>http://blog.gogrid.com/2009/01/14/building-a-house-in-the-cloud-cloudcenters-vs-infrastructure-web-services/comment-page-1/#comment-977</link>
		<dc:creator>Chris S</dc:creator>
		<pubDate>Thu, 15 Jan 2009 18:07:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=618#comment-977</guid>
		<description>I&#039;ve been wanting to try Windows Server 2009. Should be a major improvement over 2008. : ) </description>
		<content:encoded><![CDATA[<p>I&#039;ve been wanting to try Windows Server 2009. Should be a major improvement over 2008. : )</p>
]]></content:encoded>
	</item>
</channel>
</rss>
