Static IP address lifetime in Windows Azure
The use of static addresses is a frequently used practice on the Internet. For example, access to Contoso web services can only be done from specific IP addresses (Figure 1)
Fig. 1. An example of using static IP addresses
The question immediately arises about the lifetime of the static IP addresses of the application in Windows Azure. This article discusses the process of saving static IP addresses for both PaaS and IaaS in Windows Azure.
Note : these are only public VIPs (virtual IP addresses).
In PaaS, the IP address is assigned to the deployment (production or staging) of the package you created (Figure 2). The IP address will remain unchanged throughout the deployment life cycle. There is currently no way to save an IP address beyond the life of the deployment .
Fig. 2. Deployment Example
Thus, if you do not want a VIP change, consider the possibility of an on-site upgrade or VIP exchange.
')
In the case of IaaS, there is only a production deployment. A VIP address is assigned only when a virtual machine is added to an empty cloud service (Fig. 3)
Fig. 3. No VIP change after adding a new virtual machine.
Fig. 4. Cloud service without virtual machines
In case you need to delete all virtual machines, but do not want to lose the public IP, deploy a temporary virtual machine in the same cloud service.
Thus, in this article we examined the situations in which (or not) public IP addresses change for both PaaS and IaaS in Windows Azure. I hope this article will give you a more complete picture of managing public VIPs in Windows Azure.
Fig. 1. An example of using static IP addresses
The question immediately arises about the lifetime of the static IP addresses of the application in Windows Azure. This article discusses the process of saving static IP addresses for both PaaS and IaaS in Windows Azure.
Note : these are only 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 (Figure 2). The IP address will remain unchanged throughout the deployment life cycle. There is currently no way to save an IP address beyond the life of the deployment .
Fig. 2. Deployment Example
VIP address will NOT change
- In the case of on-site updates, VIP exchange between stage and production within one service, and scaling;
- In any case, hardware recovery after a failure.
VIP address will change
- When uninstalling a cloud service deployment. For a new deployment, a new VIP will be assigned.
Thus, if you do not want a VIP change, consider the possibility of an on-site upgrade or VIP exchange.
')
IaaS: Virtual Machines
In the case of IaaS, there is only a production deployment. A VIP address is assigned only when a virtual machine is added to an empty cloud service (Fig. 3)
Fig. 3. No VIP change 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;
- Similar to PaaS, the VIP address does not change in any case of hardware disaster recovery.
VIP address will change
- If there are no virtual machines in the cloud service (fig. 4)
Fig. 4. Cloud service without virtual machines
In case you need to delete all virtual machines, but do not want to lose the public IP, deploy a temporary virtual machine in the same cloud service.
Conclusion
Thus, in this article we examined the situations in which (or not) public IP addresses change for both PaaS and IaaS in Windows Azure. I hope this article will give you a more complete picture of managing public VIPs in Windows Azure.
Source: https://habr.com/ru/post/165207/
All Articles