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 up running containers inside VMs to reuse existing infrastructure, or you start dividing your data-center into a container- and a VM-world. Either way, you have two management solutions and non optimal resource management. But what if we put VMs inside containers? Would such a copernican revolution give us some benefits? This talk covers our research around using Kubernetes as a virtual machines 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 up running containers inside VMs to reuse existing infrastructure, or you start dividing your data-center into a container- and a VM-world. Either way, you have two management solutions and non optimal resource management. But what if we put VMs inside containers? Would such a copernican revolution give us some benefits? This talk covers our research around using Kubernetes as a virtual machines 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 are enforced on VMs. In our research we used oVirt, so comparing its host side stack (VDSM/libvirt/QEMU/systemd) to Kubernetes container host side stack (kubelet/docker/rkt/systemd/cni). At the end we will have a better understanding of the differences and overlaps, and can therefore consider how to manage Pet-VMs and containers in the same cluster, managed by kubernetes.