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 over 2 years ago. Updated over 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 #1

Updated by okurz over 2 years ago

  • Copied from action #110467: Establish reliable tap setup on ow14 added
Actions #2

Updated by okurz over 2 years ago

  • Project changed from openQA Infrastructure to openQA Project
  • Subject changed from Dry-run for openqa-clone-job to Command export feature for openqa-clone-job size:M
  • Description updated (diff)
  • Category set to Feature requests
  • Status changed from New to Workable
Actions #3

Updated by mkittler over 2 years ago

  • Assignee set to mkittler
Actions #4

Updated by mkittler over 2 years ago

  • Status changed from Workable to In Progress
Actions #5

Updated by openqa_review over 2 years ago

  • Due date set to 2022-05-17

Setting due date based on mean cycle time of SUSE QE Tools

Actions #6

Updated by mkittler over 2 years ago

  • Status changed from In Progress to Feedback
Actions #8

Updated by mkittler over 2 years ago

  • Status changed from Feedback to Resolved

Yes. I have tested it locally which should be sufficient.

Actions #9

Updated by mkittler over 2 years ago

  • Copied from deleted (action #110467: Establish reliable tap setup on ow14)
Actions #10

Updated by okurz over 2 years ago

  • Due date deleted (2022-05-17)
Actions

Also available in: Atom PDF