RHEL Strategic Migration RHEL Strategic Migration PlanningPlanning

Michael LessardMichael LessardSolutions ArchitectSolutions Architect

From Unix and WindowsFrom Unix and Windows

Richard SéguinRichard SéguinFederal Account ManagerFederal Account Manager

Michael LessardMichael LessardSolutions ArchitectSolutions Architect

Christine StegerChristine StegerCanada Sales ManagerCanada Sales Manager

2

Intros & Objectives

Red Hat Overview

Unix migration

Windows migration

Questions

Red Hat Overview

4

Company Vital StatsCompany Vital Stats

Headquarters in Raleigh, NCHeadquarters in Raleigh, NC

Founded in 1993Founded in 1993

Over 3,200 employees in 65 offices worldwide, 75 employees in CanadaOver 3,200 employees in 65 offices worldwide, 75 employees in Canada

Cash and investments: $959 millionCash and investments: $959 million

Debt: $0Debt: $0

FY10 revenues: $748 million, 15% increase from FY09FY10 revenues: $748 million, 15% increase from FY09

IPO, 1999 (NYSE: RHT)IPO, 1999 (NYSE: RHT)

Added to the S&P 500 in July 2009Added to the S&P 500 in July 2009

Forbes 50 Forbes 50

Red Hat - Overview

5

Red Hat - Overview

7

● Red Hat is the trusted, Market share leader in Open SourceRed Hat is the trusted, Market share leader in Open Source

● 1000+ Certified Hardware Platforms1000+ Certified Hardware Platforms

● 2200+ Certified ISV & 3500+ Certified Applications2200+ Certified ISV & 3500+ Certified Applications

● 75% of Red Hat customers plan to EXPAND their Red Hat footprint75% of Red Hat customers plan to EXPAND their Red Hat footprint23% plan to maintain current levels (Piper Jaffray 2009 survey)23% plan to maintain current levels (Piper Jaffray 2009 survey)

● Top Quartile Performance Top Quartile Performance ● +40% annual growth rate over the past 5 years+40% annual growth rate over the past 5 years● No. 11 on Forbes' 2009 survey of the 25 fastest-growing US Tech companiesNo. 11 on Forbes' 2009 survey of the 25 fastest-growing US Tech companies● Added to the S&P 500 in JulyAdded to the S&P 500 in July

Red Hat - Overview

From Unix to LinuxFrom Unix to Linux

Three Main Objections to Unix/RISC Migrations

• Red Hat Enterprise Linux on x86 hardware doesn’t have the Reliability, Availability, and Serviceability (RAS) features required by my mission-critical applications.

• Linux can’t vertically scale to meet my most demanding, high-performance workloads.

• Migrating applications off of RISC platforms is expensive, difficult, and a high-risk endeavor.

Migration is not rocket science!(but it’s probably more complex than you think!)

RAS FeaturesRAS Features

MemoryIntel® SMI Lane Failover

Intel® SMI Clock Fail OverIntel® SMI Packet Retry

Intel® Scalable Memory Interconnect

QPIQPI Self-Healing

Intel QPI Protocol ProtectionIntel QPI Packet RetryQPI Clock Fail Over

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 proprietary platforms

• Now available on more efficient mainstream platforms

I/O HubPCI-E Hot Plug

CPU/SocketOS CPU Onlining

Partitioning Via VirtualizationElectronically Isolated Partitioning

Memory

QPI

• 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

bullet-proof this support

• Hardware-Only Plus RHEL 5 enablement moves the bar even higher

A Focus on RAS: New With RHEL 5.5

I/O Hub

CPU/Socket

Memory

QPI

• 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• Machine Check Architecture (MCA) recovery• Corrupt Data Containment• Corrected Machine Check Interrupt (CMCI)• Physical CPU Board Hot Add/remove

• Intel Quickpath Interconnect• QPI Viral Mode

• I/O Hub• Physical IOH Hot Add• Dynamic/OS IOH On-lining (capacity change)

A Focus on RAS: Coming in RHEL 6

ScalabilityScalability

Nehalem-EX – Extreme Scalability

4 Sockets / 64 Threads

Intel® Scalable Memory Interconnect with Buffers

2X Memory Capacity

16 DIMMs per Socket

64 DIMMs per platform

1 Terabyte of memory (4skt)

Advanced Virtualization & I/O Technologies

Nehalem-EX Performance Highlights

• Early benchmarks are promising:

• Dell SPECint on PE R810 (360) vs. Sun SPARC T5440 (338)

• But at 1/5 the cost!

• Dell PowerEdge R910 server achieved a SPECfp_rate_base2006 score of 482, an 89.8 percent increase over the Sun SPARC Enterprise T5440 server with a score of 254

• Dell PowerEdge R910 server achieved a SPECjbb2005 score of 1,868,708, a 122.1 percent increase over the Sun SPARC Enterprise T5440 server

• NEC 8-socket running SAS benchmark

• Linear scaling, SAS is extremely pleased with the results

• SAP Benchmarks using KVM virtualization showing linear guest scaling, and linear socket scaling

Results – Comparing I/O Throughputs

Twice more load, twice more resources, constant elapsed Twice more load, twice more resources, constant elapsed time = linear scalability!time = linear scalability!

SAS Real Time Ave Sustained MB/s Peak MB/s Total IO in GB0

200

400

600

800

1000

1200

1400

1600

1800

2000

RHEL5.4z w NEC Intel EX 64 core Using SAS mixed analytics IO workload

32 core

64 core

Pe

rfo

rma

nc

e (

2x

loa

d, 2

x T

ime

+ IO

)

Risk EliminationRisk Elimination

The Strategic Migration Planning Process

Unix to RHEL Ecosystem Analysis – Mapping the Unix ecosystem into the RHEL ecosystem and creating a RHEL Standard Operating Environment (SOE)

1

2

3

4

5

Functional Applications Analysis – High level analysis of business applications to be migrated.

Organizational Readiness & Risk Analysis – Analysis of organizational readiness factors, project risks, and risk mitigation strategies.

Strategic Migration Roadmap Creation – Combining everything into a single, holistic roadmap for migration.

Migration Implementation – Execution of the Strategic Migration Roadmap.

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.

Ecosystem Mapping Scenarios

Built-in Functionality to Built-in Functionality

Solaris Infrastructure App to RHEL Infrastructure App

Solaris Infrastructure Application to RHEL Functionality

Solaris Functionality to RHEL Infrastructure Application

Common Ecosystem Component Mappings

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

Deployment Scenarios

Consolidation Dispersion

Aggregation Cloud Migration

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.

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

Unix to RHEL MigrationUnix to RHEL Migration

Technical ConsiderationsTechnical Considerations

Technical Migration Considerations

• Development Environment

• Kernel Tuning

• Security

• Filesystems

• Debugging, Tracing, Profiling

• Software Management

• Virtualization

• 3rd Party Application Considerations

Development Environment

• Code 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

issues

• Endianness – 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 Tuning

• In many cases, RHEL’s kernel can be tuned dynamically without rebooting

• In Solaris, kernel changes are done in /etc/system and require a reboot to take effect

• Some instant changes are possible in Solaris through tools such as ndd, adb, Dtrace

• In Linux, pseudo-filesystem /proc is the kernel's memory, available for instant modification

• Changes can persist reboots in /etc/sysctl.conf

Security

• BART-like functionality available through AIDE (Advanced Intrusion Detection Environment)

• Tripwire also available• Security Enhanced Linux (SELinux) co-

developed by the NSA is included with all versions of RHEL

• No separate “insecure” version of RHEL (Solaris vs. “Secure Solaris”)

• Common Criteria/EAL4+ certification• Services are disabled by default even after

installed or configured to listen to localhost

File Systems

• 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

• Solaris – 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

Debugging, Tracing, Profiling

Software Management

• Linux 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 dependencies

• Satellite can handle updates, rollbacks, etc.

Virtualization

• Kernel Virtual Machine uses Intel's VT-x CPU extensions to offload virtualization tasks to the CPU

• Effectively provides new privilege level

• Removes need for hypervisor to scan and rewrite kernel code

• Extended Page Tables in Nahalem

• I/O Offloading (VT-D) – PCI Pass-through

• Single Root I/O Virtualization (SR/IOV) – Split PCI devices into virtual ones

• Uses mature, stable, and proven kernel

• Same security and performance as RHEL

3rd Party Application Considerations

• Thousands of 3rd party applications are certified on RHEL• https://www.redhat.com/wapps/partnerlocator/web/home.html

• Check Red Hat Software Catalog:• https://www.redhat.com/wapps/isvcatalog/home.html

• Check ISV site

Unix to RHEL MigrationUnix to RHEL Migration

Customer Success StoriesCustomer Success Stories

Customer Success Stories

City of Chicago

Carving Out CostMigrated their mission critical Oracle database environment to Red Hat Enterprise Linux on HP servers because they needed to:

•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.

Customer Success Stories (cont.)

Whole Foods

Management & ScaleMigrated to a Red Hat solution to obtain an easy-to-use and reliable systems management solution that enabled increased productivity and reduced costs. Whole Foods needed:

•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.

Customer Success Stories (cont.)

NYSE Euronext

Innovating For Success

Migrated to Red Hat solutions so NYSE Euronext could focus on diversifying its product base and developing a global platform for trading. To achieve this, they needed:

•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/

Windows MigrationWindows Migration

Must be fast

Must Scale

Need to move from proprietary RISC machines to industry-standard x86 servers

Want ability to take advantage of multicore x86 hardware

Would like to deploy virtualization for further savings

Performance

Windows? No. Red Hat Enterprise Linux.

Cost

Your Double-Edged Challenge

SPECjbb2005 Benchmark

Java faster on Red Hat Enterprise Linux than on Windows

TPC Benchmark results

Red Hat Enterprise Linux: Faster and less expensive than Windows

46

OS choices for the Content Management server

Microsoft

Windows Server 2008 Enterprise* Edition

- $3999 License per server- Add 20%/yr Software Assurance- Phone support requires - Requires the purchase of Client Access-Licenses (CALs) to support more than 25 users ($200 for each additional 5 users)

Red Hat

Red Hat Enterprise Linux Standard

- $799 Subscription/Server- All updates and patches included- Web based support unlimited Incidents- Unlimited number of users

*- Windows Server 2008 Enterprise Edition license includes 25 CALs

Content Management Servers(clustered)

Attributes/requirements:

Allow multiple users to access to shared content cluster

Support adding users with minimal interuption or cost

47

Operating system costs for CMS server

Red Hat Enterprise Linux costsremain fixed regardless of the number of users being supported

Questions ?Questions ?