Skip to main content

Internal Static IP on VM in a Virtual Network from Windows Azure

In general I don’t discuss about IT PRO features from Windows Azure, but some of them are very important. Why: because in the end we design solution to run somewhere. In today post we will talk about how static IP on VM from Windows Azure.
I assume that this is the first time when you hear about this subject. Let’s start with the begging. On Azure we have a Virtual Network where we can add our VM. Of course each machine from this network will have an IP based on the Virtual Network configuration (subnet range, available IPs in our Virtual Network and so on).
When we restart of machine (OS upgrades, application upgrades, …) the IP allocated to the machine will remain the same. If we deallocate one of VM machines from Virtual Network, the IP will be automatically available to other new VM that will be added. This means that if we have a machine with 192.168.1.2 (internal IP) and we deallocate it, the next VM that will be added to the network will have this IP, even if there will be other IP’s available in our network.
Unfortunately, if we deallocate our machine the machine and recreate it, the IP that is allocate to it will not be the same (if other VM were already added to the network or an IP with smaller value is available). Because of this, if we configure other VM to connect to a specific IP, we will have problems with machines IP – we will need to change the configuration of the VM that tries to connect to a resource using the IP (sticky connection).
First of all we should access the machines based on the name and not based on IP, but there are times when we cannot use the name of the machine. A new feature was added to Windows Azure that give us the possibility to configure the internal IP of a VM that is created on our private network.
This mean that when you create the VM you can specify what the internal IP will be. Unfortunately this cannot be made from Windows Azure portal (yet, in the future we may have this option available).
We can configure the internal IP using power shell scripts. In the setup of our VM we have a new configuration called “Set-AzureStaticVNetIP”. This will allow us to set the internal IP
Set-AzureStaticVNetIP -IPAddress 192.168.1.2
To get the IP of the machine we can use the following command
Get-AzureStaticVNetIP -VM {VirtualMchine}
To remove the internal static IP you need to use the following command “Remove-AzureStaticVNetIP”
Enjoy!

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…