2. Accelerating IT Migration Success with a
Rock-Solid HP and Red Hat Enterprise
Linux Platform
Alex Heublein Vedanta Barooah
Director, Solutions & Strategy , Senior Solutions Architect,
Red Hat Datacenter Linux Infrastructure,
Hewlett-Packard

3. Today’s Speakers
Alex Heublein
Director, Solutions & Strategy, Red Hat Professional Services
Alex Heublein is the Director of Solutions and Strategy for Red Hat's Global Professional
Services business unit. He is responsible for the technology strategy for the business unit as well
as a portfolio of productized services solutions. Alex has over twenty years of experience in the
IT industry encompassing a wide variety of roles including senior management, strategic
technology and business consulting, enterprise architecture, and mission critical solution
architecture, design, & development.
Vedanta Barooah
Senior Solutions Architect – Datacenter Linux Infrastructure, Hewlett-Packard
Vedanta Barooah is a senior solutions architect with Hewlett-Packard Technology Services and
specializes in large-scale implementation of Linux and open source in enterprise datacenter
environments. His areas of interest include: virtualization, server consolidation, enterprise
directories, systems redundancy, IT infrastructure, middleware, and databases. In his spare
time, he prefers developing in PHP, Python, and Perl, and is an enthusiastic learner of web
standards and technologies.

4. Agenda
Customer Challenges Today
Linux Migration Drivers
Building a Rock-Solid Linux Platform
Migration Planning Strategies
Landscaping a Large Scale Migration
Application Migrations
Database Migrations
Customer Success Stories

5. Customer Challenges Today
Business savings demand faster migration to Linux on standard servers
Distribution selection still a challenge
Applications often require wide mix of Operating System components
Linux DC environment must support a hybrid mix of Commercial and Open
Source applications and components
Challenges in technology mapping from other platforms
HA, Clustering, Virtualization, DR, Backup, Monitoring and others
Governance and Manageability require more discipline
Tools mapping from legacy Unix/Windows still a challenge
Multiple schools of thoughts around Linux integration to Core IT Infrastructure
Platform, Application and Database Patching process still tedious

6. Linux Migration Drivers
• Tactical business drivers
– Reduce support costs by replacing end of life server hardware and
moving to a commodity hardware platform
– Improve capability by upgrading legacy enterprise applications and
database
– Better performance and lower cost by porting custom applications
• Strategic business initiatives and IT objectives
– Simplify and consolidate IT for maximum efficiency
– Accelerate new service development and deployment
– Reduce infrastructure, operational and support costs to decrease TCO
– Technology Modernization and adaption of Open Standards

7. Recent HP + RedHat ROI Migration Study Solaris to Linux
Summary Financials
Financial Metric Value
Total Investment $ 4,714,000
Net Present Value of Savings: $ 5,628,839
Year 3 After-Tax Savings: $ 2,661,937
Return on Investment (%): 27.4%
Payback (Months): 32
Monthly Cost of Delay $ 156,357
Total Cost of Use Comparison
Total Cost of Use Comparison
16,000,000
15,000,000
14,000,000
15,000,000
13,000,000
14,000,000
12,000,000 13,000,000
$ 12,000,000
11,000,000
11,000,000
10,000,000 10,000,000
9,000,000
$ 9,000,000
8,000,000
8,000,000 7,000,000
7,000,000 6,000,000
Year 1 Year 2 Year 3
6,000,000
Existing Linux on Blades
Year 1 Year 2 Year 3
Existing Linux on Blades

8. Building a Rock Solid Platform

9. Building a Rock-Solid Linux Platform
Enterprise Datacenter Linux
Single
Sign-On Patch & Governance
& Update
Enterprise Management
Directory
Middleware
Best
Practices Go to Production
Testing & Acceptance
Migration
Platform
Best Consolidation
Practices Performance
Datacenter Rollout
&
Platform & Optimization
Platform Deployment Middleware
Security
Platform Design
and Migration Planning
Disaster
Management

