With this comment, I'm poking at getting the engine to run directly on the node. I figure worst case, I might try throwing it in a container if there's package conflicts. That'll at least give me the lighter-engine I'm looking for, along with not having to manage it's resources.
Looks like the powertools repo isn't enabled by default on the node, so following this guide let me enable all the different modules for the engine: https://computingforgeeks.com/enable-powertools-repository-on-centos-rhel-linux/ The engine-setup command is apart of "rpm install ovirt-engine-setup-base", which CentOS 8 can find, but not the node. It's inside the ovirt-4.4 repo too, so I have no idea why the node can't find it. To get the engine setup running on CentOS, I also needed to install ovirt-engine-setup-plugin-ovirt-engine-common (this bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1114978), and the node couldn't find this package either. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/E5Z5RXJHWWESTOYSH546IN7CMO6LUAS3/
