ovirt-scheduler-proxy: subproject health check
Hi, oVirt Scheduler Proxy has been introduced in oVirt 3.3.1 back in 2013. Last update on master branch is dated November 2017 with 0.1.8 released. The package has been shipped till oVirt 4.2.8 and it has not been shipped in oVirt 4.3 despite no official deprecation has been announced. According to Gerrit, current maintainers are Doron Fediuck and Martin Sivak. According to Bugzilla there are no open bugs or RFEs for this project. The project has no documentation available on oVirt website. Can we declare this subproject retired from oVirt project and drop CI automation for it? Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig>
Hi, The project was definitely supposed to be shipped with oVirt 4.3. There was no deprecation and it still works. It is a simple proxy that allows adding external rules to engine scheduler. There are no bugs and so there are no fixes.. does not mean it is dead. There used to be documentation based on examples.. but apparently it got lost. https://web.archive.org/web/20170326001609/https://www.ovirt.org/documentati... This is not widely used feature however there were users and use cases for it. I found a question about it from 2017 for example: https://lists.ovirt.org/pipermail/users/2017-July/083232.html Best regards Martin Sivak On Fri, Mar 8, 2019 at 10:41 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, oVirt Scheduler Proxy has been introduced in oVirt 3.3.1 back in 2013. Last update on master branch is dated November 2017 with 0.1.8 released. The package has been shipped till oVirt 4.2.8 and it has not been shipped in oVirt 4.3 despite no official deprecation has been announced.
According to Gerrit, current maintainers are Doron Fediuck and Martin Sivak.
According to Bugzilla there are no open bugs or RFEs for this project.
The project has no documentation available on oVirt website.
Can we declare this subproject retired from oVirt project and drop CI automation for it?
Thanks,
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA
sbonazzo@redhat.com
Il giorno ven 8 mar 2019 alle ore 11:01 Martin Sivak <msivak@redhat.com> ha scritto:
Hi,
The project was definitely supposed to be shipped with oVirt 4.3.
Opened https://bugzilla.redhat.com/show_bug.cgi?id=1686789 to track this.
There was no deprecation and it still works. It is a simple proxy that allows adding external rules to engine scheduler. There are no bugs and so there are no fixes.. does not mean it is dead.
There used to be documentation based on examples.. but apparently it got lost.
https://web.archive.org/web/20170326001609/https://www.ovirt.org/documentati...
Opened https://github.com/oVirt/ovirt-site/issues/1946 to track this
This is not widely used feature however there were users and use cases for it. I found a question about it from 2017 for example: https://lists.ovirt.org/pipermail/users/2017-July/083232.html
Best regards
Martin Sivak
On Fri, Mar 8, 2019 at 10:41 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, oVirt Scheduler Proxy has been introduced in oVirt 3.3.1 back in 2013. Last update on master branch is dated November 2017 with 0.1.8 released. The package has been shipped till oVirt 4.2.8 and it has not been
shipped in oVirt 4.3 despite no official deprecation has been announced.
According to Gerrit, current maintainers are Doron Fediuck and Martin
Sivak.
According to Bugzilla there are no open bugs or RFEs for this project.
The project has no documentation available on oVirt website.
Can we declare this subproject retired from oVirt project and drop CI
automation for it?
Thanks,
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA
sbonazzo@redhat.com
-- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig>
participants (2)
-
Martin Sivak -
Sandro Bonazzola