On Fri, Dec 17, 2021 at 5:08 AM <cameronsplaze222@gmail.com> wrote:


> One problem I see is that now the update of a host is driven by the engine through playbooks and is not manually doable from the host itself as some time ago. And to have a container going through making modifications to the host where it is running doesn't seem a good idea

For an hosted-engine setup, does the engine VM modify the host it's running on then? And you need the VM abstraction to update the host safely? If so, I'm guessing running the engine directly on the node isn't safe either then.
Also, if the host/node itself gets updates though `dnf upgrade`, would it be possible to let dnf handle upgrades for it? and then rebuild/pull the latest container for engine updates? Or could the updates get out of sync of one another? 

Thanks!
Cameron

I think this thread (even if the title is not so clear about the discussions born inside) could be a good read regarding single host limitations in terms of updating the environment, after the initial deployment:
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/2E6IOFCH5MJSPZ6MNSB5GIW7BGUZNXDS/#PI2LS3NCULH3FXQKBSB4IGXLKUBXE6UL

We were at 4.4.2 time and I think the point now is the same. See in particular the last 9-10 comments, starting from Sandro one at "Sunday, 4 October 11:30 p.m."
They were related to single host and update questions.
Gianluca