Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Back then...
New application in an Enterprise meant:
● Order new HW, HW fingerprint, Networking
● Reuse of environments for dev/testing
● Use of simulated integrations
Then Virtualization came
Providing:
● Reuse of HW
● Operational efficiency
● Other means for applications to solve their problems:● HA● Storage● Backup...
But...
Virtualization added an extra level of:
● Complexity
● Management
● Performance overhead
Containers
A technology emerged that provided:
● Isolation between applications/processes
● Resource control
● Security between applications
● Easy packaging of applications and its dependencies
More than traditional Virtualization
● Higher density of apps
● Faster application startup time
● Have developers create the application
(and the environment)
Also
● Easy to use (Docker)
● Running on existing and proven
technology (cgroups, kernel
namespaces, selinux)
● Standardized formats (Docker, runC,
appC, …)
● High user base
● Evolving fast
Why has gotten where it is now?
● Many people started using it
● It was hugely hyped
● Blogs, demos, samples, ....
● Internet was full of what you needed
● Everything was open sourced and shareable
And then it came the enterprise
Many Enterprise features missing (or not enterprise ready):
● Easy on a single host
● Networking
● Storage
● Security
Enterprises wanted
To complement Virtualization with this new technology:
● Expedite Innovation to market
● Accelerate application development
● Increase operational efficiency
● Enable DevOps
Something was missing
What we had
What we needed
to the rescue
Why Kubernetes?
● Google had a long experience with running containers at scale
(since early 200x)
● They had a good base (Borg and Omega) and took ideas from
them that they made public
● They open sourced the project
● They invested resources on it
Soon...
Kubernetes evolved into an awesome orchestration engine for
containers
● Not only a scheduler
● Manages networking
● Manages storage
● Extensible
What's up with
Since 2012 Red Hat has a PaaS called OpenShift that was
running on top of Linux kernel using homebrew container
technology called Gears
2015
What OpenShift means to the IT
And all this because...
We are upstream first