Hello Samu,
Thank you for the kind words and for your questions.
First, I want to be transparent about how this was done: the implementation was carried out with Claude Code, Anthropic's AI coding agent. My role was direction and supervision — deciding what to build, reviewing the results, and testing everything against real oVirt environments. This is also why community review matters so much to me: I would genuinely appreciate feedback on wrong implementations, questionable design decisions, and security issues.
On the VNC issue (broken virt-viewer on Windows): I solved it by re-implementing the console as a browser-based noVNC web console. The native client path (.vv / remote-viewer) is removed entirely — the console opens as a popup connecting over a same-origin websocket through the engine's Apache, so Windows users need nothing but a web browser: no virt-viewer install, no separate certificate acceptance. It is working today against real VMs in my environment. To be clear, this does not fix virt-viewer itself, but with this UI you no longer need it.
On sharing: I have pushed everything here: https://github.com/tkqltm/ovirt-engine-react — a fork of ovirt-engine with full upstream history. It contains the complete backend changes (GWT-RPC layer and GWT servlets removed, all client-server communication moved to the REST API, the whole codebase migrated from javax to jakarta / Jakarta EE, running on WildFly 40, Java 21, PostgreSQL 13+) and the new React 19 / PatternFly 6 frontend under frontend/webadmin-react/. The changes go far beyond the UI, so I believe the backend needs to be reviewed as a whole, not just the frontend.
One honest caveat: the base product was customized before this conversion, so it deviates from stock oVirt in places — Gluster was removed from the UI, and we use a custom "Ceph RBD" storage domain type (we originally used the ceph-iscsi gateway but hit sanlock problems, so kernel-mapped RBD devices are treated like FC LUNs instead).
I would love as much feedback and as many corrections as the community can give. And I sincerely hope this contribution brings a new atmosphere and many changes to ovirt-engine. If there is a preferred way to take this toward upstream (devel list RFC, patches, anything), please point me in the right direction.
Best regards,