Il giorno lun 21 nov 2022 alle ore 20:05 Alex McWhirter <alex@triadic.us> ha scritto:

I have some manpower im willing to throw at oVirt, but i somewhat need to know if what the community wants and what we want are in line.

1. We'd bring back spice and maybe qxl. We are already maintaining forks of the ovirt and RH kernels for this. We use ovirt currently for a lot of VDI solutions paired with nvidia grid. Not usable over VNC.

2. Hyperconverged storage is important. I'd suggest integrations with linstor. Seems well aligned with ovirt. Bringing back gluster is likely the wrong move.

3. oVirt desperately needs vxlan support. Ideally integrating with FRR on the backend so an ovirt node can just plug into an exiting EVPN VXLAN setup.

4. some things need cut from ovirt, namely hosted engine and maybe the grafana stuff. Not that these aren't nice to have, but hosted engine rarely actually works reliable in it's current state (compare mailing list complaints of hosted engine vs other issues) and the grafana stuff can be pushed into a sub project.

5. It needs to do containers. Doesn't need to be the behemoth of OKD, but something more along the lines of what k3s does, for now.


These are the thing's i'd like to see done, and maybe also cut back some of the RHEL specific stuff to allow debian deployments (would massively help with userbase). Basically for the past year i've been tasked with figuring out if we are going to fork ovirt internally or move to OpenNebula. I prefer the ovirt option if the opportunity now exists to take things in another direction.


I would suggest to open one thread per feature and discuss each one of them with the community so you'll have a better clue on the general interest on each of them.

 



On 2022-11-15 03:31, Sandro Bonazzola wrote:

 

Il giorno lun 14 nov 2022 alle ore 23:40 Frank Wall <fw@moov.de> ha scritto:
Hi Didi,

thanks for keeping us updated. However, I'm concerned...

> Ultimately, the future of oVirt lies in the hands of the community. If
> you, as a community member, use and like oVirt, and want to see it
> thrive, now is the best time to help with this!

I don't want to be rude, but this sounds to me like no developers
have shown interest in keeping oVirt alive. Is this true? Is no other
company actively developing oVirt anymore?
 
I've contacted directly all the companies with oVirt downstreams I was aware of.
I also contacted almost all the universities that asked for help in this mailing list.
I ended up contacting the major RHEL derivatives distributions.
So far nobody stepped in to take an active role on the oVirt project.
I saw some patches coming from individual contributors here and there but no company investment so far.
 
 

> We worked hard over the last year or so on making sure the oVirt
> project will be able to sustain development even without much
> involvement from us - including moving most of the infrastructure from
> private systems that were funded by/for oVirt/RHV, elsewhere - code
> review from Gerrit to GitHub, and CI (Continuous Integration) from
> jenkins to GitHub/Copr/CentOS CBS.

I appreciate the effort to make the source code accessible. However,
I'm also wondering: was any sort of governing organization established,
so that development could actually take place when RedHat pulls the
plug?
 
Yes, oVirt has an open governance: https://www.ovirt.org/community/about/governance.html
Right now in the oVirt board other than Red Hat there's a member of the Caltech university https://www.ovirt.org/community/about/board.html
 

The answer to this is probably related to my previous question, whether
or not there are any non-RedHat developers involved.


Ciao
- Frank
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
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/users@ovirt.org/message/5DQ3OLT3B5QALLFUK4OMKDYJEJXSYP7A/

 
--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle OS

Red Hat EMEA

 

sbonazzo@redhat.com   

 
 
Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.



_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
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/users@ovirt.org/message/IVCGZXVNOAFE44ASIH6UFZGURL3OUFRW/




--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle OS

Red Hat EMEA

sbonazzo@redhat.com   

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.