IBM e Server Linux on z Series Module
IBM e. Server™ Linux on z. Series Module 2: Consolidation 2004 IBM Corporation
IBM e. Server™ Consolidation with Linux on z/Series Objectives • List the six major components of TCO (Total Cost of Ownership). • Describe the differences between the three main types of consolidation from an application standpoint. • Describe the differences between the two types of consolidation from an infrastructure standpoint. • List the five factors that must be taken into account with physical consolidation. • List three considerations for virtual consolidation. • List at least four ways that consolidation impacts on TCO. • Describe the differences in disk utilization of servers in a virtual consolidated environment vs. a server farm with discrete servers. 2 © 2004 IBM Corporation
IBM e. Server™ Factors in industry § Cost: Total Cost of Ownership (TCO) § Time-to-market § Application skills 3 © 2004 IBM Corporation
IBM e. Server™ Components of TCO § Hardware § People • Servers • Disk • Network • System Management • Area • Racks (+cable) • Utilities § Software • Operating system • Linux SW support • System management • Database • Application • Full-time equivalents § Occupancy § Migration § Downtime 4 © 2004 IBM Corporation
IBM e. Server™ How to survive § Optimize IT resources. § Provide competitive advantage. § Drive automation and simplicity into the IT Infrastructure. 5 © 2004 IBM Corporation
IBM e. Server™ How does server consolidation lower TCO? 1. 2. 3. 4. 5. 6. Increases utilization of server hardware, software, and networks. Lowers employee cost, floor space, and energy. Increases availability, lower downtime costs. Allows consolidation of test and development servers. Permits faster deployment of new servers. Enhances security by protecting the kernel and most of the binaries on a z/VM read-only minidisk. 6 © 2004 IBM Corporation
IBM ^ Discrete servers Consolidated servers Larger support staff required to maintain servers and network gear. Smaller support staff required to maintain 1 or 2 servers. Disaster recovery difficult for large/complex server farms. Lower hardware reliability. Disaster recovery easy for virtual server farms. Higher hardware reliability. Higher software application cost due to the higher number of processors. Lower software application cost due to fewer hardware processors. Failover is provided by additional server hardware in “hot standby mode”. Failover is provided by virtual server in “hot standby mode”. Software resource must be duplicated for each server. Software resource shared among virtual servers. Discrete servers may require significant amounts of power and floor space. Server and disk storage subsystems require minimal power and floor space. © 2004 IBM Corporation
IBM e. Server™ Types of consolidation from an application standpoint • Centralization • Physical consolidation • Application integration 8 © 2004 IBM Corporation
IBM e. Server™ Centralization What is it? Geographically distributed servers (WANS) are consolidated into one or a few centralized servers. Benefit? Personnel consolidation utilizes advances in network reliability. 9 © 2004 IBM Corporation
IBM ^ Physical consolidation What is it? Servers running the same applications can be consolidated by merging them together onto one server. When to use? When the servers being consolidated are generally of low/medium utilization. If servers have not been recently updated to newer, faster machines. Benefit? Significantly lower the expense and effort of administration and maintenance. Savings in software license fees. © 2004 IBM Corporation
IBM ^ Applications integration What is it? This is a consolidation of different servers running different applications to one server. Benefit? Similar to physical consolidation in floor space, employees, etc. © 2004 IBM Corporation
IBM e. Server™ Types of consolidation from an infrastructure standpoint • Full consolidation • Virtual consolidation 12 © 2004 IBM Corporation
IBM e. Server™ Full consolidation What is it? Several servers, running either the same or different applications, are consolidated on one server and one operating system image. Considerations • Security • Stability • Maintenance • Flexibility • Support 13 © 2004 IBM Corporation
IBM e. Server™ Virtual consolidation What is it? • Servers are consolidated into the same number of operating system images running on one box by using the virtualization technology of z/VM on z. Series (n-to-n). • z/VM virtualization technology allows sharing of resources between the guest systems. Considerations • Network: more network bandwidth from computer center to the distributed locations. • Personal cost savings: • from changes in processes/organization • no change = small personnel savings • Depreciation of existing equipment. 14 © 2004 IBM Corporation
Virtual consolidation IBM e. Server™ 2004 IBM Corporation
IBM e. Server™ Considerations in virtual consolidation § ISV software § Networking § Personnel cost savings § Depreciation § Leasing or other contracts 16 © 2004 IBM Corporation
IBM e. Server™ Server consolidation with Linux on z/VM 17 © 2004 IBM Corporation
IBM e. Server™ Reasons driving consolidation § Avoid server farm growth problems. § Increased availability of a consolidated server farm. § Streamlining of a server farm environment. 18 © 2004 IBM Corporation
IBM ^ Shared disk space Discrete servers • Each server needs own disk space. • Many redundant files/data. Consolidated Linux on z. Series Virtual Servers • Share disk space among virtual Linux images. • Version control for your application software. © 2004 IBM Corporation
IBM ^ Allowing for growth Horizontal Growth • Ideal for fast growing server environments. • Allows you to easily add servers. © 2004 IBM Corporation
IBM e. Server™ Consolidation formula § So how many distributed servers can be consolidated onto one machine? § Workload Dependency Factors • Application path length • Application specifics (Java, PHP, WAS, DB, etc. ) • IO values for storage • IO values for the network • Cache and memory efficiencies dependent on architecture 21 © 2004 IBM Corporation
IBM e. Server™ Consolidation formula § Formula: Processorsz = (Utilizationother * Processorsother * MHzother) / (MHzz * WLF) § Factors • Degree of utilization of servers • Number of processors • MHz rate of the servers • Workload factor (WLF) 22 © 2004 IBM Corporation
IBM e. Server™ Example calculation § Sample simple calculation (not a official sizing) • 100 Intel single CPU machines • Clock speeds of 200 MHz • 5% CPU Utilization • Putting the workload onto a z 800 running at 80% CPU utilization • The workload can be handled with 2 - 3 processors (CPUs) 23 © 2004 IBM Corporation
IBM e. Server™ Sample consolidation with Samba Windows Environment: 105 servers, 5 PDCs, 30 print servers and 70 file servers § Hardware • 5 PDCs: 500 MHz P 4, 512 MB RAM, 1 Fast. Ethernet adapter, 30 GB disk • 30 print servers: 2 x 500 MHz P 4, 1 GB RAM, 1 Fast. Ethernet adaptor and 60 GB disk • 70 file servers: 500 MHz P 4, 512 MB RAM, 1 Fast. Ethernet adapter and 120 GB disk • 10 x 19" racks with, each for 11 servers plus network switch § Power • 115 x 300 W = 34, 5 KW § Space • 10 x 19" racks floor space § Software • 105 Windows NT installations § Network • 10 network switches, with 11 x Fast. Ethernet ports and a GB-Ethernet port to for the connection to the company backbone network § People • 6 system administrators (~15 servers per administrator) 24 © 2004 IBM Corporation
IBM e. Server™ Samba Linux Consolidated Samba on Linux for z. Series environment: 105 Linux instances running under z/VM § Hardware • 4 z. Series IFLs on existing HW, 32 GB RAM, 2 GB Ethernet adapters, for disk 12 ESS • storage system with 8 TB § Power and space • 7 KW for one ESS storage system • One ESS storage system, floor space similar to 4 x 19" racks. • No additional space and power for z. Series system. § Software • Cost for a Linux distribution (and consider, the Debian distribution is available for free) • z/VM for 4 IFLs § Network • 2 shared GB Ethernet adapters already mentioned in Hardware § People • In a highly optimized environment, 3 system administrators 25 © 2004 IBM Corporation
IBM ^ Sample infrastructure consolidation: L. L Bean • Direct merchant with over $1 billion yearly sales. • Replaced e-mail system for high priority applications with Sendmail/SUSE solution on z. Series. • 5 X performance improvement over older system. • Sendmail is easier to use and more flexible than older system. • Mainframe reliability and scalability come to high priority e-mail application. • Software costs for traditional software running on same system unaffected due to use of IFL. © 2004 IBM Corporation
IBM e. Server™ Sample Web serving environment UNIX environment: 50 Intranet Web servers § Hardware 50 Sun 220 R system: 2 x Ultrasparc II 300 MHz, 512 Mb RAM, 2 Fast. Ethernet cards, • 18 GB disk • § Power • 50 x 300 W = 15 KW • 5 x 19" racks floor space • Solaris is included with the HW • 5 Fast. Ethernet Network switches plus cables • 4 system administrators § Space § Software § Network § People 27 © 2004 IBM Corporation
IBM e. Server™ z. Series Web serving environment § Hardware • 4 IFLs, 16 GB RAM, 1 GB Ethernet adapter and 512 GB disk space • None additional, add to existing z. Series and ESS systems • None additional § Power § Space § Software Cost for a Linux distribution (For example, Debian is free, but offers no commerical support. ) • z/VM for 4 IFLs • § Network • 1 shared GB Ethernet adapters, already mentioned in hardware • 3 system administrators § People 28 © 2004 IBM Corporation
IBM e. Server™ Sample server hosting consolidation: Sonera Entrum • Sonera Entrum is the leading broadband Internet provider in Finland. • Provides high-speed Internet access for 500, 000 private and 70, 000 corporate subscribers. • Uses z 900 and Linux to run 500 virtual servers on a single z. Series Server. • Uses ESS (SHARK) and both Red Hat and Su. SE Linux. 29 © 2004 IBM Corporation
IBM e. Server™ Getting started § Important to start small. § Choose application and set of servers that can be easily consolidated as a pilot; like infrastructure workloads. § Begin with an analysis of TCO goal to have a clear goal and measurable objective. § TCOnow! is one tool that analyzes this for you. 30 © 2004 IBM Corporation
IBM ^ Conclusion: Discrete vs. Consolidated Servers Server farm growth leads to increased expenses in: • hardware price and maintenance • floor space, power, cooling • additional support staff/overall employees • per server (engine) software fees • network cabling (kilometers of cables) • spares/re-boots to aid high availability • disaster recovery testing is difficult to accurately implement z/VM Consolidated Servers: • resource sharing • one-to-one mapping • high availability • benefits from mainframe QOS • benefits from mainframe disaster recovery services • can connect to discrete servers as required • no cabling within server, transfers at memory to memory speeds with Hipersockets © 2004 IBM Corporation
IBM e. Server™ Conclusion § The six major components of TCO are: • Hardware • Software • People • Occupancy • Migration • Downtime 32 © 2004 IBM Corporation
IBM e. Server™ Conclusion The differences between the three main types of consolidation from an application standpoint § In centralization geographically distributed servers (WANS) are consolidated into one or few centralized servers. § In physical consolidation servers running the same applications can be consolidated by merging them together onto one server. § In application consolidation different servers running different applications are merged onto one server. 33 © 2004 IBM Corporation
IBM e. Server™ Conclusion The differences between the two types of consolidation from an infrastructure standpoint § In full consolidation several servers, running either the same or different applications, are consolidated on one server and one operating system image. § In virtual consolidation servers are consolidated into the same number of operating system images running on one box by using the virtualization technology of z/VM on z. Series (n-to-n). z/VM virtualization technology allows sharing of resources between the guest systems. 34 © 2004 IBM Corporation
IBM e. Server™ Conclusion Five factors that must be taken into account with physical consolidation are: • Security • Maintenance • Stability • Flexibility • Support 35 © 2004 IBM Corporation
IBM e. Server™ Conclusion Factors that must be taken into account with virtual consolidation: • Networking • ISV software availability • Personal cost savings • Depreciation • Leasing or other contracts 36 © 2004 IBM Corporation
IBM e. Server™ Conclusion How consolidation impacts TCO: § Increase the utilization of server hardware, software and networks. § Lower employee cost, floor space, and energy. § Increase availability, lower downtime costs. § Consolidation of test and development servers. § Permit faster deployment of new servers. § Security enhanced by protecting the kernel and most of the binaries on a z/VM read-only minidisk. 37 © 2004 IBM Corporation
IBM e. Server™ Conclusion The differences in disk utilization of servers in a virtual consolidated environment vs. a server farm with discrete servers • Discrete Servers: each server needs its own disk space creating many redundant files/data. • Consolidated Linux for z. Series Virtual Servers share disk space among virtual Linux images which eliminates waste, increases utilization, and has the added benefit of additional version control for your application software. 38 © 2004 IBM Corporation
- Slides: 38