It’s a lot of work and I see it as a waste of time at this point. We already have a mechanism to either install it or not (install foreman-ovirt or remove it). Building a plugin means setting up the whole gem, publishing it, doing packaging, think about the migration, doing regression testing.
Rather than forking the gem, why not get involved in oVirt development and do it proper?
One of the oVirt developers was so kind to issue release 4.6.0. Currently waiting for upload to rubygems.org… 
I see we have ovirt-engine-sdk 4.6.0 in our repos for a while. Has someone tried this on our Foreman 3.10 EL9 builds or 3.11 RC? I wonder, whther there’s other Ruby 3 related issues.
Hello,
What is the status of ovirt supported by foreman ?
I just read satellite release note that says , I quote:
Provisioning on Red Hat Virtualization
The integration of Red Hat Virtualization (RHV) with Satellite was deprecated in 6.13. All the existing compute resources of RHV type will be removed and the hosts associated with RHV will be disconnected. The RHV provider will be removed in the Satellite 6.18 release.
Satellite 6.18 = foreman 3.14
and I’m not seeing this news in foreman release note.
The RFC for dropping it can be found at RFC: Deprecation and removal of oVirt Compute Resource, not sure how far the plans of ATIX to create a plugin for it are.
thank you for the link
Satellite 6.17 (GA last week) is on 3.14. Sat 6.18 will be on 3.15/3.16