Actions
action #152737
opencoordination #112862: [saga][epic] Future ideas for easy multi-machine handling: MM-tests as first-class citizens
coordination #111929: [epic] Stable multi-machine tests covering multiple physical workers
Support for triggering parallel (multi-machine-)tests within a configured zone or location
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
One openQA instance can happily run with openQA workers connected from various locations as we use for both o3 and osd. However for something like multi-machine tests having them run across multiple locations might introduce all kinds of problems hence it would be beneficial to restrict multi-machine parallel clusters to specific zones or locations, e.g. based on WORKER_CLASS settings, so that all jobs of a parallel cluster on request run within the same zone/location.
Acceptance Criteria¶
- AC1: If configured accordingly all jobs of a parallel cluster run within the same configured zone or location
- AC2: By default if not restricted by configuration jobs of a parallel cluster are still allowed to be triggered on any host of matching worker class
Suggestions¶
- Follow #135035
- Extend the scope of #135035 but towards zone/location
- Use Documentation Driven Development to write documentation first of how you would like the feature to work before implementing
- Define corresponding naming conventions for WORKER_CLASS values
- Adapt WORKER_CLASS settings accordingly in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls and correspondingly on o3 workers
- Implement
Updated by okurz 11 months ago
- Copied from action #135035: Optionally restrict multimachine jobs to a single worker added
Actions