Drum roll please! We are excited to announce the availability of GoGrid version 2.0, released today to all users. This is an important release from a product standpoint as it positions GoGrid firmly as the easiest to use hosting provider within the Cloud Computing Infrastructure marketplace.

What is new with GoGrid in the 2.0 release?

• MyGSI – GoGrid Server Images
• Improved Server Deployment Times
• IP Addresses in Passwords Tab

The 10,000 Foot View

Before I get into the 100 foot view, it is probably important to talk about what MyGSIs mean to you from a higher level.

The great thing about using a MyGSI for server creation is that you are creating copies of a server that you have already pre-configured. Some use cases that immediately come to mind are:

• Vertical Scaling – if you find that your current server needs more RAM to run more efficiently, you can quickly deploy a new server based on a MyGSI with more RAM allocated in minutes
• Horizontal Scaling – now you can create “clones” of a master image (MyGSI), all running the same customized code that is defined in the MyGSI
• Server Parking – many GoGrid users have been asking for a way to “park” a server without having to leave it fully deployed. Once you create a MyGSI, you store in within Cloud Storage for a nominal monthly fee. Servers can be instantiated quickly from MyGSIs, used, and then deleted, eliminating the need to always have a GoGrid server running.

A bit more detail on using Cloud Storage to store MyGSIs. For one, you can utilize the free 10 GBs we give you with every GoGrid account. Also, since each additional GB on Cloud Storage is $0.15/GB/mo, you can effectively store multiple MyGSIs for just a couple of dollars a month. When a MyGSI is prepped for storage, we heavily compress it before loading it there. Typically, Linux MyGSIs are just a few GBs in size and Windows MyGSIs slightly larger. For example, an 8GB MyGSI would cost you only $1.20 per month!

So, let’s get into the practical details of this release.

MyGSI – GoGrid Server Images

Perhaps the most exciting feature in the GoGrid 2.0 release is MyGSIs. Back in April, I gave some information about MyGSIs. Today, the full details are revealed. We have stuck to making the process of creating personal server images on GoGrid as straight-forward and easy as possible. There are THREE steps:

1. Add an Image Sandbox
2. Run the Preparation Script
3. Save your Image

Really, that is all there is to it! We mirrored much of the functionality you were already accustomed to when you create a GoGrid server, again with the goal of making your work intuitive and simple.

Understanding the Terms

• Image Sandbox – the Image Sandbox is a development environment (an actual server running on GoGrid) where you create a “MyGSI”. The Image Sandbox varies slightly from a traditional GoGrid server in that it has a fixed hard-drive size (20 GB) and RAM allotment (2 GBs).
• MyGSI – a personal server image that is used as a “Golden Master” server image to deploy GoGrid servers based on that image.
• Preparation “Prep” Script – a script that resides on all Image Sandboxes that allows you to prepare a server for imaging. The script is available on Linux and Windows servers and is executed by the end-user once the Image Sandbox is fully configured and ready to be imaged.

Step 1 – Adding an Image Sandbox

You will notice now that we have reorganized and added some things to the Add menu of the GoGrid Dashboard (which has some changes as well including a new Images tab).

At the top, you now see Image Sandbox which is where you start when you want to create a new MyGSI. Also note that we have changed the order of the elements, since logically, you only deploy a Load Balancer at the end of an Infrastructure build-out. Note: Please be sure that you have Cloud Storage deployed before trying to save a MyGSI (at the end of the process).

To start creating an Image Sandbox, click Add > Image Sandbox. You will be presented with Step 1 of the Image Creation process:

Be sure to familiarize yourself with the steps and details of each item (note: the text in these screenshots may not accurately represent the final wording within GoGrid as they were taken prior to the release of GoGrid v2.0). Once you have read the details, click Yes, Continue to proceed.

You will see the familiar Server Image selection widget:

Note: Some server image availability may change over time

With this recently introduced Server Image widget, you can search, sort, filter, group and drill-down quickly and easily until you find the GoGrid server image you would like to base your Sandbox Image on. In the image below, I have filtered by “Database Server” and “CentOS” operating system.

Note: Some server image availability may change over time

Click Next to continue. You will be presented with a form where you can define the Name, Description and IP Address of your Image Sandbox.

Note: Some server image availability may change over time

Once you have completed the information, click Save and the server will be saved to your GoGrid dashboard.

Step 2 – Run Preparation Script

