Skip to main content

GoGrid MyGSI First Thoughts – follow up

I recently embarked an creating my first GoGrid MyGSI and in my previous post I mentioned that I had an open support case to resolve the fact that I could not create an instance from the image that I saved.

After five long days of waiting for some sort of resolution finally the Engineers decide that the image is “unclean” and they can’t debug the issue any further.

They did suggest however that I create another MyGSI from scratch. 

I wasn’t happy to accept this as a one off problem as I still needed to move an instance over from EC2 so I decided to test the system myself.

I created another instance without installing any application files or additional components and connected to the Cloud Storage then ran the prep script.

Again I got the same result. It booted me out of RDP but did not change to the status which allows saving the image.

I submitted another support request and the finally the cause was identified.

Assigning an Internal IP Address (which is required for Cloud Storage)was the culprit.

Admittedly this does make sense from a technical perspective, however as an end-user it would be nice if this was detailed in the documentation or if there was some sort of error or log message.

I’m pleased to say that after the cause of the problem was identified I was able to successfully migrate from EC2 to GoGrid albeit 2 weeks later than anticipated.

After becoming confident that service did in fact work it came time to create images for my running instances that were created before MyGSI was available.

The requirements for the machine are:

  1. Windows Server 2008
  2. SQL Server 2008 Express with Advanced Services SP1
  3. IIS7.0
  4. SMTP Server
  5. FTP Server
  6. MSMQ
  7. .NET 3.5 SP1

I created my instance and set about installing all of the required components. I then came to installing SQL Server and to my dismay found that there wasn’t enough room left on the sandbox.

This is before even installing any application files or databases.

Again another waste of time. In a world where data is cheap why put unnecessary restrictions? My guess is they are aiming at start-ups with very small databases, but not allowing enough space to do a standard web server install is pretty weak. 

This whole experience has been nothing short of frustrating but I guess that’s the price you pay for being an early adopter and working with Beta software. It should be said that the support is really good and you can always get quick responses on Twitter.

GoGrid MyGSI shows good potential but there are a few thing’s you need to be aware of before diving in.

  • 20GB Limits on the Image Sandboxes.                           Actual limit of 6.18 GB on Win2008 after OS footprint.
  • No way to create an image from a running instance.
  • No Windows Server 2008 Pre-Installed Images at present
  • No equivalent EBS solution
  • Light documentation
  • Setting up the Private network for Cloud Storage causes the Image shutdown to fail. Remember to remove any routes and disable the LAN2 before running the prep script.

Popular posts from this blog

Freeing Disk Space on C:\ Windows Server 2008

  I just spent the last little while trying to clear space on our servers in order to install .NET 4.5 . Decided to post so my future self can find the information when I next have to do this. I performed all the usual tasks: Deleting any files/folders from C:\windows\temp and C:\Users\%UserName%\AppData\Local\Temp Delete all EventViewer logs Save to another Disk if you want to keep them Remove any unused programs, e.g. Firefox Remove anything in C:\inetpub\logs Remove any file/folders C:\Windows\System32\LogFiles Remove any file/folders from C:\Users\%UserName%\Downloads Remove any file/folders able to be removed from C:\Users\%UserName%\Desktop Remove any file/folders able to be removed from C:\Users\%UserName%\My Documents Stop Windows Update service and remove all files/folders from C:\Windows\SoftwareDistribution Deleting an Event Logs Run COMPCLN.exe Move the Virtual Memory file to another disk However this wasn’t enough & I found the most space was

3 Reasons Why Progressive Web Apps (PWAs) Won’t Replace Native Apps

Many people believe Progressive Web Apps (PWAs) are the future of the mobile web, but in my opinion, PWAs are not a replacement for native mobile apps. Here are three reasons why: 1. Native mobile apps provide a smoother & faster experience  Mobile websites, progressive or otherwise are slower and not as smooth. 90% of the time spent is spent using apps vs the browser . The single most significant contributing factor to a smooth experience on mobile is the speed of the network and latency of the data downloaded and uploaded. When you visit websites on desktop or mobile, there is a lot of third-party code/data that gets downloaded to your device, which more often than not has zero impact on the user experience. This includes: CSS (Cascading Style Sheets) JavaScript Ad network code Facebook tracking code Google tracking code The median number of requests a mobile website makes is a shocking  69 . On the other hand, native apps only get the data that is requi

Consuming the SSRS ReportExecutionService from a .NET Client

  I’ve just finished writing a nice wrapper which internally calls the SSRS ReportExecutionService to generate reports. Whilst it was fairly simple to implement there has been some major changes between 2005 and 2008 and the majority of online and documentation is based on the 2005 implementation. The most important change is that the Report Server and Report Manager are no longer hosted in IIS which will be a welcomed change to Sys Admins but makes the security model and hosting model vastly different. So far I’ve yet to figure out how to allow Anonymous Access, if anyone knows how to do this leave a comment and it will be most appreciated. Getting Started To get started you’ll want to add a service reference to http://localhost/ReportServer_SQL2008/ReportExecution2005.asmx where ReportServer_SQL2008 is the name you configure in the Reporting Services Configuration Manager. The Web Application files are located in C:\Program Files\Microsoft SQL Server\MSRS10.SQL2008\R