[ https://ovirt-jira.atlassian.net/browse/OVIRT-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40611#comment-40611 ] Anton Marchukov commented on OVIRT-2968: ---------------------------------------- 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.

Maintaining Selenium Grid Infrastructure Research -------------------------------------------------

Key: OVIRT-2968 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2968 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra

During work on OST conversion it was found that we might benefit from having selenium grid infrastructure [1] 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. [1] https://www.selenium.dev/documentation/en/grid/ -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100130)