Apr 30, 2018 - OpenShift. ⢠Ranger. ⢠Google Cloud ... Docker Datacenter. 18. 30.04.2018 We orchestrate our IT lands
Alles Container oder was? Wir orchestrieren unsere IT-Landschaft Trivadis triCast 24.04.2018, 16:00 bis 16:45 Uhr Andy Moncsek Stefan Bartram
@trivadis
BASEL BERN BRUGG DÜSSELDORF HAMBURG KOPENHAGEN LAUSANNE
tricast
FRANKFURT A.M. FREIBURG I.BR. GENF MÜNCHEN STUTTGART WIEN ZÜRICH
Alles Container oder was? Wir orchestrieren unsere ITLandschaft Andy Moncsek Principal Consultant
[email protected] Twitter: @AndyAHCP
BASEL BERN BRUGG DÜSSELDORF HAMBURG KOPENHAGEN LAUSANNE
FRANKFURT A.M. FREIBURG I.BR. GENF MÜNCHEN STUTTGART WIEN ZÜRICH
Agenda 1. Basics 2. Overview orchestration 3. Challenges 4. Conclusion
3
30.04.2018
We orchestrate our IT landscape
Classification
4
30.04.2018
We orchestrate our IT landscape
Classification
5
30.04.2018
Container & Orchestration introduction
Classification
6
30.04.2018
Container & Orchestration introduction
Classification
7
30.04.2018
Container & Orchestration introduction
Container
8
30.04.2018
We orchestrate our IT landscape
Developer: Build once, run anywhere
Operator: Configure once, run anythin
Multiple HW env
Multiple Stacks
Container
9
30.04.2018
We orchestrate our IT landscape
Docker
10
30.04.2018
We orchestrate our IT landscape
Docker Build • Images with your application & entire env/system Ship • Share images (dockerhub.com, private registry) Run • Docker Client, Daemon, Registry
11
30.04.2018
Conclusion Docker For Developers •
Isolated, repeatable and relocatable runtime environment setup
•
Isolation between containers and against the host
•
Fast and Simple in Use
For Operators
12
30.04.2018
•
A standard format for an „executable“
•
A unified API for operating these executables
We orchestrate our IT landscape
Docker competitor
A lightweight, OCI - compliant container runtime
• • • •
13
30.04.2018
Optimized for Kubernetes Any OCI-compliant registry Improved security Performance at scale
We orchestrate our IT landscape
We need more than containers
14
Scheduling
Security
Decide where to deploy containers
Control who can do what
Lifecycle and health
Scaling
Keep containers running despite failures
Scale containers up and down
Discovery
Persistence
Find other containers on the network
Survive data beyond container lifecycle
Monitoring
Aggregation
Visibility into running containers
Compose apps from multiple containers
30.04.2018
We orchestrate our IT landscape
Orchestration
15
30.04.2018
Bezeichnung Präsentation
Docker/Container Orchestrierung
16
30.04.2018
We orchestrate our IT landscape
Markt & Technologie Kubernetes • • • •
17
OpenShift Ranger Google Cloud ...
30.04.2018
Mesos •
DC/OS
We orchestrate our IT landscape
Docker • Docker Enterprise
Others • •
CloudFoundry AWS
Docker Datacenter
18
30.04.2018
We orchestrate our IT landscape
Docker Datacenter
19
30.04.2018
We orchestrate our IT landscape
Mesosphere DC/OS
20
30.04.2018
We orchestrate our IT landscape
Mesosphere DC/OS
21
30.04.2018
We orchestrate our IT landscape
Kubernetes
22
30.04.2018
We orchestrate our IT landscape
Kubernetes
23
30.04.2018
We orchestrate our IT landscape
Markt & Technologie Kubernetes • • • •
OpenShift Ranger Google Cloud ...
Mesos •
DC/OS
Docker •
Docker Enterprise
Kubernetes support 24
30.04.2018
We orchestrate our IT landscape
Others • •
CloudFoundry AWS
CaaS vs. PaaS
Kubernetes
OpenShift
25
30.04.2018
We orchestrate our IT landscape
Challenges
26
30.04.2018
We orchestrate our IT landscape
Architecture - initial
27
30.04.2018
We orchestrate our IT landscape
o
Move existing apps to container
o
Scaling
o
Restart
Architecture - state
28
30.04.2018
We orchestrate our IT landscape
o
Stateful (JSF) / Stateless (SPA)
o
Session replication
o
Redeployment
o
Stateful sets
Architecture o
Container services using other services (from container or on-prem.)
o
Integrated with existing architecture
o
Interacts with external services (cloud)
o
Scaling / Healing / Workload
o
Fast (re-)start
o
Stateless …
29
30.04.2018
–
We orchestrate our IT landscape
modularized & integrated
Architecture
30
30.04.2018
We orchestrate our IT landscape
hybrid
o
Outsource workloads to the Cloud (on demand)
o
Access internal services from the Cloud
Service discovery
31
30.04.2018
We orchestrate our IT landscape
o
Discover by name or labels
o
Discovery through namespaces
o
Discover external services
o
Expose services
o
Routing
Build & Deploy
o
Integrate with existing pipeline
o
Build pipeline in CaaS/PaaS
o
Namespaces & stages
o
Rolling updates, A/B testing
o
Dev(Sec)Ops
32
30.04.2018
We orchestrate our IT landscape
Configuration
33
30.04.2018
We orchestrate our IT landscape
o
Configuration injection
o
Secrets
o
Environments
Security
34
30.04.2018
We orchestrate our IT landscape
o
Communication with other system in house
o
in-going / outgoing traffic
o
Communication between containers
o
Traffic interception
o
Role based access
o
…
Persistent storage
35
30.04.2018
We orchestrate our IT landscape
o
Integrate with existing storage
o
Cluster FS
o
Cloud storage
Packaging
https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/
36
30.04.2018
We orchestrate our IT landscape
o
Container repositories
o
App container
o
Configuration
o
Packaging
o
Versioning
Monitoring
37
30.04.2018
We orchestrate our IT landscape
o
Cluster / Application & Container metrics
o
Distributed logging
o
Tracing
o
Log analysis
Summary & Conclusion
38
30.04.2018
We orchestrate our IT landscape
Summary ▪ Containerize you IT landscape is “No free lunch” ▪ Decide wisely between CaaS & PaaS
▪ If the your IT remains the same (ops, build, …) and Container is only a runtime to you, go with CaaS
▪ If DevOps is an option/goal, choose PaaS
39
30.04.2018
We orchestrate our IT landscape
Conclusion ▪ With PaaS you have more “vendor lock-in”, (even when building on standards)
▪ Think of support vs. diy ▪ Update & security
▪ Knowhow
40
30.04.2018
We orchestrate our IT landscape
Conclusion ▪ CaaS & PaaS usage is constantly growing ▪ Increases development velocity & robustness ▪ Operational efficiancy ▪ Basis for concepts like FaaS & “modern” architectures
41
30.04.2018
We orchestrate our IT landscape
Thank you Andy Moncsek Principal Consultant
[email protected] Twitter: @AndyAHCP
42
30.04.2018
We orchestrate our IT landscape
Fragen und Antworten Andy Moncsek Senior Consultant
[email protected]
Stefan Bartram Senior Partner Manager
[email protected]
43
30.04.2018
Trivadis triCast
triCast & Veranstaltungshinweise Die nächsten triCast Termine Jeweils Dienstags, um 16 Uhr
Trivadis LIVE Veranstaltungen (https://www.trivadis.com/de/events)
(http://m.trivadis.com/tricast-about)
44
▪
24.04.2018 - Alles Container oder was? Wir orchestrieren unsere IT-Landschaft
▪
29.05.2018 - NLG – Natural Language Generation: Enter Narratives
30.04.2018
Trivadis triCast
▪
JAVA Forum 2018 05. Juli 2018 in Stuttgart
▪
11. Finanzplatztag der WM-Gruppe 07. – 08. März 2018 in Frankfurt
Schön, dass Sie dabei waren! Stefan Bartram Senior Partner Manager Tel. +49 89 99 27 59 322
[email protected]
@trivadis
tricast