Project

General

Profile

Actions

action #110515

closed

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

Added by okurz about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-04-29
Due date:
% Done:

0%

Estimated time:

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; in post_jobs within CloneJob.pm. One can then modify the worker classes as needed and post the jobs manually.
Actions

Also available in: Atom PDF