Skip to main content

Azure and IP Persistence - VM,Web/Worker Roles

If you already worked with Windows Azure, especially with worker roles, web roles or VM I suppose that you noticed that Azure don’t guaranty a static IP of this machines. Because of this it is not recommended to access or connect different Azure resources based on the IP (internal IP).
But in the same time, there are moments when the IP is persisted. For example when you restart the resource. In this blog post I will try to explain when the IP of the resources will not change and will remain the same after different actions.

Case: Upgrade
Let’s suppose that our resource is restarted after an update. In this case the original IP of it will be persisted.
Example:
Before:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11 (restarted)
After:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11

Case: Hardware fail
When we have a resource that I take down because of different situations (for example hardware fail) the original IP of the machine will be persisted after the instance is re-deployed. Even if the instance is moved on a different physical device.
Example:
Before:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11 (hardware fail)
After:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11

Case: Resource reboot
In the moment when a resource is rebooted the original IP will be persisted.
Example:
Before:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11 (reboot)
After:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11

Case: Scale up with a new image
When we need to scale up, allocating a new image of our resource a new IP will be allocated to this resource. The existing images will remain with the same IP as before.
Example:
Before:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11
After:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11
VM_IN_2 – 10.0.0.11

Case: Scale up after a scale down
After a scale up and a scale down, the next operation of scale up will not create a new image of the resource with the same IP as last time when we scale up.
Example:
Before:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11
Scale up:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11
VM_IN_1 – 10.0.0.12
Scale down:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11
After (scale up second time):
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11
VM_IN_2 – 10.0.0.13

Case: Resource is de-allocated (stop de-allocate)
When we have a resource that is de-allocated we cannot assume that the current IPs will be persisted until the resource will be allocated again. Allocating the resource again will use different IPs
Example:
Before:
VM_IN_0 – 10.0.0.10
VM_IN_1 – 10.0.0.11
De-allocate
After (allocate resource again):
VM_IN_0 – 10.0.0.12
VM_IN_1 – 10.0.0.13

If we have situations when the IP of the resource is the same, there is another story with MAC address. Don’t assume that if the IP will be the same, than the MAC address will persist also. For example for the hardware fail case, the MAC address will change because another VM will be used.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP