How can we improve Azure Cloud Services (Web and Worker Role)?

Allow a Role instance count of 0

In many scenarios it is useful to have a role that is only run for certain periods of the day. At present this is very complex to achieve as it involved using the management API to deploy and undeploy a whole service (from Blob storage). it would be much more elegant if the role count could be set to Zero thus undeploying all instances of just that role. In this way other services in the project could use the management API to start and stop just that Role.

994 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chris AuldChris Auld shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Anders MadsenAnders Madsen shared a merged idea: Support worker roles with zero instances  ·   · 
    Chris WiederspanChris Wiederspan shared a merged idea: Allow the lower-end of the AutoScale's Instance Range to start at 0 instead of 1.  ·   · 
    bojingobojingo shared a merged idea: Stop billing for stopped Cloud Services  ·   · 
    btmibtmi shared a merged idea: Make it easier to remove or disable or keep a staging build after it has moved into production  ·   · 

    30 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        oh never mind I see the 969 people before me have already moved to AWS. last one out turn off the lights.

      • ErikErik commented  ·   ·  Flag as inappropriate

        I doubt Microsoft will implement it. Reason is money. With this feature customers could pay less by not paying for idle computing. Unacceptable by profit driven management.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        2+ years and no response? Seriously Microsoft, WTH is this nonsense? Are you trying to force your customers to Service Fabric (which does not support 0 instances either, mind you)? Is it because some internal stats show you that a majority of PaaS customers are internal Microsoft and so you decide to ***** over the few PaaS customers out there?

        Your CEO shouts about "cloud first" and how we wants an Azure run-rate of $18 billion USD by 2018 and with stuff like this, what do you expect the customers to do?

        Worst of all, when a Group Program Manager talks about something being "Under Review" and then conveniently forgets to provide status update, even after 2+ years, what does it speak about a company like Microsoft?

        There are several features that the community has been clamoring for the past several years:
        1) This ask
        2) Allow multiple Worker Roles to run on 1 or fewer VMs (let us control how many VMs Worker Roles create)
        3) Have a Resource Provider for Cloud Services so that they can be deployed through ARM templates.

        Fix this broken piece of **** Microsoft!

      • DudeDude commented  ·   ·  Flag as inappropriate

        Hey, Microsoft, it's been a 5+ years since the first ask. How many CEOs and reorgs does it take to ******* do this? Unless, of course you don't want us to use Azure.

      • Eivind TjoreEivind Tjore commented  ·   ·  Flag as inappropriate

        Any news on this? Allowing instance count of 0 would greatly improve life for azure-developers :)

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please provide an update. This is an important feature and I now see that Azure competitors are providing functionality to facilitate - e.g. AWS Lambda

      • Leon MeijerLeon Meijer commented  ·   ·  Flag as inappropriate

        Please provide an update. For development purposes, 0 role instances (or via Azure Automation) would be appreciated

      • LeroyLeroy commented  ·   ·  Flag as inappropriate

        What surprises me is that we can deprovision a VM, but not a Worker Role or a Web Role. Currently this is only possible if we remove the deployment, which is quite cumbersome.

        "Post Fall 2012" is quite a broad timeframe. Can you please provide one that is more accurate?

      • Anonymous commented  ·   ·  Flag as inappropriate

        Is there any update on this feature? Now that cloud services can have reserved IPs providing this feature for Cloud Services only with reserved IPs would be okay with me.

      • Jeroen LandheerJeroen Landheer commented  ·   ·  Flag as inappropriate

        Today they have released pricing changes on Azure, but unlike virtual machines, it does not look like charges stop if cloud services or role instances are stopped. (The portal still tells you that you continue to incur charges until a deployment is deleted.) If this changes there might be a work around or even a solution to this.

      • Thomas (Mentum)Thomas (Mentum) commented  ·   ·  Flag as inappropriate

        I'd second that. Rule #1 when setting status on an idea. Don't tell dates if it's not planned.

        BTW: the suggestion with removing instances from the load balancer totally mis the point: keep configuration while not paying. I' m not sure when it would make sense to have a hot standby, that is not doing anything, if you still pay for it.

      ← Previous 1

      Feedback and Knowledge Base