JOURNEY OF CONTAINERSMr. Mayur S Patil,

Hire me for Full time: Python, Devops & Virtualization,Pune, India.

Email: ram.nath241089@gmail.com Mob: +919421827519

Contents:

• About Me•What are containers?• Rise of containers• Linux Containers• Docker• Kubernetes• Apache Mesos• Conclusions

About Me

•Working on Python3 for faster work and style• System Level technology buff[2]•Automation Enthusiast like Euca-install, Nagios•Presented talks Marathi & Eng in GNUNify & Fudcon.•Always focus on Basics rather than “Plain” learning.• Thinking about insane ideas to turn into investing ones.•Waiting to get hired.

• Who:• Jacques Gélinas – Multiple servers on single system• Paul Menage – cgroups• Tejun Heo - massive redesign for containers

• What:• Instance of OS Image.• OS virt technique to use hardware virtualization for creation

of isolated environments similar like namespaces.• Cgroups = limits how much you can use;

namespaces = limits what you can see (and therefore use)

Containers

Containers• How:

•Work:•Uses OS & CPU level resources directly•Host OS is sufficient•You can run containers on Linux machine itself

•Different than VM•Not using Whole OS•Puts emphasis on Host OS; not Hypervisor.•Lightweight.

• When:• Frequent Environmental changes• Application Deployment Specific• Less workload as well as resource utilizations

• Limitations:• Not right for all scenarios• Failed to match performance in case of cross platform• Weaker isolation• Crippled in case of dependency break

Containers

• Who:• Solomon Hykes

• What:• Software Std platform required to run containers• Directly virtualizes OS, VT-X for performance. [That’s why OS Virt]• Probs Solves:• Dependency Crippling• Cross platform support• Layer of Security

• How:• Work (Windows):• Docker uses OS Virtualization without using anything.• If not, it takes support of hypervisors for it.• After that it loads boot2iso file as a means of Linux Container in which docker

client will run.

Docker

• When:• Portability• Community & Enterprise supported Images• As version control system for your entire app's operating system along with team• To run your code on your laptop in the same environment as you have on your

server (try the building tool)• To devtestops• With your Puppet Manifests (remember, Docker doesn't do configuration

management)

• Limitations:• Networking between containers is tedious in docker.• Also, for docker on cross platforms• Backward compatibility• Not ready Cross Platform

Docker

• Who• Joe Beda, Brendan Burns and Craig McLuckie

• What• Open Source Orchestration Framework for life cycle management of Containerized

applications.• If you want to manage containers (with or without docker) hosted on different hosts

than your current one, Kubernetes will help you to network them and even manage their creation, run, stop and destruction also.

• How:• Heterogeneous set of user-specified containers are neatly and automatically packed

into the available nodes by Kubernetes.

Kubernetes:

•When:• Verifying identity, and setting up rules for authorization of users.• Debugging your applications.• Logging application events, which help in debugging and monitoring the health of

your clustered.• Monitoring resource use among the different components of a clustered.• Automatically scaling the resources needed.• Managing allocation of files to containers.

• Limitations:• Replication issue at data centers: auto discovery & • Long way to learn• [Current] No company using it in Production.

Kubernetes:

• Who• Benjamin Hindman, Andy Konwinski, and Matei Zaharia, as well as professor Ion

Stoica {University of Berkeley}. • What• It provides efficient resource isolation and sharing across distributed applications, or

frameworks.• Mesos is a kernel designed to run on distributed systems.• In a distributed environment, Mesos runs on every machine.• Scheduler capable of handling multiple resources.

• How:• Mesos controller with Master slave/agent architecture

Apache Mesos

•When:• Proven to scale, used at Apple with 75.000 nodes• Extremely flexible. It is currently used in production by many enterprises and there

are many Mesos frameworks available that can fit different needs.• Relatively old, easier to find production stories and best practices to use it.• It can use different formats than docker containers

Apache Mesos

• Kubernetes • It is a great place to start if you are new to the clustering world; it is the quickest,

easiest and lightest way to kick the tires and start experimenting with cluster oriented development. It offers a very high level of portability since it is being supported by a lot of different providers (Microsoft, IBM, Red Hat, CoreOs, MesoSphere, VMWare, etc).

• Mesos• If you have existing workloads (Hadoop, Spark, Kafka, etc), Mesos gives you a

framework that let's you interleave those workloads with each other, and mix in a some of the new stuff including Kubernetes apps.

Kubernetes vs Mesos

• Containers have triggered Devops platform to new height.

• It can used as standalone as well as in Integration with Cloud.

• Containers are lightweight than VMs yet portable in distributed clusters.

• Docker has given popularity hike to containers.

Conclusions

Fun time

THANKS!