<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;font-size:12pt">I'm going to try top posting this time to see if it ends up looking a bit better on the list.<br><br>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.<br><br><div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Fabian Deutsch <br> <b><span style="font-weight: bold;">To:</span></b> Paul Jansen <br><b><span style="font-weight:
bold;">Cc:</span></b> Doron Fediuck; users<br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, 7 April 2014 5:20 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Users] node spin including qemu-kvm-rhev?<br> </font> </div> <div class="y_msg_container"><br>Am Sonntag, den 06.04.2014, 19:15 -0700 schrieb Paul Jansen:<br clear="none">> My mail client might mangle the bottom-posting here, so we'll see how<br clear="none">> it goes.<br clear="none">> I saw a post from Fabian that he had re-enabled jenkins builds of the<br clear="none">> node image based on Fedora 19/20 (but not yet including the VDSM<br clear="none">> plugin). Presumably the main goal of this is to ensure that things in<br clear="none">> node land are OK for an upcoming spin based on EL7?<br clear="none"><br clear="none">EL7 is one point, but there were users also asking for Fedora based<br clear="none">Nodes and we use Fedora for
development, to have stable Nodes (at some<br clear="none">point later) based on CentOS.<br clear="none"><br clear="none">> If ovirt does go back to having Fedora and EL based node images in the<br clear="none">> short term it would mean that live migration will work on the Fedora<br clear="none">> images.<br clear="none"><br clear="none">The Fedora based images are at least for now available from Jenkins.<br clear="none"><br clear="none">> If it was also decided to allow the EL based node image to include the<br clear="none">> recompiled qemu-kvm-rhev package the Ovirt release notes could then<br clear="none">> say that when using an ovirt node image live migration is supported,<br clear="none">> as is when a fedora install has the ovirt hypervisor packages<br clear="none">> installed.<br clear="none"><br clear="none">What is this ovirt hypervisor package you mention?<br clear="none"><br clear="none">- fabian<div
class="yqt5664411254" id="yqtfd44699"><br clear="none"><br clear="none">> It would only be that an EL based system - built up to then also<br clear="none">> include the ovirt hypervisor packages - that live migration would not<br clear="none">> be supported - at this stage.<br clear="none">> This can change when the details are further worked out with the<br clear="none">> Centos people about how the updated qemu-kvm packages will be hosted<br clear="none">> and made available.<br clear="none">> In the meantime, people that want to set things up so that live<br clear="none">> migration is there can do so.<br clear="none">> <br clear="none">> Once live migration is in place I think it would be interesting to try<br clear="none">> and find out from people interested (or already testing ovirt) that<br clear="none">> have VMware backgrounds/experience what they think is the the largest<br clear="none">> outstanding
issue feature wise when comparing ovirt to Vcenter. What<br clear="none">> would stop them from migrating from vcenter to ovirt?<br clear="none"><br clear="none"><br clear="none"></div><br><br></div> </div> </div> </div></body></html>