Skip to main content

Azure Automation - A new service available on Microsoft Azure

There is a new great service available on Microsoft Azure. Yes, you heard me, another new service!
The new service that is available now on cloud is called Azure Automation and it is can be very useful when you need to manage application hosted on Microsoft Azure. Before talking about Azure Automation let’s see what we didn’t had until now.
Imagine that we have an application that contains a web sites, 2-3 worker roles, a database and use different services from Azure like Service Bus, Storage and Media Services. At each deploy, we need to ensure that we follow the steps defined in our deployment document. If something’s would go wrong or we forget a step that we are doomed, there are cases when we cannot revert the action that we done. Also, at monitoring level, our team will do the same tasks over and over again, they will get bored – in the end we lose time and money when we don’t automate this kind of actions (also human errors can appear very easily).
A solution that we have out of the box is Power Shell scripts. For each of this tasks we can create scripts that will be executed by our team when is needed. This script can manage and configure almost all the services available on Microsoft Azure.
The only thing that we don’t have when we use this scripts is a workflow support, where we can order script, execute them in a transaction way (if is possible) and schedule them – in one world we are referring to automation.
For all this issues, Microsoft come with a solution called Azure Automation. Basically, over all the actions that can be done using Power Shell, we have now support to a workflow execution engine. Using this engine, we can automate our script, without needing a human intervention.
Theoretically, that could be done by our administrators, but Azure Automation offer us the possibility to create restoring points. This means that in the moment when a crash or error appears, the system will be able to recover – ‘workflow power’.
With this new service we need to enrich our vocabulary with some new terms.
Runbook – Is the workflow from Azure Automation that give us the possibility to automate all the actions.
A Runbook can be created directly from the portal and can be found under New App Services section (in this moment is in preview and you need to sign in to the preview program if you want to try it). From some configuration options, a Runbook is pretty similar with a job because you need to add the script to the portal and also you have the possibility to schedule it or to trigger it. Similar with a scheduler job, you have the possibility to see the status of last runs from dashboard.
Additional to this, a nice feature that I think that can be very useful is log level that is configured (debug, verbose, process).
All the Runbooks will run on Microsoft Azure on worker roles. It is important to know that the management of this worker role is done by the cloud provider and not by us – w don’t need to create our own worker roles for this. Because of this you don’t have control one what machine the Runbook will run, but in the end you don’t care about this.
I already imagine a case where I would like to integrate this service. I would create a Runbook that to clean some directories from web and worker roles. Additional to this I would also trigger some cleaning actions at storage level. Also, it will be very interesting if we would create Runbook for deployments.
Costs – In this moment (in preview) Azure Automation is FREE. After this preview phase, we will be able to run jobs that takes maximum 500 minutes per month free. If we need more, we will need to pay 20$ for month and will have 10.000 minutes available (yes, I wrote 10.000 minutes =  166h ~ 7 days).
From now we can automate all the administrative process related to deployment and management actions or operational and support activities.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…