This document provides an introduction and overview of containers, Kubernetes, IBM Container Service, and IBM Cloud Private. It discusses how microservices architectures break monolithic applications into smaller, independently developed services. Containers are presented as a standard way to package applications to move between environments. Kubernetes is introduced as an open-source system for automating deployment and management of containerized applications. IBM Cloud Container Service and IBM Cloud Private are then overviewed as platforms that combine Docker and Kubernetes to enable deployment of containerized applications on IBM Cloud infrastructure.

1. Presented by:
Introduction to Containers,
Kubernetes, IBM Container
Service and Cloud Private
Eric Cattoir
Yves Debeer

2. • A µServices based architecture takes a monolithic problem and break it down to be delivered as a set
of independently, individually developed, run and operated services
• Instead of building a single, monolithic application, the idea is to split your application into set of
smaller, interconnected services
• Each µService might have its own architecture, implementation language, configuration, release
cycle
• Each µService might expose a set of APIs to other services or clients.
Same Function
But broken down to a
collection of collaborating
services
Microservices
https://www.nginx.com/blog/introduction-to-microservices

3. • The Benefits of µServices are very apparent at large scale development and delivery
• It tackles the problem of complexity
• each service can be constrained to scope of one business value
• easier to develop and maintain
• Enables each service to be developed independently
• separate teams for each service, different technology stack
• enables each µServices to be deployed independently
• one team (UI for example) can iterate features more rapidly
• Each service to be scaled independently
• number of nodes per service
• hardware used for each node
• µServices makes DevOps possible
• It is much easier to DevOps a set of µServices compared to a single monolithic app that needs to
be updated all at once
Microservices

4. Like any other approach, the µServices architecture has its drawbacks and costs.
• While small µServices are preferable, too many µServices might lead to unacceptable performance and lots
of operational overhead
• The goal of µServices is to sufficiently decompose the application in order to facilitate agile application
development and deployment
• Very small services == communication, maintenance, and operational overhead
• Complexity arises from the fact that a µServices application is a distributed system
• Tolerance for partial failure. Much more complex than intra-process method invocation in monolithic
design
• Harder to test and operate
• Very little help in terms of tools and IDEs
• Implementing changes that span multiple services
• Although its not recommended, but this might happen
(happens too often? you’re composing µServices wrong!)
• Deploying a µServices-based application might be more complex
• Need to deploy a number of moving parts
Drawbacks of Microservices

5. • A µServices based architecture takes a monolithic problem and breaks it down to be delivered as a set of
independently, individually developed, run and operated services
• The benefits of µServices are very apparent at large scale development and delivery
• Like any other approach, the µServices architecture has its drawbacks and costs
• Containers to the rescue!
Microservices
https://www.nginx.com/blog/introduction-to-microservices

6. A standard way to package an application and
all its dependencies so that it can be moved
between environments and run without changes.
Containers work by isolating the differences
between applications inside the container so that
everything outside the container can be
standardized.
Containers

7. • Docker is a (traditionally) Linux Container environment that includes specifications, APIs, tools, daemons, image
libraries, etc.
• Docker regulates how users:
• Build images
• Share images with others
• Run images inside Linux Containers
• Linux Containers are
• An operating system–level virtualization method for running multiple isolated Linux systems (containers) on a
single host with high levels of isolation
• A large number of Linux specific technologies are required to make Linux Containers happen
• Namespaces (mnt, pid, net, ipc, uts/hostname, user ids)
• Cgroups (cpu, memory, disk, i/o - resource management)
• AppArmor, SELinux (security/access control)
• seccomp (computation isolation)
• chroot (file system isolation)
• The greatness in Docker is not the “invention” of containers (they were out there already) but making containers
available to the greater community that do not want to understand the above set of technologies
What is Docker?

8. Key Docker containers concepts

9. Everyone’s container journey starts with one container….

10. At first the growth is easy to handle….

11. But soon it is overwhelming… chaos reins

12. Regain control with Containers and Kubernetes

13. Kubernetes is an open-source
system for automating
deployment, scaling, and
management of containerized
applications.
It groups containers that make up an
application into logical units for easy
management and discovery. Kubernetes
builds upon 15 years of experience of
running production workloads at Google,
combined with best-of-breed ideas and
practices from the community.
What is
Kubernetes?
Production-Grade Container
Orchestration

14. © IBM Corporation 14
Image Registry
API
UI
User
Interface
CLI
Command
Line
Interface
Kubernetes
Master
Worker Node 1
Worker Node 2
Worker Node 3
Worker Node n
Kubernetes Architecture

15. IBM Confidential 15
IBM Cloud Container Service

16. Combining Docker and Kubernetes to deliver powerful tools, an intuitive user
experience, and built-in security and isolation to enable rapid delivery of
applications - all while leveraging IBM Cloud Services including cognitive
capabilities from Watson.
IBM Cloud Container Service

17. Kubernetes abstracted
K8S master K8S worker-1 K8S worker-2 K8S worker-3Hosts (VMs)
e.g. DAL10DataCenter
Containers
Owned by IBM Owned by customer
Kubelet Kubelet Kubelet

18. Intelligent Scheduling Self-healing Horizontal scaling
Service discovery & load balancing Automated rollouts and rollbacks Secret and configuration management
IBM Cloud Container Service

19. Cluster Management
Capabilities

20. Simplified Cluster Management Container Security & Privacy Design Your Own Cluster
Leverages IBM Cloud & Watson Native Kubernetes Experience Integrated Operational Tools
IBM Cloud Container Service

21. + =
www.ibm.com/cloud-computing/bluemix/containers
IBM Cloud
Container Service

22. IBM Confidential
IBM Cloud Private

23. Accelerate your digital transformation
Create new cloud-native
apps
Streamline development
with built-in microservices,
runtimes, containers and
Kubernetes orchestration
plus integrated management.
Modernize your heritage apps
on cloud
Move your apps to the cloud or
re-factor an app and use it in
new development and
application workload models.
Open your data center to work
with cloud services
Protect and leverage your in-
house data and pull in external
sources to fuel your apps.

24. Hybrid Cloud – Where Your Innovation Happens
24
Public Dedicated
Private
Cloud
Traditional
On-Premises
Cloud Provider Network
Customer Network
Customer’s own
• databases,
• heritage solutions,
• authentication provider,
• etc
On-Prem Traditional SWOn-Prem Single Tenant
Private Cloud (IaaS + PaaS)
Off-Prem Single Tenant Private
Cloud (IaaS + PaaS)
IBM managed –OR-
customer managed
Off-Prem Multi Tenant
Public Cloud (IaaS + PaaS)
IBM Cloud
Private
Bluemix

25. IBM Cloud 25
A Cloud Native platform with Enterprise grade content
Leverage existing
investments
Open by design,
preventing vendor
lock-in
Enterprise grade
operations, across
your Hybrid IT
environment
Enterprise grade
services for
Middleware, Data,
Analytics, DevOps
IBM Middleware, Data, Analytics and Developer Services
Cloud enabled middleware, messaging, databases, analytics, and
cognitive services to optimize current investments while rapidly
innovating
Core Operational Services
Simplify Operations Management, Security, and Hybrid integration
Provision infrastructure and apps across Multi-Cloud environments
Kubernetes-based Container
Platform
Industry leading container
orchestration platform across
private, dedicated & public clouds
Cloud Foundry
For prescribed app
development &
deployment
Runs on existing IaaS: System Z IBM
Spectrum
Third Party alliances: Dell Cisco NetApp Lenovo Canonical …
CMS
DevOps
Open
Source

26. Open/Public Content
https://github.com/kubernetes/charts/tree/master/stable
• GitHub repositories
Stable for those to use, Incubator for those to play with
• Add to App Center
Add Helm repo link into ICp and charts will appear in App Center
Add open source capabilities into IBM Cloud Private!

27. Patterns and Templates – Content
Cloud Automation Manager – October
27
Products Product Version(s) Templates
IBM Installation Manager 1.8.6 WAS/IHS/Liberty
WebSphere Base, ND 9.0.0.x, 8.5.5.x Standalone
WAS/IHS Cell
DB2/WAS dev
WebSphere Liberty, Core, ND 17.0.0.x Standalone
Farm
IBM HTTP Server 9.0.0.x, 8.5.5.x Standalone
WAS/IHS Cell
IBM MQ 9.0.x, 8.0.x Single
with MQSC
DB2 ESE 11.x, 10.5.5.x Standalone
Multi-disk
Oracle * Database Enterprise Edition 12c Standalone
Open MySQL Community Edition 5.7 Standalone
Apache HTTP 2.4 Standalone
Apache Tomcat 8.5.11 Standalone
LAMP stack
Terraform templates – Deploy to VMware infrastructure
Automation &
Orchestration
(Chef, Terraform
etc.)
Patterns
Templates
* Oracle supports RHEL7 onlyTemplates support RHEL7 and Ubuntu 16

28. 28
Use Cases
Examples of IBM Cloud Private in use

29. Who are we targeting, and what they can do
Todd
Operations / Admin
Responsible for infrastructure, security,
and management of the environment.
Jane
Enterprise Developer
Responsible for modernizing existing applications
and creating new Cloud Native Workloads.

30. 1. Optimize legacy
apps with cloud
Containers &
Common Services
Next Generation Middleware,
Data & Analytics
Automation & Orchestration
Cloud-enabled
middleware
Self-service Experience
2. Open your datacenter to work with
cloud services
Integration Services
& Cloud Native Programming
Models
Integration & Hybrid
Cloud
APIs
Public Cloud
Services
Machine Learning
on p/z
Blockchain
Business Process
Data & Apps
3. Create new cloud
native applications
Cloud Native
Services & Runtimes
New
Applications
New Applications
On-Premises Software
& Services
Containers &
Common Services
Automation & Orchestration
Containers &
Common Services
Automation & Orchestration
Use Cases driving private cloud adoption

31. Your data center
• Learn from Knowledge Center
• Download Community Edition (does not include master/proxy HA)
• Download Enterprise Edition from Passport Advantage (accept licenses)
• Prepare VMs and Storage, Move binaries to Boot node
• Install (guided UI) – can be offline (no Internet connection)
• Import Helm Charts, Images into IBM Cloud Private
• Update ICp from boot node, user workloads unaffected
Download, Install, Configure, Update
Download binaries from passport advantage, prepare your infrastructure, install
Passport
Advantage
Master
VMs
Storage Proxy
VMs
Worker
VMs
IBM Cloud Private
Boot
node
Private Docker
Registry
Internal Services
Network mesh with tenant isolation
Persistent
Volumes
Offline
Install
Source

32. Free support
Getting Help
Free and Paid support
Slack Channel: Join us on Slack
Ask a question on Stack Overflow
Paid Support
Middleware Products
(WAS, DB2, MQ, etc.)
IBM Cloud Private
Support
IBM Cloud Private
Triage Team
Open Source Support
(Redis, etc.)
Purchased
Watson Cloud Platform
Products
Watson enabled chatbot as a
support entry point to improve
the overall support experience

33. Meetup
https://www.meetup.com/Brussels-PaaS-IBM-Bluemix-and-Cloud-
Computing-Meetup/events/245663906/
33

34. IBM Confidential© 2016 IBM Corporation IBM Cloud
34
Thank You