On Fri, Dec 10, 2021 at 10:30 PM <cameronsplaze222@gmail.com> wrote:
Hi,
... You might want to check the list archives for previous discussions about this ...
Thanks for those links! I have an idea for a path forward, but I'm not sure it's supported. It looks like oVirt used to have a "all-in-one" option,
Indeed, until 3.6.
but the hosted engine replaced that.
hosted-engine was introduced at 3.3/3.4, so not an exact replacement, but yes.
I'd like to clarify that a hosted-engine deployment isn't always the best approach for a single machine setup.
The other path I can see is installing the vanilla "engine-setup" to an oVirt node directly.
This is exactly what all-in-one used to do, back then. At the time, this didn't work "out-of-the-box", so the all-in-one support (engine-setup plugin) was needed. Since it was removed, we got a few reports here and there about people doing this, and it mostly seems to work - but it seems no-one cares enough to document the issues if any, and especially to update this document per release. So YMMV.
That way the engine isn't inside a VM
Indeed
(I just hate how much cpu/ram you have to dedicate to the VM, and it's not even dynamic).
How much? if it's just for development/testing, you can try as little as 2GB. If it breaks, just try a bit more. In ovirt-system-tests we use 3171MB (~ 3GB) and it works.
Is it in a VM for security?
Main feature you get from having the engine in its own VM is that you can live-migrate this VM to another host, if/when you need to take down a host for maintenance.
I'll never need to move it for my use case, so I can live without the adaptability VM's come with.
Perhaps clarify your needs? Are you sure oVirt is the right solution? You can also use plain virsh/virt-manager.
If installing the engine directly to the node IS supported, this was where I was hitting my problem: ```bash yum upgrade -y yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm yum upgrade -y yum install ovirt-engine # HERE, can't find it. I can still install ovirt-engine-appliance for the hosted-engine setup.
ovirt-node, generally speaking, is an OST _image_. It's designed to allow upgrading to a later version by installing an update image and rebooting, also allowing rolling back to the previous version (image). If you want to try running the engine on a host, perhaps try plain el8, not node. If you want to try on node, please note that node disables/excludes all repos/packages by default, other than node update images. So you'll need to enable relevant repos.
``` I was also hitting a problem at this step, with the machine not knowing the modules exist: https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager... (i.e `dnf module enable javapackages-tools` returns `missing groups or modules: javapackages-tools`)
If installing the engine directly to a node ISN'T supported, what other routes for a single host setup are there? The only replacement for the all-in-one I can find, is the hosted-engine route.
Depends on needs. For studying/testing/development (other than specifically hosted-engine- related stuff), I think it might be best to create separate VMs on your host for separate uses - one for the engine, perhaps another for storage, one or more for hosts (so that you can test live-migration/ha), etc.
I suppose most people do supply a name here, and the few that don't, just retry without reporting a bug
I saw a lot of people using input files anyways to automate the install, so I think I'll go that route too, if hosted-engine still ends up taking the least resources of the possible options.
+1 for automation. Re "lease resources" - perhaps first explain your needs. Best regards, -- Didi