Daniel TIZON on Tue, 25 Jul 2017 14:51:32
I provisionned the AzureStack App Service RP (ASDK) with one default "Web worker Shared role".
I would like to know how we can we add additional worker (shared, medium or large) roles safely?
In CTP3 it was : Resource providers > App Service Management > Settings > Roles > New Role Instance, as documented here: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-app-service-add-worker-roles
In ASDK, the "New Role Instance" button is disabled...so what is the new procedure?
- In the APP SERVICE Resource Group, Go to scale 'Virtual Machine Scaleset' -> Scaling -> change number of instances->Save?
- Resource providers > App Service Management > Settings > Roles > Add Role Instance?
- Do additional steps in the CN0-VM ?
Daniel TIZON on Tue, 25 Jul 2017 16:58:05
Here is an update.
I succeded in adding a "Web worker Large role" with my first idea:
In the APP SERVICE Resource Group, Go to scale 'Virtual Machine Scaleset' -> Scaling -> change number of instances->Save
it took 4 hours to see the instance in the ready state in both the CN0-VM and in the App Service Management --> Settings --> Role
No additional steps done to make it working.
Hoping this is the supported way to do it.
Is it ?
Gary Gallanes [MSFT] on Tue, 25 Jul 2017 18:29:29
The method you used to scale-out additional worker roles is supported.
There are actually 2 supported methods for doing this:
- Add additional workers directly from with within the App Service Resource Provider Admin.
- Create additional VMs manually and add them to the App Service Resource Provider.
Please the following link for complete details: Add More Web Worker Roles
Andrew Westgarth on Tue, 25 Jul 2017 20:00:07
that is indeed one way in which you can scale out instances however to enable the integrated experience you must complete the post deployment steps to configure the service principal and single sign on as detailed in the deployment documentation - https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-app-service-deploy#configure-aad-service-principal-for-virtual-machine-scale-set-integration-on-worker-tiers-and-single-sign-on-for-the-azure-functions-portal-and-advanced-developer-tools
Did you complete those steps in your installation?
Mr David Fleming on Fri, 28 Jul 2017 00:10:38
I'm seeing the same issue as Daniel. I've deployed 3 ASDK servers with identical hardware and following the same process for each. I've managed to add a dedicated small web worker to the first two deployments but when going to add one to the third, the option is grey out.
Apologies for the picture size, it's 1AM here and my Surface scaling has went a little mental :)
I'll likely just add one manually in the interim but I just wanted to report this doesn't appear to be an isolated issue for Daniel.
Thanks in advance.
Daniel TIZON on Fri, 28 Jul 2017 23:42:30
Since I executed the "UpdateConfigOnController.ps1" the button "New Role Instance" is no more disabled, and I can scale from here.
Andrew Westgarth on Sat, 29 Jul 2017 00:18:37
this option will be greyed out unless you complete the post deployment steps as I mentioned to Daniel. He has now completed those and is able to add new role instances.
The steps are documented in the deployment documentation.
The specific instructions for AAD Deployments are:
And for ADFS
Mr David Fleming on Sat, 29 Jul 2017 07:56:08
Yup, totally my fault. For some reason I'd completely overlooked this step on this server, that's what happens when deploying 3 at once :)
I've now completed the task and as expected it's all working perfectly.