VIP互换与持久性 - 当究竟贵宾得到回收？ [英] VIP Swaps and Persistence - when exactly do VIPs get recycled?
问题描述
<一个href=\"http://stackoverflow.com/questions/20863752/how-is-vip-swapping-cnames-better-than-ip-swapping-a-records/20863895?noredirect=1#comment31303553_20863895\">How是VIP交换+的CNAME不是IP交换+ A记录？
从上面的延续 - 我非常接近回复到A记录由于<一个href=\"http://stackoverflow.com/questions/20863012/site-url-not-working-with-windows-azure-cloud-service\">issues我在在Azure的CNAME记录。
As a continuation from the above - I'm very close to reverting back to A records due to issues I'm having with CNAMEs in Azure.
从href=\"http://www.windowsazure.com/en-us/develop/net/common-tasks/custom-dns/\" rel=\"nofollow\"> Azure的文档的
From the Azure docs, it's stated:
请注意，然而，因为IP地址的寿命相关联的
与部署中，如果不删除您的部署是非常重要的
你所需要的IP地址持续。便利地，一个IP地址
给定部署插槽（生产或分期），使用时应坚持
这两个升级机制，在Windows Azure中：VIP互换和就地
升级。
Note, however, because the lifetime of the IP address is associated with a deployment, it is important not to delete your deployment if you need the IP address to persist. Conveniently, the IP address of a given deployment slot (production or staging) is persisted when using the two upgrade mechanisms in Windows Azure: VIP swaps and in-place upgrades.
我 myapp.cloudapp.net ，当前指向的VIP 1.1.1.1 。如果我想部署一个版本，我的应用程序来临时，我会和我的应用程序旋转切入插槽起来，做一些测试，然后通过做掉VIP的无缝升级。该应用程序现在将使用 2.2.2.2 - 虽然，如果我在这一点上再做DNS查找，对于A记录 myapp.cloudapp.net 仍将指向 1.1.1.1 ，因为VIP互换对DNS没有影响，对不对？
I have myapp.cloudapp.net, currently pointing to a VIP of 1.1.1.1. If I want to deploy a version of my application to Staging, I'll spin the Staging slot up with my application, do some testing, and then do a seamless upgrade via VIP swap. The application will now be using 2.2.2.2 - though if I do a DNS lookup again at this point, the A record for myapp.cloudapp.net will still point to 1.1.1.1, since VIP swaps have no impact on DNS, right?
如果是这样，那么会发生什么，当我杀了我的分期部署，以节约成本？将两者 1.1.1.1 和 2.2.2.2 留给我的服务？我希望如此，因为这意味着我可以有我的A记录指向1.1.1.1所有的时间，通过分期部署依赖于它，而不必担心CNAME麻烦。但是，这意味着，<一href=\"http://stackoverflow.com/questions/20850585/staging-with-a-multi-tenant-app-in-azure-cloud-services\">this回答是不正确。
If so, then what happens when I kill my staging deployment to save cost? Will both 1.1.1.1 and 2.2.2.2 be reserved for my service? I hope so, because that means I can have my A record point to 1.1.1.1 all the time, depend on it through staging deployments, and not worry about CNAME hassles. But that means that this answer is incorrect.
如果不是，那么这意味着VIP互换的做的对DNS记录的影响，对不对？否则，我将能够做到这一点：
If not, then this means that VIP swaps do have effects on DNS records, right? Otherwise, I would be able to do this:
- 1.1.1.1> 2.2.2.2，降分期，1.1.1.1被回收
- 旋转起来再次上演，2.2.2.2> 3.3.3.3，但DNS A记录仍然指向1.1.1.1的myapp.cloudapp.net。
这最后一点也没有任何意义，所以无论是DNS记录的做的得到更新，或3.3.3.3从未进入图片和1.1.1.1 2.2.2.2和总是在一起，只要我的云服务不会被删除。
That last bit wouldn't make any sense, so either DNS records do get updated, or 3.3.3.3 never enters the picture, and 1.1.1.1 and 2.2.2.2 are always together, as long as my cloud service doesn't get deleted.
我很困惑这事 - 任何指导意见将是巨大的。
I'm very confused with this matter - any guidance would be great.
更新 - 我只是用下面的测试这样的：
UPDATE - I just tested this with the following:
CHECK DNS - get 1.1.1.1
READ PROD - get 1.1.1.1
DEPLOY STAGING
READ STAGING - get 2.2.2.2
VIP SWAP
READ PROD - get 1.1.1.1
READ STAGING - get 2.2.2.2
CHECK DNS - get 1.1.1.1
KILL STAGING DEPLOYMENT
READ PROD - get 1.1.1.1
所以看来 A记录可用于 - 即使分期/生产之间切换时，督促VIP保持不变，但在部署被换。删除升级和重新部署分期得到一个新的辅助VIP，但主要的VIP也保持不变。我会等待，直到有人比我更可靠的可张贴这作为一个答案之前，这里附和
So it appears that A records CAN be used - even when switching between staging / production, the PROD VIP stays the same, but the deployments get swapped. Dropping staging and re-deploying staging gets a new secondary VIP, but the primary VIP does stay constant. I'll wait until someone more reliable than me can chime in here before posting this as an answer.
推荐答案
VIP交换不会改变你的公网IP。这是说，如果你有你的应用程序部署在督促插槽，1.1.1.1和β部署在分期插槽，2.2.2.2，你的公网IP仍然是1.1.1.1 VIP交换后还是一样。这是因为，VIP只是一个负载均衡的配置变化。您可以安全地从分段插槽（原PROD插槽），其中的IP是2.2.2.2删除原来的应用程序。
VIP swap will not change your public IP. That's saying, if you have your application deployed in prod slot with 1.1.1.1 and beta deployed in staging slot with 2.2.2.2, your public IP will still be 1.1.1.1 even after VIP swapped. This is because VIP is just a load balance configuration changing. You can safely delete your original application from the staging slot (originally prod slot) which the IP was 2.2.2.2.
希望这有助于
这篇关于VIP互换与持久性 - 当究竟贵宾得到回收？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
