去小机化专题研讨.pptx

1、凤凰传媒去小机化专题研讨,2014.3.28,提纲,建设目标和原则 去小机化的背景 U2VL的技术可行性研究 性能分析 可靠性分析 投入产出比 U2VL架构对比 U2VL的最佳实践 U2VL案例,规划愿景和原则,愿景： 去小机化是由于维保期已到，后续面临昂贵的小机采购费用以及续保费用，在当前X86服务器性价比如此明显的形势下，大部分应用已经可以由高性能X86服务器结合虚拟化技术承担，因此尝试去小机化是一个可行之路。 原则： 1、系统稳定性 2、技术先进性 3、规划全面性 4、成本节约性 5、管理便捷性,4,全球发展趋势：小机营收逐年逐季度降低,某厂商小型机营收变化走势图,U2VL的客观动因:

2、技术进步，市场趋势，客户需求，政策驱动,U2VL的 驱动力,技术,市场,X86架构和Linux,虚拟化和云计算,客户对控制 TCO的要求,政策,促进客户应用迁移到新平台的要素,X86架构日益成熟，RAS和性能不断提高接近甚至超过传统的RISC架构，能耗降低；反之RISC的发展陷入瓶颈 Linux 系统日益成熟，已经能够胜任BCA需求,虚拟化使得客户对硬件有了选择的自由，应用不再被绑定某个特定平台。 资源池化，抽象化，自动化都使得IT部署和交付模式发生了巨大改变 云计算的发展使得业务敏捷性的要求得到支持，极大地促进了业务创新,减少CAPEX，减少硬件和软件license费用降低TCO；OPEX降

3、低（MA，耗电和碳排放） 内建机制使高可靠性，容灾和扩展性方面的花费降低，更加灵活方便 降低人工和运营费用,国家云计算产业政策 大企业集团采购对Unix服务器的规定 上市公司的合规性要求,如何理解Unix To Virtualization Linux （U2VL）,U2VL就是服务器虚拟化 服务器虚拟化是基础，可能会对客户的IT架构，流程甚至组织结构都会产生影响 U2VL就是关键业务虚拟化（BCA） BCA和nonBCA都是U2L的机会和目标 U2VL很大程度上就是DB迁移 Application server的数量远远超过DB数量，不能轻易放过。 U2VL是一个solution 首先是一个

4、solution，其次还有更多 U2VL是一个project 以一个project的方式来看待，会更加全面的理解U2L要做的事情，才能将U2VL实施 Emphasis service led: Access/Design/Implement/Management/PMO,用什么替代了原来的小机呢： X86+VL,7,U2VL，为什么VMware是核心？,没有V的U2VL就像化学试验没有催化剂，是起不了化学反应的。,有了V的U2VL让IT完全不同，发生了质变。,U2VL的技术成熟度,X86+虚拟化+Linux可靠性超过小机+UNIX X86芯片的RAS特性媲美小机芯片 X86服务器设计越来越多的

5、引入小机的理念 虚拟化软件提供了更高的业务连续性保证 本地可用性（vMotion,Storage vMotion,HA, FT） 远程灾备（SRM）,U2VL技术成熟度-可用性保证（RAS）,Xeon E7相比以前的产品具有更强的RAS特性,X86架构与UNIX服务器的RAS特性对比,RAS特性以前是小型机与x86服务器之间的最主要的分水岭 但情况已经发生变化：,XX保險公司 Oracle OLTP 線上交易 虛擬化最終測試結果,結論：x86 Xeon-7650 比 Power6 CPU處理能力高33.7%,X86-E7-ESX 性能 优于 Power6 25% X86-E7-ESX 性能与

6、Power7 相当,银行基金WAS+DB2应用性能测试比较x86 与 Power6,（1）更好的性能 - 改变x86-Power性能认识与关键应用真正的虚拟化,每个核的性能 Power7 与 x86相当 每Ghz的性能 x86 与 Power7相当 X86 ESX5.0虚拟化平台 与实体 x86 相差 6%,SAP-2tier 比较x86 Intel Xeon系列与 Power7,（1）更好的性能 - 改变x86-Power性能认识与关键应用真正的虚拟化,R A S,Reliability - 可靠性,Availability - 可用性,Serviceability- 可服务性,不用太在意系

