DOCSLIB.ORG

Practical Migration to Linux on System Z

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Practical Migration to Linux on System Z Front cover Practical Migration to Linux on System z Overview and migration methodology Migration analysis Hands-on migration case study Lydia Parziale Joseph Apuzzo Saulo Augusto M Martins da Silva Louis Henderson Manoj Srinivasan Pattabhiraman Richard Sewell ibm.com/redbooks International Technical Support Organization Practical Migration to Linux on System z October 2009 SG24-7727-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (October 2009) This edition applies to z/VM Version 5.3 and Version 5.4, Novell SUSE Linux Enterprise Server Version 10 and Version 11, and Red Hat Enterprise Linux Version 5.3. © Copyright International Business Machines Corporation 2009. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Preface . xv The team who wrote this book . xv Become a published author . xviii Comments welcome. xviii Part 1. Overview and migration methodology . 1 Chapter 1. Migration considerations . 3 1.1 Reason to migrate systems. 4 1.1.1 How green is your data center . 4 1.1.2 The IBM Big Green server consolidation . 7 1.2 Benefits of migrating to Linux on System z . 7 1.3 Reasons to select Linux on System z . 9 1.3.1 System z strengths . 10 1.3.2 Value of Linux on System z. 12 1.3.3 Choosing workloads to migrate to IBM System z . 13 1.4 z/VM virtualization for Linux on IBM System z . 13 1.4.1 Leveraging the power of z/OS for distributed platforms . 15 1.4.2 What is Linux on System z . 15 1.5 Sizing workloads for migration . 17 1.6 Total Cost of Ownership analysis . 18 Chapter 2. Stakeholder considerations. 23 2.1 Stakeholder definitions . 24 2.1.1 Business stakeholders . 24 2.1.2 Information Technology stakeholders . 25 2.2 Assembling the stakeholders . 28 Chapter 3. Migration methodology . 31 3.1 Migration approach . 32 3.1.1 Identify the stakeholders . 33 3.1.2 Pre-assessment . 34 3.1.3 Define success criteria . 34 3.1.4 Finalize the new environmental stack . 34 3.1.5 Pilot proof of concept . 35 3.1.6 Decision to migrate . 36 © Copyright IBM Corp. 2009. All rights reserved. iii 3.1.7 Resource estimation . 36 3.1.8 Actual migration . 37 3.1.9 Verification testing. 37 3.1.10 Verification of success criteria. 38 Chapter 4. Migration Planning checklist . 39 4.1 The Planning checklist . 40 4.2 Hardware Planning checklist . 40 4.3 Product and Tools checklist . 41 4.3.1 Application Implementation checklist . 42 4.3.2 Training checklist . 44 4.3.3 Application Environment checklist. 45 Part 2. Migration analysis. 47 Chapter 5. z/VM and Linux on System z technical concepts . 49 5.1 Virtualization concepts . 50 5.1.1 z/VM Operating System components . 51 5.1.2 Logical partition . 52 5.1.3 CPU. 52 5.1.4 Memory . 52 5.1.5 Disk . 55 5.1.6 Network . 56 Chapter 6. Network analysis. 57 6.1 Network migration overview . 58 6.1.1 Single network scenario . 58 6.1.2 Multiple network scenario . 62 6.2 Steps for a successful network migration . 69 Chapter 7. Storage analysis . 71 7.1 Data migration . 72 7.1.1 Online data migration . 72 7.1.2 Offline data migration . 73 7.1.3 Steps for a successful offline storage migration . 76 7.2 Linux on System z - preinstallation considerations . 76 7.2.1 Linux file system . 77 7.2.2 Shared file system. 80 7.2.3 ECKD and zFCP devices . 82 7.2.4 Logical Volume Manager devices . 82 Chapter 8. Application analysis . 85 8.1 Why to migrate applications . 86 8.2 Which applications can be migrated . 86 iv Practical Migration to Linux on System z 8.2.1 Financial benefits of a migration . 87 8.3 Selecting an application for migration to Linux on System z . 87 8.3.1 Applications unsuitable for migration to Linux on System z . 88 8.3.2 Applications suitable for migration to Linux on System z . 88 8.4 Applications best suited for migration . 89 8.4.1 IBM software . 89 8.4.2 Oracle . 89 8.4.3 Other software. 90 8.4.4 Selecting an application for a proof of concept . 92 8.4.5 Applications not supported on Linux on System z . 93 8.4.6 Application interdependencies . 93 8.5 Successful application migration . 94 8.5.1 Special considerations for migrating a Java application . 94 8.5.2 Special considerations for migrating C++ applications . 94 8.5.3 Steps for an application migration. 96 Chapter 9. Database analysis. 99 9.1 Prior to database migration . 100 9.1.1 Migrating a single instance . 100 9.1.2 Migrating multiple instances . ..
Load more

