towo
commented
2 years ago VirtualDomains don't need any special support, they're realized via resource agents, just as any other resource. As long as the distribution you're using is shipping the ocf:heartbeat:VirtualDomain resource agent, you can just use said agent.
The roadmap being outdated is still an artifact of this module being put into Vox Pupuli hands, we're mostly just helping people to integrate patches and do some basic maintenance. On that topic, this might change a bit, since I'm feeling a bit of ownership of this module ATM, so there may be cleanups incoming next year.
If you have further questions, just hit the comments again with a reopen; I'll consider your initial question answered with this and thus close it.
Does this module support VirtualDomains/libvirt?
Managing VMs instead of services is our use-case for Corosync/Pacemaker. I feel like this is a pretty fundamental use of Corosync/Pacemaker.
The roadmap hasn't been updated in years: https://github.com/voxpupuli/puppet-corosync/blob/master/ROADMAP.md
So it's hard to tell where this project is headed. Is there any insight that can be given?
Some resources about VirtualDomains: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_high_availability_clusters/assembly_configuring-virtual-domain-as-a-resource-configuring-and-managing-high-availability-clusters
Cheers