Azure的VIP（虚拟IP地址）

本文介绍了Azure的VIP（虚拟IP地址）的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

可能有人请帮助我了解以下相关Azure的VIP？

Could someone please help me understand following related Azure VIP?

生产是否VIP插槽得到改变，当我们做VIP SWAP？

请问新的部署改变了VIP？

在什么样的情景呢贵宾变化？

如果我删除分段插槽和重新部署，并执行VIP掉那么就会产生新的VIP？

感谢您

推荐答案

交换VIP不改变达官贵人，它交换不变的部署，所以xxx.cloudapp URL现在指向$ P $的VIP pviously分期（现在生产）的部署和RandomGuid.cloudapp现在指向previously生产（现分期）部署的VIP。交换只影响URL-> VIP映射，闲来无事，贵宾本身是preserved。

"Swap VIP" doesn't change VIPs, it swaps the deployments unchanged, so the xxx.cloudapp URL now points to the VIP of previously staging (and now production) deployment and RandomGuid.cloudapp now points to the VIP of previously production (now staging) deployment. The swap only affects the URL->VIP mapping, nothing else, VIPs themselves are preserved.

当你删除它的部署VIP是由天青回收。当你创建一个新的部署可能会重复使用previously回收VIP或获得一个新的 - 这是不确定的。直到你删除它的部署是VIP preserved。

When you delete a deployment its VIP is reclaimed by Azure. When you create a new deployment it may reuse that previously reclaimed VIP or get a new one - that's unspecified. Until you delete a deployment its VIP is preserved.

所以...

如果我删除分段插槽和重新部署，并执行VIP掉，然后将它产生新的VIP？

If I delete the Staging Slot and redeploy and perform VIP swap then will it generate new VIP?

一旦你删除分段部署其VIP是由天青回收。当你创建一个新的分期部署会重复使用VIP或换新的。与此同时，生产部署preserves的VIP。然后，你做交换 - 生产变得分期和分期成为生产，他们仍然preserve他们的贵宾

Once you delete the staging deployment its VIP is reclaimed by Azure. When you create a new staging deployment it will reuse that VIP or get a new one. Meanwhile the production deployment preserves its VIP. Then you do the swap - production becomes staging and staging becomes production and they still preserve their VIPs.

例如。你有生产与VIP 1.1.1.1和2.2.2.2 VIP分期。所以yourapp.cloudapp点1.1.1.1您删除并重新创建分期和它发生到现在已经有VIP 3.3.3.3（它也可以同样爬不起来2.2.2.2 - 你不能predict这一点）。生产仍具有1.1.1.1 - 有保证。你做掉 - 现在3.3.3.3贵宾变成生产和贵宾与1.1.1.1成为举办这样yourapp.cloudapp现在指向3.3.3.3他们交换时preserve他们的贵宾，只有URL-> VIP映射更改。

For example. You have production with VIP 1.1.1.1 and staging with VIP 2.2.2.2. So yourapp.cloudapp points to 1.1.1.1 You delete and recreate the staging and it happens to now have VIP 3.3.3.3 (it could just as well get 2.2.2.2 again - you can't predict that). The production still has 1.1.1.1 - that's guaranteed. You do the swap - now the VIP with 3.3.3.3 becomes production and VIP with 1.1.1.1 becomes staging so that yourapp.cloudapp now points to 3.3.3.3 They preserve their VIPs during the swap, only URL->VIP mapping changes.