Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #SAT-31687 - Deprecate oVirt #3724

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

stejskalleos
Copy link
Contributor

What changes are you introducing?

oVirt integration is going to be deprecated in 3.15 and removed in 3.16

Why are you introducing these changes?

https://community.theforeman.org/t/rfc-deprecation-and-removal-of-ovirt-compute-resource/42527
https://projects.theforeman.org/issues/38266
https://issues.redhat.com/browse/SAT-12005

Anything else to add?

@maximiliankolb Atix folks probably take over the ownership and extract the code to the plugin, so there should be a doc variant for your docs.

@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Mar 11, 2025
Copy link
Contributor

@maximiliankolb maximiliankolb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. I will keep you updated if there's any news from ATIX about oVirt+Foreman/Katello.

Comment on lines 18 to 20
=== Compute resources - oVirt
* The oVirt compute resource has been deprecated and will be removed in a future release.
* Migrate your data with the "foreman-rake ovirt:drop" task.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
=== Compute resources - oVirt
* The oVirt compute resource has been deprecated and will be removed in a future release.
* Migrate your data with the "foreman-rake ovirt:drop" task.
=== The {oVirt} compute resource
The {oVirt} compute resource has been deprecated and will be removed in a future release.
Migrate your data with the `foreman-rake ovirt:drop` comand.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit more information about what the rake command does and what happens during the migration would be useful. Alternatively, you could just link to docs that explain it but I don't think we have them (yet).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... or just what @maximiliankolb said :) Looks like he was faster with his review.

@stejskalleos
Copy link
Contributor Author

Updated formatting. About the rake task description, I'll describe it in the release notes as well, once the theforeman/foreman#10469 get merged.

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't use Fixes #SAT-something. That is really only used for Redmine.

There are no deprecations with Foreman {ProjectVersion}.
=== Compute resources - {oVirt}

* The {oVirt} compute resource has been deprecated and will be removed in a future release.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A concrete timeline is always appreciated, if available.

@@ -15,4 +15,7 @@ There are no upgrade warnings with Foreman {ProjectVersion}.
[id="foreman-deprecations"]
== Deprecations

There are no deprecations with Foreman {ProjectVersion}.
=== Compute resources - {oVirt}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -15,4 +15,7 @@ There are no upgrade warnings with Foreman {ProjectVersion}.
[id="foreman-deprecations"]
== Deprecations

There are no deprecations with Foreman {ProjectVersion}.
=== Compute resources - {oVirt}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
=== Compute resources - {oVirt}
// There are no deprecations with Foreman {ProjectVersion}.
=== Compute resources - {oVirt}

suggestion: Please keep this handly little sentence on "master". Not blocking your PR because we could also revert any commits after branching on master again. However, it might be easier to just drop any release notes after branching 3.15.

@ekohl
Copy link
Member

ekohl commented Mar 20, 2025

@maximiliankolb Atix folks probably take over the ownership and extract the code to the plugin, so there should be a doc variant for your docs.

If there is a new plugin and that's used in upstream, then IMHO it shouldn't be deprecated. Instead we should point out (at least in upstream) that it's going be migrated.

Until that's decided I don't think we should merge this. In other words, only once consensus is reached in https://community.theforeman.org/t/rfc-deprecation-and-removal-of-ovirt-compute-resource/42527 should we proceed with steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants