Project

General

Profile

Actions

action #7982

closed

multi machine test that actually involves different machines

Added by lnussel over 9 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
2015-06-22
Due date:
% Done:

0%

Estimated time:

Description

multi machine scheduling currently assumes that all linked jobs run on the same machine. There should be a way to have different machines talk to each other. Maybe with a syntax like like PARALLEL_WITH="test@machine"?


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure (public) - action #33253: [salt] add support for multiple multi-host worker clusters - connect multiple workers using GRE within the same WORKER_CLASSResolvedthehejik2018-03-14

Actions
Actions #1

Updated by okurz almost 8 years ago

  • Assignee deleted (nadvornik)
  • Priority changed from Normal to Low
  • Target version set to future

@nadvornik: Please do not ignore tickets that long. It is ok if you just unassign with a comment why you do not want to work on it

Actions #2

Updated by okurz over 6 years ago

  • Target version changed from future to future
Actions #3

Updated by okurz over 6 years ago

  • Related to action #33253: [salt] add support for multiple multi-host worker clusters - connect multiple workers using GRE within the same WORKER_CLASS added
Actions #4

Updated by thehejik about 6 years ago

multi machine scheduling currently assumes that all linked jobs run on the same machine

^ that's not true anymore, as we did support for GRE tunnels connecting several (currently 7) worker hosts into one huge mm cluster.

It should also support other architectures than x86_64 - the job will just run in different vlan.

Please close this.

Actions #5

Updated by coolo about 6 years ago

  • Status changed from New to Rejected

Let's say it's duplicating 40415 now

Actions

Also available in: Atom PDF