Slide 1

Slide 1 text

LEARNING DOCKER AND KUBERNETES WITH OPENSHIFT A Hands-on Lab Exclusively for DevFestMN Keith Resar Container PaaS Solution Architect February 4th, 2017 @KeithResar [email protected]

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

@KeithResar 1: GETTING TO CONTAINERS THE BASICS, WHERE WE EXPLORE “WHY CONTAINERS?” AND “WHY ORCHESTRATION?” 2: ARCHITECTURE AND DISCOVERY LAB DIVE INTO KUBERNETES, OPENSHIFT 3: SOURCE TO IMAGE AND APP LAB FROM SOURCE CODE TO RUNNING APP

Slide 4

Slide 4 text

@KeithResar Keith Resar: Bio Wear many hats @KeithResar [email protected] Coder Open Source Contributor and Advocate Infrastructure Architect

Slide 5

Slide 5 text

GETTING TO CONTAINERS

Slide 6

Slide 6 text

CHALLENGE #1 INFRASTRUCTURE LIMITS YOUR APPS

Slide 7

Slide 7 text

KEY TECHNOLOGY TRENDS

Slide 8

Slide 8 text

KEY TECHNOLOGY TRENDS

Slide 9

Slide 9 text

CONTAINERS MAKE MICROSERVICES COST EFFECTIVE

Slide 10

Slide 10 text

CHALLENGE #2 CONTAINER MANAGEMENT IS HARD

Slide 11

Slide 11 text

For those of you not in the room, this is where I saved you from cliche images of container ships in disaster. You’re Welcome!

Slide 12

Slide 12 text

CHALLENGE #2 CONTAINER MANAGEMENT IS HARD

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

@KeithResar

Slide 15

Slide 15 text

@KeithResar

Slide 16

Slide 16 text

ARCHITECTURE DETAILS

Slide 17

Slide 17 text

@KeithResar 10,000 foot overview

Slide 18

Slide 18 text

@KeithResar OpenShift runs on your choice of infrastructure

Slide 19

Slide 19 text

@KeithResar Nodes are instances of Linux where apps will run

Slide 20

Slide 20 text

@KeithResar Apps and components run in containers Container Image Container Pod

Slide 21

Slide 21 text

@KeithResar Pods are the orchestrated unit in OpenShift

Slide 22

Slide 22 text

@KeithResar Masters are the Control Plane

Slide 23

Slide 23 text

@KeithResar API and Authentication

Slide 24

Slide 24 text

@KeithResar Desired and Current State

Slide 25

Slide 25 text

@KeithResar Orchestration and Scheduling

Slide 26

Slide 26 text

@KeithResar Placement by Policy

Slide 27

Slide 27 text

@KeithResar Services connect application components

Slide 28

Slide 28 text

@KeithResar Health and Scaling

Slide 29

Slide 29 text

@KeithResar What about unhealthy Pods?

Slide 30

Slide 30 text

@KeithResar The Master remediates Pod failures

Slide 31

Slide 31 text

@KeithResar What about app data?

Slide 32

Slide 32 text

@KeithResar Routing layer for external accessibility

Slide 33

Slide 33 text

@KeithResar Access via Web UI, CLI, IDE, API

Slide 34

Slide 34 text

SOURCE TO IMAGE

Slide 35

Slide 35 text

Source 2 Image Walk Through Code Developers can leverage existing development tools and then access the OpenShift Web, CLI or IDE interfaces to create new application services and push source code via GIT. OpenShift can also accept binary deployments or be fully integrated with a customer’s existing CI/CD environment.

Slide 36

Slide 36 text

Source 2 Image Walk Through Container Image Registry Build OpenShift automates the Docker image build process with Source-to-Image (S2I). S2I combines source code with a corresponding Builder image from the integrated Docker registry. Builds can also be triggered manually or automatically by setting a Git webhook. Add in Build pipelines

Slide 37

Slide 37 text

Source 2 Image Walk Through Container Image Registry Deploy OpenShift automates the deployment of application containers across multiple Node hosts via the Kubernetes scheduler. Users can automatically trigger deployments on application changes and do rollbacks, configure A/B deployments & other custom deployment types.

Slide 38

Slide 38 text

@KeithResar Community Callouts DOCKER MEETUP KUBERNETES MEETUP OPENSHIFT MEETUP ANSIBLE MEETUP

Slide 39

Slide 39 text

@KeithResar @KeithResar [email protected]

Slide 40

Slide 40 text

@KeithResar