After clicking Save, you will be presented with Step 2 of the Image Creation process. This is known as the Image preparation stage.

During this stage, you should fully configure your server to your liking. What that means is you can upload data, code, programs, web applications, etc. to your Image Sandbox, essentially anything that you would want to include in future GoGrid servers that are spawned based on this image. If you do have lots of data you want to include, it is recommended that you store this within Cloud Storage and then retrieve the data from there once other servers have been instantiated from the MyGSI.

Connect to your Image Sandbox the same way you would a standard GoGrid server, either via SSH (for Linux servers) or RDC (for Windows servers). Your Image Sandbox will feel and act like a traditional GoGrid server. Once you have configured the Image Sandbox and you feel it is ready to be “imaged,” you need to execute the Preparation Script.

The Preparation Script is conveniently located within both Windows and Linux servers:

Linux – In the root directory, type “ls” and you will see a script called: “prep.py“:

To execute this script, type: “./prep.py” and hit Enter. You will be presented with some information about the Preparation Script:

If you are ready to start the Imaging process, type “yes” otherwise type “no”. You can execute the script whenever you are ready. When the script starts, you will receive the following message:

Windows – to execute the preparation script in Windows, go to the Start button and select “Run”. In the Run box, type in “prep” and hit Enter.

When the preparation script runs, you receive the following alert. If you are ready to image your server, click Yes, otherwise, click No.

Once you click Yes, you have another chance to exit out of the imaging process. Read through the information carefully.

After clicking Yes, the script will start and the imaging process will begin.

At this point on either Linux or Windows, your Image Sandbox will shut itself down. Return to the GoGrid Dashboard and wait until the icon that indicates that status of your server turns RED.

Once your Image Sandbox has stopped, you are ready for Step 3 of the Image Creation process.

Step 3 – Save Your Image

Now that your Image Sandbox is in a stopped state, you can save it as a MyGSI which will load it to Cloud Storage for later use.

When you select your Image that you want to save, you will see a new action that you can do, either by right-clicking on the image:

Or by looking at the menu on the dashboard:

The action you would take is Save. Choosing this will delete the Image Sandbox and transfer it over to Cloud Storage. When initiating this process, you see Step 3.

It is at this point that you should be sure that you have Cloud Storage mounted within your GoGrid Dashboard. Once you click Yes, Continue you are asked for an Image Name and Description:

This process typically takes about 15 minutes to 1 hour to complete, depending on the Operating System and the amount of data you have loaded to the Image Sandbox. Once the imaging is complete, the Image Sandbox will no longer appear on the Grid Dashboard but will appear under the new Images section. The picture below shows the image being saved:

Once the process is complete, the State column will show “Available” meaning that the image can be used for creation of GoGrid servers. Note: the current release does not support the deletion of stored images, however, we will be releasing this functionality shortly.

You can always see a history of all of the actions that take place within the Jobs tab.

You are now ready to deploy new GoGrid Cloud Servers using your newly created MyGSI!

Creating Servers from MyGSIs

The process for creating a new GoGrid server from a MyGSI is the same as creating a standard GoGrid server. Simply click Add and launch the Server Selection widget:

Note: Some server image availability may change over time

You will see that the MyGSI created earlier appears with the Name that you entered when defining the MyGSI as well as has an Owner name different than “GoGrid”. In the example above, the owner is called “ServePath”.

Note: Some server image availability may change over time

Remember that you can Group columns within the Server Image widget, making it quite easy to find the MyGSIs you have created previously.

Note: Some server image availability may change over time

Another nice thing is, if you want to create a new MyGSI based on a previously created MyGSI, you can do this the same way you would create a new MyGSI. This allows you to create different “versions” of your own images which is especially helpful if you are doing lots of performance tuning of your code or trying new configurations.

So there you have it, MyGSIs in a nutshell. I will bet you didn’t think it would be THAT easy to do!

Improved Server Deployment Times

While much of our engineering effort was focused on bringing MyGSIs to life, in that process we also completely overhauled the system that stores the base GoGrid server images, resulting in a dramatic decrease in deployment times. We have benchmarked the following:

• Linux servers now deploy in less than 2 minutes and are accessible via SSH after 5 minutes
• Windows servers instantiate in less than 5 minutes and are available via RDC after 8 minutes

Do note, however, server deployment times can vary depending on overall system load (e.g., if multiple “adds” are being processed in succession), but on average, users should see much faster deployment times as of this release.

IP Addresses in the Passwords Tab

