DOCSLIB.ORG

Linux on Z Platform ISV Strategy Summary

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Linux on Z Platform ISV Strategy Summary Linux on IBM Z / LinuxONE Open Source Ecosystem Status and Strategy for NY/NJ Linux Council Meeting on March 1, 2019 Enyu Wang Program Director, Ecosystem Strategy and Business Development [email protected] As an enterprise platform WHY ARE WE INVESTING IN OPEN SOURCE ECOSYSTEM? IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 2 TREND: Enterprise Going Open Source • 83% hiring managers surveyed for the 2018 Open Source Jobs report said hiring open source talent was a priority this year • Some of the biggest trends in enterprise IT, such as containers and hybrid cloud, rely on open source technologies including Linux and Kubernetes IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 3 OPEN SOURCE Building Blocks for Enterprise Digital Transformation IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 4 OUR MISSION Provide a Rich and Robust Ecosystem to Clients. Help Accelerate their Digital Transformation IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 5 Rich Open Source Ecosystem on Linux on Z/LinuxONE Analytics/ Distributions Hypervisors PaaS / IaaS Languages Runtimes Management Database ML LPA R IBM Cloud Private Community Versions LLVM vRealize LXD (Ubuntu) Apache Tomcat DPM Db2 IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 6 Building an Open Ecosystem Isn’t Just Porting… IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 7 Composition of Open Source Ecosystem on Z – a combination of community based projects and vendor governed projects https://www.ibm.com/developerworks/community/groups/community/lozopensource Objective for technical enablement and support on Z is making Z part of supported architecture for the project 1Community based support with no SLA 2 Enterprise support (9x5, 24x7, etc) IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 8 Open Source Characteristics and What It Means to Z IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 9 Z Open Ecosystem Work Flow IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 10 Make More Binaries Available on Z Request for Binaries Multi-proned Approach on Z • Customers don’t always want to build • Leverage distro repos open source binaries from source, • Invite communities to build on Z on especially for complex Often times LinuxONE Community Cloud and binaries can be downloaded from a Dallas ISV Center website or install from repos • Make z QEMU available for packages • Challenges for Z: Z hardware isn’t that are built using emulation pervasively used as x86 for building packages • Enable build services (Jenkins, Travis- CI) on Z • Publish Docker images on Docker Hub through a Docker build tool hosted at UIUC IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 11 Support for Open Source Support options on x86 Support options on Z • Community based support • Community based support • Distro support • Distro support • Vendor support • Vendor support for a selection of software • Business partners provide enterprise support for popular packages • RogueWave, Rocket Software, SNA • IBM (TSS) support IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 12 Technology Focus Areas What’s enabled, what is being worked on, what is in the pipeline IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 13 Market Challenge with growth opportunities Today’s multicloud reality presents new opportunities for clients, as well as new challenges $438B in 2020 $609B in 2020 ‘18-’20 CAGR 15% ‘18-’20 CAGR 18% A real world look at multicloud Private Public Clouds Dedicated of enterprise customers are using Clouds & SaaS Clouds 94% multiple cloud environments (public and/or private) of enterprise customers are using 67% more than one public cloud provider Traditional (expected to remain constant or increase by 2022) IT $640B in 2020 ‘18-’20 CAGR -9% priority concern Connectivity 82% Consistency 67% between clouds of management Source: IBM MD&I; BCG and McKinsey research 14 IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 14 Containers Are the Foundation for Cloud Native Apps IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 15 Where Is Z in Cloud Native Technology Adoption FIE Early Middle Traditional Z Adopters Ground Customers Project Maturity Levels IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 16 Cloud Native Ecosystem Strategy Make Z the most secure Align with Tech Trend server for cloud • Shift from VM to Containers Key Differentiator: Security • Kubernetes are the new Linux No other Linux server can deliver more protection against both internal and • as a Service is the trend external cyber threats – faster and without changes to applications. • Hybrid Cloud goes mainstream • Customers requires cloud like Other Differentiator experience for on prem, ie. life and shift on converged infrastructure Performance scalability • Open-ness: Rometty said the battle for cloud computing will be 'open HA/DR versus proprietary', and she has Consolidation placed all her backing behind open source. zOS Cloud Broker IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 17 What a Cloud Platform Needs to Deliver Cloud Native Applications Developer / DevOps Engineer Cloud Platform DevOps Data Event Data Lake Services Warehouse Streaming Platform as a Service CI / CD Relational NoSQL Pub/Sub Blockchain Analytics Database Database Messaging Platform Admin / Engineer Source Code Repo Platform Ops Stateless Stateful Image Container Batch Job Services Infrastructure Platform Deployment Deployment Registry as Code Monitoring Test Container Object Load Service Container Automation Cluster Storage Balancing Mesh Infrastructure Logging as a Service Virtual Block Virtual Monitoring Bare Metal File Storage DNS Machine Storage Network IAM Configuration Hypervisor Software Defined Storage Software Defined Network Management Infrastructure Server Storage Network Backup IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 18 IDC Market Glance: Cloud Platform Landscape IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 19 Cloud Native Ecosystem Partners IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 20 Linux on Z/LinuxONE Cloud Platform Enablement Status Observatory Security PaaS & Analysis Image build KeyStone Monitoring (openstack) Prometheus Cloud App Definition and Dev Foundry Docker Compose Minukube Helm Sysdig Sysdig Secure Heapster Splunk Secure Splunk (To) ICP Orchestration Container Orchestration Coordination & Service Discovery Service Proxy Service Mesh & Management consu Splunk (From) etcd Nginx Kubernetes l Istio HAProxy Docker Swarm zookeeper coreDNS Logging OpenShift Mesos Rancher OpenResty Enterprise fluentd Cloud-Native Storage SCC Runtimes Container Runtime Cloud-Native Networking GlusterFS PortWorx Calico Open vSwitch Apache: Elastic Qradar Pivotal IBM Spectrum Kata Flume Scale Ceph Flannel UCarp Logstash Beats Swift Docker Engine ELK Guardium (OpenStack) Provisioning Automatic Configuration Image registry Docker EE Visualization Hyperledger Infrastructur Julu SaltStack Chef Docker Registry Fabric e as code Terraform Graphana Ansible Puppet Jfrog ArtifactoryRegistry OpenShift IaaS OpenStack Kibana Hyper protect Origin crypto services Virtual Infrastructure Physical Infrastructure Vendor or community enabled Not covered here: •DB Underway •Steaming and Messaging Under evaluation •CI/CD Vendor work required •API gateway IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 21 Cloud Native Ecosystem Focus Areas IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 22 Data Serving Ecosystem IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 23 Linux on IBM Z/LinuxONE for Open-Source Databases The most scalable, reliable and securable hardware and the most popular open-source database management system IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 24 OSDBs are preferred for more than half of the database types: You now have as many choices for •Graph DBMS •Search engines OSDBs as for •Key-value stores commercial DBs •Document stores (170 vs. 173) •Time series DBMS •Wide column stores DB-Engines.com top 5 open source systems January 2019 All of them run on Linux on Z/LinuxONE Over the past six years, OSDBs have Rank System Score taken 13% market share 1. MySQL 1154 away from commercial DBs 2. PostgreSQL 466 3. MongoDB 387 4. Redis 149 5. Elasticsearch 143 IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 25 Data-serving challenges: disruption caused by Big Data IDC and EMC projected By 2020 data will grow to 40 zettabytes; 50-fold growth from 2010 Scalability Server Sprawl Availability In Jan 2017 ... 27,000 MongoDB databases were stolen! Ensuring Privacy 25% of the 100,000 deployed MongoDB databases in the world have been compromised. IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 26 Why Linux on Z/LinuxONE for Open Source Database? IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 27 Why Linux on Z/LinuxONE for Open Source Database Security Pervasive encryption across the entire system Protected keys • Safer than open-key • Up to 28x faster than secure-key Isolation on IBM Z/LinuxONE starts in the hardware ... "What happens in a VM stays in a VM” IBM Z / Open Source Ecosystem / Mar 1, 2019 / © 2019 IBM Corporation 28 Why Linux on Z/LinuxONE
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]
  • Apache Sentry
    Apache Sentry Prasad Mujumdar [email protected] [email protected] Agenda ● Various aspects of data security ● Apache Sentry for authorization ● Key concepts of Apache Sentry ● Sentry features ● Sentry architecture ● Integration with Hadoop ecosystem ● Sentry administration ● Future plans ● Demo ● Questions Who am I • Software engineer at Cloudera • Committer and PPMC member of Apache Sentry • also for Apache Hive and Apache Flume • Part of the the original team that started Sentry work Aspects of security Perimeter Access Visibility Data Authentication Authorization Audit, Lineage Encryption, what user can do data origin, usage Kerberos, LDAP/AD Masking with data Data access Access ● Provide user access to data Authorization ● Manage access policies what user can do ● Provide role based access with data Agenda ● Various aspects of data security ● Apache Sentry for authorization ● Key concepts of Apache Sentry ● Sentry features ● Sentry architecture ● Integration with Hadoop ecosystem ● Sentry administration ● Future plans ● Demo ● Questions Apache Sentry (Incubating) Unified Authorization module for Hadoop Unlocks Key RBAC Requirements Secure, fine-grained, role-based authorization Multi-tenant administration Enforce a common set of policies across multiple data access path in Hadoop. Key Capabilities of Sentry Fine-Grained Authorization Permissions on object hierarchie. Eg, Database, Table, Columns Role-Based Authorization Support for role templetes to manage authorization for a large set of users and data objects Multi Tanent Administration
    [Show full text]
  • Cómo Citar El Artículo Número Completo Más Información Del
    DYNA ISSN: 0012-7353 Universidad Nacional de Colombia Iván-Herrera-Herrera, Nelson; Luján-Mora, Sergio; Gómez-Torres, Estevan Ricardo Integración de herramientas para la toma de decisiones en la congestión vehicular DYNA, vol. 85, núm. 205, 2018, Abril-Junio, pp. 363-370 Universidad Nacional de Colombia DOI: https://doi.org/10.15446/dyna.v85n205.67745 Disponible en: https://www.redalyc.org/articulo.oa?id=49657889045 Cómo citar el artículo Número completo Sistema de Información Científica Redalyc Más información del artículo Red de Revistas Científicas de América Latina y el Caribe, España y Portugal Página de la revista en redalyc.org Proyecto académico sin fines de lucro, desarrollado bajo la iniciativa de acceso abierto Integration of tools for decision making in vehicular congestion• Nelson Iván-Herrera-Herreraa, Sergio Luján-Morab & Estevan Ricardo Gómez-Torres a a Facultad de Ciencias de la Ingeniería e Industrias, Universidad Tecnológica Equinoccial, Quito, Ecuador. [email protected], [email protected] b Departamento de Lenguajes y Sistemas Informáticos, Universidad de Alicante, Alicante, España. [email protected] Received: September 15th, 2017. Received in revised form: March 15th, 2018. Accepted: March 21th, 2018. Abstract The purpose of this study is to present an analysis of the use and integration of technological tools that help decision making in situations of vehicular congestion. The city of Quito-Ecuador is considered as a case study for the done work. The research is presented according to the development of an application, using Big Data tools (Apache Flume, Apache Hadoop, Apache Pig), favoring the processing of a lot of information that is required to collect, store and process.
    [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]
  • Database Licensing Information User Manual
    Oracle® Database Database Licensing Information User Manual 19c E94254-04 April 2019 Oracle Database Database Licensing Information User Manual, 19c E94254-04 Copyright © 2004, 2019, Oracle and/or its affiliates. All rights reserved. Contributors: Penny Avril, Prabhaker Gongloor, Mughees Minhas, Anu Natarajan, Jill Robinson This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [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]
  • Bigchaindb Server Documentation Release 1.2.0
    BigchainDB Server Documentation Release 1.2.0 BigchainDB Contributors Nov 13, 2017 Contents 1 Introduction 1 2 Quickstart 3 3 Production Nodes 5 4 Clusters 13 5 Production Deployment Template 15 6 Develop & Test BigchainDB Server 65 7 Settings & CLI 73 8 The HTTP Client-Server API 85 9 The Events API 103 10 Drivers & Tools 107 11 Data Models 109 12 Transaction Schema 117 13 Vote Schema 121 14 Release Notes 123 15 Appendices 125 Python Module Index 169 HTTP Routing Table 171 i ii CHAPTER 1 Introduction This is the documentation for BigchainDB Server, the BigchainDB software that one runs on servers (but not on clients). If you want to use BigchainDB Server, then you should first understand what BigchainDB is, plus some of the spe- cialized BigchaindB terminology. You can read about that in the overall BigchainDB project documentation. Note that there are a few kinds of nodes: •A dev/test node is a node created by a developer working on BigchainDB Server, e.g. for testing new or changed code. A dev/test node is typically run on the developer’s local machine. •A bare-bones node is a node deployed in the cloud, either as part of a testing cluster or as a starting point before upgrading the node to be production-ready. •A production node is a node that is part of a consortium’s BigchainDB cluster. A production node has the most components and requirements. 1.1 Setup Instructions for Various Cases • Quickstart • Set up a local BigchainDB node for development, experimenting and testing • Set up and run a BigchainDB cluster There are some old RethinkDB-based deployment instructions as well: • Deploy a bare-bones RethinkDB-based node on Azure • Deploy a RethinkDB-based testing cluster on AWS Instructions for setting up a client will be provided once there’s a public test net.
    [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]
  • 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]
  • Flume 1.8.0 Developer Guide
    Apache ™ Flume™ Flume 1.8.0 Developer Guide Introduction Overview Apache Flume is a distributed, reliable, and available system for efficiently collecting, aggregating and moving large amounts of log data from many different sources to a centralized data store. Apache Flume is a top-level project at the Apache Software Foundation. There are currently two release code lines available, versions 0.9.x and 1.x. This documentation applies to the 1.x codeline. For the 0.9.x codeline, please see the Flume 0.9.x Developer Guide. Architecture Data flow model An Event is a unit of data that flows through a Flume agent. The Event flows from Source to Channel to Sink, and is represented by an implementation of the Event interface. An Event carries a payload (byte array) that is accompanied by an optional set of headers (string attributes). A Flume agent is a process (JVM) that hosts the components that allow Events to flow from an external source to a external destination. A Source consumes Events having a specific format, and those Events are delivered to the Source by an external source like a web server. For example, an AvroSource can be used to receive Avro Events from clients or from other Flume agents in the flow. When a Source receives an Event, it stores it into one or more Channels. The Channel is a passive store that holds the Event until that Event is consumed by a Sink. One type of Channel available in Flume is the FileChannel which uses the local filesystem as its backing store.
    [Show full text]