During work on OST conversion it was found that we might benefit from
having selenium grid infrastructure  to be available as a general
service inside CI. This is basically by design. You can maintain selenium
grid and worker nodes and then expose it over network for general use.
Right now each OST run sets it up on its own each run. So I think having
dedicated and support infrastructure should be beneficial and could be part
of the infra.
Opening this ticket for research and discussion.
Associate Manager - RHV DevOps - Red Hat
The major problem that I see is that the oVirt that we tests runs inside some local network on a jenkins slaves. And selenium will just open a browser that needs to access that oVirt.
However, if this could be solved it might also have additional benefits where people may use some internal VPN to directly access oVirt under test, e.g. when running manual job or debugging.
Closing since we found the way to use selenium on RHEL8 in Padman when we get rid of mock (in progress).