Desired storage options Desired single server setup with included maintenance and updates made easy Backup improvements desiderata Thanks, Gianluca On Tue, Apr 27, 2021 at 10:16 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote:

Hi, On 4/27/21 10:13 AM, Sandro Bonazzola wrote: maybe something about most wanted new feature? Cheers, Jiri > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com <mailto:sbonazzo@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. > * > * > > * > > _______________________________________________ > 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/S25LWSV7WLA... >

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?

hi Sandro, SW components used for cluster like: - RHEL8 for Ovirt management + Ovirt node for hosts - RHEL8 for Ovirt management + Alma linux node for hosts - Centos 8 Stream for Ovirt management + Centos 8 Stream for hosts ... Marek Dne 27/04/2021 v 10:13 Sandro Bonazzola napsal(a):

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

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

On Tue, Apr 27, 2021 at 9:55 PM Jiří Sléžka <jiri.slezka(a)slu.cz&gt; wrote: Perhaps add one or more questions about the base OS. E.g.: * What are your plans regarding the base OS, with the recent changes in CentOS? - Stay on oVirt 4.3 + CentOS 7 for the time being - Manually upgrade to CentOS Stream on both engine and hosts - Use only ovirt-node and the appliance [2] - Migrate to Red Hat Enterprise Linux or some rebuild of it (and please provide details - which one?) - More than one of the above, depending on use case (and please provide details) And perhaps also ask about plans in light of Red Hat's RHV roadmap [1], to slowly phase out RHV in favor of OpenShift Virtualization: * What are your plans for the next 2-3 years for your virtualization use (see also [1])? - Migrate to OKD/kubevirt - Stay on oVirt for the time being - Migrate to Oracle's OLVM and expect/ask that they continue supporting it further - Migrate to some other FOSS virtualization project (which? Please provide details) - Migrate to some proprietary product (which? Please provide details) [1] https://access.redhat.com/support/policy/updates/rhev [2] ovirt-node and ovirt-engine-appliance are images created by oVirt for releases. These are going through at least basic testing before announcing a release. If/when oVirt starts basing them on CentOS Stream, one can expect them to be tested before the release, at least so that they can be considered some kind of a “stable base” to work from. Then, updating to newer versions of packages provided by CentOS Stream is up to the user: Some would prefer to not ever do this (until the next release of oVirt), some would cherry-pick specific updates as needed/relevant (e.g. security-related updates), and some might update everything daily (e.g. for testing). Best regards, -- Didi

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>*