简体繁体 English

使用Microsoft Azure进行连续部署

[英]Continuous deployment with Microsoft Azure

原文 2016-04-21 19:03:15 5 1 windows/ azure/ continuous-integration/ release-management/ continuous-deployment

If a worker role or for that matter web roles are continuously serving both long/short running requests. 如果一个工作角色或与此相关的Web角色正在持续服务长期/短期运行请求。 How does continuous delivery work in this case? 在这种情况下，连续交付如何工作？ Obviously pushing a new release in the cloud will abort current active sessions on the servers. 显然，在云中推送新版本将中止服务器上当前的活动会话。 What should be the strategy to handle this situation? 处理这种情况应采取什么策略？

1 个解决方案

Cloud Services have production and staging slots, so you can change it whenever you want. 云服务具有生产和登台插槽，因此您可以随时更改它。 Continuous D or I can be implemented by using Visual Studio Team Services, and i would recommend it - we use that. 连续D或I可以通过使用Visual Studio Team Services来实现，我会推荐-我们使用它。 As you say, it demands to decide when you should switch production and staging slots (for example, we did that when the user load was very low, in our case it was a night, but it can be different in your case). 正如您所说，它需要决定何时切换生产和登台插槽（例如，我们在用户负载非常低的情况下（在我们的情况下是一个夜晚，但是在您的情况下可能会有所不同）这样做。 Slots swapping is very fast process and it is (as far as i know) the process of changing settings behind load balancers not physical deployment. 插槽交换是一个非常快速的过程，据我所知，它是更改负载均衡器后面的设置而不是物理部署的过程。

https://azure.microsoft.com/en-us/documentation/articles/cloud-services-continuous-delivery-use-vso/#step6 https://azure.microsoft.com/zh-CN/documentation/articles/cloud-services-continuous-delivery-use-vso/#step6

UPD - i remember testing that, and my experience was that incoming connections were stable (for example, RDP) and outgoing are not. UPD-我记得测试过，我的经验是传入连接稳定（例如RDP），传出不稳定。 So, i can not guarantee that existing connections will be ended gracefully, but from my experience there were no issues. 因此，我不能保证现有的连接会正常结束，但是从我的经验来看，没有任何问题。