If you have a monitoring system then you should be able to monitor for the specific condition of one or more of these VMs being down and that monitoring system calling the playbook. We currently use Xymon and it has been trivial to integrate Ansible Tower with Xymon to do exactly this kind of thing.

The playbook I gave you merely informs oVirt (actually RHV in our case) of the VM's required state. If the VM is already running Ovirt won't do anything as the VM is already at desired state.

Hope that helps

On Tue, 16 Jul 2024 at 20:37, Sergei Panchenko <daemonff@gmail.com> wrote:

Dear Colin!

Thank You for your answer.

However, as far as I understand, this is a manual method (the playbook must be run by an administrator or user). And this will not prevent the administrator or user from starting the virtual machines in a different order.

And a more complex question about the procedure for restarting the VM. In my case, it is necessary to preserve the startup order across reboots: if VM2 was forced to restart (for example, due to a host failure), then after starting VM2, it is necessary to restart VM3. Is it possible?
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/FGMMJXMMTEDDCE3DSJJKCHHOLBAS6TUU/