[ovirt-users]Re: About oVirt’s future

Hi Alex, > On 21. 11. 2022, at 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. > I don't think anyone would oppose adding a new features. Removing is challenging, but w

[ovirt-users]Re: About oVirt’s future

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. som

[ovirt-users]Re: About oVirt’s future

Il giorno lun 21 nov 2022 alle ore 20:05 Alex McWhirter 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 ov

[ovirt-users]Re: About oVirt’s future

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 soluti

[ovirt-users]Re: About oVirt’s future

Hi, Sandro, What are plans for oVirt development and/or migrations for large users, for example Brussel Airport ? > On 15 Nov 2022, at 10:31, Sandro Bonazzola wrote: > > > > Il giorno lun 14 nov 2022 alle ore 23:40 Frank Wall > ha scritto: > Hi Didi, > > thanks for

[ovirt-users] Re: About oVirt’s future

Hello all, For anyone's wondering about oVirt's chances of ongoing development, this: https://github.com/oVirt/ovirt-engine/pulse/monthly is the current monthly stats (issues closed, commits made, number of contributors, etc.) on just the engine's GitHub repo, within the oVirt organization. (I.e.

[ovirt-users]Re: About oVirt’s future

Il giorno lun 14 nov 2022 alle ore 23:40 Frank Wall 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, n

[ovirt-users]Re: About oVirt’s future

Sad news. On 11/15/2022 9:44 AM, Nathanaël Blanchet via Users wrote: Hello all, This is definitely a really sad new, but it is a natural consequence of rhv die and I don't know why redhat should continue to invest in ovirt. I believed that more professional developpers were involved in RHV pro

[ovirt-users]Re: About oVirt’s future

Hello all, This is definitely a really sad new, but it is a natural consequence of rhv die and I don't know why redhat should continue to invest in ovirt. I believed that more professional developpers were involved in RHV project, beginning by big companies as oracle who provides downstream OLVM.

[ovirt-users]Re: About oVirt’s future

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

[ovirt-users]Re: About oVirt’s future

On Mon, Nov 14, 2022 at 6:29 PM Strahil Nikolov wrote: > > Hey Didi, > > thanks for the recap. > I hope that soon I will have some free time and I can more actively involve > in the next months. Thanks! > > I would like to get some hints about the Ansible code. How do we test it ? Do you refe

[ovirt-users]Re: About oVirt’s future

Hey Didi, thanks for the recap.I hope that soon I will have some free time and I can more actively involve in the next months. I would like to get some hints about  the Ansible code. How do we test it ? Best Regards,Strahil Nikolov  On Mon, Nov 14, 2022 at 9:14, Yedidyah Bar David wrote: