Red Hat for IBM System z Update v5


Published on

Red Hat for IBM System z Update v5


Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Red Hat for IBM System z Update v5

  1. 1. Red Hat for IBM System z Update Filipe Miranda Global Lead for Linux on IBM System z and Power Systems
  2. 2. Agenda ! • Red Hat Inc. Overview (updated) • Red Hat & IBM Collaboration (updated) • Red Hat Lifecycle Roadmap • RHEL7 (updated) • RH Satellite Overview • High Availability • Customer References
  3. 3. Red Hat Inc Overview
  4. 4. © 2014 IBM Corporation #powersystems 1993 1999 2002 2006 2008 2010 2011 FOUNDED IPO FIRST RELEASE OF ENTERPRISE LINUX JBOSS ACQUIRED RED HAT ENTERPRISE VIRTUALIZATION RELEASED JBOSS EAP 4.3 RELEASED MAKARAACQUIRED GLUSTER ACQUIRED JOINS S&P 500 CLOUD FORMS & OPENSHIFT RELEASED 2012 QUMRANET ACQUIRED 2009 $1 BILLION IN REVENUE OFFICES WORLDWIDE GLUSTER ACQUIRED RED HAT STORAGE RELEASED 80% MORE THAN FORTUNE 500COMPANIES of use PRODUCTS & SOLUTIONS. RED HAT OPEN SOURCE COMPANY $ DOLLAR The FIRST in the WORLD. Source: Red Hat, Inc. BILLION 1 6200+ Employees 0$ Debts 1M + Red Hat certified IT Specialists 90% MORE THAN WORLD Source: Red Hat Inc. $1.5 BILLION DOLLAR * archive/2014/3/red-hat-reports-fourth- quarter-and-fiscal-year-2014-results Fiscal Year 2014 Results: Red Hat is growing 15% Year-over-Year*
  5. 5. Red Hat Open Source Model How we do it
  6. 6. Corporate Contributions to Linux (Kernel 3.3 - 3.10) *The developers who are known to be doing this work on their own, with no financial contribution happening from any company' are not grouped together as 'None' and instead are considered part of the 'long tail,' as are contributors of academic or unknown sponsorship. Red Hat Development Powerhouse Company / Organization *
  7. 7. Red Hat and IBM Collaboration
  8. 8. More than 13 years of collaboration between Red Hat and IBM to offer choice to our customers: Red Hat Enterprise Linux Certified on all IBM platforms System x Power Systems System z
  9. 9. IBM System z Enterprise Class Servers Red Hat Enterprise Linux Hardware Certification z10 EC z196 zEC12 Hardware Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 IBM z10 Enterprise Class (2097) Server 5.1 6.0 —- IBM z196 (2817) Server 5.5 6.0 7.0 IBM zEC12 (2827) Server 5.8 6.3 7.0
  10. 10. z10 BC z114 zBC12 Hardware Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 IBM z10 Business Class (2098) Server 5.2 6.0 — IBM z114 (2818) Server 5.5 6.0 7.0 IBM zBC12 (2828) Server 5.8 6.3 7.0 IBM System z Business Class Servers Red Hat Enterprise Linux Hardware Certification
  11. 11. Red Hat is currently part of IBM’s solutions such as: ! • Offered in zCloud • Embedded as “KVM” in: • IBM SmartCloud • zBX (x86 Blades virtualization) • PureFlex Systems • Embedded in Netezza • IBM’s Watson Cluster • Running on Power Systems
  12. 12. •JBoss® Enterprise Application Platform (JBoss EAP) is supported on a variety of market-leading operating systems, Java™Virtual Machines (JVMs), and database combinations. •IBM JDK is supported (1) and ready to run on Red Hat Enterprise Linux for IBM System z •Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments. JBoss addingValue to your solution Take advantage of Java on Red Hat Enterprise Linux for IBM System z
  13. 13. Source: Red Hat RHEL for System z revenue growth % - installed base WW 35% 81% 10% 18% 28%
  14. 14. Red Hat and IBM LifeCycle Roadmap
  15. 15. Red Hat Enterprise Linux • Stable, mature, commercial product • Extensive Q&A, performance testing • Hardware & Software Certifications • 10yr maintenance • Core ABI compatibility guarantee • Major releases ~2-3yr cycle • Minor releases ~8-12 mo cycle Red Hat Development Model The same for all supported architectures, x86_64, PPC64 and x390x
  16. 16. Fedora • Most current, sets direction for RHEL technologies • Community Supported • Released ~6 mo cycles Red Hat Development Model Benefit from Fedora for s390x! Fedora for Power Systems Project Page ! Become a contributor, talk to package maintainers !
  17. 17. Red Hat extended from 7 to 10 years standard technical support Current Platform Lifecycle *All dates are approximate and subject to change
  18. 18. Red Hat Enterprise Linux 7.0 Public release Jun 2014 • RHEL7 Basic Facts ! • What’s changed ? • What can we benefit from RHEL 7 on s390x? ! • New Enhancements and Expanded Choices ! • What’s System z specific ?
  19. 19. Red Hat Enterprise Linux 7 Basic Facts • Based on Fedora 19 and Kernel 3.10 ! • Supported Architectures: x86_64, IBM Power Systems and System z ! • 64bit! 32-bit libraries will be made available
  20. 20. Red Hat Enterprise Linux 7.0 What is new for RHEL 7 on System z? Application Isolation with Linux Containers Microsoft Windows Interoperability More easy to Install, Deploy and Manage File System Choice Optimal Performance and Security
  21. 21. Red Hat Enterprise Linux 7: Pre-installation tips on System z • RHEL6 would usually need: • Kernel.img • initrd.img • PARM file (GENERIC.PRM) • CONF file • redhat.exec file • RHEL7 will only need, all items from the CONF file were moved to the PARM file and we had a few syntax changes: • Kernel.img • initrd.img • PARM file (GENERIC.PRM) • redhat.exec file CONF file for RHEL6PARM file for RHEL6 New PARM file for RHEL7
  22. 22. • The RHEL 7 installation procedure presents a user friendly interface that allows RHEL to be installed a more comprehensive installation process rather than having 13 linear screens • Easy to go back to a main page • Warnings and errors provided to guide the user Red Hat Enterprise Linux 7: Installer
  23. 23. RHEL 5 RHEL 6 RHEL 7 Red Hat Enterprise Linux 7: System Initialization and service manager • Uses Systemd, a system and service manager ! • Compatible with SysV and LSB init scripts ! • Allows more work to be done concurrently (possibly in parallel) at system startup resulting faster system boot times. ! • Integrates chkconfig + service
  24. 24. ! service httpd start -> systemctl start httpd.service chkconfig httpd on -> systemctl enable httpd.service ! -rwxr-xr-x. 1 root root 2779 Apr 2 11:38 /usr/sbin/service -rwxr-xr-x. 1 root root 40944 Jan 29 08:40 /usr/sbin/chkconfig -rwxr-xr-x. 1 root root 362080 Apr 2 09:30 /usr/bin/systemctl ! ! ! init 3 -> systemctl isolate (or) systemctl isolate Init 5 -> systemctl isolate (or) systemctl isolate ! lrwxrwxrwx. 1 root root 22 Jun 23 23:23 /usr/sbin/init -> ../lib/systemd/systemd ! ! /etc/inittab -> systemctl enable --force SERVICES RUNLEVEL DEFAULT RUNLEVEL Red Hat Enterprise Linux 7: Systemd Crash Course
  25. 25. RHEL6 # service sshd status ! openssh-daemon (pid 3051) is running… !! RHEL7 # systemctl status sshd Red Hat Enterprise Linux 7: Systemd Crash Course [root@train7 ~]# systemctl status sshd sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled) Active: active (running) since Mon 2014-07-14 11:26:59 EDT; 4min 51s ago Process: 1374 ExecStartPre=/usr/sbin/sshd-keygen (code=exited, status=0/SUCCESS) Main PID: 1384 (sshd) CGroup: /system.slice/sshd.service └─1384 /usr/sbin/sshd -D ! Jul 14 11:26:59 systemd[1]: Started OpenSSH server daemon. Jul 14 11:26:59 sshd[1384]: Server listening on port 22. Jul 14 11:26:59 sshd[1384]: Server listening on :: port 22. Jul 14 11:27:26 sshd[2432]: Accepted password for root from port 49...sh2 Hint: Some lines were ellipsized, use -l to show in full.
  26. 26. • SELinux (Provides an extra layer of security, mandatory by Government and Military customers) • Simplified tool chain for troubleshooting • Improved performance ! • Firewalld • firewalld provides a dynamically managed firewall with support for network/firewall zones to define the trust level of network connections or interfaces. # firewall-cmd --state # firewall-cmd --get-active-zones # firewall-cmd --reload # firewall-cmd --panic-on # firewall-cmd --zone=home --remove-service=http # firewall-cmd --permanent --zone=home --add-port=443/tcp Red Hat Enterprise Linux 7: Security
  27. 27. Red Hat Enterprise Linux 7: File Systems - Many choices
  28. 28. Red Hat Enterprise Linux 7: Linux Containers - Application isolation Application isolation mechanism for light-weight, multi-tenancy environments with a single underlying OS
  29. 29. Software packaging concept that typically includes an application and all of its runtime dependencies. ! • Easy to deploy and portable across host systems • Isolates applications on a host operating system. • In RHEL, this is done through: • Control Groups (cgroups) • kernel namespaces • SELinux, sVirt Red Hat Enterprise Linux 7: Linux Containers - Benefits and Key Elements
  30. 30. Red Hat Enterprise Linux 7: Windows Interoperability • Out-of-the-box Linux support of direct interoperability with Active Directory • Automatic detection of the domain controller to join (AD/IDM) • Simple, integrated set-up of the authentication configuration
  31. 31. • Enhanced DASD statistics for PAV and HPF • DASD sanity check to detect path connection error • Architecture level set for IBM System z196 and newer • Support for zEC12 Flash Express (TP) • Support for zEC12 Crypto Express4S • Crypto adapter resiliency • Support of VEPA (Virtual Ethernet Port Aggregator) • Cross Memory Attach for System z • Provide PCHID mapping • Fuzzy live dump for System z (TP) • Two Stage Dumper (TP) • Safe offline interface for DASD devices • Linux support for concurrent Flash MCL updates (TP) • Transactional memory support (for zEC12 and newer) • End-To-End data consistency checking for zfcp (TP) Red Hat Enterprise Linux 7.0 Linux on System z specific features • IPv6 support for qetharp tool • Exploitation of Data Routing for FCP • zipl to automatically calculate boot device ramdisk address • Enhancement in the configuration tool for System z network devices • libhugetlbfs support for System z • Optimized compression library zlib for Linux on System z • Kernel support to improve Java performance for Linux on System z (TP) • Support of transparent large pages for System z • Automated LUN scanning for NPIV only • Implement write protection based dirty page detection • Improve performance of dasdfmt (TP) • Enable LLVM pipe for System z
  32. 32. High Availability for Red Hat Enterprise Linux for IBM System z
  33. 33. High Availability Fail-over, Clustered FileSystem and Load Balancing • Based on the same software source code solution offered by Red Hat on x86 but enhanced for the IBM System z. ! • Supported by SNA on RHEL 6.2+ and RHEL7.0 ! • Technical Support available Globally as a third party add-on directly from the developer - SNA - Standard and Premium 24/7, email and telephone support More Information please contact: David Boyes Sine Nomine Associates +1 703 723 6673
  34. 34. Additional Linux on System z Documentation IBM Redbooks and DeveloperWorks
  35. 35. Customer References of Red Hat Enterprise Linux on IBM System z For a complete list of customer success stories please access:
  36. 36. Danke Thank you Grazie Obrigado Gracias Filipe Miranda Global Lead for Linux on IBM System z and Power Systems
  37. 37. Red Hat Enterprise Linux 6.5 GA Dec 2013 RHEL on Power Features • Performance enhancements • Updated Drivers • More Stable
  38. 38. This feature enables the linux perf tool to use hardware counters that are provided by the CPU-measurement counter facility via an s390x specific performance measurement unit. It provides three sets of counters, the basic- problem state- and crypto-activity counter sets ! This RAS feature simplifies the performance analysis for software on Linux on System z by enabling the usage of performance data within the performance tool. System z performance counters in perf tool
  39. 39. Linux support for concurrent Flash MCL updates This feature is to ensure that concurrent microcode level upgrades (MCL) can be applied without impacting I/O operations to the Flash storage media and to notify users of the changed Flash hardware service level ! This feature implements the System z intrinsic RAS expectations on concurrent microcode upgrade also for the new Flash storage media
  40. 40. Provide resiliency for the AP crypto device driver by detecting the loss of an adapter, reflect it in userspace and trigger adapter recovery where possible. If no transparent recovery is possible the failure should be reflected in user space ! Provide System z typical RAS for the crypto adapters including possible events triggered by Linux guest relocation (LGR) or suspend/resume activities Crypto Adapter Resiliency
  41. 41. Fuzzy live dump for System z This feature provides a tool that can extract the current memory state of the kernel by extracting an elf dump from crash (used on a live system) for filtering with makedumpfile.This dump may not be 100% consistent since the memory recorded may change while being recorded. ! This RAS feature allows Service-personel to help customers that cannot afford to take down their system for problem analysis.
  42. 42. Safe offline interface for DASD devices In addition to the existing functionality for DASD device offline, that sets the device offline and returns outstanding I/O as failed this feature is to provide an additional interface that allows to set a DASD device offline and write all outstanding data to the device before setting offline. ! Give customers the choice to use a "safe offline" of DASD devices with completing all outstanding write requests before the device get offline increases the positive RAS experience and enables customer to use DASDs in in a way they expect them to work.
  43. 43. Support ofVEPA mode OSA (andVSWITCHes on top of it) can be set intoVEPA mode (VEPA =Virtual Ethernet Port Aggregator), to enable forwarding of packets to a physical switch before sending to another virtual machine The switch must be set up in hairpin mode and reflect those packets back, which should get back to an OS instance behind the OSA the packet came from. ! Linux has support for setting port isolation mode ("forward") appropriately. However, it can be that a STOPLAN with an error code shows up.This error is to indicate FORWARD port isolation is not supported or not supported any more (configuration change of the switch). Linux needs to print out an appropriate error message on this STOPLAN event. !
  44. 44. Enhanced efficiency and security control for network traffic between virtual machines on the same server. Offloading switching activities from a virtual switch to a physical switch reduces the computing overhead on the virtual servers and takes advantage of the security, filtering, and management features of the physical switch. There are two scenarios addressed with this feature: ! (1)The STOPLAN flow is only going to occur when an External Switch Port has been configured in VEPA Mode and the Set Access Control has been set to FORWARD and the Set Access Control Primitive completed successfully. When theVEPA setting changes on the External Switch, e.g. disabled by a network administrator OSA will send a STOPLAN on every QDIO Interface defined inVEPA Mode at this time. ! (2) On the initialization flow when the Set Access Control Primitive is issued, if the Switch Port does not supportVEPA Mode orVEPA Mode is turned off, the Set Access Control Primitive will be replied with a Failure Return Code if the FORWARD Mode is set.A STOPLAN will not be sent in this scenario. Support of VEPA mode
  45. 45. Provide PCHID mapping Enable Linux users to determine the physical channel-ID (PCHID) associated with a CHPID. A CHPID is a logical channel-path identifier which is unique only within the context of a single LPAR.The PCHID is a machine-wide unique channel-path identifier which can be used to determine the actual hardware associated with a CHPID or I/O device.The ability to map CHPID to PCHID values is important for maintenance and error determination processes. ! Improve platform RAS value by enabling customers to determine the actual hardware associated with a CHPID (Channel Path ID) that is unique for LPAR context only via a machine wide unique identifier, the Physical Channel ID (PCHID).This feature also enables advanced health checks which rely on PCHID information.