action #110515
coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #109659: [epic] More remote workers
Command export feature for openqa-clone-job size:M
Start date:
2022-04-29
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
User story¶
As an worker administrator I would like to call openqa-clone-job with an option to output what it would execute to be able to tweak the actually executed command, e.g. to trigger a 2-machine-cluster on two separate, specific worker hosts
Acceptance criteria¶
- AC1: openqa-clone-job can be called to output the equivalent openqa-cli commands it would call without actually executing
Suggestions¶
- To spawn a parallel job cluster where some jobs are running on Nürnberg workers and some on Prague workers one can modify openqa-clone-job to print the parameters instead of posting them by putting
print STDERR join(' ', map { "'$_=$composed_params{$_ }'" } sort keys %composed_params); exit 0;
inpost_jobs
withinCloneJob.pm
. One can then modify the worker classes as needed and post the jobs manually.
History
#1
Updated by okurz 3 months ago
- Copied from action #110467: Establish reliable tap setup on ow14 added
#5
Updated by openqa_review 3 months ago
- Due date set to 2022-05-17
Setting due date based on mean cycle time of SUSE QE Tools
#9
Updated by mkittler 3 months ago
- Copied from deleted (action #110467: Establish reliable tap setup on ow14)