10. Linux Server in a Data Center
SSL Traffic
DMZ
Non SSL Traffic
Server
Middleware
Installation
Identity Directory
System
Software
Security
Components
Update Linux OS
and Configuration
Patch Management
Repository
Monitoring and
Management
Log Server

11. 1
Server Hardware Settings & Configuration
Hardware
Preparation
2
Server Firmware & BIOS Update
3
Standard Linux Build
4
Driver Updates & Server Agent
Linux Build
5
Security, Management and Monitoring Tools
Deployment Methodology
6
Middleware Specific Linux
Profile
7
Middleware Components
8
System Hardening
Security

12. Accelerating IT Migration Success with a Rock-Solid HP and Red Hat Enterprise Linux Platform
HP + REDHAT - A FOCUS ON RAS

13. A Focus on RAS: Hardware-Level-Only [RHEL 5]
• Hardware-Only is a Good Thing!
• Typically better performance
• Typically better reliability
• Sometimes a feature can only be done in HW
• The economics need to be right
• Memory and Interconnect
• Better handling of memory and interconnect
errors
• Software handling could have resulted in
system halt!
• These are features found in higher-end Memory
Intel® SMI Lane Failover
proprietary platforms Intel® SMI Clock Fail Over
• Now available on more efficient mainstream Intel® SMI Packet Retry
Intel® Scalable Memory Interconnect
platforms
QPI
QPI Self-Healing
Intel QPI Protocol Protection
Intel QPI Packet Retry
QPI Clock Fail Over

14. A Focus on RAS: New With RHEL 5.5
• CPU/Socket and I/O Hub
• All of these features were enabled in
earlier versions of RHEL 5
• But these features are just now
coming out in hardware
• We have had several releases to
I/O Hub
bullet-proof this support PCI-E Hot Plug
CPU/Socket
OS CPU Onlining
• Hardware-Only Plus RHEL 5 Partitioning Via Virtualization
Electronically Isolated Partitioning
enablement moves the bar
even higher
Memory
QPI

15. A Focus on RAS: Coming in RHEL 6
• Red Hat is working with Intel upstream to
harden these features in time for RHEL 6:
• Memory
• Inter-socket Memory Mirroring
• Failed DIMM Isolation
• Physical Memory Board Hot Add
• Dynamic Memory Migration
• Dynamic/OS Memory On-lining (capacity change)
• Demand and Patrol scrubbing
• Mirrored Memory Board Hot Add/Remove
• CPU/Socket I/O Hub
• Machine Check Architecture (MCA) recovery
• Corrupt Data Containment CPU/Socket
• Corrected Machine Check Interrupt (CMCI)
• Physical CPU Board Hot Add/remove
• Intel Quickpath Interconnect
• QPI Viral Mode
Memory
• I/O Hub
• Physical IOH Hot Add QPI
• Dynamic/OS IOH On-lining (capacity change)

16. Migration Planning Strategies

17. The Strategic Migration Planning Process
1 Unix to RHEL Ecosystem Analysis – Mapping the Unix
ecosystem into the RHEL ecosystem and creating a RHEL
Standard Operating Environment (SOE)
2 Functional Applications Analysis – High level analysis of
business applications to be migrated.
3 Organizational Readiness & Risk Analysis – Analysis of
organizational readiness factors, project risks, and risk
mitigation strategies.
4 Strategic Migration Roadmap Creation – Combining
everything into a single, holistic roadmap for migration.
5 Migration Implementation – Execution of the Strategic
Migration Roadmap.

18. Phase I: Unix to RHEL Ecosystem Analysis
• Examine existing Unix ecosystem and
determine the equivalent capabilities in
the RHEL ecosystem.
• Create a gap analysis and plan to
address all gaps (if needed).
• Create a Standard Operating
Environment (SOE), an organization's
standard implementation of RHEL,
including base operating system, a
custom configuration, standard
applications, software updates and
service packs.