7、统厂商提供的可靠性数据， 可用性才是关键,（2） 更高的可用性 - 选用可靠的高可用的软件,x86虚拟化平台提供最好的可用性,AIX,数据库,PowerVM Hypervisor,RedHat, Windows, Novell,Solaris, Debian,vSphere ESXi,HACMP PowerHA,HA,应用,数据库,应用,IVT=Intel Virtualization Technology AMD-V =AMD Virtualization,PowerHA ： 不可用的高可用解决方案,Firmware,（2） 更高的可用性 - 选用可靠的高可用的软件,x86虚拟化平台提供最好

8、的可用性,RedHat 等等,ESX,HA,数据库,应用,AIX,数据库,PowerVM Hypervisor,HA-CMP Pwr HA,应用,RedHat 等等,ESX,HA,数据库,应用,解决所有问题,解决关键问题,（2） 更高的可用性 - 选用可靠的高可用的软件,x86虚拟化平台提供最好的可用性,Step 1. Install the PowerHA softwareYou can purchase this software from IBM directly (see Resources for a link); the file sets all start with the w

9、ord cluster. Use the installp command to install the software, much like any other licensed program package (LPP).Step 2. Edit some flat filesPut all of the IP addresses associated with the clusterboot, persistent, and serviceinto each /etc/hosts file on each node of the cluster. Do the same with th

10、e /usr/es/sbin/cluster/etc/rhosts file. Verify that the server hostnames match the appropriate IP addresses; the servers hostname should also match with the persistent IP address.Step 3. Configure the boot IP addressesRun the smitty chinet command, and set the boot IP addresses for each network adap

11、ter. Make sure that you are able to ping and connect freely from node to node on all respective networks. Also, double-check to make sure that the default route is properly configured. If it isnt, run smitty tcpip, go into the Minimum Configuration menu, enter the default route for the primary adapt

12、er, and press Enter.Step 4. Make application start and stop scriptsCreate two simple Korn shell scriptsone that starts an application and one that stops an application. Keep these scripts in identical directories on both nodes.Step 5. Define the clusterRun the command:smitty cm_config_an_hacmp_clust

13、er_menu_dmnThen, define the cluster, including naming it appropriately.Step 6. Define the nodesRun the command:smitty cm_config_hacmp_nodes_menu_dmnDefine every node within the cluster on both nodes.Step 7. Define the networksRun the command:smitty cm_config_hacmp_networks_menu_dmnThis defines one n

14、etwork per Ethernet adapter. I prefer to use the Pre-defined option as opposed to the Discovered path, but that is up to your discretion. Check the subnet masks for consistency.Step 8. Define the boot IP addressesRun the command:smitty cm_config_hacmp_communication_interfaces_devices_menu_dmnThis de

15、fines the boot IP addresses on the respective network adapters. This address should be the same IP addresses you used in step 3. Make sure you define these addresses within the proper respective PowerHA-defined network.Step 9. Define the persistent IP addressesRun the command:smitty cm_config_hacmp_

16、persistent_node_ip_label_addresses_menu_dmnThis defines the persistent IP addresses, again paying attention to pick the proper respective PowerHA-defined network.Step 10. Define the service IP addressesRun the command:smitty cm_config_hacmp_service_ip_labels_addresses_menu_dmnThis defines the servic

17、e IP addresses. Step 11. Perform a discovery and rebootBy this point, the nodes should have the ability to communicate with each other and keep the information stored in the nodes Object Data Managers (ODMs) in sync. Make the nodes within the cluster communicate with each other by running the comman

18、d:smitty cm_extended_config_menu_dmnSelect the Discover PowerHA-related Information from Configured Nodes option, and check for errors to fix. Generally, rebooting each node can clear up any minor problems, and this is a good point to test restarting each server anyway.Step 12. Define the resource g

19、roupRun the command:smitty cm_hacmp_extended_resource_group_config_menu_dmnDefine the resource group. Then, perform these steps:Select all participating nodes in the cluster.Set the Startup Policy to Online On First Available Node.Set the Fallback Policy to Never Fallback. This setting prevents the

20、resources from going back to the original server when it is brought up, which is a wise thing to do. Step 13. Create a shared volume groupNote: Run this command only on one node.Run the smitty cl_vg command, and create a shared volume group. When you create a shared volume group, you only need to se

21、lect one of the nodes, because the disk is shared.Step 14. Create a heartbeat diskFirst, run the smitty cl_convg command, and then select Create a Concurrent Volume Group with Data Path Devices. Choose one node and the target disk. Next, run the command:smitty cm_config_hacmp_communication_interface

22、s_devices_menu_dmnRepeat step 7, except this time, select the Discovered option and the target disk.Step 15. Define an application serverRun the command:smitty cm_cfg_app_extendedThis defines an application server for an application that PowerHA will manage. Use the scripts you created in step 4.Ste

