none
Windows Azure Dynamic Scaling on Developer Fabric

    Question

  • I've been playing around with the Azure samples on codeplex to dynamicly scale out my worker role. I've been looking at the AzureScale sample (http://code.msdn.microsoft.com/azurescale), but can't get it to work on my dev fabric. A couple of questions:

    1. How do I get the SubscriptionId on my dev fabric?

    2.In order to get a IServiceManagement I need I need a endpointConfigurationName. In the sample this is set to "WindowsAzureEndPoint". How do I get this on the dev fabric?

    var channel = ServiceManagementHelper.CreateServiceManagementChannel("WindowsAzureEndPoint", this.Certificate);

    Thanks,

    //Mikael

     

     

    How to get the SubscriptionId on Develper Fabric?


    If this answers your question, please use the "Answer" button to say so... Mikael - http://blogical.se/blogs/mikael
    Thursday, October 28, 2010 6:41 AM

Answers

  • Apperantly Azure Service Management API doesn't work on Developer Fabric :(
    If this answers your question, please use the "Answer" button to say so... Mikael - http://blogical.se/blogs/mikael
    Thursday, October 28, 2010 11:37 AM

All replies

  • Apperantly Azure Service Management API doesn't work on Developer Fabric :(
    If this answers your question, please use the "Answer" button to say so... Mikael - http://blogical.se/blogs/mikael
    Thursday, October 28, 2010 11:37 AM
  • The following on scaling up and down is from a post I did on the service runtime:

    Steven Nagy has a good post on Azure configuration demonstrating the use of the Changing and Changed events. In the comments to that post, Mike Kelly has the interesting reminder that the csrun command can be used to to manually update the Service Configuration file in the development fabric, as follows:

    csrun /update:1729;ServiceConfiguration.cscfg

    csrun is located in the bin directory of the Windows Azure SDK. ServiceConfiguration.cscfg is the updated configuration file. 1729 is the deployment Id, in the development fabric, of this example and should be replaced by the appropriate deployment Id. This update technique works well when the service is not being debugged, successfully handling configuration changes and increases to the number of instances – although it explicitly does not handle a reduction in the number of instances. When the update is applied to a service being debugged, the change initially appears to work but then the service undergoes a tear down and stops.

    Thursday, October 28, 2010 4:33 PM
  • Does Azure Management REST API still don't work on Dev Fabric?
    http://hsuhanda.wordpress.com/
    Tuesday, December 28, 2010 2:05 PM