I'm using Ansible do deploy some stuff from templates. I think that terraform is also used with oVirt, so you can give it a try. Best Regards, Strahil Nikolov

Hi Gervais, Have you checked examples for the ovirt_vm module? https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_... Or if you need something more "high level" there is also vm_infra role: https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/vm_infra Both are provided by oVirt Ansible Collection, which is a preferred and supported solution for automated management of oVirt installations. Regards, Martin On Tue, Jan 5, 2021 at 4:06 PM Gervais de Montbrun <gervais(a)demontbrun.com&gt; wrote: -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

On Tue, Jan 5, 2021 at 7:56 PM Strahil Nikolov via Users <users(a)ovirt.org&gt; wrote: We also have oVirt Terraform provider https://github.com/oVirt/terraform-provider-ovirt It doesn't yet have the coverage of oVirt Ansible Collection, so any contribution is welcome. -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

Hello Gervais, I have asked our developers who use the plugin and here is the response. Regards, Paul S. Hi Paul, We have had to maintain our own changes to the oVirt Vagrant plugin. Probably we need to start committing to and publishing our own fork. Theres an obtuse and broken long one liner that get's the IP addresses, which has always been a bit problematic, and stopped working altogether with the newest release of oVirt we are using. Anyway, here are the changes we made to get the IP addresses working with the new versions of oVirt: line 58 wait_till_up.rb ip_addr = nil vm_nics_service = server.nics_service nics = vm_nics_service.list nics.each { |nic| puts "Waiting on #{nic.mac.address}" vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { |device| device.ips&.each {|ip| puts "ip: #{ip.to_s}" if ip && ip.version == 'v4' && ip.address ip_addr = ip.address break end } } } Also same in read_ssh.rb: ip_addr = nil vm_nics_service = server.nics_service nics = vm_nics_service.list nics.each { |nic| vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { |device| device.ips&.each {|ip| if ip && ip.version == 'v4' && ip.address ip_addr = ip.address break end } } } Sorry it's not the best way to share code, but feel free to pass this along. Cheers, Cliffe. . ________________________________ From: Gervais de Montbrun <gervais(a)demontbrun.com&gt; Sent: 04 January 2021 18:14 To: users(a)ovirt.org <users(a)ovirt.org&gt; Subject: [ovirt-users] Ovirt and Vagrant Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Anyone using vagrant with oVirt 4.4? I am trying to get the vagrant plugin working with oVirt, but I am experiencing issues. https://github.com/myoung34/vagrant-ovirt4/issues/120<https://eur02.sa... I wonder what other folks are using or if someone has any suggestions to offer. We are trying to switch from vSphere to oVirt for internal, developer vm's at my office and we have a successful workflow using vagrant-vsphere plugin. Switching to oVirt should have been a simple step, but the issue I an having is a blocker. I built a single hyperconverged server to test with. Everything seems to work fine when I bring up vm's manually in my "cluster." Networking, console, etc all work fine. Ovirt-guest-additions work fine and display the vm's ip in the gui. When I try with the vagrant plugin, there seems to be a communication issue. Even though I can see the vm reporting its IP address fine in the ovirt web gui, it seems like the vagrant plugin is unable to do the same. The maintainer of the code says that he no longer runs oVirt which is why I am reaching out here to see if anyone has a suggestion or even an alternative to suggest. Cheers, Gervais To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/