Tuesday, May 3, 2011

TechDays 2011: Some great Windows Azure tips

Last week I attended TechDays Belgium. During two sessions about Windows Azure, Christian Weyer gave a lot of interesting tips.

AzureWatch

The first thing he mentioned was a tool called AzureWatch. This tool enables the automatic scaling functionality that is not available out-of-the box. It monitors your performance counters, instance statuses, queue information and other metrics and passes all this information to some rule engines that can take decisions based on this input. 

Most important features are:

    • Automatically scale-up or scale-down your Azure instances based on...
      • Real-time demand using latest values of performance counters
      • Historical demand based on aggregated values of performance counters
      • Rate of increase of decrease in demand
      • Time of day
      • Sizes of Azure queues
      • Instance Ready/Unresponsive/etc statuses
      • Any or all of the above combined
    • Receive email alerts when user-defined conditions are met, such as...
      • When instances become unresponsive
      • When quantity of instances reaches maximum threshold but your system is still under heavy load
      • At predefined intervals with up-to-date performance metrics
    • Gain visibility into performance of your Azure applications with...
      • Powerful and comprehensive dashboard
      • Single Perfmon that displays performance metrics of your application averaged across all Azure instances
      • Analyze, print, or export performance metrics dating up to a month back
      • Drill-down reports and charts showing key performance indicators on a monthly, daily, or captured level
    • Safety mechanisms
      • Built-in limits prevent your instance count from going outside of a predefined range
      • Built-in throttle controls prevent your applications to not scale up or down too frequently

Deployment in 3 seconds

Another thing he showed us was a way to easily deploy Windows Azure applications without having to go through the entire deployment process of Windows Azure(which takes time).

The idea is the following:

  • use Windows Azure Blog Storage to host the website/webservice package
  • use a 3rd party tool to map the blob storage account as a folder in Windows Explorer
  • Build the application, zip the output and copy the zip file to this folder
  • On your webrole add some code that checks for new files in this blob storage location. If new files are found extract the package and deploy it in IIS on the web role.

This idea takes advantage of the fact that starting from SDK 1.3 the web app and the roleentrypoint code run in their own process(Christian called this the ‘web-workerrole’ functionality).

If you are looking for a tool to mount your storage accounts locally in Windows Explorer,he recommends Gladinet Cloud Desktop.

During his talk he gave a demo where he was able to deploy a website in a few seconds.

For more information about this, check out Christian’s blog.

Azure versioning

At the moment there are 2 families of the Azure OS available:

If you create a new instance, by default it’s configured to use version 1. Christian recommends to always upgrade this to version 2 and don’t specify a specific version(by doing this your system will be upgraded automatically).

<ServiceConfiguration osVersion="*" osFamily="2" serviceName="CloudService1" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration">
<Role name="WebRole1" >
<Instances count="1" />
<ConfigurationSettings>
<Setting name="DiagnosticsConnectionString" value="UseDevelopmentStorage=true" />
<Setting name="DataConnectionString" value="UseDevelopmentStorage=true" />
</ConfigurationSettings>
</Role>
<Role name="WorkerRole1">
<Instances count="1" />
<ConfigurationSettings>
<Setting name="DiagnosticsConnectionString" value="UseDevelopmentStorage=true" />
</ConfigurationSettings>
</Role>
</ServiceConfiguration>

More information about this here.



Thanks Christian for all these tips!

No comments: