Migrate to the Future: Mitigate risks and reduce ... - IBM to the Future: Mitigate risks and reduce...

© 2009 IBM Corporation© 2009 Red Hat Corporation1 2009-11-05

Migrate to the Future:

Mitigate risks and reduce costs with IBM and Red Hat

Martin Long, Senior Technical Solution Manager, IBM Migration FactoryAlex Heublein, Director, Strategy and Solutions, Red Hat Consulting

© 2009 IBM Corporation© 2009 Red Hat Corporation2 Migrate to the Future: IBM and Red Hat2009-11-05

Migration customer concerns

Question:“What do you think about when confronted with a migration?”Answer:“I don’t think …I worry.”


Are the required resources available?How will the existing systems administration and application development team skills be transitioned?How will retraining be performed?

Skills and Culture

How well will it work?How will the migrated workload be tested?Will the performance and reliability meet business requirements?Will it work the same way on the target platform or will changes in customer, supplier or user interfaces be required?

Operational

Can it be done on time?How much downtime will be required for transition?When can the business support this change?

Schedule

Can it be done within the budget?How will the migration cost be funded?Does the business case have a positive ROI?

Cost

Can it be done?Are required ISV products available on the target platform?What differences need to be addressed such as application APIs, threading and data formats?Are there tools available to help minimize the complexity and risk?

TechnicalKey QuestionsRisk

What migration risks concern customers?

CompetitivePlatforms

IBMPlatforms


IBM Migration Factory: Proven Methodologies for Successful Migrations


IBM Migration Factory objectives

To help minimize the cost of transition/ migration services so they do not become the main objection to moving to IBM–The Migration Factory’s core competencies–Provide and leverage many person-years of

application migration experience–Mitigate and reduce the risk in moving

applications from one platform to another–Reduce the cost of moving applications from one

platform to another–Support success through process, expertise and

project management


What does the Migration Factory offer?

1. Migrations for custom-coded applications, databases and many packaged ISV applications, legacy and UNIX environments

2. In-depth skills for moving Solaris, HP-UX, and other UNIX database and application servers to IBM solutions

3. Integration with Red Hat other IBM service groups

4. Twenty-five years of experience, the people, tools and a proven process enhanced by global IBM support


Migration Factory core competenciesDatabase migration– DB2– Informix®– Oracle– Sybase– SQL Server

Other– z/OS mainframe– Microsoft® Windows®– Unisys– Tandem– HP3000 MPE– OpenVMS

UNIX– IBM AIX, DYNIX/ptx®– x86 Linux®, Linux on Power and

Linux on System z– Sun Solaris– HP HP-UX, HP Tru64 UNIX– DG DG-UX– SGI IRIX– SCO– NCR– AT&T

Package applications– SAP– PeopleSoft– Oracle E-Business Suite


Basic migration types

1. Infrastructure Migrations2. Data Base Migrations3. Custom Code Migrations4. ISV Migrations

– ISV applications … moving their source code to another platform.

– ISV packaged applications … moving ISV functionality to another platform (SAP)


Phase 0

Pre-Sales

Phase 1

Assessment & Planning

10-15%

Phase 2

Migration

20%-40%

Phase 3

Testing

30-60%

Phase 4

Performance & Tuning

5-10%

Phase 5

Training & Deployment

5-15%

Migration Lifecycle

Current percentage of migration effort

Custom Applications

Migration time

Migration com

plexity

Workload migration difficulty

ISV Applications•SAP

•PeopleSoft

•Oracle e-Business Suite

•C/C++

•Java, HTML

•Cobol, scripts

Databases•Rdb

•DB2, Oracle, Sybase, Informix

Infrastructure

• Print and file management• Web• Security/firewall• Technical• Application development• Other

Complexity and time drive migration costs

Moving HP and Sun UNIX workloads to IBM involves four basic types of migration, with varying levels of difficulty.Oracle database migrations are frequently a starting point to introduce IBM hardware.


Key tools and services

Database migration–Vendor supplied tools–Xenobridge for Oracle, Informix, Sybase migrations –Replication Products when required

Custom Application Migration Analyzer (CAMA)–C/C++ application analysis–Solaris API analysis and sizing metric collection–Tru64

Other tools–IBM proprietary–Commercial tools and services–Discovery scripts for database migrations


Migration Factory best practices

Utilize tools wherever possible — standard UNIX tools, commercial tools and our own custom toolsReuse code where ever possible, recode only when necessaryFor custom applications migrate like for like, bugs as well!Code synchronizations available for new development and defect fixesMigrating new applications in development involves too much riskISV applications and databases can be upgraded to new versions as part of the migration process


Migration Factory best practices

Test, test, test … then test again! An integral part of our methodology —it provides the roadmap to success.

Testing practices–Verify against an established baseline–Unit, system and acceptance tests–Use customer-based testing suites whenever

possible


Strategic Migration Planning Process: The First Step Towards a Successful Migration


The Strategic Migration Planning Process

1. Solaris vs. RHEL Ecosystem Analysis – Mapping the Solaris 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 and 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.


Phase 1: Solaris vs. RHEL Ecosystem Analysis

Examine existing Solaris 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.


Ecosystem mapping scenarios

Solaris Functionality to RHEL Infrastructure Application

Solaris Infrastructure Application to RHEL Functionality

Solaris Infrastructure App to RHEL Infrastructure App

Built-in Functionality to Built-in Functionality

© 2009 IBM Corporation© 2009 Red Hat Corporation17 Migrate to the Future: IBM and Red Hat2009-11-05 •17

Common ecosystem component mappings


