添加的Azure虚拟机到现有的可用性组 [英] Adding Azure Virtual machine to an existing availability set

问题描述

我想创建在天青两个虚拟机不应当彼此连接。我创建第一个虚拟机，并​​还创建了一个可用性设置其创作过程的一部分。

I want to create two virtual machines in Azure which should not be connected to each other. I created first virtual machine and also created an availability set as part of its creation process.

现在，当我创建第二个虚拟机的话，我没有得到在下拉可用性集列表第一虚拟机的一部分创建可用性集。

Now when I create the second virtual machine then I don't get the availability set created as part of first virtual machine in the drop down list of availability sets.

但是，如果我尝试到第二个虚拟机连接为第一个，然后我能看到的第一个虚拟机的一部分创建的可用性组的一部分。

However if I try to connect the second virtual machine as part of first one then I am able to see the availability set created as part of first virtual machine.

这是必须的虚拟机可以连接到对方，这样我可以将它们添加到相同的可用性组？这是一个只能从蔚蓝的门户限制，有解决方法使用PowerShell的？

Is it mandatory for virtual machines to be connected to each other so that I can add them to the same availability set? Is this a limitation only from azure portal and there is a workaround using powershell?

更新：

如果我们连接两个虚拟机，那么我们就可以得到一套可用的好处。然而，在同一时间两个虚拟机成为同云服务的一部分，因此被载湛蓝不支持粘性会话平衡。

If we connect two virtual machines then we can get the benefit of availability set. However, at the same time both virtual machine becomes part of same cloud service and hence are load balanced by azure which does not support sticky session.

我之情况是，我有相同的前端，需要支持粘性会话。因此，我不想将它们连接到对方。不过，我想作为的该套的。

My scenerio is that I have identical front-ends which needs to support sticky session. Therefore I don't want to connect them to each other. However, I want to get the benefits of availability sets as mentioned in the article on Availability sets.

所以我可以设置可用性不相互连接两个相同的虚拟机设置？

So can I set availability set for two identical virtual machines not connected to each other?

推荐答案

术语可用性设置意味着你要一个服务组内带来的一个或多个虚拟机宕机的事件过程中最大限度的可用性。所以你看在Azure门户是什么正确的行为，但是你可能有一些误解，对于可用性设置。你可以阅读更多的可用性集这里。

The term "Availability Set" means that you want to bring one or more VM within one service group for maximize the availability during an event of downtime. So what you see on Azure Portal is correct behavior however you might have some misunderstanding with regard to Availability Set. You can read more on "Availability Set" here.

所以，当你尝试第二个虚拟机连接为第一部分，你看到的可用性组，因为这样一来，你希望你的虚拟机从第一次使用的设置并添加其他VM能够在同一组，以最大限度地提高可用性。该第二虚拟机成为第一个的一部分。

So when you try to connect second virtual machine as part of first, you do see the availability set, because this way you want your VM to use the settings from the first and add another VM to the same group to maximize the availability. This second VM becomes the part of first one.

当您创建一个独立的虚拟机（调用是第二次或第三次或任何），你实际上是创建一个全新的虚拟机这是怎么回事，为什么你没有看到独立运行的任何其他虚拟机，你可能会或可能不会有和多数民众的可用性SET相反，你可以创建一个新的基于这一新的虚拟机可用性集。

When you create an independent VM (call is second or 3rd or any) you are actually creating a brand new VM which is going to run independent to any other VM you may or may not have and thats why you dont see "availability set" instead you can create a new "availability set" based on this new VM.

这篇关于添加的Azure虚拟机到现有的可用性组的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！