Lastly, I want to mention a small but incredibly useful change. We have added “IP Address” as an additional column to the Passwords tab. With this change, you now have all of the required information to connect to your servers remotely in one place:

In Summary

Pretty exciting stuff if I do say so myself. We would love to get your feedback on all of the new features and the performance of GoGrid version 2.0 so drop us a note or leave a comment! Remember, more information can also be found on the GoGrid product site, within the GoGrid Wiki (for full documentation) and in the GoGrid Forums. We have some showcase videos posted to the main GoGrid site as well so be sure to review the “How It Works” section.

Last night we release a new version of GoGrid that has a few notable changes, specifically:

• Server Image Selection Widget
• Smart selection of RAM allocations (and 8 GB RAM options in web GUI)
• Updates to GoGrid API
• Enhancements to underlying Architecture

Server Image Selection Widget

The biggest visual change in this release is to how Windows and Linux Database, Web and Applications server images are selected within the GoGrid web interface. This is essentially the framework that will be used for the upcoming MyGSI feature. Since we continue to add new images to the GoGrid image repository, and we will be enabling your own personal server images to be stored within GoGrid, we realized that the current selection process of Application & Database servers doesn’t scale very well.

Our software engineering team has come up with an elegant image selection widget that will allow you to quickly drill-down to the image type you wish. Instead of trying to articulate what the new selector looks like, here are some screenshots of what to expect.

After you click on the Add Web/Application Server Icon, you are presented with a list of all available images:

You can see that the list shows the Name, Operating System (OS), Architecture type (32/64-bit), Type of server (Web/DB), Price (e.g., MS SQL, for example, shows a charge – see below) and the Date the image was Updated.

The image below shows a list of Database Servers filtered by “64-bit” Architecture (note the icon in the upper left-hand corner).

The image below shows the filter for Architecture for Web & Application Servers.

Below is the Operating System filter.

If you know the Name or keywords relating to the image (“PHP” for example), you can type it in. To filter the list, simply hit ENTER and the results will only show those images that match your keywords. The free-form text filter works on Name, OS, Application Stacks and Architecture fields.

Each of the Columns also allow for sorting, filtering and grouping.

Smart Selection of RAM Allocations (8GB via Web Portal)

Once you have chosen the image that you want by highlighting the image and clicking the Next button, you are presented with a screen where you can enter in the Name, Description, Public IP address and RAM for that particular server. An important change in this release is the ability now to select 8 GB RAM allocations for certain images.

Some images are not available in the larger (4 and 8 GB RAM allotments) and the UI now filters out those options (e.g., Windows Server 32-bit images are only available in 512 MB, 1 GB and 2 GB configurations).

However, 64-bit Windows Server images do have 4 and 8 GB options.

API Version 1.1 released

We have incremented the version of the GoGrid API to version 1.1. There are not any new API methods or object, just simply some updates to attributes. Details can be found on the GoGrid Wiki. Items that have been updated include:

• Server Image (Object)
  • architecture
  • type
  • state
  • price
  • billingTokens
• IP (Object)
  • state
• Billing Summary (Object)
  • startTimestamp
  • endTimestamp

Enhancement to Underlying Architecture

Lastly, we have made some non-visible changes to the underlying architecture of GoGrid in preparation for the launch of the MyGSI functionality. While these are not immediately obvious to the end user, they will help with the forthcoming release of MyGSIs.

As always, we sincerely hope that you enjoy this GoGrid release. Comments, suggestions and feedback are always appreciated and welcome!

If you are a GoGrid customer, you recently received the April GoGrid newsletter that talks about one of the exciting new features coming from GoGrid, specifically “Personal Server Images” which we call “MyGSIs.”

Definitions

First, it probably would be helpful to understand some of the new & current terms we are using:

• Base GoGrid Server Image is a standard GoGrid server images (e.g., Windows or Linux) that is created by GoGrid and currently available within the GoGrid system for deploying servers
  
• Image Sandbox is a development environment where you can create a “MyGSI.” Server Images created within the Sandbox are unique in that they have a predefined RAM allocation and hard drive sizes and are only used temporarily to create a Server Image. Images created within the Sandbox contain any and all custom code or applications that you choose to put on them.
  
• MyGSIs are based on either a Base GoGrid Server Image or other MyGSIs but where you have the ability to personally configure, customize and save it to your liking from the Image Sandbox environment. They are used to spawn or instantiate new custom servers within GoGrid, with all your customizations, code and applications present.
  

