- Devel - oVirt List Archives

[RFE] Notification emails merging and localization #798
by Sandro Bonazzola 07 Feb '23

07 Feb '23

Hi, Stepan Ermakov submitted https://github.com/oVirt/ovirt-engine/pull/798 proposing enhancement to the email notification system. Developers community. can you please review? CC Users community in case someone wants to review as well. Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System 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.*

1 0

oVirt 4.5.4 is now generally available
by Sandro Bonazzola 06 Dec '22

06 Dec '22

oVirt 4.5.4 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.5.4, as of December 5th, 2022. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.4. Important notes before you install / upgrade Some of the features included in oVirt 4.5.4 require content that is available in RHEL 8.7 (or newer) and derivatives. NOTE: If you’re going to install oVirt 4.5.4 on RHEL or similar, please read Installing on RHEL or derivatives <https://ovirt.org/download/install_on_rhel.html> first. Documentation Be sure to follow instructions for oVirt 4.5! - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.5.4 Release? This release is available now on x86_64 architecture for: - CentOS Stream 8 - CentOS Stream 9 - RHEL 8.7 and derivatives - RHEL 9.1 and derivatives This release supports Hypervisor Hosts on x86_64: - oVirt Node NG based on CentOS Stream 8 - oVirt Node NG based on CentOS Stream 9 - CentOS Stream 8 - CentOS Stream 9 - RHEL 8.7 and derivatives - RHEL 9.1 and derivatives Builds are also available for ppc64le and aarch64. Known issues: - On EL9 with UEFI secure boot, vdsm fails to decode DMI data due to Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> - python-dmidecode module fails to decode DMI data oVirt Node will be released as soon as GitHub Runners will be back online (Ticket opened: https://issues.redhat.com/browse/CPDEVOPS-606 ) See the release notes for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.5.4 release highlights: https://www.ovirt.org/release/4.5.4/ - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System 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.*

1 1

vdsm maintainers changes
by Michal Skrivanek 28 Nov '22

28 Nov '22

Hi all, FYI recently the VDSM maintainers proposed the following changes that i'm now applying in GitHub. Vojtech Juranek is stepping down from Storage subsystem maintainership Albert Esteve is the new Storage subsystem maintainer Many thanks to Vojta's past contributions, and congrats to Albert! michal

1 0

About oVirt’s future
by Yedidyah Bar David 14 Nov '22

14 Nov '22

Hi all, Red Hat Virtualization (RHV) recently entered maintenance phase[1], and the RHV development team is gradually shifting its efforts over to other projects. We are still around, subscribed to the mailing lists, answering questions and help as needed. There is a strong trend in the industry towards containers and microservices, and Red Hat's part of that is OpenShift. People that want to use OpenShift and still need virtualization, until they transition their workloads to run in containers, would best be served by using OpenShift Virtualization. Following this, if you are an oVirt user, you might want to try OKD Virtualization [2], the Community Distribution of Kubernetes that powers Red Hat OpenShift, and Forklift [3], a migration tool that facilitates the transition of VM workloads from oVirt to OKD Virtualization. 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. We see lots of activity in the community both trying and using oVirt, and helping each other, which is great! We also see some work done on basing oVirt on Rocky/Alma Linux, which is also great! We’ll be happy to help with this, where our specific expertise is needed. 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! In particular, we welcome long-time, active members of this list to join the list moderation team. If you want to help with this, please contact me directly, or email ovirt-users at ovirt.org. I am posting this message to both lists - users and devel, separately - deliberately not cross-posting. If you are subscribed to both, and feel like replying, please choose the list that best matches the content of your reply. Thanks! :-) Best regards, [1] https://access.redhat.com/support/policy/updates/rhev [2] https://docs.okd.io/latest/virt/about-virt.html [3] https://www.konveyor.io/tools/forklift/ -- Didi

1 0

oVirt 4.5.2 - Add Gluster Volume fails via Ansible & Cockpit
by simon＠justconnect.ie 13 Nov '22

13 Nov '22

I posted this in the Users group but perhaps it needs to be in Development as I’ve not had a response yet. Hi, In 4.4 adding additional gluster volumes was a simple ansible task (or via cockpit). With 4.5.2 I tried to add new volumes but the logic has changed/broken. Here's the error I am getting: TASK [gluster.infra/roles/backend_setup : Create volume groups] ******************************************************************************************************************************** failed: [bdtovirthcidmz02-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010442", "end": "2022-11-10 13:11:16.717772", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:11:16.707330", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz03-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010231", "end": "2022-11-10 13:12:35.607565", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:12:35.597334", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz01-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.011282", "end": "2022-11-10 13:13:24.336233", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:13:24.324951", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} The vg was created as part of the initial ansible build with logical volumes being added when required. Any assistance would be greatly appreciated. Kind regards Simon

