DOCSLIB.ORG

Getting Started with Z/OS Container Extensions and Docker

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Getting Started with Z/OS Container Extensions and Docker Front cover Getting started with z/OS Container Extensions and Docker Lydia Parziale Zach Burns Marco Egli Redelf Janßen Volkmar Langer Subhajit Maitra Edward McCarthy Eric Marins Jim Newell Redbooks IBM Redbooks Getting started with z/OS Container Extensions November 2019 SG24-8457-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (November 2019) This edition applies to z/OS Version 2 Release 4, Program Numner 5650-ZOS with APARs OA58008 and at least OA58267. © Copyright International Business Machines Corporation 2019. 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 . ix Trademarks . .x Preface . xi Authors. xi Now you can become a published author, too! . xiii Comments welcome. xiii Stay connected to IBM Redbooks . xiii Chapter 1. Introduction. 1 1.1 z/OS Container Extensions overview . 2 1.2 Container concepts . 2 1.2.1 Why do we have containers . 4 1.2.2 Docker overview . 6 1.3 zCX architecture . 9 1.4 Why use z/OS Container Extensions . 13 1.4.1 Qualities of service . 14 1.4.2 Colocation of applications and data . 14 1.4.3 Security . 16 1.4.4 Consolidation . 17 1.4.5 Example use cases. 18 1.5 Additional considerations . 18 Chapter 2. z/OS Container Extensions planning . 19 2.1 Prerequisites . 20 2.1.1 IBM Z hardware . 20 2.1.2 z/OS Version 2, Release 4 . 24 2.1.3 z/OS Management Facility (z/OSMF) . 25 2.1.4 Base DASD requirements. 27 2.1.5 Planning for network connectivity . 31 2.2 Planning for containers . 36 2.3 Private registry considerations . 36 2.4 Backup and recovery considerations . 36 Chapter 3. Security - Overview . 39 3.1 zCX instance security . 40 3.1.1 Implications of zCX running as a started task. 40 3.1.2 zCX RACF planning . 40 3.1.3 RACF groups and user IDs for zCX . 41 3.1.4 zFS files and VSAM linear data sets. 41 3.1.5 USS directory and files . 42 3.1.6 TCPIP Networking . 43 3.1.7 z/OSMF. 43 3.1.8 Other data sets . 43 3.2 Security within the zCX instance. 43 3.2.1 Linux in the zCX instance . 43 3.2.2 The SSH container . 43 3.2.3 zCX administration user IDs . 44 3.3 Docker in zCX versus Docker on distributed. 45 © Copyright IBM Corp. 2019. All rights reserved. iii 3.3.1 Docker capabilities of the SSH container . 45 3.3.2 Considerations regarding the mounting of file systems . 45 Chapter 4. Provisioning and managing your first z/OS Container . 47 4.1 Overview of zCX provisioning process . 48 4.2 RACF planning . 48 4.2.1 Overview . 48 4.2.2 The zCX Admin user ID . 49 4.2.3 Planning the first logon to a zCX instance . 49 4.2.4 Create RACF groups . 50 4.2.5 Create RACF user IDs . 50 4.2.6 Create SSH Keys . 51 4.3 USS planning . 52 4.3.1 zCX directories . 52 4.4 z/OSMF . 53 4.4.1 z/OSMF configuration . 53 4.5 Configure TCPIP addresses . 55 4.6 SMS planning . 57 4.7 zCX property file . 58 4.7.1 Customizing the properties file . 58 4.7.2 Setting the SSH key in property file . 59 4.8 Run zCX provisioning workflow. 60 4.8.1 Log on to z/OSMF. 60 4.8.2 Select the zCX provisioning workflow . 61 4.8.3 Execute the first step of the workflow . ..
Load more