Think of MyGSIs as originals that can be used to make copies, much the way you would have a Golden Master CD and you would make copies or clones based off of that Golden Master.

Usage

From a high level, creating a Sandbox Image can be done in 3 easy steps:

1. Add an Image Sandbox;
2. Install, Configure & Prepare (bundling scripts) your Image Sandbox for imaging;
3. Save your Server Image from your Image Sandbox to your personal Images repository on Cloud Storage.

With a bit more granularity, it is a way for you to build and save a custom and personal server image. MyGSIs are created like this:

1. Add an Image Sandbox (an Image Sandbox has a server “development environment” of 2 GB of RAM and 20 GB of storage);
2. Remotely log in to the Server you are creating within the Image Sandbox via SSH or RDC (just as you would with a normal Cloud Server on GoGrid) and upload your applications or code. Configure the server to your exact specifications and lastly run “bundling scripts” which we provide to prepare the Image Sandbox for imaging;
3. Save new, MyGSIs from your Image Sandbox to GoGrid Cloud Storage. Note: you can store unlimited server images in Cloud Storage;
4. Deploy new server instances using the saved MyGSI which are great for rapid horizontal scaling, changing RAM allocations, or re-imaging a server (see “High-level Use Cases” below)

The monthly price to store a MyGSI relates to the amount of data in the contained within that Image. For example, if your Image contains 5 GB of data (your code and Operating System), you pay roughly $0.45/month. We compress the Image before it goes to Cloud Storage, so your 5 GB Server Image becomes roughly 3 GB, saving you some money in the process. GoGrid Cloud Storage costs $0.15/GB and the first 10 GB are free.

A Personal Server Image can be deployed as a new Server Instance by simply selecting the appropriate image from your repository, configuring the amount of RAM and the IP address of the new server instance, naming it and deploying. It really is that simple.

However, there are some IMPORTANT changes to workflow that you should start considering now.

Current Workflow (Pre-MyGSIs)

Right now, with GoGrid, a common workflow might consist of the following:

1. Create Web/App Servers individually based on Base GoGrid Server Images
2. Create DB Servers individually based on Base Server GoGrid Images
3. Configure Web/App Servers individually
4. Configure DB Server individually
5. Create Load Balancer
6. Tie it all together via a private network

While this is very straight forward and easy to do currently on GoGrid, if you are deploying and configuring large infrastructures, this process can become a bit time consuming and increases the chance of mis-configuration or human errors. We understand this and thus MyGSIs were born.

Future Workflow (MyGSIs)

It is VERY IMPORTANT to review this new workflow model. Following it will save you time and money as well as reduce the possibility for error.

In the current workflow (pre-MyGSIs), you focus on creating an infrastructure “live”, that is to say, configuring servers real-time that will be used in production. It’s a one-to-one setup, one server at a time. Once MyGSIs are rolled out, you can prototype and develop your server configurations within a specialized environment and create “masters” of which copies are spawned to production. This is more of a one-to-many setup where one “Golden Image” or “Golden Master” can be used to deploy multiple copies, all based on the original. This allows for better and faster scalability and much easier management of your infrastructure.

The new workflow would consist of:

1. Create & Configure a Web/App within the Image Sandbox and save as a MyGSI
2. Create & Configure a DB within the Image Sandbox and save as a MyGSI
3. Deploy multiple instances of new GoGrid Web/App Servers based on the MyGSI
4. Deploy multiple instances of new GoGrid DB Servers based on the MyGSI
5. Create Load Balancer
6. Tie it all together via a private network

Note: once you save your MyGSI, your Image Sandbox is “destroyed” and the Image is copied to Cloud Storage as a server image.

While this is the same amount of steps, if you are creating a redundant & high availability environment (see “How to Set Up High Availability Web Applications in the Cloud using GoGrid“), you actually eliminate some steps because you only have to configure your servers (the MyGSIs) once and then deploy multiple server instances based on that MyGSI with a couple of clicks. In the pre-MyGSI workflow, you would need additional steps for each server you configure and deploy.

So, the important thing to consider as you plan for this exciting release is that you will start your workflow within the Image Sandbox and then move from there. Unfortunately, there will not be a way with this first release to turn actively deployed GoGrid servers into Personal Server Image.

High-level Use Cases

There are several use cases that come to mind that will be simplified with the MyGSI release. While I will not go into the details, here are a few that people should consider:

• True Horizontal Scaling
• Changing & Optimizing RAM Allocations
• Re-imaging Servers
• Disaster Recovery & Failover Environments

I will explore some of these use cases in subsequent posts.

Lastly, for those of you ready to try out GoGrid, I encourage you to set up a GoGrid account NOW. You will be able to familiarize yourself with its workings, test out the different images and templates currently available and then design your strategy for when MyGSIs roll out.

Be sure to check the GoGrid blog for updates on this release which is expected to roll out at the end of July. I hope you are as excited as I am about this upcoming feature release!

Last week, we quietly released some new larger GoGrid Cloud server instances. Today we are making that announcement a bit louder. What does this mean to you? Well, your GoGrid cloudcenter just got a bit broader and more powerful. For a year now, we have been offering 0.5, 1 and 2 Gigabyte RAM options in both Windows and Linux, now we have 4 and 8 GB RAM instances available. These larger instances, available on all 64-bit operating systems, allow for new types of higher-end environments to be spun up using all of the characteristics of Cloud Computing.

The lower size RAM instances (0.5, 1 & 2 GB) are perfect for a web front-end, where either Apache or IIS are running. For extremely high-performance and high I/O instances, we have been offering Cloud Connect as a way to create a dedicated hybrid infrastructure where Cloud Web Servers running on GoGrid can be linked via private dedicated network connections to dedicated and managed servers within the ServePath network.

With the new 4 and 8 GB RAM options, you can now set up a infrastructure with a robust set of high-performance application servers within the Cloud. These types of high RAM instances are perfect for users who want to take advantage of the increased RAM, CPU cores and persistent storage, especially when used in conjunction with specific applications (e.g., Microsoft SQL server or other Enterprise applications) that require more larger amounts of resources like RAM or CPU.

The 4 GB RAM server images can be deployed via the GoGrid web portal and API. The 8 GB RAM server images currently may only be deployed via the GoGrid API. I recommend reading the API section of the GoGrid wiki in order to fully understand how to deploy 8 GB RAM instances.

The 4 and 8 GB RAM images, available for Red Hat Enterprise Linux 5.1, CentOS 5.1, and Windows Server 2003 and Windows Server 2008 64-bit operating systems bring a new level of performance to the GoGrid line. 4 GB Cloud Servers have 3 CPU Cores and 8 GB have 6 CPU Cores, ensuring dedicated CPU allocations and high performance.

All GoGrid Cloud Servers come with persistent storage. The new larger RAM allocations announced today, are delivered with increased persistent storage: 4 GB Cloud Servers have 240 GB of hard drive space and 8 GB have 480 GB of storage allocated at boot time. Additional storage can be added using GoGrid’s dynamically scalable Cloud Storage offering which includes a 10 GB free allotment to start with. Each 1 GB thereafter costs $0.15/GB/month.

Our current breakdown of GoGrid Cloud Servers and associated RAM/CPU/Persistent Storage is as follows:

Further information on the new 4 and 8 GB RAM GoGrid Cloud Servers can be found on the GoGrid site. Server Release Information on these new images can be found on the GoGrid wiki. We have also posted a Server Compatibility Matrix that graphically shows what server instances are available with the associated RAM allocations.

If you are a Windows user, we ask that you please our Release and Errata pages as there are some known issues specific to 8 GB Windows Servers which may require a workaround and that they should be aware of before using 8 GB GoGrid Servers with Windows.

Our full Press Release on this information can be viewed here as well as on the GoGrid site.

As always, please leave any questions or comments here on this blog post, or open a Support case via the GoGrid portal should you need technical assistance.

2008 was an action-packed year for us here at GoGrid and ServePath and we have many accomplishments to be proud of. I thought it would make sense to reflect back on what major things we did over the year as well as a few other notables that happened within the industry. The easiest way for me to do this is through a blog post Chronology (not every post is highlighted):

1st Quarter 2008