Phase 2: 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.


Deployment scenarios

“Cloudification”Aggregation

DispersionConsolidation


Phase 3: Organizational Readiness and 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.


Phase 4: The 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.


IBMRed Hat

Clients

IBM and Red Hat: Over ten years helping clients reduce risks and save money


Questions


Technical migration considerations

Development environmentKernel tuningSecurityFilesystemsDebugging, tracing, profilingSoftware managementVirtualization3rd party application considerations


Development environmentCode Compilation– Differences in compilers & flags (gcc vs. cc) – Versions of make (make, nmake, gmake) – Linker option differences– System-specific APIs such as Solaris “doors” can

cause issuesEndianness – the “NUXI” problem– Systems can be “big-endian”, “middle-endian”, or

“little-endian”– A date analogy:

• US date format is middle-endian: 10/06/2009• EU date format is little-endian: 06/10/2009• Big-endian date format would be: 2009/10/06

– For the most part, SPARC, PA-RISC, and IBM Power are big-endian

– Linux / x86 is little-endian– Can cause lots of problems, particularly in programs

that access large amounts of shared memory.


Kernel Ttuning

In many cases, RHEL’s kernel can be tuned dynamically without rebootingIn Solaris, kernel changes are done in /etc/system and require a reboot to take effectSome instant changes are possible in Solaris through tools such as ndd, adb, DtraceIn Linux, pseudo-filesystem /proc is the kernel's memory, available for instant modificationChanges can persist reboots in /etc/sysctl.conf


Security

BART-like functionality available through AIDE (Advanced Intrusion Detection Environment) Tripwire also availableSecurity Enhanced Linux (SELinux) co-developed by the NSA is included with all versions of RHELNo separate “insecure” version of RHEL (Solaris vs. “Secure Solaris”) Common Criteria/EAL4+ certificationServices are disabled by default even after installed or configured to listen to localhost


Filesystems

Solaris: Primarily ZFS and UFS

RHEL: EXT3/4, LVM, GFS, XFS–LVM – Logical Volume Manager

• Physical Volume = physical partition / disk• Volume Group = collection of volumes /

disks• Logical Volume = allocated “slice” from the

Volume Group pool of available space• Filesystem is then created on the LV• Can be resized live (extend/reduce) and

extra PVs can be added or removed live• Snapshot capability

–GFS – Global File System• Clustered LVM


Debugging, tracing, profilingSolaris – Dtrace is very popular and powerful

RHEL and Linux community use SystemTap and Oprofile – RH has core developers on both teams

SystemTap:– Scripting language with full control structures– Millions of probe points in kernel & user spaces– Probe arbitrary statements in code– Symbolically extract arbitrary data at probe point– End-user extendable probe library (tapsets) – Protected probe execution environment– Division by zero, null pointer, infinite loop protection

Oprofile:– System-wide profiling of all running code– Unobtrusive, low overhead, no recompilation– Post-profile analysis


Software managementLinux software is packaged for ease of administration in RPM format–Was “Red Hat Package Manager” now just

“RPM Package Manager”–RPM contains all patches, scripts,

documentation, information–Database keeps track of changes, time

stamps, checksums, etc.Built on dependency mechanism.–Try to install Package_A. It depends on

Package_B. Both will automatically be installed if needed.

GUI frontend and YUM available to solve dependenciesSatellite can handle updates, rollbacks, etc.


Virtualization

Kernel Virtual Machine uses Intel's VT-x CPU extensions to offload virtualization tasks to the CPUEffectively provides new privilege levelRemoves need for hypervisor to scan and rewrite kernel codeExtended Page Tables in NehalemI/O Offloading (VT-D) – PCI Pass-throughSingle Root I/O Virtualization (SR/IOV) –Split PCI devices into virtual onesUses mature, stable, and proven kernelSame security and performance as RHEL


Backup Slides

32


IBM Migration Factory


Migration Factory model

More than 300 trained Migration/Consolidation Engineers in US and IndiaBenefits of a Factory Approach

– Linkage between tools, skills, experience and methods

– Efficient labor models & rapid resource leveling

– Rapid ability to grow and expand to meet project needs

– Provide solutions from customer assist thru end-to-end migration

Value of Closed-loop Process– Efficient migration/server

consolidation requires an understanding of both infrastructure and applications

– Leverage historical data as benchmarks to quickly estimate new engagements

– Consistent feedback between sales and delivery

– Real-time development of ICAP


InfrastructureCustom Applications

DatabaseISV Package Applications

Barclays Bank New York Life BellSouth AT&T Mobility

La Quinta (Informix 4GL)Bloomberg (C/C++)The Home Depot (Informix 4GL/Java/C++)Dow Jones (C/C++/Sybase)Reuters (C/C++/Java)

VerispanDollar Thrifty (Oracle)IVAX (Oracle)Portland General Electric (Oracle)Wells Dairy (Oracle)Pitney Bowes (Oracle)Polo Ralph Lauren (Oracle)Wellington Management (Oracle)

Baylor College of Medicine (SAP)Invensys (SAP)Key Bank (PeopleSoft)Randstad(PeopleSoft)PetSmart (SAP)Pratt & Whitney (SAP) Philips Medical (SAP)Osram Sylvania (SAP)Adecco (PeopleSoft/OEBS)

Sample migrations by workload type

Migrate to the Future: Mitigate risks and reduce ... - IBM to the Future: Mitigate risks and reduce...

Documents

Transcript of Migrate to the Future: Mitigate risks and reduce ... - IBM to the Future: Mitigate risks and reduce...