思杰服务器虚拟化Xenserver解决案例设计介绍.pptVIP

* XenMotion allows running Guest VM’s to be migrated without service downtime Zero down-time during planned maintenance Load Balance VMs over different servers XenServer supports several features to guarantee service uptime in the event of infrastructure failure. Firstly, resource pools can be configured for automated high-availability. This deals with individual host failures by restarting VMs that were running on that host onto the next available machine in the resource pool. Notable features include: Peer-to-peer self-healing architecture ensures there is no single point of management failure. Set VM restart priorities individually, to control the order in which services are restarted in the event of host failure. Dynamic failure planning algorithms allow administrators to see how many hosts failures can be tolerated without compromising services. Presentation Title Goes Here Insert Version Number Here ? 2007 Citrix Systems, Inc.—All rights reserved. * The inability to combine disparate host hardware into a resource pool makes it difficult for customers to expand their deployments over time. Anything that requires creation of an additional pool creates increased management costs for pool-based configuration settings, SRs, and templates, and limits migration agility. XenServer 5.5 requires host CPU models within a pool to be identical in order to ensure successful live migrations. However, major system vendors, HP, Dell, and IBM included, add and discontinue CPU offerings within the lifecycle of a server model, making it difficult to purchase truly identical servers over time. Both Intel (FlexMigration) and AMD (Extended Migration) offer technologies in their recent CPUs that provide CPU masking or leveling. These features allow a CPU to be configured to appear as providing a different make, model, or functionality than it actually does, enabling pools of hosts with disparate CPUs to safely support live migrations. HCL will be extended to include CPU combina