Making Linux POCs successful

1. Making LinuxPOCs successful Andy Greco Mainline Information Systems andy.greco@mainline.com

2. CONTENTS Why Mainline? Why linux on z Series? Steps for a successful POC What apps make sense? POC organizational issues Next steps after successful POC

3. About Mainline Founded in 1989; 20 year partnership with IBM Specializing in System z, System p, System i, System x, System Storage, Software Networking, Retail and Services Has grown to become an IBM Premier Business Partner and global provider of information technology and infrastructure solutions with more than 600 employees nationwide Offices are located in Tallahassee, Los Angeles, Chicago, Jersey City, Nashville Sao Paulo, and Monterrey

4. Revenue Growth

5. Product Mix

6. 2007 Performance Highlights Top IBM SP1 Solution Provider (buy direct from IBM) #1 IBM System z SP1 #1 IBM System Storage SP1 #1 IBM System p SP1 #1 IBM System i SP1 #1 IBM System x SP1 #1 IBM Software SP1 #1 IBM IGS SP1 #1 IBM IGF SP1

7. Local Teams, National Coverage

8. Why linux on z series?

9. Late 90�s ..new workloads.. �.Linux and IFL in mid 2000/ 2001. Late 90�s ..new workloads.. �.Linux and IFL in mid 2000/ 2001.

10. What System z brings to Linux

11. Potential for dramatic reductions in software expense for processor based licenses Significant reductions in power and cooling costs are typical Cost curve is not linear: when will infrastructure break? Reductions in Floor Space People savings from virtualization Increased processor utilization Source David Heap 2002 Source David Heap 2002

12. Bank consolidates 45 Oracle x86 Servers to one System z ! Real BANKING CUSTOMER implementation Source: zNTC (that is, the System z New Technology Center)" Contact : Gerard Laumay Note: HW Acquisition cost reflected only for System z as the HP and Dell were existing HW. An upgrade was required for the Mainframe with specialty engines to run the increased workloads/ Real BANKING CUSTOMER implementation Source: zNTC (that is, the System z New Technology Center)" Contact : Gerard Laumay Note: HW Acquisition cost reflected only for System z as the HP and Dell were existing HW. An upgrade was required for the Mainframe with specialty engines to run the increased workloads/

13.

14. Business Case for Linux on System z Increased solutions through Linux application portfolio Large number of highly skilled programmers familiar with Linux Integrated business solutions Data richness from System z Wide range of Linux applications Industrial strength environment Flexibility and openness of Linux Qualities of service of System z Unique ability to easily consolidate large number of servers

15. Steps in a successful POC Pick appropriate application, appropriately sized for a POC Build POC organization / team Detail project plan with success criteria Execute the plan Present results to customer management Define next steps

16. Leverage classic strengths of the System z High availability High i/o bandwidth capabilities Flexibility to run disparate workloads concurrently Requirement for excellent disaster recovery capabilities Security Shortening end to end path length for applications Collocation of applications Consolidation of applications from distributed servers Reduction in network traffic Simplification of support model Consolidation Effect Power requirements Software costs People Costs Real Estate Workloads requiring EXTREME Flexibility What makes best fit?

17. Best Fit applications

18. What Makes Good Fit Applications Evaluate server choices Correct application availability, Supporting applications, Total Cost of Ownership (TCO) Politics within the organization. Porting issues Shortening end to end path length for applications Collocation of applications Consolidation of applications from distributed servers Reduction in network traffic Simplification of support model

19. Good Fit Application Workloads UDB (DB2) Informix, (IDS) Apache web serving SAMBA TIM/TAM (LDAP Services) TSM Existing Linux Workloads

20. Selecting an application Performance on System z CPUs is superior to any other CPUs on any other platforms CPU speed is not the entire story � it�s in the architecture! Architecture designed for multiple or consolidated workloads System z has definite advantage with applications that have mixed CPU and I/O System z10 Enterprise Quad Core 4.4 GHZ System z and z/VM provide the best virtualization capabilities All workload types are eligible Good planning is essential Mainline with IBM�s assistance can: Perform sizing estimate with actual server statistics Perform Application Assessment Perform TCO Business Case Analysis (Alinean tool,RACEv) Assist with planning and initial installation needs

21. Organizational issues that need to be addressed Need executive sponsor Customer must provide systems, application and network representation Customer must have dedicated resource for the POC Get distributed team engaged Customer assigned tasks and accountability Status calls required on a weekly basis measuring progress

22. Detailed project plan Project plan clearly defined and agreed upon by all parties involved (examples are available upon request) CLEARLY defined success criteria must be agreed upon (examples available upon request) Dates and names assigned to each task Loaner equipment (if required) needs lead time for paperwork to be processed and equipment installed Determine loaner software (if needed) with required lead time Weekly status calls required for measure of progress Engage technical resources (MIS and IBM) when issues arise

23. What�s next after success? Present success story to customer management Get management commitment for production Plan for production Develop support organization structure within customer Plan for additional applications Develop a cross platform virtualization strategy