----- Original Message ----- > From: "Paul Jansen" <[email protected]> > To: "users" <[email protected]> > Sent: Wednesday, April 2, 2014 11:38:29 AM > Subject: [Users] node spin including qemu-kvm-rhev? > > I understand that there are ongoing discussions with the Centos people > regarding a suitable home for recompiled qemu-kvm packages. > Given that the ovirt node is our own spin, is there any reason why that > couldn't include the recompiled qemu-kvm packages that will then allow us to > use live snapshots and do live migrations? Itamar recently mentioned that we > already build these via a jenkins task. > > Nodes built on top of a Centos install will still be an issue but I think its > reasonable that the ovirt-node iso could include these custom packages. > This way we don't have to potentially wait until 3.4.1 or 3.5 to get the live > snapshot/migration features. The caveat would be that these features would > only be supported if the nodes were all ovirt node iso based. > > What are people's thoughts? > > Sounds reasonable as long as you understand mix and match will become an issue. The questions is how do we differentiate between the nodes to make sure no one mixes them by mistake? 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? 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. 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. 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?
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
