Slide 1

Slide 1 text

OpenShift 101: Learn about Enterprise Kubernetes Containers & OpenShift Developer Advocacy Tokyo Team Developer Advocate Yasushi Osonoi

Slide 2

Slide 2 text

Yasushi Osonoi IBM Developer Advocacy Group, Client Developer Advocate Twitter: @osonoi Facebook: @osonoi Follow me! BlogLJapanese) https://qiita.com/osonoi (Qiita) https://blogs.itmedia.co.jp/osonoi/ (IT Media)

Slide 3

Slide 3 text

Deploy Application on OpenShift using S2I Source code is in GitHub. K8s Deploy Docker hub Build docker registry Docker file Source Code (Node.js) Catalog template (JSON/YAML) S2I Build DevOps Pipeline Today’s workshop GitHub https://github.com/IBM/node-s2i-openshift

Slide 4

Slide 4 text

1. If you donʼt have an account, Please register here. https://ibm.biz/BdqvrE Itʼs free and all you need to register is email address. Please login to IBM Cloud

Slide 5

Slide 5 text

Group Name / DOC ID / Month XX, 2018 / © 2018 IBM Corporation ↳ Why Containers? 5

Slide 6

Slide 6 text

Containerization “In 1955, former trucking company owner Malcom McLean worked with engineer Keith Tantlinger to develop the modern intermodal container.” Containerization also reduced congestion in ports, significantly shortened shipping time and reduced losses from damage and theft. “Containers can be made from a wide range of materials such as steel, fibre-reinforced polymer, aluminium or a combination of all.” (Wikipedia https://en.wikipedia.org/wiki/Containerization) https://en.wikipedia.org/wiki/Malcom_McLean

Slide 7

Slide 7 text

Also happening in IT industry. Containerization made Business revolution Land Transportation Loading Unloading Marine Transportation Loading Unloading Land Transportation Dev. Test Production

Slide 8

Slide 8 text

Why Containers? 8 Resource(memory, storage) required Better Portability

Slide 9

Slide 9 text

Create & Deliver container application Dockerfile Docker image Container Registry Describe details in YAML file Developer Create Image Register Image developer Deploy Dev Process

Slide 10

Slide 10 text

Why Containers? • Agile • Continuous Deployment • Separation of Concerns • Observability • Consistency • Management • Microservices • Resource Isolation • Resource Utilization

Slide 11

Slide 11 text

Orchestration • Scheduling • Cluster management • Service discovery • Provisioning • Monitoring • Configuration management

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

Kubernetes key features Scale Out Load Balancing Version management Rollouts/Rollbacks Network service Self-Healing Machine Management Declarative object configuration

Slide 14

Slide 14 text

Kubernetes Master API UI CLI Node 1 Node 2 Node 3 Node n Image Registry Kubernetes Architecture Cloud provider manage (Cloud K8S service) Developer Pod (apps) Deploy YAML file For configuration

Slide 15

Slide 15 text

3 key term in Kubernetes Pod A Pod (as in a pod of whales or pea pod) is a group of one or more containers (such as Docker containers), with shared storage/network, and a specification for how to run the containers. A Pod's contents are always co-located and co-scheduled, and run in a shared context. A Pod models an application-specific "logical host" - it contains one or more application containers which are relatively tightly coupled Pod IP 10.1.206.34 10.1.206.128

Slide 16

Slide 16 text

Deployment A Deployment provides declarative updates for Pods and ReplicaSets. You describe a desired state in a Deployment, and the Deployment Controller changes the actual state to the desired state at a controlled rate. You can define Deployments to create new ReplicaSets, or to remove existing Deployments and adopt all their resources with new Deployments. Pod IP 10.1.206.34 10.1.206.110 Node Node 3 key term in Kubernetes

Slide 17

Slide 17 text

Service Pod IP 10.1.206.34 10.1.206.110 Node Node 30010 30010 3 key term in Kubernetes An abstract way to expose an application running on a set of Pods as a network service. With Kubernetes you don't need to modify your application to use an unfamiliar service discovery mechanism. Kubernetes gives Pods their own IP addresses and a single DNS name for a set of Pods, and can load-balance across them.

Slide 18

Slide 18 text

Group Name / DOC ID / Month XX, 2018 / © 2018 IBM Corporation ↳ OpenShift 1

Slide 19

Slide 19 text

© 2019 IBM Corporation OPENSHIFT Extension OpenShift CICD Application (container) Kubernetes Application (Container) Ubuntu / CentOS… Linux Kubernetes Application (Container) Runtime engine Linux OS Orchestration RHEL / RHCOS Runtime engine What is an OpenShift CI/CD Support Security ….

Slide 20

Slide 20 text

K8s Deploy Docker hub Build docker Registry Docker file Source code n GitHub (Java, js, Py..etc) Catalog template (JSON/YAML) s2i Build Several way to deploy apps on OpenShift Deploy from Public registry Use own Image (Build on OpenShift) Use s2i to make image from source Directly Execute From Catalog DevOps Pipeline

Slide 21

Slide 21 text

Group Name / DOC ID / Month XX, 2018 / © 2018 IBM Corporation ↳ Conclusion & Lab 2 IBM Developer SF Team / Introduction to Kubernetes and OpenShift / October 30, 2019 / © 2019 IBM Corporation

Slide 22

Slide 22 text

Deploy Application on OpenShift using S2I Source code is in GitHub. K8s Deploy Docker hub Build docker registry Docker file Source Code (Node.js) Catalog template (JSON/YAML) S2I Build DevOps Pipeline Today’s workshop GitHub https://github.com/IBM/node-s2i-openshift

Slide 23

Slide 23 text

https://bit.ly/OCIBM0701

Slide 24

Slide 24 text

Lab Preparation, Associate cluster with your IBM ID https://os101ws.mybluemix.net/ “oslab” your IBM ID (Email address) *This cluster will be available next 24 hours

Slide 25

Slide 25 text

Go back to INB Cloud at https://ibm.biz/BdqvrE

Slide 26

Slide 26 text

Select [xxxxxxx – Adovowork] Go back to IBM Cloud at https://ibm.biz/BdqvrE Click here

Slide 27

Slide 27 text

You can see the Cluster Click here

Slide 28

Slide 28 text

You have OpenShift! Click here

Slide 29

Slide 29 text

OpenShift cluster in Details Click here to go to OpenShift Console

Slide 30

Slide 30 text

You are ready to have lab

Slide 31

Slide 31 text

No content