--708812334-390794442-1396859291=:39119 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I'm going to try top posting this time to see if it ends up looking a bit b= etter on the list.=0A=0ABy the 'ovirt hypervisor packages' I meant installi= ng the OS first of all and then making it into an ovirt 'node' by installin= g the required packages, rather than installing from a clean slate with the= ovirt node iso.=A0 Sorry if that was a bit unclear.=0A=0A=0A=0A___________= _____________________=0A From: Fabian Deutsch =0ATo: Paul Jansen =0ACc: Dor= on Fediuck; users=0ASent: Monday, 7 April 2014 5:20 PM=0ASubject: Re: [User= s] node spin including qemu-kvm-rhev?=0A =0A=0AAm Sonntag, den 06.04.2014, = 19:15 -0700 schrieb Paul Jansen:=0A> My mail client might mangle the bottom= -posting here, so we'll see how=0A> it goes.=0A> I saw a post from Fabian t= hat he had re-enabled jenkins builds of the=0A> node image based on Fedora = 19/20 (but not yet including the VDSM=0A> plugin).=A0 Presumably the main g= oal of this is to ensure that things in=0A> node land are OK for an upcomin= g spin based on EL7?=0A=0AEL7 is one point, but there were users also askin= g for Fedora based=0ANodes and we use Fedora for development, to have stabl= e Nodes (at some=0Apoint later) based on CentOS.=0A=0A> If ovirt does go ba= ck to having Fedora and EL based node images in the=0A> short term it would= mean that live migration will work on the Fedora=0A> images.=0A=0AThe Fedo= ra based images are at least for now available from Jenkins.=0A=0A> If it w= as also decided to allow the EL based node image to include the=0A> recompi= led qemu-kvm-rhev package the Ovirt release notes could then=0A> say that w= hen using an ovirt node image live migration is supported,=0A> as is when a= fedora install has the ovirt hypervisor packages=0A> installed.=0A=0AWhat = is this ovirt hypervisor package you mention?=0A=0A- fabian=0A=0A=0A> It wo= uld only be that an EL based system - built up to then also=0A> include the= ovirt hypervisor packages - that live migration would not=0A> be supported= - at this stage.=0A> This can change when the details are further worked o= ut with the=0A> Centos people about how the updated qemu-kvm packages will = be hosted=0A> and made available.=0A> In the meantime, people that want to = set things up so that live=0A> migration is there can do so.=0A> =0A> Once = live migration is in place I think it would be interesting to try=0A> and f= ind out from people interested (or already testing ovirt) that=0A> have VMw= are backgrounds/experience what they think is the the largest=0A> outstandi= ng issue feature wise when comparing ovirt to Vcenter.=A0 What=0A> would st= op them from migrating from vcenter to ovirt? --708812334-390794442-1396859291=:39119 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"color:#000; background-color:#fff; font-family:He= lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;fo= nt-size:12pt">I'm going to try top posting this time to see if it ends up l= ooking 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 'no= de' by installing the required packages, rather than installing from a clea= n slate with the ovirt node iso. Sorry if that was a bit unclear.<br>= <br><div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Ar= ial, Lucida Grande, Sans-Serif; font-size: 12pt;"> <div style=3D"font-famil= y: times new roman, new york, times, serif; font-size: 12pt;"> <div dir=3D"= ltr"> <hr size=3D"1"> <font face=3D"Arial" size=3D"2"> <b><span style=3D"f= ont-weight:bold;">From:</span></b> Fabian Deutsch <br> <b><span style=3D"fo= nt-weight: bold;">To:</span></b> Paul Jansen <br><b><span style=3D"font-wei= ght: bold;">Cc:</span></b> Doron Fediuck; users<br> <b><span style=3D"font-weig= ht: bold;">Sent:</span></b> Monday, 7 April 2014 5:20 PM<br> <b><span style= =3D"font-weight: bold;">Subject:</span></b> Re: [Users] node spin including= qemu-kvm-rhev?<br> </font> </div> <div class=3D"y_msg_container"><br>Am So= nntag, den 06.04.2014, 19:15 -0700 schrieb Paul Jansen:<br clear=3D"none">&= gt; My mail client might mangle the bottom-posting here, so we'll see how<b= r clear=3D"none">> it goes.<br clear=3D"none">> I saw a post from Fab= ian that he had re-enabled jenkins builds of the<br clear=3D"none">> nod= e image based on Fedora 19/20 (but not yet including the VDSM<br clear=3D"n= one">> plugin). Presumably the main goal of this is to ensure that= things in<br clear=3D"none">> node land are OK for an upcoming spin bas= ed on EL7?<br clear=3D"none"><br clear=3D"none">EL7 is one point, but there= were users also asking for Fedora based<br clear=3D"none">Nodes and we use= Fedora for development, to have stable Nodes (at some<br clear=3D"none">point later) = based on CentOS.<br clear=3D"none"><br clear=3D"none">> If ovirt does go= back to having Fedora and EL based node images in the<br clear=3D"none">&g= t; short term it would mean that live migration will work on the Fedora<br = clear=3D"none">> images.<br clear=3D"none"><br clear=3D"none">The Fedora= based images are at least for now available from Jenkins.<br clear=3D"none= "><br clear=3D"none">> If it was also decided to allow the EL based node= image to include the<br clear=3D"none">> recompiled qemu-kvm-rhev packa= ge the Ovirt release notes could then<br clear=3D"none">> say that when = using an ovirt node image live migration is supported,<br clear=3D"none">&g= t; as is when a fedora install has the ovirt hypervisor packages<br clear= =3D"none">> installed.<br clear=3D"none"><br clear=3D"none">What is this= ovirt hypervisor package you mention?<br clear=3D"none"><br clear=3D"none"=
- fabian<div class=3D"yqt5664411254" id=3D"yqtfd44699"><br clear=3D"none"><br clear=3D"= none">> It would only be that an EL based system - built up to then also= <br clear=3D"none">> include the ovirt hypervisor packages - that live m= igration would not<br clear=3D"none">> be supported - at this stage.<br = clear=3D"none">> This can change when the details are further worked out= with the<br clear=3D"none">> Centos people about how the updated qemu-k= vm packages will be hosted<br clear=3D"none">> and made available.<br cl= ear=3D"none">> In the meantime, people that want to set things up so tha= t live<br clear=3D"none">> migration is there can do so.<br clear=3D"non= e">> <br clear=3D"none">> Once live migration is in place I think it = would be interesting to try<br clear=3D"none">> and find out from people= interested (or already testing ovirt) that<br clear=3D"none">> have VMw= are backgrounds/experience what they think is the the largest<br clear=3D"n= one">> outstanding issue feature wise when comparing ovirt to Vcenter. What<br clear=3D= "none">> would stop them from migrating from vcenter to ovirt?<br clear= =3D"none"><br clear=3D"none"><br clear=3D"none"></div><br><br></div> </div>= </div> </div></body></html> --708812334-390794442-1396859291=:39119--