[PDF] Getting Started with z/OS Container Extensions and Docker





Previous PDF Next PDF



Grafana Dashboard Json Example

can be of an example since the full list of the example grafana dashboard json to set. The json format examples of csv files using a case datasources.



grafanalib: Dashboards as code

Why not just generate the JSON correctly instead? 10. Page 11. ? As simple as possible—mostly data. ? No 



Viewing MQ configurations with Grafana

30 sept 2019 The mysqlsh utility makes it very simple to import JSON files into a MySQL database. If a table of the given name does not already exist it ...



AWS IoT TwinMaker - User Guide

30 nov 2021 Applications: AWS IoT TwinMaker provides a plug-in for Grafana and ... The following JSON samples are examples of response and request ...



Amazon Managed Grafana - User Guide

24 mar 2021 For more information see Sample policies for Amazon ... Some queries accept filters in JSON format and Grafana supports the conversion of ...



Deploying and Upgrading AMQ Streams on OpenShift

26 abr 2022 Importing the example Grafana dashboards ... AMQ Streams release artifacts include sample YAML files to help you deploy the components of ...



UNIVERSIDAD AUTÓNOMA DE MADRID TRABAJO FIN DE

Figura 4.5 - Cuadro de mando Grafana - cdmconsultores.com 127.0.0.1 - peter [9/Feb/2017:10:34:12 -0700] "GET /sample-image.png. HTTP/2" 200 1479.



nmon njmon nmon njmon

11 may 2020 Very simple endpoint install ... JSON output for Elastic (ELK) & Splunk ... FREE Basic Grafana Performance Graphs on njmon AIX data ...



Getting Started with z/OS Container Extensions and Docker

8 nov 2019 This information contains examples of data and reports used in ... ENV GF_INSTALL_PLUGINS grafana-clock-panelgrafana-simple-json-datasource.



/metrics

POST /metrics In Panel > Queries page. When configuring a query request using Builder mode, it will send the request to obtain the available metrics. The request body will carry the current metric and payload. In the Builder mode, if the reloadMetricvalue in the load configuration is true, the api will also be triggered when the value is modified /...

/Metric-Payload-Options

POST /metric-payload-options When the payload type is select or multi-select and the payload optionsconfiguration is empty, expanding the drop-down menu will trigger this API. The request body will carry the current metric and payload. Example Request: Example Response: The display is as follows:

/Query

POST /query Example request: Response body can contain anything that is or can be converted to a Grafana DataFrame using this function.Returned data will be mapped to a DataFrame through that. Example response (metric value as a float , unix timestamp in milliseconds): The relation between target in request and response is 1:n. You can return multi...

Is there a JSON API for Grafana?

Yes. Configuration | JSON API for Grafana I suggest you edit your post to include your CURL example (hide keys etc) as well as specify exactly what parameters you have in your datasource config and panel config. e.g. What are your Datasource settings and panel Params / Headers / Body data you have tried so far?

How do I use Grafana?

Grafana is just a visualisation tool. It needs a data source to query data and display. It is optimised for time series data, but static data can also be displayed easily. Use the API plugin . You can also use TestData DB data source which is available within Grafana to test scenarios. (does not use json though)

How to create JSON based alerts in Grafana?

The best option for json based alerts is to add the alert code to the API framework that Grafana calls. I use Python code to run Grafana API and injest the alert rules from an external API call. The data is then used to compile a special metric when the rule is fired programmatically.

    Past day

    How to make Simple-JSON variable template query in grafana?

    2 Answers Sorted by: 2 You can write arbitrary text in the timeserie query, it doesn't need to be one of the hardcoded metrics that /search returns. There is also the simpod json datasource plugin. https://grafana.com/grafana/plugins/simpod-json-datasource built on top of the Simple JSON Datasource. lgo algo-sr relsrch richAlgo" data-d61="645f62c71bfb4">stackoverflow.com › questions › 56547108How to make Simple-JSON variable template query in grafana? stackoverflow.com › questions › 56547108 Cached

Redbooks

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

IBM Redbooks

Getting started with z/OS Container Extensions

November 2019

SG24-8457-00

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

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.

Note: Before using this information and the product it supports, read the information in "Notices" on

page ix. © Copyright IBM Corp. 2019. All rights reserved.iii

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

iv Getting started with z/OS Container Extensions

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

4.8.4 Execute remaining workflow steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4.8.5 Viewing created instance directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4.8.6 Obtain the command to start the zCX instance. . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.9 Starting the zCX instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.9.1 Assigning user ID that zCX instance runs under. . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.9.2 Access to zCX instance directory by the zCX started task . . . . . . . . . . . . . . . . . . 72

4.9.3 Start the zCX instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.9.4 Check zCX startup messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.9.5 Step failure in the workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.10 Log on to the zCX instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4.11 Reconfiguring a zCX instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4.11.1 What is reconfigured?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.11.2 Checking current settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.11.3 Create reconfiguration zCX workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.11.4 Execute the reconfiguration workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4.11.5 Stop and start the zCX instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.11.6 Verifying reconfiguration changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.12 Adding a volume to a zCX instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.12.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.12.2 Checking default disk space allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4.12.3 Create add data disks zCX workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4.12.4 Run the Add Data Disks workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4.12.5 Stop and start the zCX instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

4.12.6 Verifying Add Data Disk changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

4.13 Deprovisioning a zCX instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.13.1 Create deprovisioning zCX workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

4.13.2 Execute the deprovision workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

4.13.3 Verify that the zCX instance has been deprovisioned. . . . . . . . . . . . . . . . . . . . . 92

Contents v4.14 Other provisioning workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4.15 How to rerun a workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 5. Your first running Docker container in zCX. . . . . . . . . . . . . . . . . . . . . . . . . 95

5.1 Overview of the process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.1.1 Provision your instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.1.2 Get a Docker image to run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.1.3 Start your image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.1.4 Access the provided service by the image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.2 Get an image from Docker Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.2.1 Download from Docker Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.2.2 Download via a local Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.2.3 Load the image from a .tar file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.3 Run your Docker image on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.3.1 hello-world. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.3.2 HTTP Server (nginx). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

5.3.3 Enhanced installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

5.4 Managing your Docker image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

5.4.1 Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

5.4.2 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

5.4.3 Stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

5.4.4 Terminate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 6. Private registry implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

6.1 Private registry overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

6.2 Tag discussion for images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

6.3 Building a private registry image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

6.4 Running a local private registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

6.4.1 Stopping a private registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

6.4.2 Removing a private registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

6.5 Deploying a secure private registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

6.5.1 When zCX appliance is behind a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

6.6 Creating TLS certificates on Windows or Macintosh. . . . . . . . . . . . . . . . . . . . . . . . . . 130

6.7 Working with tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

6.8 Deleting an image from a private Docker registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

6.9 Using the private registry to create containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Chapter 7. Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

7.1 Software maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

7.1.1 Maintenance for zCX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

7.1.2 Maintenance for containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

7.1.3 Building and maintaining your own image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

7.2 Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

7.2.1 Automating zCX instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

7.2.2 Automating containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

7.3 Backup and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

7.3.1 Backup and recovery on zCX instance level. . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

7.3.2 Backup and recovery on container level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

7.4 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

7.4.1 Ways to check healthiness of zCX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

7.4.2 Gathering problem data for zCX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

7.5 Monitoring with RMF on zCX instance level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

7.5.1 RMF overview display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

7.5.2 RMF CPC capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

vi Getting started with z/OS Container Extensions

7.5.3 RMF job information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

7.6 Configuring Grafana to monitor zCX containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

7.6.1 Install Node-Exporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

7.6.2 Install cAdvisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

7.6.3 Install Prometheus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

7.6.4 Installation of Grafana. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

7.6.5 Adding Prometheus as data source to Grafana . . . . . . . . . . . . . . . . . . . . . . . . . 172

7.6.6 Creating a first dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

7.7 Monitoring with Grafana on container level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

7.7.1 Adjusting the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

7.7.2 Instance level data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

7.7.3 Container level data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 8. Integrating container applications with other processes on z/OS. . . . . . 187

8.1 Interconnecting IBM MQ on z/OS with IBM MQ in zCX . . . . . . . . . . . . . . . . . . . . . . . 188

8.1.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

8.1.2 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

8.1.3 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

8.1.4 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

8.2 Accessing Db2 from within Docker container when you are using Jupyter Notebook 199

8.2.1 What is a Jupyter Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

8.2.2 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

8.2.3 Creating a Docker Image with Jupyter installed . . . . . . . . . . . . . . . . . . . . . . . . . 200

8.2.4 Using a Jupyter Notebook to access Db2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

8.3 Accessing application in a zCX container from z/OS . . . . . . . . . . . . . . . . . . . . . . . . . 209

8.3.1 Target application in Docker container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

8.3.2 Setting up the etcd container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

8.3.3 Build the etcd Docker image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

8.3.4 Run the etcd Docker image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

8.3.5 The z/OS application to call etcd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

8.3.6 Detail on setting up an etcd container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

8.3.7 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Chapter 9. zCX user administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

9.1 Local user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

9.1.1 Adding Docker users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

9.2 Configuring zCX to use an LDAP server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

9.2.1 LDAP server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

9.2.2 Creating the LDAP configuration file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

9.2.3 Enabling LDAP server authentication through z/OSMF Workflows . . . . . . . . . . 226

9.3 Resources on the provisioning server and verifying that LDAP is enabled. . . . . . . . . 228

Chapter 10. Persistent data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

10.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

10.2 Using Docker volumes for persistent data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Chapter 11. Swarm on zCX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

11.1 Swarm introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

11.2 zCX in swarm mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

11.2.1 Removing node from swarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

11.2.2 Initializing swarm mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

11.2.3 Adding node manager to the cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

11.2.4 Adding worker nodes to the manager node . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

11.2.5 Creating a Docker service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Contents vii11.2.6 Scaling up a container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

11.2.7 Changing node availability to simulate a scheduled maintenance . . . . . . . . . . 247

11.2.8 Promoting a worker node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

11.2.9 Demoting a manager node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

11.2.10 Scaling down a service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

11.2.11 Considerations regarding the number of manager nodes. . . . . . . . . . . . . . . . 249

Appendix A. Obtaining the additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

viii Getting started with z/OS Container Extensions © Copyright IBM Corp. 2019. All rights reserved.ix

Notices

This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in

that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult

your local IBM representative for information on the products and services currently available in your area. Any

reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not

infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to

evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The

furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing, IBM Corporation, North Castle Drive, MD-NC119, Armonk, NY 10504-1785, US INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED

TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in

certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made

to the information herein; these changes will be incorporated in new editions of the publication. IBM may make

improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the

materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate without

incurring any obligation to you. The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, their published

announcements or other publicly available sources. IBM has not tested those products and cannot confirm the

accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the

capabilities of non-IBM products should be addressed to the suppliers of those products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and

represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them

as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely

coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in

any form without payment to IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,

cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are

provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

x Getting started with z/OS Container Extensions

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines

Corporation, registered in many jurisdictions worldwide. Other product and service names might be

trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml

The following terms are trademarks or registered trademarks of International Business Machines Corporation,

and might also be trademarks or registered trademarks in other countries.

AIX®

CICS®

Cloudant®

Cognos®

Db2®

DB2®

GDPS®

HyperSwap®

IBM®IBM Cloud™

IBM Z®

IBM z14®

IBM z15™

MQSeries®

MVS™

OS/390®

Parallel Sysplex®

RACF®Redbooks®

Redbooks (logo) ®

Tivoli®

UrbanCode®

WebSphere®

z/OS® z/VM® z15™ The following terms are trademarks of other companies:

The registered trademark Linux® is used pursuant to a sublicense from the Linux Foundation, the exclusive

licensee of Linus Torvalds, owner of the mark on a worldwide basis. Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its

affiliates. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. © Copyright IBM Corp. 2019. All rights reserved.xi

Preface

IBM® z/OS® Container Extensions (IBM zCX) is a new feature of the next version of the IBM z/OS Operating System (z/OS V2.4). It makes it possible to run Linux on IBM Z® applications that are packaged as Docker container images on z/OS. Application developers can develop, and data centers can operate, popular open source packages, Linux applications, IBM software, and third-party software together with z/OS applications and data. This IBM Redbooks® publication helps you to understand the concepts, business perspectives, and reference architecture for installing, tailoring, and configuring zCX in your own environment.

Authors

This book was produced by a team of specialists who gathered from around the world to work at IBM Redbooks Center in Poughkeepsie. Lydia Parziale is a Project Leader for the IBM Redbooks team in Poughkeepsie, New York, with domestic and international experience in technology management including software development, project leadership, and strategic planning. Her areas of expertise includequotesdbs_dbs20.pdfusesText_26
[PDF] simple json example in android studio

[PDF] simple json example python

[PDF] simple json example url

[PDF] simple linear equations examples

[PDF] simple math in french

[PDF] simple php class example

[PDF] simple programming language download

[PDF] simple programming language to learn

[PDF] simple programs of 8086 microprocessor pdf

[PDF] simple reminder app for android source code

[PDF] simple report writing examples for students pdf

[PDF] simple restaurant dialogue in spanish

[PDF] simple sentence

[PDF] simple software design document template

[PDF] simple stock calculator