This is a multi-part message in MIME format. --------------060207080809040703050302 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sven Kieske wrote:
+1 from me, this should work without manual tweaking (except for live snapshots).
Am 09.06.2014 20:32, schrieb Joop:
If you install a minimal Centos-6.5 and add the ovirt repository and then add the host using the webui of engine then it will install all needed packages (vdsm/libvirt/kvm) and you're done. You can then replace the standard qemu with the one that will do live snapshots. Depending on where you're storage is located you shouldn't have to tinker with memberships etc.
Looking at this again I would like the webui install process to add the repo too :-) If engine-setup is up to date it could know the location of the ovirt-repo.rpm and install it automatically. There is probably a very good reason why it doesn't do this since I can't imagine I'm the first one to think about this. Joop --------------060207080809040703050302 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Sven Kieske wrote: <blockquote cite="mid:539AC37B.8050901@mittwald.de" type="cite"> <pre wrap="">+1 from me, this should work without manual tweaking (except for live snapshots). Am 09.06.2014 20:32, schrieb Joop: </pre> <blockquote type="cite"> <pre wrap="">If you install a minimal Centos-6.5 and add the ovirt repository and then add the host using the webui of engine then it will install all needed packages (vdsm/libvirt/kvm) and you're done. You can then replace the standard qemu with the one that will do live snapshots. Depending on where you're storage is located you shouldn't have to tinker with memberships etc. </pre> </blockquote> <pre wrap=""><!----> </pre> </blockquote> Looking at this again I would like the webui install process to add the repo too :-)<br> If engine-setup is up to date it could know the location of the ovirt-repo.rpm and install it automatically. There is probably a very good reason why it doesn't do this since I can't imagine I'm the first one to think about this.<br> <br> Joop<br> <br> </body> </html> --------------060207080809040703050302--