1 / 13

Virtualization in the Datacenter

Virtualization in the Datacenter. Timothy Antonowicz Systems Engineer Bowdoin College. Spring 2004. 76 Intel servers Projected growth for 15-25 per year No R&D infrastructure Limited Datacenter resources Need for higher availability and fault tolerance for services. Problem Statement.

kevin-long
Download Presentation

Virtualization in the Datacenter

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Virtualization in the Datacenter Timothy AntonowiczSystems Engineer Bowdoin College

  2. Spring 2004 • 76 Intel servers • Projected growth for 15-25 per year • No R&D infrastructure • Limited Datacenter resources • Need for higher availability and fault tolerance for services

  3. Problem Statement • We need to find a solution to our space and resource problem. • Address Hardware and Physical limitations • Support our diverse systems environment • Provide best use of staff resources • Consolidate to better utilize server resources

  4. Software Requirements • Flexibility • Multiple OS support • Management • Ease of Use • Rapid deployment • Backup and Recovery • Industry Standard

  5. Software: VMWare ESX Server • “Bare Metal Install” • Licensed per server, not per VM • Each VM assigned the same virtual hardware • VMs portable between different ESX servers • Image and Deploy servers in minimal time • Multiple Drive States • Use of “REDO” for changes • VM is comprised of 2 files, easy backup

  6. Task: Create Testing Infrastructure • Build virtual servers as “sandboxes” • Programmers and developers • Application support and upgrades • Standardization of platforms • Backup and recovery • Self-service option

  7. Task: Migrate or retire old servers • Replace older hardware with virtual • Application upgrades on VMs • P2V migration for static servers • “Plan for Virtual, move to Physical” • New upgrades or migrations are done to virtual servers first. If more resources are needed, it is moved to a blade at that time.

  8. Task: Build for future growth • Create Server Images • Gold Win2k3 and Linux images • Scale ESX servers for growth • VM resource allocation • Scale servers at a common base • Increase disk, memory, CPU as needed • “Added resources make happy customers”

  9. Task: Change the mindset of IT • “Plan for Virtual, move to Physical” • Projects begin with virtual servers • Charge/spec for “Server Resources” • Prove patches and upgrades in VM • Beat up on a Clone • Spread the wealth • separate file, web, and databases for security

  10. Bowdoin Systems Today • 46 X86-based servers (retired 30 servers) • 122 X86-based hosts • 10 ESX servers hosting 86 VMs • 86 Virtual hosts vs. 36 Physical hosts • 70% virtualized in the x86 space

  11. Savings • Cost of each Blade: $6,250.00 • Includes Disk, Memory, Dual Proc, etc. • Number of additional servers: • 86 virtual-10 ESX servers=76 • Cost to provide physical Servers • 76 x $6,250= $475,000.00 • ** Bowdoin did not purchase servers in FY05-06

  12. Conclusion • Server Consolidation at Bowdoin was successful at many levels • Consolidation can be done by anyone with a little time, resources and determination • Bowdoin’s effort is ongoing • ESX 3 upgrade and migration- Fall’06

  13. Thank you for attending • Tim Antonowicz Systems Engineer Bowdoin College 1-207-725-3723 tantonow@bowdoin.edu

More Related