I have deployed a managed application into Azure Marketplace. This application is installed with a Managed Resource Group containing multiple resources, including a Linux VM.
I have a DevOps account where I am setting up pipelines to perform automatic upgrades to my application which gets installed in my VM.
I need to find a way where every new VM (created as part of marketplace application install) is automatically configured with my DevOps pipeline.
I thought I could just export an ARM template for the VM which would include the 'Continuous Delivery' configuration, and club it to my mainTemplate.json(marketplace template). But as I checked, Azure doesn't allow that. Can someone advise on how I can achieve this?
Thanks in advance.
Related
We have our own Virtual Network. Now we want to deploy WebApp into an existing Virtual Network. Looking for the available options in Azure, is there any ARM template available?
One option I found - App Service Environment V2
Please help me for other options and ARM template to create the Infrastructure and WebbApp.
Thanks.
Regards,
Deb
App Service Environment is the only option to deploy Azure Web App into existing VNet/Subnet (Private).
Yes. Azure App Service Environment is a deployment of Azure App Service into a subnet in an Azure virtual network (VNet).
Take a look at this link
https://learn.microsoft.com/en-us/azure/app-service/environment/create-external-ase
Create ASE from template
https://learn.microsoft.com/en-us/azure/app-service/environment/create-from-template
Template example on github samples
https://azure.microsoft.com/documentation/templates/201-web-app-asev2-create
If you created your resources manually you can download your ARM template from Azure. Just click your resource group and then "Automation script". You can download it and use with PowerShell to deploy everything:
Azure resource groups give a redeploy button not sure how and when to use that. Would appreciate best practices.
In general, when we facing difficulties troubleshooting, redeploying the deployment may help.
For example, when we can't connect to Azure VM or application access to windows-based Azure VM, we can try to redeploy it. When you redeploy a VM, it moves the VM to a new node within the Azure infrastructure and then powers it back on, retaining all your configuration options and associated resources.
More information about redeploy Azure VM, please refer to this link.
By default, when we select redeploy in Azure resource group deployments, Azure will use this template to deploy this resource.
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.
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: