you can’t “contain” this trend - the channel company · you can’t “contain” this trend...
TRANSCRIPT
#XSP18
YOU CAN’T “CONTAIN” THIS TREND What Solution Providers Need To Know About Docker, Kubernetes, PKS & More
#XSP18
WHOAMI
• CTO – Cardinal Solutions Group• 18+ years at Cardinal • ~500 person System Integrator
• Microsoft Worldwide Partner of the Year – “Open Source on Azure”
• Partners with Microsoft, Red Hat, and Pivotal in this space
[email protected]@bebken
#XSP18
Agenda
DevOps and the Need for Containers – the “Why”
Containers and Container Orchestrators - the “What”
Customer Approach and Vendor Landscape – the “How”
1
2
3
#XSP18
DEVOPS & WHY CONTAINERSThe “Why”
#XSP18
10+ Years AgoOrder to Cash
Line of Business 1
#XSP18
10+ Years AgoOrder to Cash
Line of Business 2 Order to Cash
Line of Business 1
#XSP18
Result: Typical Customer Scenario
• No integration / testing environment• 70+ people to deploy on Friday night• 25-50% deployment success rate• Rollback all-day Saturday• 1 person who understood how it all worked together• Production surprises, especially around performance
10+ years later --- we still have the same problems!
#XSP18
Improvements / Evolution of ITApplications Processes Infrastructure
time
Source/credit:
#XSP18
And Yet…
Applications are still deployed relatively the same way …. Complex integration, configuration, and implementation each time
devs ops
Deployment fiascos :“it worked on my machine”
QA environment nowhere like production
Weeks of integration testing for a single code change
Business: GO FASTER!
#XSP18
To the cloud!
Let’s move to the cloud so we can digitally transform!!!
• Lift and shift just recreates the same problems• Can’t simply rewrite what took years to develop• Need to develop cloud practices (governance, cost, etc.) • Afraid of getting burned or “locked in”
#XSP18
Improvements / Evolution of ITApplications Processes Infrastructure
time
Source/credit:
#XSP18
CONTAINERS & ORCHESTRATORSThe “What”
#XSP18
DEVOPS & WHY CONTAINERSThe “Why”
What is a Container?
• Isolate an application, its configuration, its dependencies into a self-contained unit that can run anywhere
• Unit can be reused in any stage of deployment – development, QA, production
Developers:
Ops: • This sounds like virtual machines
applibs
#XSP18
Understanding Containers
The big difference versus VMs: the operating system architecture is shared across containers = more server density
Hardware
Host OS
LIBS A LIBS B LIBS..
APP A APP B
Hardware
Guest OS
LIBS A
APP A
Hypervisor
Guest OS
LIBS B
APP B
Guest OS
LIBS C
APP C
Hardware
Container
LIBS A
APP A
Host Minimal OS
Container
LIBS B
APP B
Container
LIBS C
APP C
Physical Virtual Container
layer of abstraction
#XSP18
Docker
• Containers have been around for some time within Linux
• Docker created open source software to build and manage containers
• Docker made containers very easy, especially the packaging
• Docker is an open-source container format, but also makes a set of tools for managing containers (e.g. Swarm)
Docker and containers (packaging) have become synonymous
#XSP18
We Need more than Containers!!!!
SchedulingDecide where to deploy containers
Containers alone do not solve enterprise production applications
Lifecycle and healthKeep containers running despite failures
DiscoveryFind other containers on the network
MonitoringVisibility into running containers
SecurityControl who can do what
ScalingScale containers up and down
PersistenceSurvive data beyond container lifecycle
AggregationCompose apps from multiple containers
#XSP18
Container Orchestrators
• Similar to a Hypervisor, a Container Orchestrator automates deployment, scaling, and management of containerized applications – this is where the magic happens
• Kubernetes is the most prevalent Open Source Container Orchestrator, but there are others:
• Marathon container for Apache Mesos (distributed OS kernel) –Airbnb, Siri, Yelp
• Aurora – open source by twitter
Kubernetes
#XSP18
CUSTOMER APPROACH & VENDOR LANDSCAPEThe “How”
#XSP18
The Vision
• Adopting a container strategy will allow applications to be easily shared and deployed
● Consistent environment and tools
● Predictable building blocks
● Faster deployment
#XSP18
Customer Approach to App Modernization
Existing Application
APP
Modern Microservices
Add new services or start peeling offservices from
monolithic code.
Modern Methodologies
Implement CI/CDand automation.
Modern Infrastructure
Move to thecloud as VMsor Containersor refresh HW.
Containerize Applications
Re-architectapps for scale with containers.
Migration Path (i.e. Services Opportunities)
#XSP18
Commercial Implementations
Public Cloud Providers
Commercial Software