23、p 16. Configure the resource groupNote: Run this command on only one node.Run the command:smitty cm_hacmp_extended_resource_group_config_menu_dmnSelect the Change/Show Resources and Attributes for a Resource Group option. Then, perform these steps:Select the appropriate service IP addresses.Select t

24、he appropriate shared volume groups and heartbeat disk.Select the appropriate application servers. Step 17. Perform a synchronizationSynchronize the cluster configuration. Run the command:smitty cm_ver_and_syncSet Automatically correct errors found during verification? to Interactive. Correct any pr

25、oblems along the way.Step 18. Start the clusterAt this point, the cluster is ready to start. On one of the nodes, run the smitty clstart command, and pick that particular node. My preference is not to have the cluster start on reboot, because if there is a PowerHA-related problem on startup, it can

26、be difficult to troubleshoot it. After the node comes up with the resources available, start the cluster on the other node.Step 19. Perform a test failoverThe best way I have found to test PowerHAs adaptability is to reboot the active node and let things fail over naturally while running the tail f

27、/tmp/hacmp.out command on the other node to watch as things go over. Or, run the command:smitty cl_resgrp_move.node_siteSelect the Move Resource Groups to Another Node option. Step 20. Perform failure testingIf you really want to make sure your cluster is solid, perform testing by literally removing

28、 cables and seeing how the resources move back and forth. The more you test, the more reliable your cluster will be,PowerHA繁琐的配置步骤令人崩溃,PowerHA 为何不可用,AIX,AIX,第二次,要不断的保持一致性,PowerHA 是应用级别,（2） 更高的可用性 - 选用可靠的高可用的软件,保障关键应用 预防与易用性,（2） 更高的可用性 - 选用可靠的高可用的软件,选择可靠的高可用解决方案 选择VMware,VMs,ESX,ESX内置镜像(Raid卡) VM外置镜像

29、(存储提供） 数据外置镜像(LVM提供） 客户化的关键应用支持计划,数据,VMFS/RDM compat mode,Data Recovery backup,3 x 4*E7-8870 2.4Ghz, each 600Gx2 internal each 128GB memory 2 x HBA 4 x 4口 Ethernet Storage 600Gx20 SAS（28） 250Gx2 SSD（7xSSD）,OS1,HA,VMFS,数据库,应用,阿帕奇,ESX,HA,VMFS,应用,数据库,贵金属,ESX,OS2,ESX,（2） 更高的可用性 - 选用可靠的高可用的软件,Vmware高可用的

30、x86虚拟机平台本地的最佳实践,更可靠 PowerHA 不可靠 Vmware HA 更可靠 更容易 芯片 ： Power4,5,6 升级到 Power7 复杂，麻烦 Power4,5,6 到 7 需要升级操作系统与应用 Vmware 支持升级芯片而不需升级操作系统与应用 操作系统 ：AIX 升级到 Linux 更容易，更多选择 Java， Web 应用可直接运行 x86 U2L support x86利益相关方一起支持 Intel， AMD，HP，Dell，IBM， Vmware，MicroSoft,（3） 更便宜 - 按部就班逐步淘汰如RS/6000等紧耦合的专用系统,升级到x86更可靠，更

31、容易,Power your planet. Smarter systems for a Smarter Planet.,Power的IT 挺复杂的！,（3） 更便宜 - 按部就班逐步淘汰如RS/6000等紧耦合的专用系统,Regular H/W Change Active partition Mobility,（3） 更便宜 - 按部就班逐步淘汰如RS/6000等紧耦合的专用系统,向您介绍 IBM Vmotion PowerVM Live Partition Mobility,VMware Vmotion,（3） 更便宜 - 按部就班逐步淘汰如RS/6000等紧耦合的专用系统,RS/6000

32、虚拟化平台 用户为何甘愿被绑架？ 无法协商的安全感！为什么,1994-2005 -Apple uses Power. 完全竞争指不存在足以影响价格的企业的市场。是经济学上最理想的市场竞争状态,linux,松 耦 合,紧 耦 合,威盛,其它专用系统,（3） 更便宜 - 按部就班逐步淘汰如RS/6000等紧耦合的专用系统,Database Servers,Middleware Clusters,应用平台迁移前系统架构 示例(Unix服务器),Load Balancer,16 cores 64G AppServer,16 cores 64G AppServer,16 cores 64G AppServer,32 cores 256G 2 LPARS Database,16 cores 64G AppServer,电子渠道,综合理财,信贷系统,支票影像,Applicat