On 2022-11-21 19:56, Alex McWhirter wrote:
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.
That's actually great news! I appreciate that you are reaching out to the community to get early feedback.
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.
Oh, I'm puzzled, my experience is the opposite: hosted engine works great for me – and it has been this way for many years. (But I'm not using all of its features.) What would you suggest as replacement?
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.
Agreed. However, I hope that it will not impose the insane overhead like k8s.
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.
Supporting different Linux distributions is a great idea. But I'd expect this to be a huge untertaking. Adding support for flavors like Rocky Linux would probably be a good first step. If you don't plan to fork oVirt, then I'd recommend to coordinate your efforts with the oVirt board members. AFAICT the current team of developers will continue to provide minor releases until RHEV is dead, so I guess new features or feature removals need to be done in a new major release (without help from RedHat). Ciao - Frank