<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: GoGrid!</title>
	<link>http://www.lyquidity.com/devblog/?p=25</link>
	<description>Notes from a small island</description>
	<pubDate>Tue, 07 Sep 2010 05:41:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: bills</title>
		<link>http://www.lyquidity.com/devblog/?p=25#comment-35</link>
		<dc:creator>bills</dc:creator>
		<pubDate>Fri, 02 Jan 2009 21:26:57 +0000</pubDate>
		<guid>http://www.lyquidity.com/devblog/?p=25#comment-35</guid>
		<description>Your experience was not encouraging.  Did you get in touch with anyone senior at GoGrid?

What I liked about GoGrid is that it offered Windows.  If I'd just been using Linux I'd probably have stuck with EC2.  In fact now EC2 does support Windows I've moved back there.

I did have some frustrating experiences and the frontline support was not that good.  It seems to me like they cut a corner and used a help desk based in India but did not provide them with the tools to address anything more than the basics.  Any detailed questions could only be resolved when the staff on the West Coast clocked on.  However these staff did seem able to resolve problems.

In the end we did go with EC2.  I found there were connectivity issues.  I put it down to being 8 timezone (and about 30 hops) from the server.  But its not really good enough and is a part of the reason I've returned to Amazon's EC2 which I really like (see later post).</description>
		<content:encoded><![CDATA[<p>Your experience was not encouraging.  Did you get in touch with anyone senior at GoGrid?</p>
<p>What I liked about GoGrid is that it offered Windows.  If I&#8217;d just been using Linux I&#8217;d probably have stuck with EC2.  In fact now EC2 does support Windows I&#8217;ve moved back there.</p>
<p>I did have some frustrating experiences and the frontline support was not that good.  It seems to me like they cut a corner and used a help desk based in India but did not provide them with the tools to address anything more than the basics.  Any detailed questions could only be resolved when the staff on the West Coast clocked on.  However these staff did seem able to resolve problems.</p>
<p>In the end we did go with EC2.  I found there were connectivity issues.  I put it down to being 8 timezone (and about 30 hops) from the server.  But its not really good enough and is a part of the reason I&#8217;ve returned to Amazon&#8217;s EC2 which I really like (see later post).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Ludlow</title>
		<link>http://www.lyquidity.com/devblog/?p=25#comment-34</link>
		<dc:creator>Stuart Ludlow</dc:creator>
		<pubDate>Fri, 02 Jan 2009 21:11:50 +0000</pubDate>
		<guid>http://www.lyquidity.com/devblog/?p=25#comment-34</guid>
		<description>My first experience with GoGrid was terrible.  My servers had died 8 hours after initially starting them.  Within the first 72 hours, my 2 simple tomcat servers had gone down 2 times for about 6 hours each.  I asked several simple questions, such as "How can I change the allocated memory per server?" and "Why do I have to give a public IP address to a database server?"  Each response was a canned response saying it can't be done.  Very disappointing for what appears to be a decent product.</description>
		<content:encoded><![CDATA[<p>My first experience with GoGrid was terrible.  My servers had died 8 hours after initially starting them.  Within the first 72 hours, my 2 simple tomcat servers had gone down 2 times for about 6 hours each.  I asked several simple questions, such as &#8220;How can I change the allocated memory per server?&#8221; and &#8220;Why do I have to give a public IP address to a database server?&#8221;  Each response was a canned response saying it can&#8217;t be done.  Very disappointing for what appears to be a decent product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sheehan</title>
		<link>http://www.lyquidity.com/devblog/?p=25#comment-4</link>
		<dc:creator>Michael Sheehan</dc:creator>
		<pubDate>Wed, 07 May 2008 21:35:09 +0000</pubDate>
		<guid>http://www.lyquidity.com/devblog/?p=25#comment-4</guid>
		<description>Bill, 

Thank you for the nice review. I wanted to clarify some things that you have listed in the "Cons" section, namely:
* API - we will be releasing an API that will allow you to control your GoGrid servers much the same way you can within the Web UI
* Charged for stopped state - this is because the RAM allocation is dedicated and reserved for your server(s) should you need to turn them on again instantly
* Saving images - a server SnapShot feature will be rolled out fairly soon as well
Be sure to check the GoGrid blog for more updates.
-Michael</description>
		<content:encoded><![CDATA[<p>Bill, </p>
<p>Thank you for the nice review. I wanted to clarify some things that you have listed in the &#8220;Cons&#8221; section, namely:<br />
* API - we will be releasing an API that will allow you to control your GoGrid servers much the same way you can within the Web UI<br />
* Charged for stopped state - this is because the RAM allocation is dedicated and reserved for your server(s) should you need to turn them on again instantly<br />
* Saving images - a server SnapShot feature will be rolled out fairly soon as well<br />
Be sure to check the GoGrid blog for more updates.<br />
-Michael</p>
]]></content:encoded>
	</item>
</channel>
</rss>