Recommended publications
  • Opening Presentation
    Mono Meeting. Miguel de Icaza [email protected] October 24, 2006 Mono, Novell and the Community. Mono would not exist without the community: • Individual contributors. • Companies using Mono. • Organizations using Mono. • Companies using parts of Mono. • Google Summer of Code. Introductions. 2 Goals of the Meeting. A chance to meet. • Most of the Novell/Mono team is here. • Many contributors are here. • Various breaks to talk. Talk to others! • Introduce yourself, ask questions. Talk to us! • Frank Rego, Mono's Product Manager is here. • Tell us what you need in Mono. • Tell us about how you use Mono. 3 Project Status Goals Originally: • Improve our development platform on Linux. As the community grew: • Expand to support Microsoft APIs. As Mono got more complete: • Provide a complete cross platform runtime. • Allow Windows developers to port to Linux. 5 Mono Stacks and Goals. MySMQySQLL//PPosstgtrgesrsess EvEovolluutitioonn# # ASP.NET Novell APIs: MMoozzillala Novell iFolder iFolder, LDAP, Identity ADO.NET ApAapchachee MMonoono DesktoGpTK#: GTK# OpNoevenlOl LfDfAiPce GCneomceil# Windows.Forms JavaJa vCa oCommpaatitbilbitiylity Google APIs Microsoft Compatibility Libraries Mono Libraries Mono Runtime (Implementation of ECMA #335) 6 Platforms, CIL, Code Generation. 7 API space Mono 1.0: July 2004 “T-Bone” Mono 1.2: November 2006 “Rump steak” Mono 1.2 bits. Reliability and C# 2.0, .NET 2.0 scalability: • Complete. • With VM support. • ZenWorks and iFolder • Some 2.0 API support. pushed Mono on the server. • IronPython works. • xsp 1.0: 8 request/second. • xsp 1.2: 250 Debugger: request/second. • x86 and x86-64 debugger. GUI • CLI-only, limited in scenarios (no xsp).
    [Show full text]
  • Logview Studio Linux Preparation with Mono
    LogView Studio Linux Preparation with Mono 2014 by Dominik Schmidt [email protected] © 2014 Dominik Schmidt / Holger Hemmecke I LogView Studio Table of Contents Part I Linux Prepare 1 1 SSH Co..n..n..e..c..t. ........................................................................................................................ 1 2 Raspbe..r.r.y.. .P..i. ......................................................................................................................... 4 System Prepar..a..t.i.o...n.. ............................................................................................................................................... 5 Mono .......................................................................................................................................................... 6 Install Mono......................................................................................................................................................... 7 Compile Mon..o.. .f.r..o..m.. .T..A...R....................................................................................................................................... 8 Compile Mon..o.. .f.r..o..m.. .G...I.T........................................................................................................................................ 9 Testing ......................................................................................................................................................... 10 3 Cubie.t.r.u..c..k.. .........................................................................................................................
    [Show full text]
  • Metadefender Core V4.13.1
    MetaDefender Core v4.13.1 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • Manual Técnico Portal Para El Centro De Capacitación Continua De La Fica
    MANUAL TÉCNICO – PORTAL PARA EL CENTRO DE CAPACITACIÓN CONTINUA DE LA FICA MANUAL TÉCNICO PORTAL PARA EL CENTRO DE CAPACITACIÓN CONTINUA DE LA FICA INSTALACIÓN Es necesario instalar Linux Red Hat 8.0 como servidor, agregando los siguientes paquetes mínimos al momento de la instalación: Desktops: - Sistema X Window - Entorno GNOME Aplications: - Editores (Emacs, vi) - Internet gráfica Servers - Herramientas de configuración del servidor - Servidor Web - Servidor de nombres DNS (BIND) - Servidor de bases de datos - Servidor FTP - Servidor de red Development: - Herramientas de desarrollo (automake, gcc, perl, pitón y depuradores) - Desarrollo de software X (aplicaciones para X window) - Desarrollo de software de GNOME (desarrollar GTK+) System - Herramientas de administración (cuentas de usuario, gestión) - Herramientas del sistema PABLO ANDRÉS LANDETA LÓPEZ 1 UTN – FICA -EISI MANUAL TÉCNICO – PORTAL PARA EL CENTRO DE CAPACITACIÓN CONTINUA DE LA FICA - Soporte para impresión Es muy importante instalar la parte de Development, por cuanto vamos a instalar Mono desde su código fuente, y es necesario compilar las librerías utilizando por ejemplo los compiladores de C++ (gcc). Si instalamos Mono utilizando los archivos .rpm al momento de instalar las aplicaciones nos indicará las dependencias necesarias. Una vez que se tiene instalado la versión Red Hat 8.0 de Linux, e instalado la base de datos MySQL, debemos tener los instaladores (código fuente) de Mono que son los siguientes: mono-0.28.tar.gz mcs-0.28.tar.gz xsp-0.5.tar.gz Primeramente abrimos
    [Show full text]
  • ENERGY EFFICIENCY in RESIDENTIAL BUILDINGS in MOZAMBIQUE Measurements and Simulations
    Report TABK-1027 BZ info: TABK-1027 GABRIEL AUZIANE Rygg: 13,22 = 187 sidor Setup (bxh): 369,22 x 252 Upplaga: 120 Mellanblad: grå and Simulations ENERGY EFFICIENCY IN RESIDENTIAL BUI DINGS MOZAMBIQUE - Measurements Färgsidor: ingen begränsn. ENERGY EFFICIENCY IN RESIDENTIAL BUILDINGS IN MOZAMBIQUE Measurements and Simulations GABRIEL AUZIANE Building Doctoral Thesis Science DEPARTMENT OF CONSTRUCTION SCIENCES DIVISION OF BUILDING SCIENCE ISRN LUTVDG/TABK--15/1027--SE (1-176) | ISSN 1103-4467 ISBN 978-91-7623-159-3 (print) | ISBN 978-91-7623-160-9 (pdf) DOCTORAL THESIS ENERGY EFFICIENCY IN RESIDENTIAL BUILDINGS IN MOZAMBIQUE Measurements and Simulations GABRIEL AUZIANE Copyright © Gabriel Auziane 2015. Printed by Media-Tryck LU, Lund, Sweden, April 2015 (Pl). For information, address: Division of Building Science, LTH, Lund University, Box 118, SE-221 00 Lund, Sweden. Homepage: http://www.bkl.lth.se Acknowledgements I am deeply thankful to my main supervisors, Professor Bertil Fredlund and Associate Professor Susanne Heyden, my co-supervisors Dr. Kurt Källblad, Dr. Daniel Baloi, and the former Head of the Department of Construction Sciences, Professor Göran Sandberg and Professor Anne Landin for offering me the possibility of working in this project and also for support, encouragement, inspiration and patience over the years, without their help and advice this thesis work would never have been successful. Furthermore, I would like to thank the Head of the Division of Structural Mechanics, Professor Erik Serrano and Professors Jesper Arfvidsson and Petter Wallentén, for their supervision of the work and great help in the overall process of this research. I thank Asdi/SAREC for this research receiving financial support through Lund University and Eduardo Mondlane University under the coordination of Prof.
    [Show full text]
  • Programming with Windows Forms
    A P P E N D I X A ■ ■ ■ Programming with Windows Forms Since the release of the .NET platform (circa 2001), the base class libraries have included a particular API named Windows Forms, represented primarily by the System.Windows.Forms.dll assembly. The Windows Forms toolkit provides the types necessary to build desktop graphical user interfaces (GUIs), create custom controls, manage resources (e.g., string tables and icons), and perform other desktop- centric programming tasks. In addition, a separate API named GDI+ (represented by the System.Drawing.dll assembly) provides additional types that allow programmers to generate 2D graphics, interact with networked printers, and manipulate image data. The Windows Forms (and GDI+) APIs remain alive and well within the .NET 4.0 platform, and they will exist within the base class library for quite some time (arguably forever). However, Microsoft has shipped a brand new GUI toolkit called Windows Presentation Foundation (WPF) since the release of .NET 3.0. As you saw in Chapters 27-31, WPF provides a massive amount of horsepower that you can use to build bleeding-edge user interfaces, and it has become the preferred desktop API for today’s .NET graphical user interfaces. The point of this appendix, however, is to provide a tour of the traditional Windows Forms API. One reason it is helpful to understand the original programming model: you can find many existing Windows Forms applications out there that will need to be maintained for some time to come. Also, many desktop GUIs simply might not require the horsepower offered by WPF.
    [Show full text]
  • 2015 Open Source Yearbook
    Opensource.com/yearbook . ........ OPENSOURCE.COM ................... Opensource.com publishes stories about creating, adopting, and sharing open source solutions. Visit Opensource.com to learn more about how the open source way is improving technologies, education, business, government, health, law, entertainment, humanitarian efforts, and more. Submit a story idea: https://opensource.com/story Email us: [email protected] Chat with us in Freenode IRC: #opensource.com Twitter @opensourceway: https://twitter.com/opensourceway Google+: https://plus.google.com/+opensourceway Facebook: https://www.facebook.com/opensourceway Instagram: https://www.instagram.com/opensourceway FROM THE EDITOR ............................. Dear Open Source Yearbook reader, The “open source” label was created back in 1998, not long after I got my start in tech publishing [1]. Fast forward to late 2014, when I was thinking about how much open source technologies, commu- nities, and business models have changed since 1998. I realized that there was no easy way—like a yearbook—to thumb through tech history to get a feel for open source. Sure, you can flip through the virtual pages of a Google search and read the “Best of” lists collected by a variety of technical publications and writers, much like you can thumb through newspapers from the 1980s to see the how big we wore our shoulder pads, neon clothing, and hair back then. But neither research method is particularly efficient, nor do they provide snapshots that show diversity within communities and moments of time. The idea behind the Open Source Yearbook is to collaborate with open source communities to collect a diverse range of stories from the year.
    [Show full text]
  • KEMPER PROFILER Addendum 8.6 Legal Notice
    KEMPER PROFILER Addendum 8.6 Legal Notice This manual, as well as the software and hardware described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice and should not be construed as a commitment by Kemper GmbH. Kemper GmbH assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, recording, by smoke signals or otherwise without the prior written permission of Kemper GmbH. KEMPER™, PROFILER™, PROFILE™, PROFILING™, PROFILER PowerHead™, PROFILER PowerRack™, PROFILER Stage™, PROFILER Remote™, KEMPER Kone™, KEMPER Kabinet™, KEMPER Power Kabinet™, KEMPER Rig Exchange™, KEMPER Rig Manager™, PURE CABINET™, and CabDriver™ are trademarks of Kemper GmbH. All features and specifications are subject to change without notice. (Rev. September 2021). © Copyright 2021 Kemper GmbH. All rights reserved. www.kemper-amps.com Table of Contents What is new? 1 What is new in version 8.6? 2 Double Tracker 2 Acoustic Simulator Enhancements 3 Auto Swell Sensitivity 3 PROFILER Stage Wi-Fi Enhancement 4 What is new in version 8.5? 5 Important Hints for Users of KEMPER Power Kabinet 5 KEMPER Rig Manager for iOS®* 6 Wi-Fi with PROFILER Stage 9 What is new in version 8.2? 11 Power Amp
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Operations & Installation Guide: HD-XSP
    Crestron HD-XSP 7.1 High-Definition Professional Surround Sound Processor Operations & Installation Guide Important Safety Instructions • Read these instructions. WARNING: • Keep these instructions. • Heed all warnings. TO REDUCE THE RISK OF FIRE OR ELECTRIC SHOCK, DO NOT EXPOSE THIS APPARATUS TO RAIN OR • Follow all instructions. MOISTURE. THE APPARATUS SHALL NOT BE EXPOSED • Do not use this apparatus near water. TO DRIPPING OR SPLASHING. OBJECTS FILLED WITH • Clean only with dry cloth. LIQUIDS, SUCH AS VASES, SHOULD NOT BE PLACED • Do not block any ventilation openings. Install in accordance ON THE APPARATUS. with the manufacturer's instructions. WARNING: • Do not install near any heat sources such as radiators, heat registers, stoves, or other apparatus (including amplifiers) TO PREVENT ELECTRIC SHOCK, DO NOT REMOVE that produce heat. COVER. THERE ARE NO USER SERVICEABLE PARTS • Do not defeat the safety purpose of the polarized or INSIDE. ONLY QUALIFIED SERVICE PERSONNEL grounding-type plug. A polarized plug has two blades with SHOULD PERFORM SERVICE. one wider than the other. A grounding-type plug has two blades and a third grounding prong. The wide blade or the third prong are provided for your safety. If the provided plug does not fit into your outlet, consult an electrician for replacement of the obsolete outlet. • Protect the power cord from being walked on or pinched The lightning flash with arrowhead symbol, within an particularly at plugs, convenience receptacles, and the point equilateral triangle, is intended to alert the user to the where they exit from the apparatus. presence of uninsulated “dangerous voltage” within the product's enclosure t hat may be of sufficient magnitude • Only use attachments/accessories specified by the to constitute a risk of electric shock to persons.
    [Show full text]
  • Metadefender Core V4.17.3
    MetaDefender Core v4.17.3 © 2020 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of MetaDefender Core 14 1. Quick Start with MetaDefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Process Files with MetaDefender Core 21 2. Installing or Upgrading MetaDefender Core 22 2.1. Recommended System Configuration 22 Microsoft Windows Deployments 22 Unix Based Deployments 24 Data Retention 26 Custom Engines 27 Browser Requirements for the Metadefender Core Management Console 27 2.2. Installing MetaDefender 27 Installation 27 Installation notes 27 2.2.1. Installing Metadefender Core using command line 28 2.2.2. Installing Metadefender Core using the Install Wizard 31 2.3. Upgrading MetaDefender Core 31 Upgrading from MetaDefender Core 3.x 31 Upgrading from MetaDefender Core 4.x 31 2.4. MetaDefender Core Licensing 32 2.4.1. Activating Metadefender Licenses 32 2.4.2. Checking Your Metadefender Core License 37 2.5. Performance and Load Estimation 38 What to know before reading the results: Some factors that affect performance 38 How test results are calculated 39 Test Reports 39 Performance Report - Multi-Scanning On Linux 39 Performance Report - Multi-Scanning On Windows 43 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3.
    [Show full text]
  • What Every Engineer Should Know About Developing Real-Time
    Contents What Every Engineer Should Know: Series Statement................ xv Preface. ................................................................. xvii Author. ................................................................. xix Acknowledgments . ................................................... xx List of Abbreviations................................................... xxi 1 Development Processes . ......................................... 1 1.1 Introduction ............................................... 1 1.2 Concept and Market ...................................... 5 1.3 People and Disciplines . .................................. 7 1.4 Architecting and Architecture . ......................... 8 1.5 Phases of a Project . ....................................... 16 1.6 Scheduling. ................................................ 19 1.7 Documentation . ........................................... 21 1.8 Requirements and Standards ............................. 24 1.9 Analysis . ................................................ 30 1.10 Design Trade-Offs. ....................................... 31 1.11 Tests . .................................................... 38 1.12 Integration. ................................................ 42 1.13 Manufacturing. ........................................... 44 1.14 Support .................................................... 45 1.15 Disposal . ................................................ 47 1.16 Liability.................................................... 48 1.17 Priorities. ...............................................
    [Show full text]