• 01.03.08 – GoGrid Blog was launched
• 01.29.08 – “Sneak Peak” at GoGrid
• 02.01.08 – Twitter and Joyent go different ways
• 02.05.08 – Understanding “Clouded” Computer Terms – a post that made a 1st attempt to explain Cloud, Utility, Grid and other Computing terms.
• 02.13.08 – Dilbert does a series on Virtualization (here, here and here)
• 02.15.08 – Amazon’s S3 has major outage (my comments)
• 02.21.08 – GoGrid launches a new public website in anticipation of the product launch
• 03.11.08 – GoGrid Public Beta LAUNCH! After over 2 years of development, GoGrid hits the streets with many Cloud Computing firsts:
  • 1st Cloud Infrastructure provider with a Web GUI
  • 1st to offer Windows Server 2003 in the Cloud
  • 1st to offer Microsoft SQL Server in the Cloud
  • 1st with free Inbound Transfer
  • 1st with free f5 Load Balancing
  • 1st with free 24×7 Support
  • 1st with Persistent Storage
  • 1st with free managed DNS
  • 1st with 100% Uptime SLA
  • 1st with public and private VLANs
• 03.17.08 – Drilling down on the details of new GoGrid accounts
• 03.18.08 – Even I wasn’t initially on board with the whole “Cloud Computing” term. My thoughts have changed obviously.
• 03.28.08 – The initial GoGrid FAQ’s start rolling out.

2nd Quarter 2008

• 04.10.08 – GoGrid launches new templates: multiple RHEL, CentOS, Windows 2003 flavors
• 04.14.08 – GoGrid launches the Wiki (wiki.gogrid.com)
• 04.21.08 – GoGrid exhibits at the Web 2.0 Expo (some of our Expo stunts)
• 05.20.08 – GoGrid starts getting some blog traction
• 05.22.08 – Soliciting feature and images requests from the GoGrid community produced many great ideas
• 06.02.08 – NetworkWorld reviews GoGrid
• 06.04.08 – IP Suggest feature débuts
• 06.10.08 – “Cloud Computing” terms really starts trending upwards
• 06.16.08 – Cloud Computing helps build communities
• 06.19.08 – InfoWorld reviews GoGrid
• 06.24.08 – Introduction of the Cloud Pyramid
• 06.27.08 – GoGrid at GigaOM Structure ‘08 and Rafe Needleman of WebWare talks about GoGrid

3rd Quarter 2008

• 07.07.08 – GoGrid hits 1000th user and coverage by TechCrunchIT
• 07.17.08 – GoGrid launches API
• 07.18.08 – NetworkWorld, C|net & TechCrunchIT cover GoGrid’s new API
• 07.21.08 – InfoWorld does a side-by-side comparison of GoGrid, Amazon’s EC2 and Google App Engine
• 07.22.08 – Teens-in-Tech founder, Daniel Brusilovsky, interview of GoGrid
• 07.31.08 – Google Web Toolkit (GWT) showcases GoGrid
• 08.06.08 – GoGrid WINS LinuxWorld 2008 Best of Show in Product Excellence
• 08.19.08 – GoGrid is the FIRST to launch Windows Server 2008 in the Cloud
• 09.09.08 – the first NoHardware.com video is released
• 09.16.08 – Financial Markets start getting very shaky. Cloud Computing can help stabilize.
• 09.17.08 – GoGrid and RightScale partnership announced
• 09.22.08 – Feature preview of GoGrid’s Cloud Storage (now live)
• 09.23.08 – the second NoHardware.com video is released
• 09.29.08 – The “Original” Cloud Computing in Plain English produced in-house by GoGrid launches
• 09.30.08 – GoGrid and Appistry partnership announced

4th Quarter 2008

• 10.01.08 – Other Cloud providers announce Windows in the Cloud, play catch-up with GoGrid
• 10.03.08 – Recession starts hitting – 10 Tips to Survive it
• 10.07.08 – GoGrid and GigaSpaces partnership announced
• 10.08.08 – the third NoHardware.com video is released
• 10.21.08 – Cloud Computing Product Announcement Bingo Game
• 10.27.08 – GoGrid launches PHP-enabled Windows Server 2008 Clouds
• 11.03.08 – GoGrid & ServePath beta release Cloud Connect (connecting dedicated servers with the Cloud)
• 11.24.08 – Appistry & GoGrid do a joint webinar on Cloud Computing
• 12.02.08 – My 10 Cloud Computing Predictions for 2009, our CEO’s Predictions and our VP of Technology Strategy’s Predictions
• 12.11.08 – GoGrid featured again on Google Web Toolkit (GWT)
• 12.11.08 – GoGrid launches Cloud Storage v0.7
• 12.15.08 – Santa “Cloud” or how Cloud Computing saved Christmas
• 12.29.08 – Some New Years Resolutions

Happy New Year to all of you from us at GoGrid. May 2009 be happy, healthy and prosperous!