Re: [Users] node spin including qemu-kvm-rhev?

I'm going to try top posting this time to see if it ends up looking a bit better on the list.

By the 'ovirt hypervisor packages' I meant installing the OS first of all and then making it into an ovirt 'node' by installing the required packages, rather than installing from a clean slate with the ovirt node iso. Sorry if that was a bit unclear.

______________________________________________________________________ From: Fabian Deutsch To: Paul Jansen Cc: Doron Fediuck; users Sent: Monday, 7 April 2014 5:20 PM Subject: Re: [Users] node spin including qemu-kvm-rhev? Am Sonntag, den 06.04.2014, 19:15 -0700 schrieb Paul Jansen: > My mail client might mangle the bottom-posting here, so we'll see how > it goes. > I saw a post from Fabian that he had re-enabled jenkins builds of the > node image based on Fedora 19/20 (but not yet including the VDSM > plugin). Presumably the main goal of this is to ensure that things in > node land are OK for an upcoming spin based on EL7? EL7 is one point, but there were users also asking for Fedora based Nodes and we use Fedora for development, to have stable Nodes (at some point later) based on CentOS. > If ovirt does go back to having Fedora and EL based node images in the > short term it would mean that live migration will work on the Fedora > images. The Fedora based images are at least for now available from Jenkins. > If it was also decided to allow the EL based node image to include the > recompiled qemu-kvm-rhev package the Ovirt release notes could then > say that when using an ovirt node image live migration is supported, > as is when a fedora install has the ovirt hypervisor packages > installed. What is this ovirt hypervisor package you mention? - fabian > It would only be that an EL based system - built up to then also > include the ovirt hypervisor packages - that live migration would not > be supported - at this stage. > This can change when the details are further worked out with the > Centos people about how the updated qemu-kvm packages will be hosted > and made available. > In the meantime, people that want to set things up so that live > migration is there can do so. > > Once live migration is in place I think it would be interesting to try > and find out from people interested (or already testing ovirt) that > have VMware backgrounds/experience what they think is the the largest > outstanding issue feature wise when comparing ovirt to Vcenter. What > would stop them from migrating from vcenter to ovirt?