Openshift Container Platform

1. Matt Micene
Solutions Architect
matt.micene@dlt.com
14 July 2016
OpenShift Container Platform

2. OpenShift2
EVOLUTION

3. OpenShift3
CONTAINER PATHWAYS
Managing application dependencies

4. OpenShift4
APPLICATION STACK DEVELOPMENT ENVIRONMENT
WHY PAAS?
Basic OS
JVM
Static web server
Front-end platform
Database layer
Application code
Development VM
QA Server
Customer Data Center
Public Cloud
Contributors Laptop
Production Servers
Production Clusters
Application development got complex

5. OpenShift5
PLATFORM AS A SERVICE
More than just an abstraction layer

6. OpenShift6
APPLICATION STACK DEVELOPMENT ENVIRONMENT
WHY PAAS?
Basic OS
JVM
Static web server
Front-end platform
Database layer
Application code
Development VM
QA Server
Customer Data Center
Public Cloud
Contributors Laptop
Production Servers
Production Clusters
Application development got complex

7. OpenShift7
OPENSHIFT CONTAINER
PLATFORM
Open source private PaaS at scale
ORCHESTRATION & MANAGEMENT
CONTAINER API
CONTAINER HOST
LANGUAGES, RUNTIMES, MIDDLEWARE,
DATABASES, OTHER SERVICES
DEVOPS TOOLS & USER EXPERIENCE
DOCKER
Standard software packaging mechanism through
lightweight Linux containerization
KUBERNETES
Cluster management and orchestration of
containers, scheduled and packed dynamically
Automatic container builds, intelligent deployments,
image management, application management, Web
Console, CLI, IDE Plugins, RESTful API, RHEL
SCL, JBoss xPaaS
OPENSHIFT
RHEL / Atomic
Enterprise grade container optimized Linux
operating system

8. OpenShift8
Software Collections & JBoss
CVE Fixes
Bug Patches
Support Life Cycle
Technical Support
Red Hat Certified Containers
CVE Fixes
Bug Patches
Technical Support
Any Docker Registry
Supported Container API
Supported Execution
SUPPORTED ECOSYSTEM
Choose the right tool for the job

9. OpenShift9
xPAAS
●
JBoss Business
Process
Management *
●
JBoss Business
Rules Management
System *
●
JBoss A-MQ
●
JBoss Fuse*
●
JBoss Data
Virtualization*
●
JBoss Enterprise
Application Platform
●
JBoss Web Server /
Tomcat
●
JBoss Developer
Studio
JBoss and middleware platforms for Openshift
Application
Container Services
Business Process
Services
Integration
Services
Mobile
Services
●
Red Hat Mobile*
* coming soon

10. How OpenShift Supports
DevOps

11. OpenShift11
BUILD & DEPLOYMENT
AUTOMATION

12. OpenShift12
APPLICATION REPO
Applications can be seeded from a canonical source repository (aka Git)

13. OpenShift13
CONTAINER CHOICE
Docker image base layer is selected from a registry

14. OpenShift14
IMAGE LAYERING
Openshift layers base images with the application repo data

15. OpenShift15
SHARING
The application image is registered and inserted into the registry

16. OpenShift16
SCHEDULING
Application containers are scheduled and deployed to nodes

17. OpenShift18
NEW IMAGES
Updated images are added back into the Registry
Application
Updates

18. OpenShift19
UPDATE STRATEGY
New Images are deployed as rolling, replacement, or custom updates
Application
Updates

19. How OpenShift Works

20. OpenShift21
INFRASTRUCTURE
Openshift runs on your choice of infrastructure

21. OpenShift22
NODES
Nodes are instances of RHEL where applications will run

22. OpenShift23
CONTAINERS
Application services run in Dockers containers, distributed across your nodes

23. OpenShift24
PODS
Pods bundle one or more Docker container(s) as a single unit

24. OpenShift25
MASTERS
Drive kubernetes to orchestrate nodes and applications

25. OpenShift26
API
A Master provides an API for authenticated users and clients

26. OpenShift27
METADATA STORE
All Masters use an etcd distributed key-value store for metadata persistence

27. OpenShift28
SCHEDULING
Pod placement is determined based on a defined, pluggable policy

28. OpenShift29
REGISTRY
Registries store images and versions for provisioning

29. OpenShift30
LIFECYCLE
The kubernetes controller manages the lifecycle for each Pod

30. OpenShift31
SERVICES
Services allow related pods to connect to one another

31. OpenShift32
PERSISTENCE
Pods can attach to storage for stateful services and applications

32. OpenShift33
ROUTING
A Software Defined Network (SDN) layer routes external application requests to the
desired pod

33. OpenShift34
ACCESS
Developers access Openshift via the Web, CLI, or IDE
* coming soon

34. OpenShift35
OPENSHIFT VALUE

35. OpenShift36
THE RED HAT SOLUTION

36. 37MICHAEL EPLEY
THANK YOU
plus.google.com/+RedHat
linkedin.com/company/red-hat
youtube.com/user/RedHatVideos
facebook.com/redhatinc
twitter.com/RedHatNews