action #20526: [tools][openqa][research] Research on Federated openQA
[epic]Refactor worker_bridge for federated openQA support
Currently the pr#1414 has a proposal of what the worker bridge could be, but is currently not in the best state, thus it needs a refactor to be able to be merged.
AC is represented as a checklist
- The worker bridge will run on a machine and will have access to a masterUI to query jobs from and to a slaveUI to proxy jobs to.
- Once the clonning of job from masterUI to slaveUI is being performed, worker bridge adds federated_report setting to the job with the url of the job it belongs to
- The masterUI should have the possibility to filter job list by job setting, avoid generating extra load when searching for jobs
- worker_bridge will report back job results to the masterUI job results once the job on the slaveUI has any new status to report (once job is set to done, regadless of the state)
#9 Updated by szarate almost 4 years ago
Following PR's are related, Add all job states to be monitored from /tests route, Add support for getting test results as json on the job json api and have been already merged.
#15 Updated by okurz over 3 years ago
- Target version deleted (
Hi, I am currently reviewing tickets assigned to older milestones and found this one. riafarov already asked you some time ago to update the target version as it was not matching anymore. I guess no harm is done when I simply remove the target version. I assume by now you use a different approach for planning anyway.
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html