We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Pet-VMs and Containers united?

Formal Metadata

Title
Pet-VMs and Containers united?
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
How do you integrate containers in your IaaS? In a VM based IaaS environment,introducing containers can be a painful experience. Most likely you end uprunning containers inside VMs to reuse existing infrastructure, or you startdividing your data-center into a container- and a VM-world. Either way, youhave two management solutions and non optimal resource management. But what ifwe put VMs inside containers? Would such a copernican revolution give us somebenefits? This talk covers our research around using Kubernetes as a virtualmachines cluster manager. How do you integrate containers in your IaaS? In a VM based IaaS environment,introducing containers can be a painful experience. Most likely you end uprunning containers inside VMs to reuse existing infrastructure, or you startdividing your data-center into a container- and a VM-world. Either way, youhave two management solutions and non optimal resource management. But what ifwe put VMs inside containers? Would such a copernican revolution give us somebenefits? This talk covers our research around using Kubernetes as a virtualmachines cluster manager. First we will briefly look into what a typical container and a typical VM is.Then we will look into the details on how resource and device limitations areenforced on VMs. In our research we used oVirt, so comparing its host sidestack (VDSM/libvirt/QEMU/systemd) to Kubernetes container host side stack(kubelet/docker/rkt/systemd/cni). At the end we will have a betterunderstanding of the differences and overlaps, and can therefore consider howto manage Pet-VMs and containers in the same cluster, managed by kubernetes.