Static IP Lifetime in Windows Azure
- Transfer
Using static addresses is a common practice on the Internet. For example, Contoso web services can be accessed only from specific IP addresses (Fig. 1)
. 1. An example of using static IP addresses The
question immediately arises about the lifetime of static application IP addresses in Windows Azure. This article discusses the process of storing static IP addresses for both PaaS and IaaS in Windows Azure.
Note : we are talking only about public VIPs (virtual IP addresses).
In PaaS, the IP address is assigned to the deployment (production or staging) of the package you created (Fig. 2). The IP address will remain unchanged throughout the deployment lifecycle. There is currently no way to save the IP address beyond the deployment lifetime .
Fig. 2. Deployment Example
Thus, if you do not want a VIP change, consider updating in place or exchanging VIPs.
In the case of IaaS, there is only a production deployment. A VIP address is assigned only when the virtual machine is added to an empty cloud service (Fig. 3)
. 3. No change in VIP after adding a new virtual machine
Fig. 4. Cloud service without virtual machines
If you need to delete all virtual machines but don’t want to lose your public IP, deploy a temporary virtual machine in the same cloud service.
Thus, in this article, we examined in what situations there is (or does not) change the public IP addresses for both PaaS and IaaS in Windows Azure. I hope this article gives you a better understanding of managing public VIPs in Windows Azure.
. 1. An example of using static IP addresses The
question immediately arises about the lifetime of static application IP addresses in Windows Azure. This article discusses the process of storing static IP addresses for both PaaS and IaaS in Windows Azure.
Note : we are talking only about public VIPs (virtual IP addresses).
PaaS: Web and Worker Roles
In PaaS, the IP address is assigned to the deployment (production or staging) of the package you created (Fig. 2). The IP address will remain unchanged throughout the deployment lifecycle. There is currently no way to save the IP address beyond the deployment lifetime .
Fig. 2. Deployment Example
VIP address will NOT change
- In case of in-place updates, exchange of VIP between stage and production within the same service, and scaling;
- In any case, hardware recovery after a failure.
VIP address will change
- When uninstalling a cloud service deployment. A new VIP will be assigned for the new deployment.
Thus, if you do not want a VIP change, consider updating in place or exchanging VIPs.
IaaS: Virtual Machines
In the case of IaaS, there is only a production deployment. A VIP address is assigned only when the virtual machine is added to an empty cloud service (Fig. 3)
. 3. No change in VIP after adding a new virtual machine
VIP address will NOT change
- In the case of vertical scaling (resizing the virtual machine) and adding new virtual machines to the cloud service;
- Like PaaS, the VIP address will not change in any case of hardware recovery after a failure.
VIP address will change
- If there are no virtual machines in the cloud service (Fig. 4)
Fig. 4. Cloud service without virtual machines
If you need to delete all virtual machines but don’t want to lose your public IP, deploy a temporary virtual machine in the same cloud service.
Conclusion
Thus, in this article, we examined in what situations there is (or does not) change the public IP addresses for both PaaS and IaaS in Windows Azure. I hope this article gives you a better understanding of managing public VIPs in Windows Azure.
