4. OS-level Isolation
• Isolation at individual kernel subsystem
level (e.g. filesystem, process table, etc)
• User-level process (LXC, libcontainer)
orchestrates these subsystems to create
a container
Existed for Many Years
Solaris Zones, FreeBSD Jails, OpenVZ
Why?
• Process isolation
• Reproducible environment
• Enables management at scaleHardware
OS Kernel
OS File system
Userspace
Container
Appprocess
Appprocess
Appprocess
Appprocess
Appprocess
Container
Appprocess
Appprocess
Introduction to Linux Containers
4
5. With containers you can move through these
stages very quickly
5
DEV TEST PROD
Drive Business Agility
7. Challenges With Container Adoption
• Automation and Management
• You can always run containers –
but who's managing the
lifecycle?
7
8. Containers and OpenStack
• OpenStack delivers the infrastructure
automation
• Containers are the popular method for
packaging and distributing applications
• Using containers to run OpenStack services.
– Multiple community initiatives containerize the
modules.
• Here to stay, integral part of the OpenStack
community going forward.
• Key projects:
– Magnum – Deploying container orchestration
systems (Kubernetes/ Mesosphere)
– Kolla – Containerizing OpenStack services
– Kuryr – Container Networking
8
Agility
Efficiency
Control
9. Value of Container Orchestration
• Container visibility – How many
and where?
• Health checks
– Ensuring that in the event of
failure, the container is brought
back to life
• Ensure host-container
affinity/anti-affinity
• Inter host container networking
• Container Lifecycle
Management
CONFIDENTIAL 9
10. Deploying Kubernetes for Orchestration
Many options:
• Deploy from source
• Manually deploy pre-built
binaries on OpenStack
instances
• Use open source community-
developed automation solutions
in your OpenStack cloud. i.e
Kargo
• Use Magnum
CONFIDENTIAL 10
15. Summary
15
1 Why Containers? To Increase options for application deployment
2 Why Containers and OpenStack? Get infrastructure automation for container hosts
3 Why Container Orchestration? Simplify container lifecycle management
4 Why OpenStack with VMware?
Simplified private cloud on proven enterprise grade
infrastructure
VMware Integrated OpenStack (VIO)
16. More on Containers @OpenStack East
• Extending Cinder to Containers… Beyond the Stack!
– John Griffith – NetApp
• Leveraging OpenStack to run Meso/Marathon at Time
Warner Cable
– Kevin Wood – Charter Communications
– Charlie Cano – AVI Networks
CONFIDENTIAL 16
17. Thank you! Q&A
To Learn More Visit:
http://www.vmware.com/products/openstack
Try the VIO Hands On Lab!
www.vmware.com/go/openstacklab
Editor's Notes
To keep up, you need to innovate, its no longer about the best car, it is about delivering new features quickly without disruption – Speak of other examples – John Deere, Sonos, Kaiser Permanente etc.
Source:
http://www.businessinsider.com/elon-musk-on-tesla-over-the-air-software-update-summon-feature-2016-1
Containers to the rescue
Question to the audience
How many of you have been using Containers in production or thinking about them?
Containers allow developers to package up their applications and then seamlessly move through the application development lifecycle, from coding on their laptop, to testing in a staging environment, to production where they can deliver that application out to end users. VMware is seeing a lot of interesting use cases with containers from developers and application teams.
Because containers are portable across different types of infrastructure — they can run in AWS just as easily as they can on bare-metal servers — containers make deployment of code extremely convenient. For development and test workloads this eliminates a lot of the guesswork and finger pointing that tend to occur when slight difference between the development and test environments causes a deployment to fail.
For developers, containers are super easy to use. All you need is Docker and a laptop and you’re off and running.
But for operations, containers are much more challenging to operate in production. You don’t just need Docker, but you also need enterprise grade networking, security, data persistence, monitoring, logging, backup, disaster recovery, availability, and so on. Essentially you need to all the characteristics of any application that is run in production. This is hard!
Magnum – Deploying container orchestration systems (Kubernetes/ Mesosphere)
Kolla – Containerizing OpenStack services – separate from Mirantis, Rackspace and Intel initiatives
Kuryr – Container Networking
High-level architecture of Kubernetes on VIO. The orange App boxes represent containers. The gray boxes represent VMs running on top of vSphere.
Kubernetes management dashboard
Weave Scope: open source tool for visualizing Kubernetes workloads and the connections between containers