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:
Related
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
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.
In Azure there are 2 options available to create virtual machines.
A. normal VM
B. Classic VM
Does anybody know what is the difference between both option? When do we use one over other?
Short answer to your question is Normal VM or Virtual Machines is the new way of deploying your Virtual Machines whereas Classic VM or Virtual Machines (Classic) is the old way of deploying them. Azure is pushing towards the new way of deploying resources so the recommendation would be to use it instead of old way. However please keep in mind that there're some features which are available in the old way that have not been ported on to the new way so you just have to compare the features offered and only if something that you need is not available in new way, you use the old way.
Now comes the long answer :)
Essentially there's a REST API using which you interact with Azure Infrastructure.
When Azure started out, this API was called Service Management API (SMAPI) which served its purpose quite well at that time (and to some extent today). However as Azure grew, so does the requirements of users and that's where SMAPI was found limiting. A good example is access control. In SMAPI, there was access control but it was more like all-or-none kind of access control. It lacked the granularity asked by users.
Instead of patching SMAPI to meet user's requirement, Azure team decided to rewrite the entire API which was much simpler, more robust and feature rich. This API is called Azure Resource Manager API (ARM). ARM has many features that are not there in SMAPI (my personal favorite is Role-based access control - RBAC).
If you have noticed that there are two Azure portals today - https://manage.windowsazure.com (old) and https://portal.azure.com (new). Old portal supports SMAPI whereas new portal supports ARM. In order to surface resources created via old portal into new portal (so that you can have a unified experience), Azure team ended up creating a resource provider for old stuff and their names will always end with (Classic) so you will see Virtual Machines (Classic), Storage Accounts (Classic) etc. So the resources you create in old portal can be seen in the new portal (provided the new portal supports them) but any resources you create in the new portal using ARM are not shown in the old portal.
The Azure Virtual Machine (classic) is based on the old Azure Service Management Model (ASM). Which revolved around the concept of a cloud service. Everything was contained inside a cloud service, and that was the gateway to the internet. While it is still used (extensively) Azure is now moving over to the Azure Resource Management Model (ARM).
ARM uses the concept of declarative templates to configure an entire solution (rather than individual components) So you can create an entire Sharepoint stack, rather than just a singular machine.
ARM also has a much more logical approach to networking. Instead of having a monolithic VM in an obscure cloud service. You have a VM, that you attach a network card to. You can then put the Network card into a VNet and attach a public IP (if you need one)
Unless you have a compelling reason to use ASM (classic) You should create your solution using ARM. As this is the MS recommendation going forward (todo find a link to that) It also means that you can create templates for your deployments, so you can have a repeatable solution.
On the negative, the old portal manage.windowsazure.com can not manage anything that is deployed using ARM, and there are still parts of ASM that haven't been migrated over to ARM yet. For instance you cannot configure Azure VM backup, since Azure backup is ASM and it can't 'see' ARM VMs
It very largely depends on your circumstances though, what it is you are planning for, the method you are going to deploy with. If you are just looking to stand a machine up to do a single task, it makes very little difference. If you are looking to deploy into an environment that will have some concepts of DevOps going forward, then ARM is the way to go.
The one big differences is for resource management. For that new version is called Azure Resource Manager VM (ARM VM).
ARM VM is better in terms of;
Classic VM must be tied with Cloud Service, and Cloud Service consumes resource limitation and not-so-flexible network configuration.
ARM VM is managed under Azure Resource Manager (ARM) which can be organized with/without other Azure services. ARM is like a folder of Azure services, and it gives you more fine-grained resource management.
Classic VM can be migrated to ARM VM version, but you have to afford service downtime. To migrate from classic VM, read the official article: Considerations for Virtual Machines.
Azure provides two deploy models now: Azure Resource Manager(Normal) and Azure Service Management(Classic) and some important considerations you should care when working Virtual Machines.
Virtual machines deployed with the classic deployment model cannot be included in a virtual network deployed with Resource Manager.
Virtual machines deployed with the Resource Manager deployment model must be included in a virtual network.
Virtual machines deployed with the classic deployment model don't have to be included in a virtual network.
I want to configure an ILB for my Azure Cloud Service, similar to discussed in this article https://azure.microsoft.com/en-us/documentation/articles/load-balancer-internal-getstarted/
- but using the .Net SDK instead of powershell. (Also I have some conceptual confusion about the article/powershell maybe people will be able to explain. For VM scenario you have to explicitly create the ILB, but it seems like for cloud service you do not - is it already created, or automatically created? Why are New-AzureVM commandlets being used in a cloud service context?)
Documentation has been updated
https://azure.microsoft.com/en-us/documentation/articles/load-balancer-get-started-ilb-classic-cloud/
Or are you looking for a C# sample?
You should probably not be using cloud services. These are being deprecated. Just use v2 - Azure Resource Manager (portal.azure.com) and create a load balancer instead of a cloud service. Regardless, in v1 (Azure Service Management), when you create a VM, you automatically get a cloud service if you don't have one already - which is why new-azurevm is being used in cloud service context.