Re: [ovirt-users] Node hypervisor

Hello Harald, welcome to the ovirt mailing list! On 14.11.2014 14:35, Harald Wolf wrote: Where exactly is the issue there? Please point to the exact doc you are refeffing to. There are several versions and flavors of ovirt (3.4 branch plus minor version, 3.5 branch , nightlies; AllInOne, Hosted Engine, 'Normal' Engine). For future posts, it is quite helpful if you supply this. Also, be aware of some general oVirt terminology: - The (oVirt) Engine is the controller and data collector for your guests, - A 'Host' is generally a physical machine used to run guests on, - Hosts are grouped together in clusters of similar hardware providing migration and other capabilities, - A Datacenter is a logical entity of clusters (hosts) and storage connections, networks, disks, ect. shared between them; - VDSM is the daemon running on the hosts to make this all happen; imagine it as a super process for qemu processes. The above said, you basically need a psychical or virtual machine for the Engine and some additional hosts to run your guests (not true for AllInOne; witch should IMHO only used for demo/lab purposes. Imagine oVirt Node as something similar to EXi hypervisor; it is an imae containing all the stuff you need to add a machine as host to ovirt. The same can be achived by installing ovirt from the repos on a (preferring minimal) CentOS, RHEL, Fedora install. There is no problem with that and Windows is very well supported as guest OS. For all of those, have a look on the excellent ovirt admin Guide [1]. This is still for oVirt 3.4 - but most of the stuff is true for 3.5 as well. Have fun with oVirt! [1] -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767