How VMware and VMware Capacity Planner Helped Justify John

How VMware and VMware Capacity Planner Helped Justify John Deere’s Transition to a Virtual Infrastructure Bob DeBlaey, Infrastructure Analyst deblaeyboba@johndeere.com Agenda Introduction Deere history Current challenges Our history with VMware Planning our virtual infrastructure VMware Capacity Planner Changes Our future Our History 1837 – John Deere develops the world’s first commercially successful, self-scouring steel plow, opening the West to economic development 1918 – Modern tractor era begins (Waterloo Boy) 1937 – Sales reach $100 million in centenary year 1956 – Construction equipment business launched, International manufacturing begins 1958 – John Deere Credit Company launched 1963 – Lawn and grounds care business launched 1998 – Earnings reach $1 billion John Deere Today The world’s leading producer of Agricultural Equipment A Construction Equipment industry leader and world’s premier producer of timber-harvesting equipment World leader in premium Commercial and Consumer turf-care equipment and work vehicles John Deere Today Valley City, ND Fargo, ND Edmonton, Alberta Langley, British Columbia Rock Valley, IA Des Moines, IA Ottumwa, IA Springfield, MO Coffeyville, KS Greeneville, TN Minneapolis, MN Woodstock, Ontario Welland, Ontario Klemme, IA Waterloo, IA Dubuque, IA Horicon, WIDavenport, IA Moline, IL East Moline, IL Kernersville, NC Fuquay-Varina, NC Augusta, GA Torreon, Mexico Monterrey, Mexico Thibodaux, LA Saltillo, Mexico Santiago, Chile Catalao, Brazil Santo Angelo, Brazil Horizontina, Brazil Rosario, Argentina Madrid, Spain Saran, France Arc-les-Gray, France Richards Bay, South Africa Nigel, South Africa Tokoroa, New Zealand Orenburg, Russia Pune, India Tianjin, China Zweibruecken, Germany Bruchsal, Germany Poznan, Poland Joensuu, Finland Enschede, Netherlands Horst, Netherlands Gummersbach, Germany Stadtlohn, Germany Mannheim, Germany Jiamusi, China Agricultural Equipment $9.7 Billion in Sales World’s premier farm machinery manufacturer ‘Ag Server Services’ Transitioned from a unit based IT support group to a unified division based group Our Mission: “Develop architectures, establish standards, define and implement services and support models that leverage IT resources to meet business goals at the highest possible value.” “Virtual team” is distributed among, and supports, multiple locations across North America Our Current Challenges Containing server sprawl Server consolidation Out of warranty servers High Availability, Business Continuity, and Disaster Recovery planning Our History With VMware VMware Workstation: 2001 - 2004 GSX Server: 2003 - 2005 Only concern was scalability The Solution VMware ESX Server and VirtualCenter The Plan Perform a complete assessment of our current server environment Use the data to begin our virtual infrastructure planning project Show the financial benefits of a virtual infrastructure The Plan Show the hard dollar cost benefit and capital expenditures for each of our locations Provide consolidation estimates Create a test ESX Server environment Design and document our architecture Financial Justification Deere uses Net Present Value (NPV) for evaluating the financial benefits of IT projects NPV is the future stream of benefits and costs converted into equivalent values today. This is done by assigning monetary values to benefits and costs, discounting future benefits and costs using an appropriate discount rate, and subtracting the sum total of discounted costs from the sum total of discounted benefits Our project estimated a 23.1% rate of return with a hurdle rate of 12% Financial Justification We estimated we could virtualize about 25%50% of our total environment Potential savings in future capital expenditures would save millions over the next five years Additional Analysis VMware Capacity Planner Engaged VMware to provide us with some in-depth analysis and recommendations on our current physical server environment They recommended an assessment using VMware Capacity Planner What Is VMware Capacity Planner and How Does it Work? Uses native Windows Performance Monitor API’s to collect performance stats on “live” servers at specified interval Collects data on a central server and uploads it to the Capacity Planner Dashboard Ran against our physical servers for the entire month of April 2005 Why Use VMware Capacity Planner? Validate our conclusions from our server analysis project Have enough “ammunition” to justify our actions Optimize our investment in VMware software and hardware Provides guidelines on capacity planning in a virtual world VMWare Capacity Planner Implementation Details Required a physical server Local admin rights required on all target servers The collector system must be authorized and able to connect to all the systems that it is to manage using the protocols and ports that are outlined in the VMWare Capacity Planner Getting Started Guide Verify that you are able to upload HTTPS through a proxy connection to the Capacity Planner site VMware Capacity Planner: Implementation Details Capacity Planner Dashboard Web Infrastructure Assessments Capacity Planning Server Consolidation Industry Data Hosted Secure Site Information Warehouse Data Analyzer Data Upload HTTPS Client IT Environment Client Site Agent-less Data Collection Data Manager Discovery Performance Inventory Data Synch Data Collector VMware Capacity Planner Executive Summary Data was analyzed, scrubbed, and presented to us by VMware Estimated we could virtualize 80%-90% of our environment Confirmed and surpassed all of our assumptions Provided us accurate, “real”, and useful data VMware Capacity Planner Results Server Utilization Rates Group Ava ila ble M e m ory (M B) 2,453 % CP U CP U Q ue ue P a ge s/se c P a ge File % Av. Disk % Busy Disk Av. Q ue ue Ne tw ork Tra ffic Indus try Average All Monitored 6.71 1707.01 1.33 10.05 5.38 2.34 0.31 109,379 3 .4 7 0 .8 4 4.22 0.81 1.62 0.07 33,227 Well Below Industry Standards VMware Capacity Planner Results Number of Servers at nth% Utilization Number of Servers at n% CPU Utilization Number of Servers Prime Time Peak >0% <10% ≥10% <20% ≥20% <30% ≥30% <40% ≥40% <50% ≥50% <60% ≥60% <70% ≥70% <80% ≥80% <90% n% CPU Utilization ≥90% ≤100% VMware Capacity Planner Results Actual Statistics Performance Statistics C PU C ount 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 C PU Utilization % Used Prim e Tim e 0.190721636 0.282436606 0.286981722 0.348920168 0.493727623 0.513437578 0.554166466 0.707956471 0.713763089 0.780703487 0.825222679 0.856825141 0.937988998 1.068260246 1.109039185 1.150092206 1.267322262 1.297821583 % Used Peak Tim e 0.600153502 0.580775977 0.368084517 0.542080322 0.737068778 0.97715804 1.83732027 0.869523558 2.00459124 1.374716565 1.440449039 1.462333168 3.208315836 1.632577938 1.551966033 1.303753206 2.547243767 2.890420975 Total RAM (MB) RAM Used (MB) Disk Utilization % Busy Network Pages/Per By tes Per Second Second DiskQueue 0.016723799 0.011782563 0 37625.65153 0 239057.783 Dom ain Hostnam e W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS W IDGETS SERVER1 SERVER2 SERVER3 SERVER4 SERVER5 SERVER6 SERVER7 SERVER8 SERVER9 SERVER10 SERVER11 SERVER12 SERVER13 SERVER14 SERVER15 SERVER16 SERVER17 SERVER18 1024 375.406276 1.6584596 4096 927.245018 0.5891182 1024 437.284874 0.5934382 512 234.865032 0.2749127 2048 537.776464 0.3802531 2560 384.524843 0.4614689 2048 477.518246 0.4640688 4096 1422.30202 0.113051 2048 479.007855 0.7130034 2304 505.553587 0.8827533 2048 651.063895 1.6423018 4096 1089.51497 4352 0.387409 1278.3933 0.9261022 0.00593443 0.006510687 280917.7515 0.005499158 0.007049024 110926.1331 0.007605009 0 12728.15459 13326.6596 0.009229152 0.041778298 0.009280126 0.031817223 31090.40903 0.003390742 0.007371371 28820.39569 0.007130209 0.000924659 33999.52134 0.017655512 0.00397332 36325.55397 0.03284587 0.073715049 43779.16431 0.011622281 0.318331333 47832.25819 0.018521808 0 35571.53317 0.009064266 2.426333918 11161.82097 0.016213905 0.005438325 11197.13733 0.016148925 0.206158546 11286.36809 0.031470931 0.167408822 11791.96767 0.017924154 0.038604222 496681.2579 1536 1165.02025 0.2266157 4096 1140.81462 0.5404998 4096 885.136445 0.5383119 4608 1505.30562 1.0490728 1536 555.275137 0.8960576 VMware Capacity Planner Results Bad Candidates Bad Candidates for Virtualization CPU Tota l RAM RAM Disk Disk Ne tw ork Utiliza tion (MB) Use d % Busy Que ue Usa ge W IDGETS BADSERVER1 2 43.7568025 1536 691.30662 0.502542 0.01508 18723.41 W IDGETS BADSERVER2 2 52.8391443 1536 605.65714 3.264448 0.09793 19204.91 W IDGETS BADSERVER3 2 58.2158906 1536 658.62053 12.21732 0.31498 16519.64 W IDGETS BADSERVER4 2 67.2799959 4608 1916.7213 19.32431 0.59732 11915.11 W IDGETS BADSERVER5 2 71.7332187 4096 680.10761 4.866089 0.15453 87472.41 W IDGETS BADSERVER6 2 76.276942 2048 684.26865 1.423794 0.08742 17823.15 W IDGETS BADSERVER7 2 85.8844797 2304 814.28981 19.28764 0.44894 24927.63 W IDGETS BADSERVER8 4 24.2875611 4096 1126.8722 22.71291 0.60632 46912.71 W IDGETS BADSERVER9 4 23.6242964 4096 1118.731 17.59259 0.38299 47365.28 Marked in RED is the resource utilization that indicates this workload may not be suitible for running in a virtual Any System utilizing more than 40% of 2 CPUs and/or 3.6GB of memory is determined to be a bad candidate for Dom a in Hostna m e CPU Count VMware Capacity Planner Results Reusable Servers Repurpose Servers as Virtualization Platform Servers Here is the list of all systems in the All Servers (1, 2, 4 CPU) consolidation scenario that potentially could be repurposed as Virtualization Platform Servers or for other purposes. Domain WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS Hostname GOODSERVER1 GOODSERVER2 GOODSERVER3 GOODSERVER4 GOODSERVER5 GOODSERVER6 GOODSERVER7 GOODSERVER8 GOODSERVER9 GOODSERVER10 GOODSERVER11 GOODSERVER12 GOODSERVER13 GOODSERVER14 GOODSERVER15 GOODSERVER16 GOODSERVER17 GOODSERVER18 GOODSERVER19 GOODSERVER20 GOODSERVER21 GOODSERVER22 GOODSERVER23 GOODSERVER24 GOODSERVER25 Chassis Model ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 ProLiant DL380 G3 CPU Count 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 CPU Speed 2791 2791 2791 2791 2791 2790 2790 2790 2790 2790 2789 2789 2789 2788 2788 2786 2786 2785 2784 2784 2784 2783 2392 2388 2386 RAM Disk Space (MB) (GB) 4096 1230.58823 4096 1230.58823 2048 820.392151 4096 820.392151 4096 820.392151 2048 410.196075 2048 820.392151 2560 820.392151 2048 820.392151 2048 820.392151 4608 1230.58823 2560 1230.58823 4096 313.25592 4608 1230.58823 4096 1230.58823 4096 1230.58823 4608 1230.58823 4096 1230.58823 2048 104.41864 4096 820.392151 4096 156.62796 4096 1230.58823 2560 820.392151 4096 156.62796 2560 410.196075 NIC(s) 7 8 7 7 7 7 8 7 8 7 6 8 7 6 7 8 8 7 7 7 8 8 7 7 7 VMware Capacity Planner Results Obsolete Servers Obsolete Servers The following table lists all obsolete servers and their specifications. All systems listed here in RED candidates for virtualization in the All Servers (1, 2, 4CPU) consolidation scenario. Domain WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS WIDGETS SERVER1 SERVER2 SERVER3 SERVER4 SERVER5 SERVER6 SERVER7 SERVER8 SERVER9 SERVER10 SERVER11 Chassis Model NetServer LH 3 NetServer LH 3 NetServer LH 3 NetServer LH 3 NetServer LH 3 NetServer LH 3 PowerEdge 6300/400 PowerEdge 6300/400 HP NetServer HP NetServer HP NetServer CPU Count 1 1 1 1 1 2 4 4 4 4 4 CPU Speed 399 399 399 399 399 399 400 400 550 550 550 RAM (MB) 512 512 512 1024 768 1024 4096 4096 4096 4096 4096 Disk Space NICs (GB) 50.84966183 5 33.8895607 5 33.89722109 5 33.89722109 5 33.90488148 7 59.322052 5 3.968081474 5 16.94478035 5 152.6102686 5 152.6102686 5 152.6102686 5 Project Results Currently 25% of our environment virtualized since August Nearly 50% of environment will be virtualized by end of year Current CPU utilization on ESX hosts under 15% Memory utilization under 15% Consolidation ratios could easily hit 20:1 Culture Change All servers will now be virtualized Server builds take minutes Response time to business is much quicker Other units and divisions are following our lead Process Change Disaster Recovery and Business Continuancy plans have been greatly simplified Vmotion has enabled us to become more flexible Virtual Machines specs based on Capacity Planner results Our capacity planning analysis and skills must change Technical skills have been updated Our Future Continue Consolidating Servers Dual-core servers Virtual machine clusters Continue integrating IT groups from other divisions Optimize our current environment Questions