Recommended publications
  • IBM Z Systems Introduction May 2017
    IBM z Systems Introduction May 2017 IBM z13s and IBM z13 Frequently Asked Questions Worldwide ZSQ03076-USEN-15 Table of Contents z13s Hardware .......................................................................................................................................................................... 3 z13 Hardware ........................................................................................................................................................................... 11 Performance ............................................................................................................................................................................ 19 z13 Warranty ............................................................................................................................................................................ 23 Hardware Management Console (HMC) ..................................................................................................................... 24 Power requirements (including High Voltage DC Power option) ..................................................................... 28 Overhead Cabling and Power ..........................................................................................................................................30 z13 Water cooling option .................................................................................................................................................... 31 Secure Service Container .................................................................................................................................................
    [Show full text]
  • Of Friday 13 June 2008 Supplement No. 1 Birthday Honours List — United Kingdom
    05-06-2008 13:04:14 [SO] Pag Table: NGSUPP PPSysB Job: 398791 Unit: PAG1 Number 58729 Saturday 14 June 2008 http://www.london-gazette.co.uk B1 [ Richard Gillingwater. (Jun. 14, 2008). C.B.E. Commander of the Order of the British Empire, 2008 Birthday Honours, No. 58729, Supp. No. 1, PDF, p. B7. London Gazette. Reproduced for educationaly purposes only. Fair Use relied upon. ] Registered as a newspaper Published by Authority Established 1665 of Friday 13 June 2008 Supplement No. 1 Birthday Honours List — United Kingdom CENTRAL CHANCERY OF Dr. Philip John Hunter, C.B.E., Chief Schools THE ORDERS OF KNIGHTHOOD Adjudicator. For services to Education. Moir Lockhead, O.B.E., Chief Executive, First Group. St. James’s Palace, London SW1 For services to Transport. 14 June 2008 Professor Andrew James McMichael, F.R.S., Professor of Molecular Medicine and Director, Weatherall The Queen has been graciously pleased, on the occasion Institute of Molecular Medicine, University of Oxford. of the Celebration of Her Majesty’s Birthday, to signify For services to Medical Science. her intention of conferring the honour of Knighthood William Moorcroft, Principal, TraVord College. For upon the undermentioned: services to local and national Further Education. William Desmond Sargent, C.B.E., Executive Chair, Better Regulation Executive, Department for Business, Enterprise and Regulatory Reform. For services to Knights Bachelor Business. Michael John Snyder. For services to Business and to the City of London Corporation. Paul Robert Stephenson, Q.P.M., Deputy Commissioner, Dr. James Iain Walker Anderson, C.B.E. For public and Metropolitan Police Service.
    [Show full text]
  • Best Practices and Getting Started Guide for Oracle on IBM Linuxone
    Front cover Best practices and Getting Started Guide for Oracle on IBM LinuxONE Susan Adamovich Sam Amsavelu Srujan Jagarlamudi Raghu Malige Michael Morgan Paul Novak David J Simpson Redpaper International Technical Support Organization Best practices and Getting Started Guide for Oracle on IBM LinuxONE June 2020 REDP-5499-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (June 2020) This edition applies to Oracle 12c, Release 2. This document was created or updated on June 2, 2020. © Copyright International Business Machines Corporation 2020. 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 . vii Trademarks . viii Preface . 1 Authors. 1 Now you can become a published author, too! . 2 Comments welcome. 3 Stay connected to IBM Redbooks . 3 Chapter 1. Running Linux virtual servers under IBM z/VM . 5 1.1 z/VM fundamentals . 6 1.2 Pre-requisites and assumptions . 6 1.2.1 Pre-requisites . 6 1.2.2 Assumptions . 6 1.3 Configuring a workstation for mainframe access . 7 1.3.1 3270 emulators . 7 1.3.2 Virtual Network Computing client . 7 1.3.3 Connecting from a Linux workstation . 8 1.3.4 Connecting from a MacOS workstation. 8 1.3.5 Connecting from a Windows workstation . 9 1.4 Service validation and notice subscription . 10 1.4.1 RSU validation . 10 1.4.2 Subscribing to service notifications. 10 1.5 Tailoring z/VM for Linux workloads .
    [Show full text]
  • 1. D-Bus a D-Bus FAQ Szerint D-Bus Egy Interprocessz-Kommunikációs Protokoll, És Annak Referenciamegvalósítása
    Az Udev / D-Bus rendszer - a modern asztali Linuxok alapja A D-Bus rendszer minden modern Linux disztribúcióban jelen van, sőt mára már a Linux, és más UNIX jellegű, sőt nem UNIX rendszerek (különösen a desktopon futó változatok) egyik legalapvetőbb technológiája, és az ismerete a rendszergazdák számára lehetővé tesz néhány rendkívül hasznos trükköt, az alkalmazásfejlesztőknek pedig egyszerűen KÖTELEZŐ ismerniük. Miért ilyen fontos a D-Bus? Mit csinál? D-Bus alapú technológiát teszik lehetővé többek között azt, hogy közönséges felhasználóként a kedvenc asztali környezetünkbe bejelentkezve olyan feladatokat hajtsunk végre, amiket a kernel csak a root felasználónak engedne meg. Felmountolunk egy USB meghajtót? NetworkManagerrel konfiguráljuk a WiFi-t, a 3G internetet vagy bármilyen más hálózati csatolót, és kapcsolódunk egy hálózathoz? Figyelmeztetést kapunk a rendszertől, hogy új szoftverfrissítések érkeztek, majd telepítjük ezeket? Hibernáljuk, felfüggesztjük a gépet? A legtöbb esetben ma már D-Bus alapú technológiát használunk ilyen esetben. A D-Bus lehetővé teszi, hogy egymástól függetlenül, jellemzően más UID alatt indított szoftverösszetevők szabványos és biztonságos módon igénybe vegyék egymás szolgáltatásait. Ha valaha lesz a Linuxhoz professzionális desktop tűzfal vagy vírusirtó megoldás, a dolgok jelenlegi állasa szerint annak is D- Bus technológiát kell használnia. A D-Bus technológia legfontosabb ihletője a KDE DCOP rendszere volt, és mára a D-Bus leváltotta a DCOP-ot, csakúgy, mint a Gnome Bonobo technológiáját. 1. D-Bus A D-Bus FAQ szerint D-Bus egy interprocessz-kommunikációs protokoll, és annak referenciamegvalósítása. Ezen referenciamegvalósítás egyik összetevője, a libdbus könyvtár a D- Bus szabványnak megfelelő kommunikáció megvalósítását segíti. Egy másik összetevő, a dbus- daemon a D-Bus üzenetek routolásáért, szórásáért felelős.
    [Show full text]
  • Introducing Linux on IBM Z Systems IT Simplicity with an Enterprise Grade Linux Platform
    Introducing Linux on IBM z Systems IT simplicity with an enterprise grade Linux platform Wilhelm Mild IBM Executive IT Architect for Mobile, z Systems and Linux © 2016 IBM Corporation IBM Germany What is Linux? . Linux is an operating system – Operating systems are tools which enable computers to function as multi-user, multitasking, and multiprocessing servers. – Linux is typically delivered in a Distribution with many useful tools and Open Source components. Linux is hardware agnostic by design – Linux runs on multiple hardware architectures which means Linux skills are platform independent. Linux is modular and built to coexist with other operating systems – Businesses are using Linux today. More and more businesses proceed with an evolutionary solution strategy based on Linux. 2 © 2016 IBM Corporation What is IBM z Systems ? . IBM z Systems is the family name used by IBM for its mainframe computers – The z Systems families were named for their availability – z stands for zero downtime. The systems are built with spare components capable of hot failovers to ensure continuous operations. IBM z Systems paradigm – The IBM z Systems family maintains full backward compatibility. In effect, current systems are the direct, lineal descendants of System/360, built in 1964, and the System/370 from the 1970s. Many applications written for these systems can still run unmodified on the newest z Systems over five decades later. IBM z Systems variety of Operating Systems – There are different traditional Operating Systems that run on z Systems like z/OS, z/VSE or TPF. With z/VM IBM delivers a mature Hypervisor to virtualize the operating systems.
    [Show full text]
  • 2020 Linux on IBM Z and Linuxone Client Workshop November 9-13
    2020 Linux on IBM Z and LinuxONE Client Workshop November 9-13 Securing Workloads with Red Hat OpenShift Container Platform on IBM Z / LinuxONE — Pradeep Parameshwaran Security & Compliance Lead, Linux on IBM Z & LinuxONE [email protected] Linux on IBM Z and LinuxONE Client WS 2020 / © 2020 IBM Corporation Contents • Why OpenShift on IBM Z ? • The cloud with the Privacy and Security • Deployment architecture: OpenShift on IBM Z • Security blueprint: OpenShift on IBM Z • Summary of native and augmented security capabilities IDC estimates that 71% of organizations are in the process of implementing containers and orchestration or are already using them regularly. Containers are the next generation of software-defined compute that enterprises will leverage to accelerate their digital transformation initiatives,” says Gary Chen, Research Director at IDC. “IDC estimates that 71% of organizations are in the process of implementing containers and orchestration or are already using them regularly, and IDC forecasts that the worldwide container infrastructure software opportunity is growing at a 63.9 % 5-year CAGR and is predicted to reach over $1.5B by 2022. 3 Why Red Hat OpenShift on IBM Z? OpenShift a smart Kubernetes platform 5 Build once • Fully integrated and automated architecture • Seamless Kubernetes deployment on any cloud or on-premises environment • Fully automated installation, from cloud infrastructure to OS to application services • One click platform and application updates • Auto-scaling of cloud resources • Enterprise-grade security
    [Show full text]
  • IBM Cloud Private with Linux on Z
    IBM Cloud Solution Brief IBM Cloud Private with Linux on IBM Z Empower how you build, deploy and manage cloud-native applications Introduction Highlights Many organizations have unique data sensitivity needs, such as internal policies, government regulations or industry compliance requirements. • Offers the benefits of a public cloud on a security-rich, scalable private cloud As a result, these organizations typically require private cloud. Yet in a platform for developing and delivering world of changing business demands, they also need to run demanding cloud-native apps applications and use multiple services both on-premise and on multiple • Helps make heritage applications cloud- clouds for the sake of agility. ready • Helps protect confidential and proprietary IBM Cloud™ Private with Linux® on IBM Z® provides the advantages of a Kubernetes and Docker workloads with IBM Secure Service Containers private cloud on a server platform optimized for data and cognitive • Enables organizations to build new services, and is designed to deliver the benefits of a public cloud in a microservice-based apps for improved security-rich, scalable and reliable environment. It enables enterprises to agility and innovation accelerate innovation using modern agile processes, integrates with • Designed to more securely use data and existing systems, and provides a strategic platform for multi-cloud services from external private cloud integration while maintaining the control and compliance that sources organizations need. • Supports heavy workloads with thousands of parallel users and thousands of Linux servers–in one box Connect almost anything on premise and in cloud IBM Cloud Private gives developers and IT operations a combination of critical capabilities to transform the enterprise.
    [Show full text]
  • Architectural Decisions for Linuxone Hypervisors
    July 2019 Webcast Virtualization options for Linux on IBM Z & LinuxONE Richard Young Executive IT Specialist Virtualization and Linux IBM Systems Lab Services Wilhelm Mild IBM Executive IT Architect for Mobile, IBM Z and Linux IBM R&D Lab, Germany Agenda ➢ Benefits of virtualization • Available virtualization options • Considerations for virtualization decisions • Virtualization options for LinuxONE & Z • Firmware hypervisors • Software hypervisors • Software Containers • Firmware hypervisor decision guide • Virtualization decision guide • Summary 2 © Copyright IBM Corporation 2018 Why do we virtualize? What are the benefits of virtualization? ▪ Simplification – use of standardized images, virtualized hardware, and automated configuration of virtual infrastructure ▪ Migration – one of the first uses of virtualization, enable coexistence, phased upgrades and migrations. It can also simplify hardware upgrades by make changes transparent. ▪ Efficiency – reduced hardware footprints, better utilization of available hardware resources, and reduced time to delivery. Reuse of deprovisioned or relinquished resources. ▪ Resilience – run new versions and old versions in parallel, avoiding service downtime ▪ Cost savings – having fewer machines translates to lower costs in server hardware, networking, floor space, electricity, administration (perceived) ▪ To accommodate growth – virtualization allows the IT department to be more responsive to business growth, hopefully avoiding interruption 3 © Copyright IBM Corporation 2018 Agenda • Benefits of
    [Show full text]
  • IBM Z/VM – Frequently Asked Questions
    IBM Z August 2020 IBM z/VM Frequently Asked Questions for z/VM 7.2, z/VM 7.1 and z/VM 6.4 Worldwide LUQ12358-USEN-14 1 Table of Contents _Toc45360441 General Questions ........................................................................................................................................... 3 IBM z/VM Support for IBM z15 and IBM LinuxONE III ................................................................................ 10 Technical Questions - IBM z/VM 7.2, z/VM 7.1, and z/VM 6.4 .................................................................... 11 Efficiency and Scalability ............................................................................................................................... 21 System Ease of Use ....................................................................................................................................... 23 Hardware Currency ........................................................................................................................................ 25 Installation, Migration, and Serviceability .................................................................................................... 27 Statements of Direction from Announcements ............................................................................................ 28 Resources ...................................................................................................................................................... 31 2 General Questions What is IBM Z® and IBM® LinuxONE virtualization
    [Show full text]
  • Happy Birthday Linux
    25 Jahre Linux! Am Anfang war der Quellcode Entstehungsgeschichte und Werdegang von Linux Entwicklung und Diversifizierung der Distributionen Der Wert von Linux oder: „Wat nix kost, dat is och nix.“ Andreas Klein ORR 2016 1 Am Anfang war der Quellcode (70er) ● 1969, Ken Thompson u. Dennis Ritchie erstellen die erste Version von Unix in Assembler. ● Von 1969-1971 entwickeln sie gemeinsam die Programmiersprache B. ● Ab 1971 erweiterte in erster Linie Dennis Ritchie B, um weitere Elemente und nannte sie Anfangs NB (new B). ● 1973 waren die Erweiterungen soweit gediehen, das er die stark verbesserte Sprache C nannte (Brian W. Kernighan hat ebenfalls maßgeblich dazu beigetragen). //Unix=25 PCs ● Bis 1974 war das gesamte Betriebssystem UNIX vollständig in C implementiert und wurde mit einem C-Compiler kostenfrei an verschiedene Universitäten verteilt. ● 1978 wurden bereits über 600 Computer mit dem UNIX-Betriebssystemen betrieben. ● Das aufblühende Zeitalter der Computerisierung der 70er Jahre war geprägt vom regen und freien Austausch von Programmen und dessen zugrunde liegenden Ideen. Sinnvoller Weise tauschte man diese als Quellcode untereinander aus. ● 1979 wurde von AT&T die letzte UNIX-Version 7, mit freiem Quellcode veröffentlicht. Andreas Klein ORR 2016 2 Am Anfang war der Quellcode (80er) ● 1980 – 1983 AT&T sowie zahlreiche andere Unternehmen beginnen mit der Kommerzialisierung von UNIX, durch Koppelung an stark beschränkenden Lizenzen und Geheimhaltung des zugrunde liegenden Quelltextes. ● Richard Stallman kündigt am 27. September 1983 in den Newsgroups net.unix-wizards und net.usoft das GNU-Projekt an. ● Am 5. Januar 1984 begann Stallman offiziell mit der Arbeit am GNU-Projekt, nachdem er seine Stelle am MIT gekündigt hatte.
    [Show full text]
  • IBM Z Server Time Protocol Guide
    Front cover Draft Document for Review August 3, 2020 1:37 pm SG24-8480-00 IBM Z Server Time Protocol Guide Octavian Lascu Franco Pinto Gatto Gobehi Hans-Peter Eckam Jeremy Koch Martin Söllig Sebastian Zimmermann Steve Guendert Redbooks Draft Document for Review August 3, 2020 7:26 pm 8480edno.fm IBM Redbooks IBM Z Server Time Protocol Guide August 2020 SG24-8480-00 8480edno.fm Draft Document for Review August 3, 2020 7:26 pm Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (August 2020) This edition applies to IBM Server Time Protocol for IBM Z and covers IBM z15, IBM z14, and IBM z13 server generations. This document was created or updated on August 3, 2020. © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Draft Document for Review August 3, 2020 8:32 pm 8480TOC.fm Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Comments welcome. .x Stay connected to IBM Redbooks . xi Chapter 1. Introduction to Server Time Protocol . 1 1.1 Introduction to time synchronization . 2 1.1.1 Insertion of leap seconds . 2 1.1.2 Time-of-Day (TOD) Clock . 3 1.1.3 Industry requirements . 4 1.1.4 Time synchronization in a Parallel Sysplex. 6 1.2 Overview of Server Time Protocol (STP) . 7 1.3 STP concepts and terminology . 9 1.3.1 STP facility . 9 1.3.2 TOD clock synchronization .
    [Show full text]
  • Jul to Dec 2013
    Butterfly Conservation Hampshire and Isle of Wight Branch Page 1 of 33 Butterfly Conservation Hampshire and Saving butterflies, moths and our environment Isle of Wight Branch HOME ABOUT » EVENTS » CONSERVATION » SPECIES » SIGHTINGS » PUBLICATIONS » LINKS » ISLE OF WIGHT » MEMBERS » Wednesday 31st July Judith Frank reports from Byway stretch between Stockbridge and Broughton (SU337354) where the following observations were made: Holly Blue (2 "didn't settle long enough for me to be sure but seemed most likely to be hollies."), Peacock (1), Meadow Brown (2), Large White (9), Ringlet (9), Brimstone (1), Comma (2), Green-veined White (4), Gatekeeper (5). "On a day of only fleeting sunshine, I was interested to see what there might be on a section of byway through farmland not particularly managed for butterflies. A large patch of brambles yielded the most colour with the commas, gatekeepers and blues.". Speckled Wood Comma NT Owen reports from Roe Inclosure, Linwood (SU200086) where the following observations were made: Large White (2), Large Skipper (1), Gatekeeper (3), Small Skipper (1), Silver-washed Fritillary (4 "Including one Valezina form female"). Silver-washed Fritillary f. valezina Steve Benstead reports from Brading Down (SZ596867) where the following observations were made: Chalkhill Blue (5), Painted Lady (1), Clouded Yellow (1). "Overcast but warm". Gary palmer reports from barton common (SZ249931) where the following observations were made: Large White (2), Small White (3), Marbled White (3), Meadow Brown (20), Gatekeeper (35), Small Copper (1), Common Blue (1), vapourer moth (1 Larval "using poplar sapling"), peppered moth (1 Larval "using alder buckthorn"), buff tip moth (49 Larval "using mature sallow").
    [Show full text]