We are using Azure Automation DSC and were able to do simple things like create Automation account, create Resource group, VM creation and even able to deploy a web site on the target VM. All using powershell scripting.
How can we deploy Azure Cloud Services (web role / worker role)? what are the cmdlets? Any pointers? Please help.
What more things can be achieved using this? Moreover what limitations we can expect here.
Best Regards
Azure DSC is really focused on Azure's Infrastructure as a Service (IaaS) offering. Basically you can configure virtual servers (Windows and Linux) hosted on Azure.
To manage configurations for other services in Azure it is recommended to utilize Azure Resource Manager (ARM) which will allow you to define and configure Azure services in JSON.
Microsoft offers a lot of Quick Start ARM templates that can be accessed at the Azure Quickstart site.
Related
We have installed the windows service program in azure virtual machine. After installing the windows service that has been displayed in Services.msc - this is working fine without any issues.
But while we migrating the web application to Azure PaaS , how to configure the windows service in azure portal. Kindly provide the step by step process to achieve this.
Otherwise please provide if we have any alternate method to achieve this in azure PaaS.
Thank you in advance.
There is no "Windows Service" Paas on Azure, you need to migrate your Code to Azure Functions or Azure Appservice Webjobs.
Read more here https://mariankostal.com/2021/01/24/convert-windows-service-to-azure-function/
My understanding so far on PaaS deployment using WebRoles or Worker Roles-
Spinning Web roles or Worker roles will create Cloud service to manage it.
However, in ARM resource group, their is no concept of Cloud service, then how are web & worker roles managed in ARM resource group?
Also I tried adding the webroles via JSON Outline in VS 2015, but no option to add webroles. So not sure if you can deploy webroles via JSON template?
Any information will be of great help.
Cloud Services have been around since the beginning of Azure.
To the deploy or manage them, you have to use the old APIs (Azure Service Management).
As far as I know, they won't be migrated to the new APIs (Azure Resource Manager), but you could use Virtual Machine Scale Sets instead.
Azure Resource Manager Web apps rely on the concept of App Service Plans, rather than cloud services. Basically this is the underlying VM(s) that the service runs on. You can specify the size and number of servers that make up the App Service plan, and then deploy on to those as a single unit.
You create an App service plan, then run web / worker roles inside that (as well as Logic, API, Functions)
As far as Web / Worker roles are concerned, App Service Plans do not draw a distinction between the two. You simply deploy code to it and it will run it however it is packaged. See here
The concept of cloud services simply don't exist within the Azure Resource Management model.
You can find a template for deploying a Web App here
Is there components that Will be able to deploy a project to Azure with ARM storage?
Currently, We are using "Azure Deployment" with Azure Classic, that is working properly.
But, in that components We can'T select the ARM subscription, just only the classic one.
Do you have any information about that?
Maybe the ARM template will be the solution?
Thanks
Cloud Services can only be associated with classic storage accounts.
More information, you can refer to: How to create and deploy a cloud service.
So, you need to use Azure Deployment step/task with Azure Classic.
I would like to know how we need to define the resource in ARM template for enabling the Diagnostics extension on Cloud service deployed. In the examples that i came across, i could see it only for Virtual Machines with IaasDiagnostics. But i couldnt find anything on enabling the diagnostics on cloud service(PaaSDiagnostics).
Thanks in Advance
ARM template is used to deploy and provision all of the resources for your application in a single, coordinated operation, which is only available in Azure Resource Manager while Cloud Service is in Azure Service Manager, so you could not use cloud service in ARM template.
You could look at Create a Windows Virtual machine with monitoring and diagnostics using Azure Resource Manager Template to enable diagnostics in ARM template.
I deployed an Azure Worker Role running OWIN into a Cloud Service for very fast HTTP serving. The Cloud Service exists in the "classic" environment at manage.windowsazure.com.
I would like to deploy the same lightweight application using the new ARM bits so it can be fully managed at portal.azure.com. I don't want to use a Web Application because that includes IIS.
What is the correct Platform-as-a-Service object to use in the ARM and the new portal that gives the same performance as an old Cloud Service Worker Role?
Thanks.
There isn't a Platform-as-a-Service object to use for this in ARM. Some Infrastructure-as-a-Service options are:
Create a regular Windows Azure Resource Manager VM in the new portal and set it up as an OWIN host.
Create an Azure Resource Manager template to deploy an OWIN host to a VM or a VM Scale Set. The template would use the custom script extension and/or DSC to do the setup. This would be a good re-usable solution, but someone would need to write the template for the first time.
The lightest weight solution would be to have the server running in a Docker container on Windows. You could then choose use the VM for other purposes running in other containers or purely as a container host. Note this only runs on only runs on Windows Server 2016 Technical Preview 3. See http://anthonychu.ca/post/web-api-owin-self-host-docker-windows-containers/
Edit -
Note that Service Fabric is the recommended PaaS solution in Azure Resource Manager. It is not a direct equivalent of PaaS v1 but a rich service for developing micro-service based applications: https://azure.microsoft.com/en-us/documentation/services/service-fabric/
Not sure what you mean by V2 (new portal? ARM?). The portal is an independent tool, so I'm guessing you mean ARM. ARM doesn't support Cloud Service deployments currently, but you can still deploy either from Visual Studio (using the same interface you've used in the past, in visual studio) or from the portal, as a "classic" resource (which, underneath, uses the classic Azure management API).
In the portal, you'll find Cloud service (classic):
Now you can add a new cloud service:
And fill out the various parameters: