- Devel - oVirt List Archives

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

Adding documentation - Migrating from a self-hosted engine to a standalone
by David White 14 Oct '22

14 Oct '22

Hi. I'm working on adding instructions to the documentation for how to migrate from a self-hosted engine to a stand alone manager. This will be the first time I've contributed anything to this project (or any larger open source project for that matter), so before I get too far in the weeds, I wanted to run this by the community so as not to waste my time if this is a bad idea. My general high level documentation is here: https://pastebin.mozilla.org/YyOOVRFZ These are the steps that I took when I did my own migration. (Note to self: Need to add a step at the end to log into the Manager and disable the Gluster service by going to Computer --> Clusters --> (Edit the cluster) --> Uncheck the "Enable Gluster Service" checkbox. And I've forked the ovirt-site repo and started working on the documentation here: https://github.com/dmwhite823/ovirt-site/tree/migrate-engine-to-standalone I still have a ways to go before I'm ready to request a PR, but I'm open to any & all feedback. Sent with Proton Mail secure email.

1 0

Creating an oVirt Engine Appliance on a different EL Distro (eg Rocky Linux)
by Matthew J Black 03 Oct '22

03 Oct '22

Hi All, Here's an interesting question (that I originally asked in the Users List, but which someone suggested I ask here - so I am): What is the process (ie the Step-By-Step process) to create an/the oVirt Engine Appliance based on another version of EL (ie in my case, Rocky Linux)? Is there a "Manual" somewhere? I mean, surely the oVirt Project's Release Manager has *something* that they follow to create the relevant rpm file - no? Cheers Dulux-Oz

1 0

oVirt engine builds on el9
by Michal Skrivanek 26 Sep '22

26 Sep '22

Hi all, we are going to bundle maven dependencies in a new package ovirt-engine-build-dependencies. This allows us to use CBS to build ovirt-engine as any other package, and enable el9 builds. This is just a build dependency, there's no change to a built product. We will now start publishing el9stream builds of ovirt-engine and start switching testing to el9 Thanks, michal

2 2

oVirt bug reports to move from bugzilla to github issues in future
by Michal Skrivanek 23 Sep '22

23 Sep '22

Hi all, as a final stage of out gerrit to github transition that started ~9 months ago we are planning to eliminate the use of bugzilla.redhat.com for all oVirt projects (bugs with Classification: "oVirt") and use the native issue tracking in github as well. We used to have integrations with gerrit and bugzilla that we moved to github actions instead, and the overhead (and notorious slowness) of bugzilla.redhat.com becomes the only "benefit" of using it these days. There's about 50 bugs total left in oVirt bugzilla so it's not that much to move, the biggest change would be that the new bugs are to be filed elsewhere. This is just a heads up for now, we haven't set a cut off date just yet, but you can expect this change in the coming weeks. Thanks, michal

1 1

ovirt-engine-4.5.3 has been tagged
by Martin Perina 15 Sep '22

15 Sep '22

ovirt-engine-4.5.3 has been tagged -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

1 0

gerrit.ovirt.org migration
by Denis Volkov 13 Sep '22

13 Sep '22

Hello There's a migration of gerrit to another server. Server should change IP address I'll post update when it's done -- Denis Volkov

1 1

vbmc - simple IPMI support for oVirt VMs
by Michal Skrivanek 05 Sep '22

05 Sep '22

Hi all, I wanted to share the news about a new oVirt (mini)project - vbmc[1]. It's fairly small and simple, but it may be handy if you'd like to treat oVirt VMs as bare metal machines controllable via IPMI. It only implements power on, off, reboot, and set boot order, but that should be enough for bootstrapping over pxe. Thanks, michal [1] https://github.com/oVirt/vbmc

1 0

Re: Starting with oVirt
by Strahil Nikolov 02 Sep '22

02 Sep '22

Hardware wise - try one server with CentOS Stream 8 and check that all hardware is recognized and works as expected. You can start with a single server and expand further. RH dropped Gluster Support for their downstream solution (RHV) , yet oVirt doesn't have plans to get rid of it. The easiest for you would be to use SAN or NAS as storage. If that's not an option, you can use GlusterFS - which is a distributed File System . The latter needs a 10GBE NICs (1 Gigabit is OK, but don't expect much speed when writing in the VMs). oVirt supports GlusterFS in 2 modes:- replica 1 - a mode intended for a single host setup- replica 3 (where you have 3 copies of your data) - where the storage nodes should be multiple to 3. You can also have compute-only oVirt nodes (those do not participate in GlusterFS but have CPU & RAM to host VMs) If you configure HA VMs , the engine will take care to recover them on another host. If you loose 2 out of 3 servers - GlusterFS will loose majority of the bricks (term for a host+mount point combination) and will shutdown until majority is restored. In all cases - you should segregate the network for Storage and Compute workloads (Gluster/NFS on separate network). P.S.: iSCSI is also a storage option. Best Regards,Strahil Nikolov On Fri, Sep 2, 2022 at 9:29, Teemu Saarinen<teemu.saarinen(a)netum.fi> wrote:  Hi, Our company is planning oftaking oVirt in into our environment. We would have a few questions for that if you could guide us. Hardware: What would be the minimum configuration for us using oVirt?.Idea would be to replace all our current Linux and Windows servers withoVirt. There are currently 24 servers in use. The goal would also be that the virtual servers could be migrated live and also in the HA configuration, i.e. if onehardware crashes execution continues on the other. As far as I understand Ovirt enables this? So we would like to know what kind ofhardware (minimum) we should have for this size of environment? Storagin: Do all machines need a lot of hard disk space or is it enough to have only one or two? I'm referring to shared storage. Can you also have storagin as HA? Host: What happens to HOST1 and HOST2 virtual machines if the oVirt host server crashes? Do they continue to operate without it, or do they crash at the same time? Thank You! Teemu S. _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/CTLLKBXYUZQEL…

1 0

[ACTION REQUIRED] engine-setup: getCredentials updated
by Yedidyah Bar David 25 Aug '22

25 Aug '22

Hi all, We now merged all of these patches: [1] https://github.com/oVirt/otopi/pull/29 [2] https://github.com/oVirt/ovirt-engine/pull/585 [3] https://github.com/oVirt/ovirt-engine-keycloak/pull/53 [4] https://github.com/oVirt/ovirt-dwh/pull/47 If you have a new dwh and/or keycloak, and an older engine, and run engine-setup, and get an error about getCredentials, please update both otopi and the engine. Thanks and best regards, -- Didi

1 3