Il giorno mar 27 apr 2021 alle ore 10:13 Sandro Bonazzola < sbonazzo(a)redhat.com&gt; ha scritto: For reference, Autumn survey results: https://docs.google.com/forms/d/e/1FAIpQLSdzzh_MSsSq-LSQLauJzuaHC0Va1baXm... -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

On Tue, Apr 27, 2021 at 9:55 PM Jiří Sléžka <jiri.slezka(a)slu.cz&gt; wrote: +1 from me, but I'd like to add: Bugs and features are tracked in bugzilla. If you want a new feature, please open a bug, with subject starting with '[RFE]' (and bugzilla should automatically also add to it the keyword FutureFeature). If you are interested in an existing open bug/RFE, please comment on it saying so, preferably with concrete reasons as applicable. I also have vague memories about being about to press a "vote" button for bugs, but can't find it right now. Thanks and best regards, -- Didi

Hi Sandro First of all thank you leading this project.. can you share us what is the road map of this project for next 5 years?

Il giorno gio 29 apr 2021 alle ore 08:08 dhanaraj.ramesh--- via Users < users(a)ovirt.org&gt; ha scritto: oVirt project tracks plans in bugzilla, you can see what's being planned here: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt and contribute shaping what's coming next. Il giorno gio 29 apr 2021 alle ore 08:10 dhanaraj.ramesh--- via Users < users(a)ovirt.org&gt; ha scritto: I'm not aware of any effort planned for it -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

Il giorno gio 29 apr 2021 alle ore 09:37 marek <cervajs64(a)gmail.com&gt; ha scritto: make sense, adding. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

Hi Sandro, The question is - will ovirt plan to provide database migration scripts from deprecated OpenStack provider to cinderlib? I mean put in survey actual users and quantity of images in domain Thanks, k Sent from my iPhone

Thanks Sandro, wait for Eyal k Sent from my iPhone

Il giorno mar 4 mag 2021 alle ore 00:35 Thomas Hoberg <thomas(a)hoberg.netha scritto: more than a question to the users community this sounds like feedback on current pain points :-) - single node HCI could easily promote to 3-node HCI? +Rejy Cyriac <rcyriac(a)redhat.com&gt; how well is documented and how can we improve the experience for this step? - extra HCI nodes (say beyond 6) could easily transition into erasure > coding for good quota management, distinguishable by volumes? > - oVirt clusters supported easy transition between HCI and SAN/NFS storage > as initial 1 or 3 node HCI "succeed" into a broader deployment with role > differentiation? I think these needs further explanation but I'll let Gluster team to ask about them > - it was validated on "edgy hardware" like Atoms, which support 32GB RAM > these days, nested virtualization with affordable 100% passive hardware? Anyone willing to donate this edgy hardware to the project so we can fully validate oVirt on such hardware? https://ovirt.org/community/get-involved/donate-hardware.html > - oVirt node images were made only from fully validated vertical stacks, > including all standard deployment variants (SAN/NFS/Gluster 1/3/6/9 node > HCI) including VDO and all life-cycle operations (updates)? Can you please detail the test criteria? Just noting here we lack the hardware for testing a 9 node HCI setup in oVirt Jenkins. > - import and export of OVA were fully supported/validated standard > operations against oVirt, VMware and VirtualBox? Any specific issue seen on this? - oVirt, Docker, Podman (and OKD) could work side-by-side on hosts, > recognizing each other's resource allocations and networks instead of each > assuming it owned the host? I don't foresee this to happen, if you want to run VMs and containers on the same hosts you should probably look at OKD+Kubevirt as soltution. > - RealTek drivers, both for onboard and USB3 2.5Gbit were included in the > oVirt node images and actually worked properly across warm reboots? Yes, working with 3rd party drivers is not easy while using Node. For this case a plain CentOS / RHEL would work better. There's a bug in Anaconda that doesn't allow to easily handle 3rd party driver installation with image based installation. > - nested virtualization was fully supported with oVirt on oVirt for fully > testing migration and expansion scenarios before applying them on the > physical hardware? nested virtualization is used for testing oVirt on x86_64 always. All oVirt System Tests suite relies on nested virtualization working. > - Ansible was just 10000x faster? This is not something the oVirt team can do :-) we can suggest something to speed up: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup#deployment-tim... but it may have its corner cases when it may not work as espected. maybe worth splitting the discussion on separate threads per topic. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/S4RZUOERTVU... -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/ sbonazzo(a)redhat.com <https://www.redhat.com/ *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*