On Mon, Feb 7, 2022 at 3:04 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
Il giorno lun 7 feb 2022 alle ore 09:28 Thomas Hoberg <thomas(a)hoberg.net>
ha scritto:
> Sandro, I am ever so glad you're fighting on, buon coraggio!
>
Thanks :-)
>
> Yes, please write a blog post on how oVirt could develop without a
> commercial downstream product that pays your salaries.
>
I have no magic recipe but I know oVirt is used in several universities
with computer science departments. If just 1 student for each of them would
contribute 1 patch per semester that would help keeping oVirt alive even
without any downstream company backing it.
And there are also people in this list like @Jean-Louis Dupond
<jean-louis(a)dupond.be> who are contributing fixes, latest is here
https://github.com/oVirt/ovirt-engine/pull/59 .
I don't want to write a book on how an opensource project can be healthy,
I believe there are already out there :-) .
It would indeed help if some company or foundation would show up and get
engaged with the project but this is not strictly needed for an open source
project to be alive.
> Ideally you'd add a perspective for current HCI users, many of which
> chose this approach, because a fault-tolerant SAN or NAS wasn't available.
>
I'll let the storage team to answer here
The oVirt storage team never worked on HCI and we don't plan to work on
it in the future. HCI was designed and maintained by Gluster folks. Our
contribution for HCI was adding 4k support, enabling usage of VDO.
Improving on the HCI side is unlikely to come from Red Hat, but nothing
blocks other companies or contributors from working on this.
Our focus for 4.5 is Managed Block Storage and incremental backup.
Nir