Am Sonntag, den 06.04.2014, 11:57 -0400 schrieb Doron Fediuck: > > ----- 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?
Hey, yeah - that is also my concern. oVirt node has a mechanism (in master) to expose that features are present or not, but I don't know if vdsm has the capability to pass this on to Engine, and if Engine has the logic to detect incompatabilities based on the underlying qemu-kvm-rhev version. Greetings fabian _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
