Bug 2028192
| Summary: | [DOC] Deprecate functionality: oVirt Scheduler Proxy | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Sandro Bonazzola <sbonazzo> |
| Component: | ovirt-scheduler-proxy | Assignee: | Steve Goodman <sgoodman> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Steve Goodman <sgoodman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.4.10 | CC: | ahadas, emarcus, lsurette, michal.skrivanek |
| Target Milestone: | ovirt-4.4.10 | Keywords: | Documentation, NoDocsQEReview, Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Deprecated Functionality | |
| Doc Text: |
The oVirt Scheduler Proxy, `ovirt-scheduler-proxy` is deprecated. Development has been discontinued. It will be removed in a future release.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-25 14:55:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | ovirt-4.5.0 |
| Embargoed: | |||
|
Description
Sandro Bonazzola
2021-12-01 17:00:51 UTC
The documentation doesn't mention ovirt-scheduler-proxy. If you find it discussed, the please reopen this bug with more info. A few questions: 1. Why is the scheduler being removed? 2. How are our users going to be affected by this? What can they do now that they won't be able to do after it is removed? 3. Is there any feature that we should tell users to use as a replacement for 4. This is targeting ovirt 4.5. Should we already add a deprecation notice? (In reply to Steve Goodman from comment #4) > A few questions: > > 1. Why is the scheduler being removed? It didn't receive updates in the past few years and the original maintainers are not contributing to the project anymore. There are no reports of usage of this feature and no interest raised in last few years. > 2. How are our users going to be affected by this? What can they do now that > they won't be able to do after it is removed? > 3. Is there any feature that we should tell users to use as a replacement > for Redirecting above 2 questions to Michal > 4. This is targeting ovirt 4.5. Should we already add a deprecation notice? Yes please peer reviewed - LGTM Merged and published. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |