sent https://gerrit.ovirt.org/#/c/101876/ to move the manual job to containers, so it will have more slots to run tests.

It means that OST runs might take 20% longer to run but will have much more parallel runs available from what we had so far.

what do we need to do in order to move the manual OST job to use containers?

we can probably move the manual job to use containers if we didn't already, that aught to let it have more executors aviabale. , WDYT?

please note that moving into containers will have about 30% impact on the job performance, so we're paying in latency for greater throughput...

We have 5 servers, which are shared between CQ, OST check-patch and nightly OST Jobs. so not so much.
Is running OST Manually is an option? you can run the same way it run on the manual job.
If we see it's not enough, maybe we consider paying for renting external bare metals, or we can also look into moving another server to run inside OpenShift to run more load as I've asked and , same as KubeVirt runs.

Why do you think it's not available? as I said, its probably being taken by CQ or OST check-patch... eventually we have a limited amount of hosts, so i'm not sure there are ideal hosts

I see. So how many we have? One? Can it be shared with other hosts?
And even if we have just one right now - why is it not available? It's happening relatively frequently (roughly once in two weeks from what I've seen)

The manual job has already 10 available executors:
job-template:
name: '{project}_manual'
project: '{project}'
concurrent: true
properties:

• build-discarder:
  days-to-keep: 14

• throttle:
  enabled: true
  option: project
  max-total: 10

The fact that jobs are waiting in queue means there aren't enough hosts to run the tests, something that isn't easily solvable without buying new hardware or perhaps moving the manual job to run on containers instead of single bare metals servers.

how much time will it take to move the manual OST Job to run on containers, something that might help here?