--1060583355-253711514-1396873519=:49680 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On 04/07/2014 11:46 AM, Fabian Deutsch wrote:=0A=0A> Hey Paul,=0A>=0A> Am M= ontag, den 07.04.2014, 01:28 -0700 schrieb Paul Jansen:=0A>> I'm going to t= ry top posting this time to see if it ends up looking a=0A>> bit better on = the list.=0A>=0A> you could try sending text-only emails :)=0A>=0A>> By the= 'ovirt hypervisor packages' I meant installing the OS first of=0A>> all an= d then making it into an ovirt 'node' by installing the required=0A>> packa= ges, rather than installing from a clean slate with the ovirt=0A>> node iso= .=A0 Sorry if that was a bit unclear.=0A>=0A> Okay - thanks for the explana= tion.=0A> In general I would discourage from installing the ovirt-node pack= age ona=0A> normal host.=0A> If you still want to try it be aware that the = ovirt-node pkg might mess=0A> with your system.=0A=0AI'm pretty sure we are= on the same page here.=A0 I just checked the ovirt 'quickstart' page and i= t calls the various hypervisor nodes 'hosts'.=0Aie: Fedora host, EL, host, = ovirt node host.=0AIf the ovirt node included the qemu-kvm-rhev package - o= r an updated qemu-kvm - it would mean that both ovirt node hosts and fedora= hosts could both support live storage migration.=A0 It would only be EL ho= sts that do not support that feature at this stage.=A0 We could have a cave= at in the documentation for this perhaps.=0AFabian, were you think thinking= that if not all 'hosts' supported live migration that the cluster could di= sable that feature? Based on capabilities that the hosts would expose to th= e ovirt server?=A0 This would be another way of avoiding the confusion.=0A= =0AThanks guys for the great work you are doing with ovirt.=0A --1060583355-253711514-1396873519=:49680 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"><div style=3D"font-family: HelveticaNeue, Helvetica Neue, Hel= vetica, Arial, Lucida Grande, Sans-Serif; font-size: 12pt;"><div style=3D"f= ont-family: times new roman, new york, times, serif; font-size: 12pt;">On 0= 4/07/2014 11:46 AM, Fabian Deutsch wrote:<div class=3D"y_msg_container"><di= v class=3D"yqt3432433946" id=3D"yqtfd62072"><br clear=3D"none">> Hey Pau= l,<br clear=3D"none">><br clear=3D"none">> Am Montag, den 07.04.2014,= 01:28 -0700 schrieb Paul Jansen:<br clear=3D"none">>> I'm going to t= ry top posting this time to see if it ends up looking a<br clear=3D"none">&= gt;> bit better on the list.<br clear=3D"none">><br clear=3D"none">&g= t; you could try sending text-only emails :)<br clear=3D"none">><br clea= r=3D"none">>> By the 'ovirt hypervisor packages' I meant installing t= he OS first of<br clear=3D"none">>> all and then making it into an ovirt 'node' by ins= talling the required<br clear=3D"none">>> packages, rather than insta= lling from a clean slate with the ovirt<br clear=3D"none">>> node iso= . Sorry if that was a bit unclear.<br clear=3D"none">><br clear=3D= "none">> Okay - thanks for the explanation.<br clear=3D"none">> In ge= neral I would discourage from installing the ovirt-node package ona<br clea= r=3D"none">> normal host.<br clear=3D"none">> If you still want to tr= y it be aware that the ovirt-node pkg might mess<br clear=3D"none">> wit= h your system.</div><br clear=3D"none"><br clear=3D"none">I'm pretty sure w= e are on the same page here. I just checked the ovirt 'quickstart' pa= ge and it calls the various hypervisor nodes 'hosts'.<br>ie: Fedora host, E= L, host, ovirt node host.<br>If the ovirt node included the qemu-kvm-rhev p= ackage - or an updated qemu-kvm - it would mean that both ovirt node hosts = and fedora hosts could both support live storage migration. It would only be EL= hosts that do not support that feature at this stage. We could have = a caveat in the documentation for this perhaps.<br>Fabian, were you think t= hinking that if not all 'hosts' supported live migration that the cluster c= ould disable that feature? Based on capabilities that the hosts would expos= e to the ovirt server? This would be another way of avoiding the conf= usion.<br><br>Thanks guys for the great work you are doing with ovirt.<br><= /div> </div> </div> </div></body></html> --1060583355-253711514-1396873519=:49680--