On Mon, May 11, 2020 at 8:32 AM Nir Soffer <[email protected]> wrote: > > On Mon, May 11, 2020 at 2:24 PM Neal Gompa <[email protected]> wrote: > > > > As far as the oVirt software keeping up with Fedora, the main problem here > > has always been that people aren't integrating their software into the > > distribution itself. That's how everything can get tested together. And > > this comes back to the old bug about fixing vdsm so that it doesn't use > > /rhev, but instead something FHS-compliant (RHBZ#1369102). Once that is > > resolved, pretty much the entire stack can go into Fedora. And then you > > benefit from the Fedora community being able to use, test, and contribute > > to the oVirt project. As it stands, why would anyone do this for you when > > you don't even run on the cutting edge platform that feeds into Red Hat > > Enterprise Linux? > > This was actually fixed a long time ago. With this commit: > https://github.com/oVirt/vdsm/commit/67ba9c4bc860840d6e103fe604b16f494f60a09d > > You can configure a compatible vdsm that does not use /rhev. > > Of course it is not backward compatible, for this we need much more > work to support live migration > between old and new vdsm using different data-center configurations. >
It'd probably be simpler to just *change* it to an FHS-compatible path going forward with EL8 and Fedora and set up a migration path there, but it's a bit late for that... :( -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/SBAZ2F3FCOVGHRL7UNYTBLRX63BSBTCC/
