什么是虚拟机的经典和虚拟机在蔚蓝的区别？ [英] what is the difference between virtual machine classic and virtual machine in azure?

问题描述

在Azure中有可用于创建虚拟机的2个选项。
A.正常VM
B.经典VM

In Azure there are 2 options available to create virtual machines. A. normal VM B. Classic VM

有谁知道什么是选择两者之间的区别？我们什么时候使用一个比其他？

Does anybody know what is the difference between both option? When do we use one over other?

推荐答案

简短回答你的问题是普通虚拟机或者虚拟机是部署虚拟机的新途径而经典虚拟机或者虚拟机（经典）是部署它们的老路。 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.

现在来长的答案：）

从本质上有使用，你用Azure基础设施开发交互的REST API。

Essentially there's a REST API using which you interact with Azure Infrastructure.

在Azure中开始了，这个API被称为服务管理API（SMAPI）其中担任（在一定程度上的今天），其目的相当不错在那个时候。然而，随着Azure的增长，确实让用户的需求，这也正是SMAPI发现限制。一个很好的例子是访问控制。在SMAPI，有访问控制，但它更像是全或无类型的访问控制。它缺乏用户要求的粒度。

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.

而不是修修补补SMAPI，以满足用户的需求的，Azure团队决定重写整个API这是更简单，更强大，功能丰富。这个API被称为 Azure的资源管理器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团队结束了创建旧的东西资源提供者，他们的名字将永远与结束（经典） 所以你会看到虚拟机（经典），存储帐户（经典）等。所以，你在老门户网站创建资源可以在新的门户网站中可以看出（提供的新门户网站支持它们），但你在新的门户网站采用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.

这篇关于什么是虚拟机的经典和虚拟机在蔚蓝的区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！