在Azure中的Linux VM，坚持什么？什么盘收费？ [英] In an Azure Linux VM, what persists? what disk is charged for?

问题描述

我微软的Azure创建了一个小型的Linux虚拟机。我还创建了一个20GB的BLOB和安装它作为一个文件系统。

I created a Small Linux VM in Microsoft's Azure. I also created a 20GB BLOB and mounted it as a filesystem.

在我的虚拟机，我看到以下内容：

On my VM, I see the following:

• 根文件系统：约28GB


• boot文件系统：约500MB


• 我的20GB的文件系统


• 的/ mnt /资源 - 69GB

所以，我有问题：

（1）如果我关掉虚拟机，然后再次打开电源后，它那些文件系统/卷将在他们当VM被断电的状态持续？这已经为每个卷（我测试），但它在测试工作是不一样的保障。的情况下

(1) If I power down the VM and then power it back on later, which of those filesystems/volumes will persist in the state they were in when the VM was powered down? This has been the case for each volume (I tested) but "it worked in a test" is not the same as a guarantee.

（2）如果VM需要移动，因为在Azure的环境（自愈移民），其中那些文件系统将坚持某种硬件故障或失效的？我怀疑根本不会，但不是到/ mnt /资源？

(2) If the VM needs to move because there is some kind of hardware fault or failure in the Azure environment ("self-healing migration"), which of those filesystems will persist? I suspect root will, but not /mnt/resource?

（3）在Azure管理门户，我有我的时候创建的虚拟机时创建一个30GB的硬盘。是仙每小时VM负责该磁盘部件的成本，或者是一个单独的收费？我认为这是独立的。

(3) In the azure management portal, I have a 30GB disk that was created when I created the VM. Is the cost of that disk part of the cents-per-hour VM charge, or is that a separate charge? I think it's separate.

（4）据说一个小VM配备165GB为在VM角色的本地存储资源的磁盘空间：<一href=\"http://msdn.microsoft.com/en-us/library/windowsazure/ee814754.aspx\">http://msdn.microsoft.com/en-us/library/windowsazure/ee814754.aspx我看到69GB - ？在哪儿去休息

(4) Supposedly a Small VM comes with 165GB for "Disk Space for Local Storage Resources in a VM Role": http://msdn.microsoft.com/en-us/library/windowsazure/ee814754.aspx I see 69GB - where'd the rest go?

您以为我可以问微软这些问题，但是当我这样做，他们说Linux VM的是preVIEW及其支持拒绝回答任何Linux虚拟机的问题，除了指向，而鬼towny Azure的论坛。

You'd think I could ask Microsoft these questions, but when I did they said Linux VMs are in "preview" and their support refuses to answer any Linux VM questions, except to point to the rather ghost-towny Azure forums.

推荐答案

我不使用Linux尚未IaaS的情况下工作，但我想我可以回答这些基于我的基础设施一般是如何工作的理解

I've not worked with the IaaS instances using Linux yet, but I think I can answer some of these based on my understanding of how the infrastructure works in general.

当你创建一个虚拟机，你有操作系统磁盘（它映射到你的根上面，我相信引导的，虽然我认为这是一个基于Linux的神器，不存在在使用Windows时）。该操作系统磁盘存储在Windows Azure的BLOB存储作为一个VHD，页BLOB。与20 GB数据磁盘相同的创建。这些都是将持续可靠的驱动器和只有这些驱动器。

When you create a VM you have the OS Disk (which maps to your root above, and I believe the boot as well though I think that is a Linux based artifact and isn't there when using Windows). This OS Disk is stored in Windows Azure BLOB storage as a VHD, Page BLOB. The same with the 20 GB Data Disk you created. These are the drives that will reliably persist and ONLY these drives.

1）在你关闭电源的测试，你有没有实际删除部署或简单的关闭它？关闭VM会离开它部署（从而在同一物理机上）。刚刚被关闭不会阻止你，因为它实际上仍部署正在充电。如果删除部署，然后创建一个新的部署后指出，创建相同的操作系统和数据磁盘（你会在你的库中找到他们），你会得到的会发生什么更好的主意，如果虚拟机得到了由于移动以自我修复，因为它会被提出来很可能在不同的物理服务器上。见下面为什么我认为资源带动周边卡住。

1) In your test of powering down, did you actually delete the deployment or simply "turn it off"? Turning off the VM will leave it deployed (and thus on the same physical machine). Just being turned off doesn't keep you from being charged as it is actually still deployed. If you delete the deployment, and then create a new deployment later pointed to the same OS and data disk you created (you'll find them in your gallery) you'll get a better idea of what will happen if the VM got moved due to self healing as it will be brought up very likely on a different physical server. See below why I think the "resource" drive stuck around.

