This seems like it might be a good addition to a future version of oVirt. Add
a dependency option to a VM's configuration. And then maybe also a "Allowed to
automatically start dependency" checkbox.
___
Users mailing list -- users@ovirt.org
To unsubsc
Dear Colin!
Thank You for the clear explanation.
___
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/co
I should have also said that not just admins can use the playbook. The
credentials to oVirt should be stored ansible-vault so that they are not
visible. Its a bit of a step up and more than a bit of a learning curve but
if you use Ansible Tower (or AWX) you can trivially allow an end user to
run th
Hi
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 t
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
You could ensure the VMs don't automatically start and use an Ansible
playbook to start the VMs in the order you like.
Something like:
---
- name: Playbook to start the VMs in the required order
hosts: localhost
tasks:
- name: Authenticate with RHV
ovirt.ovirt.ovirt_auth:
url: "{{
6 matches
Mail list logo
