Johnson Controls, Inc. Managing your Virtual Infrastructure Level 3 Phillip Cramer Manager Windows Server Environment
VMware Extreme?
Benefits (First Year) Why Consolidate? Data Center Space Reduce overall footprint Space 90 sq ft to 12 sq ft (80% space savings) HVAC Costs Cooling 25 Tons to 4 Tons (151 DL360 s) Power 49 KVA to 8.1 KVA Prevent additional in room air chiller (CRAC) units Increase system utilization by 40%. Cost avoidance on hardware refresh Monthly Maintenance fees reduced by $3,400 $310,000 in hardware costs to refresh 109 systems
Planning Our Approach Engaged RapidApp through EMC for the design and initial rollout Implementation Project Plan
Scope Consolidation Methodology More than one consolidation method, none of which by itself can be a complete solution Application Stacking (10%) Running multiple applications on one server with one operating system. Running multiple instances of same application (e.g. web sites, databases) No Consolidation (20%) Not our servers Needed expansion cards Physical Consolidation (30%) Migrate to blade servers Virtual Consolidation (40%) Migrate multiple servers to one physical server Fast Path to completion through P2V
Critical Success Factors Created a pilot farm to capture baseline performance and ROI Define bad candidates Physical consolidation ratio No Lack in Performance (181/5)/4 = 9.05 ESX Hosts EMC best practices for optimal performance and scalability metalun should not be much greater than 250GB. reference Best practices for CX and VMware.pdf 10 VM guests per LUN Average server disk size 30GB (300GB LUN) = 18 LUNs
Constraints and Selection Criteria Constraints and Risks Possible risks that could affect the design Limited time to implement the company would like to see the design implemented as quickly as possible. Limited resources to reassign from other projects. Develop and Weigh Selection Criteria Criteria Group Ranking 1 Most important 10 Least important Availability 1.75 Reliability 2.0 Performance 3.0 Security 4.75 Manageability 5.25 Scalability 6.5 Recoverability 6.5 Flexibility 7.5 Interoperability 8.75 Ease of Use 9.0
Best Practices Application Owner Meeting Directors Managers Technicians/Developers Microsoft Support Policy Swing Server Assignment and VMotion
Best Practices ESX automated Deployment Transferable to other Business units Scripting deployments are not yet possible using ESX methods FTP download and install Boot Floppy Anaconda application because can read KickStart config file LDLINUX.SYS Boot sector is told to use this file SYSLINUX.CFG Configuration file used by ldlinux.sys BOOT.MSG Displays friendly instructions during install VMLINUZ Compressed executable Linux core code INITRD.IMG Uncompressed into a ramdisk during install & contains driver files necessary to the hardware KS.CFG Configuration KickStart File Detailed information for creating your own automated deployments can be found in Chapter 9 (p375) R. Oglesby, S. Herold: VMware ESX Server: (2005).
Best Practices VMware Migration Team VMware Infrastructure Primary System Administrator Scheduling and Communication Member VMware Migration System Administrator P2V Checklist Workload balancing Heterogeneous mix of environments. Share allocation development, QA and production servers 70% system utilization without a performance impact
Best Practices VMware Farm ESX Servers Redundant paths to the SAN LUN size 8 Network Interface cards 1 Console (Eth0) 2&3 VLAN1 4&5 VLAN2 6&7 NoUplink (expansion) 8 VMotion VirtualCenter Physical system SQL back end
Best Practices VMware Guest Standards Resource allocation: It is always easier to add resources in the future than to take away. CPU: One Memory: 512 MB Disk: 7gb C:\ partition, and a 5gb D:\ partition if needed (each in separate VMDK files. Backup the guests through OS level backups Backup and archive any disk images that have been created.
Best Practices P2V Process
Got' Chas HBA Cards Queue Depth Length. Our Number one Got Cha. When they say below 30 they mean BELOW (Emulex). VirtualCenter In the event any part of the farm goes down having virtual center on a physical server will help you see in to the environment SQL database owner as sa during the install.
Got' Chas Working with your vendors Hardware Run necessary utilities on the server to verify that no hardware problems exist SAN Ensure both fiber paths are up and that the Queue Depth Length is set correctly VMware Make sure that every server in the farm is EXACTLY like one another. ESX automated deployment is a must for larger farms Microsoft Support First thing out! Support policy
Today (Second Year) Who s Counting? 11 physical servers 6TB SAN space 203 Virtual servers (5.7 guests per CPU) Capacity for 75 more guests (6.2 guests per CPU) 160 p2v 43 net new
Today (Second Year) Who s Counting? 2 swing servers with less than 5 guests each <10% utilization $5,348/month in maintenance reduced ($64,176.00) 32 tons of cooling capacity regained 180 sq feet of floor space recovered 1 rack(9 sq feet) X 20 racks removed
Today (Second Year) Who s Counting? After Hours support calls average 87% are for physical systems 13% are VMguests $760,000 hardware renewal NOT spent 200 physical servers disposed/returned 9 servers between 43 and 69% utilization
Attached Files P2V Checklist Microsoft Word Document P2V Process document Microsoft Word Document Microsoft Support Policy Best practices for CX and VMware.pdf Microsoft Word Document Adobe Acrobat 7.0 Document
Questions
Presentation Download Please remember to complete your session evaluation form and return it to the room monitors as you exit the session The presentation for this session can be downloaded at http://www.vmware.com/vmtn/vmworld/sessions/ Enter the following to download (case-sensitive): Username: cbv_rep Password: cbvfor9v9r