From my limited experience, the usual flow for most users is deploying/upgrading a host and installing vdsm from the engine UI on the hypervisor machine.

In case of manual installations by non-users, it is accustomed to run "vdsm-tool configure --force" after step 3 and then reboot.

Having a host on which vdsm is not running by default renders it useless for ovirt, unless it is explicitly set to be down from UI under particular circumstances.

On Tue, Jan 28, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com> wrote:

If I do e.g.:

1. Install CentOS
2. yum install ovirt-releaseSOMETHING
3. yum install vdsm

Then reboot the machine, vdsm starts, and for this, it does all kinds of things to the system (such as configure various services using vdsm-tool etc.). Are we sure we want/need this? Why would we want vdsm configured/running at all at this stage, before being added to an engine?

In particular, if (especially during development) we have a bug in this configuration process, and then fix it, it might not be enough to upgrade vdsm - the tooling will then also have to fix the changes done by the buggy previous version, or require a full machine reinstall.

Thanks and best regards,
--
Didi
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/3YHWLO3DFU2PLPGL44DBIBG25QYGOQL7/