19. Ecosystem Mapping Scenarios
Built-in Functionality to Built- Solaris Infrastructure App to
in Functionality RHEL Infrastructure App
Solaris Infrastructure Application Solaris Functionality to RHEL
to RHEL Functionality Infrastructure Application

20. Common Ecosystem Component Mappings

21. Phase II: Functional Applications Analysis
• Analyze complexity and size of existing
functional applications to determine
macro-level migration difficulty.
• Analyze application migration
dependencies, including tightly coupled
interfaces and co-resident applications.
• Examine possible deployment scenarios
for each application and its associated
testing and staging environments based
on the four generic deployment patterns
• Create high-level functional migration
application cost analysis

22. Deployment Scenarios
Consolidation Dispersion
Aggregation Cloud Migration

23. Phase III: Organizational Readiness & Risk Analysis
• Examine organizational readiness
factors including skill gaps, IT
governance processes, and
acceptance factors.
• Perform situational SWOT analysis to
determine current-state migration
strengths and weaknesses as well as
future opportunities and threats.
• Analyze technical risks inherent in
many migrations.
• Create Risk Mitigation Strategy to
address and limit the impact of
identified risks.

24. Phase IV: Strategic Migration Roadmap Creation
• Create final list of application
workloads to be migrated.
• Perform consolidated server,
deployment, and virtualization
analysis.
• Examine hardware redeployment
scenarios and opportunities.
• Create detailed training plan to
address all identified skill gaps.
• Create detailed direct cost estimate
for the entire migration.
• Create master Migration Roadmap

25. Landscaping Large Scale Migrations

26. Building a Application and Database Ready Linux
Infrastructure

27. Landscaping a Large Scale Migration
Application Re-Platforming
•Lift and Shift Migrations
Application Migration •Java Middleware – WLS, Websphere
•Migrations across Linux Distributions
•Migration of custom code on standard middleware
Core IT Services
•Infrastructure Services
• Infrastructure Management
Complexity and Time
Database Re-Platforming Application Porting
•Oracle for other Platforms to Linux
• Porting Legacy Applications to Linux
•Sybase, DB2 and Others
• Re-implementation
Custom off the Shelf Database Migration
•Third-Party Application Middleware •Oracle to MySQL
•Version / Feature Mapping •Sybase to MySQL
•DB2 to MySQL

28. Migration Landscaping Factors
Availability of complete Application / Infrastructure catalogues
Sometimes organizations lose track of application architectures
Organization’s ability to classify and group migration candidates from catalogues
Application compatibility – Best for “lift-and-shift” type of migrations
Available downtime windows – Downtime facilitates easier migrations
End of life Application – Does not need migration, remove from list
Level of re-mapping, upgrading or modernizing
Application Modernization
Storage Layout Optimization
Opportunity for Infrastructure Optimization – Consolidation, Virtualization
Clustering – Back-end, Middle-tier
Feasibility of tools usage during migration
Commercial Migration Tools
Open Source and In-House Migration Tools

29. Application Migrations

30. Application Migration - Challenges
Development Environment Differences
Build Tools Compatibility
Code Editors, Debuggers and IDE
Migration from legacy and proprietary tool chains
Compilers and Tools
Standard Conformance
Interface and Namespace changes
Library differences
Endian Conversions
Big Endian (Most Unix) to Little Endian (x86 Linux) byte ordering
Network Data Exchange
Binary data exchange across platforms

31. Application Migration – Challenges (contd.)
Commands and System Tools
User level commands
Management Tools
System API calls
Software Management
ISV Application Migrations / Custom off the shelf
Availability and compatibility under Linux
ISV Product Migrations
Product Upgrades

32. Application Migration Tools -
Software Transition Kit (STK)
• STK provides tools to scan application source code for
transition impacts
– C/C++ source code
– Shell scripts and Makefiles
• Transition documentation and guides to help ease the migration
from other Unix to Linux
• STK is useful for planning and estimating Unix to Linux
migration projects
• Free download from www.hp.com/go/stk

