One of the cool new features of the June 2010 Windows Azure Tools + SDK is the integration of IntelliTrace to allow you to debug issues that occur in the cloud.

IntelliTrace support requires .NET 4, Visual Studio 2010 Ultimate and the cloud service has to be deployed with IntelliTrace enabled. If you are using a 32-Bit OS, you need this patch/QFE.

To enable IntelliTrace, right click on the cloud service project and select “Publish”.

At the bottom of our publish dialog, click to select “Enable IntelliTrace for .NET 4 roles”.

You can also configure IntelliTrace for the cloud settings (these are separate from the settings in Tools | Options which are used for the debug (F5) scenario which we currently do not support with Cloud Services/Development Fabric.

A couple of notes about IntelliTrace settings.

We default to high mode which is different from the F5 IntelliTrace settings in Visual Studio.  The reason is that F5 IntelliTrace includes both debugger and IntelliTrace data while in the cloud, you are only able to get back IntelliTrace data.

Additionally, we exclude Microsoft.WindowsAzure.StorageClient.dll as we found that the slow down caused by IntelliTrace instrumenting resulted in time outs to storage.  You may find you will want to remove the storage client assembly from the exclusion list.

To reset the IntelliTrace settings back to the default, you can delete “collectionplan.xml” from %AppData%\Roaming\Microsoft\VisualStudio\10.0\Cloud Tools

Click “OK” to package up everything you need to IntelliTrace the web and worker host processes in the cloud and start the deployment process.

Note: There is a current limitation that child processes cannot be IntelliTrace debugged.

The deployment process is completely asynchronous so you can continue to work while you wait for deployment the to complete and you can track the progress through the Windows Azure Activity Log tool window.

Find out more at: http://blogs.msdn.com/b/jnak/archive/2010/06/07/using-intellitrace-to-debug-windows-azure-cloud-services.aspx

GoGrid Announces Version 2.0

Today GoGrid, the Cloud Computing service from ServePath, released version 2.0 of its award-winning Cloud Computing Infrastructure solution. With this release, GoGrid users now have the ability to create personal server images, known as MyGSIs. MyGSI stands for “personal GoGrid Server Image,” a “Golden Master” server image that can be customized, saved and stored for future deployments. Users are now able to create new servers from stored MyGSIs via the GoGrid web portal or API quickly and easily.

We are extremely excited about this innovative new GoGrid release
This is an important development in the Cloud Computing marketplace, and further demonstrates our visionary approach to providing Cloud Computing functionality and features that our customers desire.
“We are extremely excited about this innovative new GoGrid release,” said John Keagy, CEO and Co-Founder of GoGrid and ServePath. “This is an important development in the Cloud Computing marketplace, and further demonstrates our visionary approach to providing Cloud Computing functionality and features that our customers desire.”

The creation of a MyGSI is an extremely simple 3-step process. First add an Image Sandbox, second, configure and prepare the Image Sandbox and third, save the Image Sandbox as a MyGSI. When a user needs to create a new Windows or Linux server based on the pre-configured MyGSI, they simply choose the saved image, fill in a few details, and instantiate the server in minutes within the GoGrid cloud.
There are several benefits and advantages of using a MyGSI to deploy servers within the GoGrid cloud:

Source Oncloudcomputing ]]> http://www.cloudtweaks.com/2009/08/gogrid-announces-version-20-cloud-computing-service/feed/ 2