问题描述
在 Azure 中有 2 个选项可用于创建虚拟机.A. 普通虚拟机B. 经典虚拟机
In Azure there are 2 options available to create virtual machines.A. normal VMB. Classic VM
有人知道这两个选项有什么区别吗?我们什么时候使用一个?
Does anybody know what is the difference between both option? When do we use one over other?
推荐答案
对您问题的简短回答是 Normal VM or Virtual Machines 是部署虚拟机的新方法，而 Classic VM或虚拟机(经典) 是部署它们的旧方法.Azure 正在推动部署资源的新方式，因此建议使用它而不是旧方式.但是请记住，有一些旧方式可用的功能尚未移植到新方式中，因此您只需比较所提供的功能，并且仅当您需要的某些功能无法以新方式提供时，你用老方法.
Short answer to your question is Normal VM or Virtual Machines is the new way of deploying your Virtual Machines whereas Classic VM or Virtual Machines (Classic) is the old way of deploying them. Azure is pushing towards the new way of deploying resources so the recommendation would be to use it instead of old way. However please keep in mind that there're some features which are available in the old way that have not been ported on to the new way so you just have to compare the features offered and only if something that you need is not available in new way, you use the old way.
现在是长答案:)
本质上有一个 REST API，您可以使用它与 Azure 基础设施进行交互.
Essentially there's a REST API using which you interact with Azure Infrastructure.
当 Azure 开始时，这个 API 被称为服务管理 API (SMAPI)，它在当时(以及在某种程度上在今天)非常适合它的目的.然而，随着 Azure 的发展，用户的需求也在增长，这就是 SMAPI 受到限制的地方.一个很好的例子是访问控制.在 SMAPI 中，有访问控制，但它更像是 all-or-none 类型的访问控制.它缺乏用户要求的粒度.
When Azure started out, this API was called Service Management API (SMAPI) which served its purpose quite well at that time (and to some extent today). However as Azure grew, so does the requirements of users and that's where SMAPI was found limiting. A good example is access control. In SMAPI, there was access control but it was more like all-or-none kind of access control. It lacked the granularity asked by users.
Azure 团队没有修补 SMAPI 以满足用户的要求，而是决定重写整个 API，它更简单、更健壮且功能更丰富.此 API 称为 Azure Resource Manager API (ARM).ARM 有许多 SMAPI 没有的功能(我个人最喜欢的是基于角色的访问控制 - RBAC).
Instead of patching SMAPI to meet user's requirement, Azure team decided to rewrite the entire API which was much simpler, more robust and feature rich. This API is called Azure Resource Manager API (ARM). ARM has many features that are not there in SMAPI (my personal favorite is Role-based access control - RBAC).
如果您注意到今天有两个 Azure 门户 - https://manage.windowsazure.com(旧)和 https://portal.azure.com(新).旧门户支持 SMAPI，而新门户支持 ARM.为了将通过旧门户创建的资源显示到新门户中(以便您可以获得统一的体验)，Azure 团队最终为旧内容创建了一个资源提供程序，它们的名称始终以 (Classic) 所以你会看到 Virtual Machines (Classic)、Storage Accounts (Classic) 等等.所以你在旧门户中创建的资源可以在新门户中看到(前提是新门户支持它们)但您使用 ARM 在新门户中创建的任何资源都不会显示在旧门户中.
If you have noticed that there are two Azure portals today - https://manage.windowsazure.com (old) and https://portal.azure.com (new). Old portal supports SMAPI whereas new portal supports ARM. In order to surface resources created via old portal into new portal (so that you can have a unified experience), Azure team ended up creating a resource provider for old stuff and their names will always end with (Classic) so you will see Virtual Machines (Classic), Storage Accounts (Classic) etc. So the resources you create in old portal can be seen in the new portal (provided the new portal supports them) but any resources you create in the new portal using ARM are not shown in the old portal.
这篇关于azure 中的虚拟机经典版和虚拟机有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！