RFC: Deprecation and removal of oVirt Compute Resource

Development RFCs
1

Hi everyone,
I would like to share our plan regarding the deprecation and eventual removal of oVirt integration in Foreman.

Summary:

  • In version 3.15, we will deprecate the integration and introduce a rake task for data migration.
  • In version 3.16, we will remove the code from Foreman core, as well as the installer and packaging.

Details:

  • The oVirt integration has been deprecated in Satellite for some time now.
  • The rake task for data migration will be cherry-picked for the older versions so the community can prepare in advance.
  • There are no plans to migrate the code to the plugin.

Links:

Thank you for your attention to this matter.

1 Like
2

I think this is a follow-up on Proposal to drop support for oVirt where @hlawatschek and @Bernhard_Suttner thought about taking over the maintenance.

3

If people want to maintain the integration, that would be awesome. The code can be extracted from the core and moved to the plugin.

But even with someone volunteering for the plugin extraction, we won’t block the removal from the core because of it.

4

Do you plan to move this to a separate plugin @lstejska ?

5

No, just code removal + rake task & migration for compute resource data.

6

Well, I guess, then we will create a plugin out of it as we still need it.
Another possibility is, to have a different approach than a separte Plugin.
We will discuss internally how to proceed.

1 Like
7

On a technical level please know that ovirt-engine-sdk already fails to build on Fedora 41 (and IIRC also EL10). Update to Ruby 3 by jhernand · Pull Request #10 · oVirt/ovirt-engine-sdk-ruby · GitHub and Extracted: Update gemspec dependencies for ruby 3 by kbrock · Pull Request #19 · oVirt/ovirt-engine-sdk-ruby · GitHub tell me that it’s hard to get changes in. You’d probably also volunteer to pick up the SDK itself.

1 Like