在21章,我们介绍了VMM(2012SP1)管理XenServer的特性,今天来介绍一下VMM管理VMware产品的支持特性。其实和XenServer一样,管理VMware同样无法做到百分百的全功能实现,但至少为我们提供了一种可能,一个统一的界面,管理异构的产品,从而抽象硬件层,实现"云"的应用。这其实是很美好的一种应用方向,使用PowerShell,可以管理其他厂商的产品,这样对于系统工程师而言,只需要学习PowerShell,基本就是万能的了。
====================我是分隔线=================
关于如何在VMM中添加VMware的产品,在本系列的前几篇文章中已经有介绍了,本文的目的仅仅是展示一下,我们可以实现哪些功能,对产品做一个全面的了解。
【惯例还是在文末有一个简单的翻译】
Supported Features
The following tables shows the VMM and VMware features that are supported when VMM manages ESX hosts through vCenter Server.
Feature |
Notes |
||||
VMM command shell |
The VMM command shell is common across all hypervisors. |
||||
Placement |
VMM offers virtual machine placement based on host ratings during the creation, deployment, and migration of VMware virtual machines. This includes concurrent virtual machine deployment during service deployment. |
||||
Services |
You can deploy VMM services to ESX hosts.
|
||||
Private clouds |
You can make ESX host resources available to a private cloud by creating private clouds from host groups where ESX hosts reside, or by creating a private cloud from a VMware resource pool. You can configure quotas for the private cloud and for self-service user roles that apply to the private cloud.
|
||||
Dynamic Optimization and Power Optimization |
You can use the new Dynamic Optimization features with ESX hosts. For example, VMM can load balance virtual machines on ESX host clusters by using Live Migration. Through Power Optimization, you can configure VMM to turn ESX hosts on and off for power management.
|
||||
Migration |
Supported VMware transfer types include the following:
Supported VMM transfer types include the following:
|
||||
Maintenance mode |
You can place an ESX host that is managed by VMM in and out of maintenance mode by using the VMM console. |
||||
Library |
You can organize and store VMware virtual machines, .vmdk (VMDK) files, and VMware templates in the VMM library. VMM supports creating new virtual machines from templates and converting stored VMware virtual machines to Hyper-V.
|
||||
Templates |
Supports the creation of templates using .vmdk files that are stored in the library. In this case, all physical files are stored in the VMM library. You can also import templates that are stored on ESX hosts. When you import a template from vCenter Server, VMM only imports template metadata. The .vmdk file is not copied to the VMM library. |
||||
Networking |
VMM supports both standard and distributed vSwitches and port groups. Be aware that you must perform all vSwitch and port group configuration by using vCenter Server. VMM recognizes and uses existing configured vSwitches and port groups for virtual machine deployment. The new VMM networking management features are supported on ESX hosts, such as the assignment of logical networks, and the assignment of static IP addresses and MAC addresses to Windows-based virtual machines that are running on ESX hosts.
|
||||
Storage |
VMM supports and recognizes VMware Paravirtual SCSI (PVSCSI) storage adapters. For example, when you use VMM to create a new virtual machine on an ESX host, you can add a SCSI adapter of type "VMware Paravirtual."
VMM supports VMware thin provision virtual hard disks through the dynamic disk type. Note the following behavior:
VMM supports the hot add and hot removal of virtual hard disks on VMware virtual machines.
|
||||
Conversion |
Converting a VMware-based virtual machine to a Hyper-V based virtual machine is supported by using the virtual to virtual (V2V) process.
|
||||
Performance and Resource Optimization (PRO) |
Monitoring and alerting for ESX hosts is possible through VMM with the integration of Operations Manager and PRO. |
Additional Support Information
-
VMM supports up to 255 GB of RAM for virtual machines that are deployed on ESX/ESXi 4.0 hosts.
-
VMM supports up to 8 virtual CPUs (vCPUs) for virtual machines that are deployed on ESX/ESXi 4.0 hosts.
-
VMM recognizes VMware fault tolerant virtual machines. In the VMM console, VMM shows only the virtual machine that is designated as the primary on the vCenter Server. If there is a failure, VMM recognizes the new primary.
-
Update management through VMM is not supported for ESX hosts. You must use your existing solution to update VMware ESX hosts.
-
The conversion of a bare-metal computer to a virtual machine host, and cluster creation through VMM is not supported for ESX hosts.
-
The Dynamic Memory feature is not supported on ESX hosts. Dynamic Memory is only supported on Hyper-V hosts that are running an operating system that supports Dynamic Memory.
相比VMM2008R2提升的特性:
-
管理VMware的ESX通过vCenter来实习,这次再也不用同步和合并VMware的树结构,因为少了这些同步过程,所以出错的机会也就少了很多。
-
VMware的模板不再是先导入到VMM的库中,用户再倒回VMware使用,而是只创建这种与模板关联的"关系",VMware的模板.vmdk文件依然保存在ESX的存储中,因为这种跨平台的不复制,导致我们可以更快速的部署。同时导入模板的时候,也和Windows下的导入不太一样,它不会删除原模板,仅仅是创建这个关系(如果看了我的这个系列的前几章,应该会明白这是什么意思)。
-
如果这个时候,你在vCenter中删除了模板,那么在VMM中的模板会显示丢失。(当然这不是个问题,因为即使是你用VMM管理HyperV,那么跳过VMM,你使用HyperV管理器删除虚拟机、模板,都会导致在VMM中的信息不同步,而显示"丢失",这本身就是一个不建议的操作)
-
VMM和ESX的通信采用HTTPS
-
VMM支持VMware的分布式虚拟交换机
-
创建网络端口的操作,需要在vCenter上提前创建好,VMM实现不了。
支持的特性:
-
支持VMM的Shell(XenServer也是如此)
-
对于VMware的私有云vCloud,VMM表示鸭梨很大,不整合。
-
支持虚拟机的创建、部署和迁移
-
支持模板
-
支持PRO,动态迁移和优化
-
支持集群内迁移和实时存储迁移(vxxx的功能)
-
可以使用VMM的维护模式,去对vCenter进行一些维护
-
刚才提到的"库"的一些支持特性的修改
-
支持VMware的网络
-
支持VMware的存储管理、支持创建动态扩展磁盘,在VMware貌似叫做精简置备磁盘
-
支持V2V,也就是VMware的虚拟机转化为HyperV的虚拟机,但是需要注意的是,VMware的虚拟机不能是挂载在IDE总线上的
-
不支持动态内存、不支持裸机部署ESX,不支持WSUS去更新ESX
===================我是分隔线=============================
看起来功能差不多也都能实现,当然,如果是为了部署微软私有云,现在这些管理特性已经足够使用了。
原创文章,转载请注明: 转载自奶油九叔