2）你是正确的，我相信资源驱动器类似于我们在Windows方作为D见：/驱动器。这是暂时的，暂存空间。该驱动器本身也是一个VHD，而不是位于BLOB存储，但实际上在物理服务器上虚拟机上运行。对于Windows这是其中存储器页文件被保持，以保持对尽可能低页文件访问的等待时间。他们担心的是，这是一个非持久化的驱动器非常坚决。在你的情况，如果你做了所有被关闭的实例，这可能还呆在附近。当实例通电后它仍然是同一物理服务器上，因此在同一个本地的资源被分配给它，这样的数据，你已经把仍然会存在那里。如果实例被重新部署的数据不会存在了。

2) You are correct, I believe the resource drive is similar to what we see on the Windows side as the D:/ drive. This is temporary, scratch space. The drive itself is also a VHD and is located NOT in BLOB storage, but actually on the physical server the VM is running on. For Windows this is where the memory page file is kept in order to keep the latency for page file access as low as possible. They are very adamant about the fact that this is a NON persisted drive. In your case this may have stuck around if all you did was turn off the instance. When the instance powered back on it was still on the same physical server, therefore the same local resource was allocated to it, thus data you had put there would still be there. If the instance was redeployed the data would not be there anymore.

3）您所看到的磁盘（操作系统磁盘以及数据磁盘）都存储在BLOB存储作为页BLOBS。这些磁盘的存储成本是从每小时收费标准不同的实际运行虚拟机。您还负责存储数据访问这些磁盘上的数据，因为他们都在运行。从定价页面检查这句话：

3) The Disks you see (the OS Disk as well as the Data Disk) are both stored in BLOB storage as Page BLOBS. The storage costs of these disks are separate from the per hour charge to actually be running the VM. You are also charged storage transactions to access the data on these disks as they are running. From the pricing page check this quote:

计算小时的收费是每当部署虚拟机，而不论其是否在运行与否。计算时不包括与Windows Azure中虚拟机上运行的图像相关的任何Windows Azure存储成本。这些费用分开收取。

Compute hours are charged whenever the Virtual Machine is deployed, irrespective of whether it is running or not. Compute hours do not include any Windows Azure Storage costs associated with the image running in Windows Azure Virtual Machines. These costs are billed separately.

4）我相信你所看到的资源驱动器是D：/驱动器相当于和不是说你已经指出了当地的资源空间。你所指出，大约在云服务（或pviously称为托管服务$ P $）上运行时，因此，使用一个Web或辅助角色越来越本地空间的访问专门说话。我不知道在使用虚拟机时，适用于相同的方式。除了页面文件在使用Windows，我相信这个资源空间也用于一点，当你的数据或操作系统磁盘，这将减少你也一样的空间量设置数据缓存。这是我的一部分，虽然投机行为。

4) I believe the resource drive you are seeing is that D:/ drive equivalent and NOT the local resource space that you have pointed to. What you have pointed to is talking specifically about getting access to local space when running in a Cloud Service (or previously known as a Hosted service), so using a Web or Worker role. I'm not sure that applies in the same way when using Virtual Machines. In addition to the page file when using Windows I believe this resource space is also used a little when you setting up data caching for the data or OS disks, which would reduce the amount of space you'd have as well. This is speculation on my part though.

您可能还需要了解缓存选项和限制使用的操作系统和数据驱动器。迈克尔Washam上倒是在博客文章。

You may also want to understand the caching options and restrictions with OS and data drives. Michael Washam touches on it in a blog post.

这篇关于在Azure中的Linux VM，坚持什么？什么盘收费？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！