Virtualization and IaaS
LXD for mixed system containers and VM workloads
Introducing LXD's new virtual machine feature
LXD is most known as a system container manager, offering a simple user experience and images for most Linux distributions.
It also offers a simple REST API, network and storage management, project views and easy clustering to dozen of hosts.
Over the past few months, LXD has now grown the ability to run virtual machines alongside containers, using the exact same REST API and configuration.
This presentation will cover that new feature, why it was done, where it's at now and where we're going with it, as well as provide a quick demo of setting up a small LXD cluster and running both containers and virtual machines on it.
LXD is an open source system container manager, developed by the team behind LXC, written in Go and that's been around for over 5 years now.
It's widely used both on servers, running the backend of services such as Travis-CI and on everyday devices like Chromebooks.
Containers are created from images with prebuilt images available for most Linux distributions.
Multiple hosts can easily be clustered together to form one large virtual host, exposing the exact same API as a single host would.
Storage pools and networks can also be created and managed through LXD and resources can be segmented into projects.
With the addition of virtual machine support (through qemu), it is now possible to manage a mixed deployment of virtual machines and containers, sharing the same configuration, storage and networks. With the use of our built-in agent, the exact same operations that are normally possible against a container also become possible against virtual machines, including executing commands, transferring files, ...
Existing API clients for LXD can also now drive both containers and virtual machines without any API changes required.
Additional information
| Type | devroom |
|---|
More sessions
| 2/2/20 |
A tribute, from the FOSDEM Virtualization & IaaS Devroom, to the memory of Lars Kurth Please note that this is a late addition to the schedule, and the program will now be starting 10 minutes earlier than originally scheduled.
|
| 2/2/20 |
Because virtualization is everywhere, new challenges in the IT world are revealing that this crucial component has to be improved on a regular basis. This requires a lot of coordination between Open Source projects as well as intense research and development efforts. NVMe storage performance revealing hidden bottlenecks, Intel CPU flaws changing the security landscape regarding isolation, increasing complexity of stacks requiring more and more components working together, hardware ...
|
| 2/2/20 |
A whole bunch of CPU vulnerabilities were revealed in the past few years: Meltdown and Spectre, SSB, L1TF and MDS -- and there's little hope that we've seen them all. Every time there is a new vulnerability released, big cloud provides on day 1 claim that their hosts were updated and that their users are secure. Is this so or do we also need to do something inside our Linux guests to mitigate these vulnerabilities? And, do we have the required tools to actually do the mitigations? Are all of ...
|
| 2/2/20 |
This talk covers the new virtio-fs shared file system that allows a host directory tree to be shared with guests. Sharing files with the guest is required by several use cases including container VMs, File-System-as-a-Service, and traditional virtualization. virtio-fs goes further than previous attempts by taking advantage of the co-location of the guest and host using DAX to share the host page cache. This presentation explains how to use virtio-fs, a bit about how it works internally, and the ...
|
| 2/2/20 |
iouring is a new kernel asynchronous I/O processing mechanism proposed as a much faster alternative for conventional Linux AIO. Patches were merged in Linux 5.1 and gave a promised performance boost. We decided to integrate it into QEMU to make virtualized storage devices work more efficiently. Let's take a look at how iouring works in QEMU.
|
| 2/2/20 |
Running applications in the Cloud has changed the way users develop and ship their code. Quite recently, the community has given rise to microservices-based approaches, towards solutions that follow the paradigm of Platform-, Software-, and Function-as-a-Service (PaaS, SaaS, and FaaS respectively). To accommodate user demands, while maintaining security and isolation, Cloud vendors have adopted a hybrid approach where user workloads are being executed in lightweight sandboxed environments, where ...
|
| 2/2/20 |
Teaching oVirt to work with 4k storage.
|
