Episode 77 - Windows Azure Powershell Updates

Play Episode 77 - Windows Azure Powershell Updates


Join Nate and Nick each week as they cover Windows Azure. You can follow and interact with the show at @CloudCoverShow.

In this episode, we are joined by Michael Washam — Senior Technical Evangelist for Windows Azure — who shows us some updates to the Windows Azure PowerShell Cmdlets. Michael walks us through a variety of scenarios that will help developers and administrators with management, deployment, and diagnostics on Windows Azure.

In the News:

In the Tip of the Week, we discuss a blog post by our good friend Wade Wegner. Wade shows us a quick tip on handling table storage queries that have no results using the .Net SDK.




Right click to download this episode

The Discussion

  • User profile image

    Aww, I miss you guys too!

  • User profile image
    Trevor Sullivan

    Good work guys -- hoping to see Service Bus functionality in the next version. Had to develop some of my own script cmdlets to manage Service Bus queues, topics, etc.

    Trevor Sullivan

  • User profile image
    Rodrigo De Castro

    Michael posted a working script on his blog:

  • User profile image
    Rodrigo De Castro

    Answering questions on Windows Azure Traffic Manager:

    QUESTION: Round Robin: when would you want to round robin?
    ANSWER: Currently round robin should distribute the traffic fairly evenly, so this could be used for A/B testing scenarios. For instance, you could test a production rollout by having ~50% of the traffic going to the new deployment and the rest to the current deployment. In the future we will offer ratio load balancing, where % of traffic for each endpoint will be allowed to be specified.

    QUESTION: Supporting both Performance and Failover at the same time?
    ANSWER: This is not currently supported, but the plan in the future is to support more complex scenarios through nested policies.

    QUESTION: trafficmanager.net or .com?
    ANSWER: trafficmanager.net

    QUESTION: How long does a monitor need to return a 200 status code?
    ANSWER: This is called monitor timeout and that’s set to 10 seconds currently. In the future this will be configurable by the user. Accepted values can be found in the API documentation (http://msdn.microsoft.com/en-us/library/windowsazure/hh758255.aspx)

    QUESTION: DNS TTL range (is 300 the lower limit?)
    ANSWER: Currently the range is from 30 seconds to 999,999 seconds. Ranges can be found in API documentation (http://msdn.microsoft.com/en-us/library/windowsazure/hh758255.aspx)

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.