KVM Forum + oVirt Developers Summit

In the, almost 8 years, since it was founded, the libvirt project grown to be leading open source API for the management of virtualization hosts, with a strong focus on supporting the open source virtualization & container technologies KVM, QEMU, Xen and LXC. Most people working in the open source virtualization management space have an understanding of the core features and architecture of libvirt. This talk will focus on a selection of recently developed features and of some of the less well known advanced features of libvirt. It will describe capabilities for mutual exclusion / locking against guest disks; fine grained access control against individual operations, users and objects in the API; the sVirt mandatory access control framework; auditing and structured logging via the systemd journal; integration with systemd for cgroups resource management; and more.

Have you ever wondered how KVM is used in a full blown Data Center virtualization solution? oVirt is an open virtualization project which enables the management of multi-host, multi-tenant virtual data centers, including high availability, VM and storage live migration, storage and network management, system scheduler and more. oVirt provides an integration point for several open source virtualization technologies, including kvm, libvirt, spice, oVirt node and numerous OpenStack components such as Neutron and Glance. The session will provide an introduction to the oVirt project and shed light on how a data center administrator's actions in a web UI are translated into KVM commands running on the hypervisors.

Session description coming soon. 

For several years now, the oVirt project is leveraging KVM and relevant technologies (ksm, etc) in data center virtualizations. Being a mature and feature reach, oVirt not takes another step forward with introducing Quality of Service management. This presentation will review recent oVirt improvements in the areas of memory and network QoS management. The first part will discuss the memory and networking QoS features from the frontend and API point of view. The second part will have a special focus on how memory overcommitment works and how it can be configured to efficiently utilize server resources using KSM and Balloon policies in MoM (Memory overcommitment manager). The last part will be dedicated to the new multi policy mechanisms in MoM and how to leverage them for a more fine grained memory policy tuning.

Every virtualisation project has to start somewhere, and each one finds its own challenges and problems as it moves forward. This presentation chronicles the journey so far in Keele University's virtualisation story, from pilots and early discontent with VM platforms (Xen and VMWare), through to production with KVM, and a promising future with oVirt and iSCSI shared storage. Martin Goldstone and Gary Lloyd will address the decisions made and why, the problems and challenges faced, along the solutions found, and will look forward to what virtualisation may mean for Keele in the future.

The Linux storage stack is composed of many layers, starting at the device itself (HW), through the kernel modules, user space daemons and the various administration tools. In this session we will review how oVirt utilizes these components in order to implement storage virtualization, using both file and block shared storage, while facing the challenges introduced when working on a distributed system. We will review the usage of the Linux storage stack by oVirt and the architecture decisions at the heart of oVirt storage by introducing the oVirt storage APIs. We shall present how the lessons learned by five years of oVirt storage development can be applied to the openstack storage stack. 

The Trusted Compute Pools (TCP) feature in oVirt provides a way for administrators to deploy VMs on trusted hosts, which run expected hypervisor on expected hardware with expected configuration. The TCP feature in oVirt comprises an attestation broker in engine, modifications to the VM creation UI and template, and enhancements for RESTful API among others. This feature requires deploying an attestation service based on OpenAttestation(OAT), an Intel  open source project  with the mission to provide an SDK to build remote attestation services for ISVs to implement cloud/enterprise security use models based on Intel® Trusted Execution Technology(Intel® TXT). This presentation will introduce the OAT project architecture, the TCP feature and its implementation details.