1. ESXi_Transition-Introduction_RevB.pptx

  1. 1、本文档共25页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
1. ESXi_Transition-Introduction_RevB

ESXi TransitionESXi TransitionSupport Readiness TrainingJohn Browne11th October 2010Rev A.You Are Here ESXi Transition - Support Readiness TrainingIntroduction AgendaModule 1 - IntroductionOverview OverviewCurrently VMware vSphere? supports two “flavors” of hypervisor – VMware? ESX? and ESXi, but starting with the next major release of vSphere ,VMware will focus solely on ESXi architecture.One of VMware’s major initiatives starting with vSphere 4.1, and continuing through the next major release of vSphere launch, is to migrate the vSphere install base from the ESX to the ESXi hypervisor architecture. Transitioning to ESXi is easy but customers with small or large ESX environments will require advance planning to migrate and they need to start preparing today.VMware is standardizing on the ESXi hypervisor architectureVMware vSphere 4.1 and its subsequent update and patch releases are the last releases to include both ESX and ESXi hypervisor architectures. Future major releases of VMware vSphere will include only the VMware ESXi architecture.VMware recommends that customers start transitioning to the ESXi architecture when deploying VMware vSphere 4.1.VMware will continue to provide technical support for VMware ESX according to the VMware vSphere support policy.Why ESXi?Next generation of VMware’s Hypervisor ArchitectureFull-featured hypervisor Superior consolidation and scalabilitySame performance as VMware ESX architectureMore secure and reliableSmall code base thanks to OS-Independent, thin architectureStreamlined deployment and configurationFewer configuration items making it easier to maintain consistencyAutomation of routine tasks through scripting environments such as vCLI or PowerCLISimplified hypervisor Patching and UpdatingSmaller code base = fewer patches Eliminates patch drifting due to single image updateThe “dual-image” approach lets you revert to prior image if desiredVMware components and third party components can be updated independentlyVMw

文档评论(0)

l215322 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档