1 0

Error during SSO authentication access_denied
by muruganc＠botvfx.com 10 Nov '22

10 Nov '22

I'm getting the below error during ovirt VM engine creation. Please help me. [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials. [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials."} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost]

2 1

Installation of Ubuntu 22.04 on my Ovirt
by co wil 10 Nov '22

10 Nov '22

Hello my dear friends, I would like to install Ovirt on my machine under an ubuntu 22.04 installation but so far I have not found any commands to install it. Please help me find a solution.

3 2

Enable DCO app on github for enforcing signed-off-by
by Nir Soffer 26 Oct '22

26 Oct '22

I'm not sure we enforce signed-off-by in all projects, but we do in the most important projects. There is a nice little app adding CI check with zero effort. Here is a bad commit: https://github.com/nirs/userstorage/pull/29 When the check fails the app provides useful help for users: https://github.com/nirs/userstorage/pull/29/checks?check_run_id=9125092601 Looks like very little effort to improve all projects! If you wandered what signed-off-by means, this is explained here: https://wiki.linuxfoundation.org/dco Nir

1 0

GWT in project ovirt
by anater78＠gmail.com 24 Oct '22

24 Oct '22

Hello! I plan to develop ui plugins. Does it make sense to use GWT? Do you plan to use GWT in the project in the future? Do you plan to switch to another technology? If something has already been written about this or there is a roadmap, I ask for a link. Thank you!

3 2

separate DWH/grafana machine with keycloak enabled
by Yedidyah Bar David 24 Oct '22

24 Oct '22

Hi all, $Subject is currently broken. We do not have yet an open bug for this but did have a few related (but different) ones, including: https://bugzilla.redhat.com/show_bug.cgi?id=2122174 https://bugzilla.redhat.com/show_bug.cgi?id=2113980 While looking at this, I decided it's about time to have ovirt-system-tests test this flow, as it seems it's not tested enough otherwise. Right now, I managed to make it all work, but do have some open questions, thus current email. What I have right now ===================== 1. This harmless patch to the engine, to just add new library code, only to be used (for now) by grafana setup code (later): https://github.com/oVirt/ovirt-engine/pull/669 I see no obvious reason to not merge it already, but if it turns out that only grafana setup is going to ever use it, it might be easier to move this code there. In principle it can be useful also for OVN, as commented there. 2. This patch to DWH. It's "mandatory", but not enough to get a complete solution. Should be ready for merge. Requires above engine patch. https://github.com/oVirt/ovirt-dwh/pull/57 3. This PR for ovirt-system-tests: https://github.com/oVirt/ovirt-system-tests/pull/293 What's inside: 3.1. "Make grafana test use grafana_fqdn" - should be trivial and harmless. 3.2. "WIP: Add separate-machine-basic-suite-master" - started as a copy of basic-suite-master. Much of it is links to there. To review the rest, you can compare with relevant files in basic-suite. "WIP", because it's not enough, see later, but is probably more-or-less also ready for merging. 3.3. "WIP: Add the dwh/grafana host name to keycloak redirect URIs" - this is where my main question/issue is. Without this, our setup code sets redirectUris to point only at the engine machine, so when trying to login to grafana with SSO, you get an error from keycloak, e.g. as in: https://stackoverflow.com/questions/51275797/invalid-redirect-uri-keycloak-… When configuring things manually, it's up to the user to handle all of this. This applies either to oVirt users that want to do this manually, or to RHV users, where keycloak is not integrated: https://blogs.ovirt.org/2019/01/federate-ovirt-engine-authentication-to-ope… https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… So it sounds like it makes sense to fix this in dwh/grafana setup code, not in OST, right? But this is slightly more risky and annoying, as we'll need to prompt asking the user for the keycloak admin password. Perhaps we do want to do this anyway, but perhaps it's enough to document how to do this manually (and keep this patch in OST as an implementation of this document). 3.4. "WIP: Copy test_verify_engine_certs to test_001" not sure I always needed it, but should be harmless. Perhaps should be done more nicely somehow also for other suites. Opinions/comments/ideas/suggestions/whatever are most welcome! Thanks and best regards, -- Didi

1 1