devfestmn 2017 - learning docker and kubernetes with openshift
TRANSCRIPT
LEARNING DOCKER AND KUBERNETES WITH OPENSHIFTA Hands-on Lab Exclusively for DevFestMN
Keith ResarContainer PaaS Solution ArchitectFebruary 4th, 2017
@KeithResar
1: GETTING TO CONTAINERSTHE BASICS, WHERE WE EXPLORE “WHY CONTAINERS?” AND “WHY ORCHESTRATION?”
2: ARCHITECTURE AND DISCOVERY LABDIVE INTO KUBERNETES, OPENSHIFT
3: SOURCE TO IMAGE AND APP LABFROM SOURCE CODE TO RUNNING APP
@KeithResar
Keith Resar: BioWear many hats
@KeithResar [email protected]
CoderOpen Source Contributor and Advocate
Infrastructure Architect
GETTING TO CONTAINERS
CHALLENGE #1INFRASTRUCTURE LIMITS YOUR
APPS
KEY TECHNOLOGY TRENDS
KEY TECHNOLOGY TRENDS
CONTAINERS MAKE MICROSERVICES COST EFFECTIVE
CHALLENGE #2CONTAINER MANAGEMENT IS
HARD
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!
CHALLENGE #2CONTAINER MANAGEMENT IS
HARD
@KeithResar
@KeithResar
ARCHITECTURE DETAILS
@KeithResar
10,000 foot overview
@KeithResar
OpenShift runs on your choice of infrastructure
@KeithResar
Nodes are instances of Linux where apps will run
@KeithResar
Apps and components run in containers
Container Image
Container
Pod
@KeithResar
Pods are the orchestrated unit in OpenShift
@KeithResar
Masters are the Control Plane
@KeithResar
API and Authentication
@KeithResar
Desired and Current State
@KeithResar
Orchestration and Scheduling
@KeithResar
Placement by Policy
@KeithResar
Services connect application components
@KeithResar
Health and Scaling
@KeithResar
What about unhealthy Pods?
@KeithResar
The Master remediates Pod failures
@KeithResar
What about app data?
@KeithResar
Routing layer for external accessibility
@KeithResar
Access via Web UI, CLI, IDE, API
SOURCE TO IMAGE
Source 2 Image Walk Through
CodeDevelopers 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.
Source 2 Image Walk Through
Container Image Registry
BuildOpenShift 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
Source 2 Image Walk Through
Container Image Registry
DeployOpenShift 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.
@KeithResar
Community CalloutsDOCKER MEETUP
KUBERNETES MEETUP
OPENSHIFT MEETUP
ANSIBLE MEETUP
@KeithResar