33. Solaris to Linux Porting Kit (SLPK)
• Solaris to Linux porting kit is a set of compiler tools, libraries, header
files and source scanners
• Compiles Solaris code on Linux, with minimal changes to application
code
• Simplifies the transition of C/C++ source code, shell scripts and
Makefile from Solaris to Linux
• Free download from www.hp.com/go/slpk
Build
Environment
Endianness Data
Structures
Solaris based
C/C++ Header
SLPK Fine Linux
Migration Tune executable
source code Files Environment Libraries
Threads Missing
functionality

34. Database Migrations

35. Database Migration - Factors
- Server Capacity vs. Consolidation/Virtualization Planning
- Critical uptime requirements demanding advanced tools to facilitate
immediate switchover
- Additional server / storage capacity to stage migration and fallback
- Existence of test use cases for data validation
- Mapping clustering technologies across platforms
- Database complexity introduced by unconventional maintenance, numerous
direct links, and invalid objects
- Storage – File Systems, Scalability, Clustering
- Capacity and growth planning

36. Optimizing Database Migrations
Design Migrate and Test Roll-out
•Infrastructure Layout •Automated Provisioning •Monitoring and Management
•Network and Storage •Automated Configuration •Security Implementation
•Redundancy and HA •Systems Engineering •Go-to-production Support
•Best Practices •Performance Optimization •Update Management
•Testing •Remediation Support
•Roll-outs
•Migration Planning •Database Installation •Monitoring and Management
•Migration Scenarios •Pre-migration Configuration •Security Implementation
•Data Migrations •Go-to-production Support
•Post-migration tasks •Update Management
•Testing and Remediation •Remediation Support
•Roll-outs
•Storage Review and Mapping •Performance Benchmarks •Performance Monitoring
•Performance Measurements •Performance Tuning •Remediation Support
•Sizing and Capacity Planning •Database Tuning •Performance Optimization
•Pre-Migration Planning •Post-migration assessment
•Configuration Planning
•Best Practices
Project and Change Management

37. Customer Success Stories

38. Customer Success Stories
City of Chicago Migrated their mission critical Oracle database
environment to Red Hat Enterprise Linux on HP
servers because they needed to:
Carving Out Cost
•Reduce server hardware, maintenance and operating
costs
•Prove Linux could effectively run enterprise-level
applications
•Increase flexibility in choosing hardware vendors for
significant potential cost savings
Red Hat solution successfully delivered in the original
environment, addressing all the initial migration drivers
and has further enabled City of Chicago to expand
these benefits to other areas.

39. Customer Success Stories (cont.)
Migrated to a Red Hat + HP solution to obtain an easy-to-
Whole Foods use and reliable systems management solution that
enabled increased productivity and reduced costs.
Management Whole Foods needed:
and Scale
•A cost-effective operating platform
•A complementary management solution
•Scalability to keep with the company's rapid growth
•Increased security, manageability, and availability of
business-critical applications
•Cheaper, faster, more reliable system
•Added enhanced capacity
•A system that guarantees security and reliability
Experienced increased performance and internal-user
satisfaction of homegrown applications, including order
processing applications.

40. Customer Success Stories (cont.)
NYSE Euronext Migrated to Red Hat + HP solutions so NYSE
Euronext could focus on diversifying its product base
Innovating For and developing a global platform for trading. To
achieve this, they needed:
Success
•To overcome the challenges with integrating varied
trading platforms from multiple acquisitions
•Produce a simplified and optimized technology
architecture
•Enhance the effectiveness of its technology through
incorporation of features needed
•Have a solution that was reliable and flexible enough
to produce the fast-paced performance demanded by
the industry.
Hear about their results at
http://customers.redhat.com/2008/05/12/nyse/