Project

General

Profile

Actions

action #157147

closed

coordination #103944: [saga][epic] Scale up: More robust handling of diverse infrastructure with varying performance

coordination #157144: [epic] Groups of worker classes: Regions, locations, etc.

Documentation for OSD worker region, location, datacenter keys in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls size:S

Added by okurz 7 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-03-13
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

Based on request by fniederwanger in Slack.
With https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/705 we have introduced region+location+datacenter keys in the worker class settings. That is generally documented as example in http://open.qa/docs/#_assigning_jobs_to_workers but not directly describes the relevant settings for OSD users. We should ensure that this concept is described with users of the OSD infrastructure in mind, e.g. in https://wiki.suse.net/index.php/OpenQA and/or https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/README.md and/or https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/README.md?ref_type=heads

Acceptance criteria

Suggestions

Incorporate ideas from #157144-2


Related issues 1 (0 open1 closed)

Related to openQA Project - action #157534: Multi-Machine Job fails in suseconnect_scc due to worker class misconfiguration when we introduced prg2e machinesResolvedokurz2024-03-19

Actions
Actions #1

Updated by okurz 7 months ago

  • Related to action #157534: Multi-Machine Job fails in suseconnect_scc due to worker class misconfiguration when we introduced prg2e machines added
Actions #2

Updated by okurz 7 months ago

  • Target version changed from Tools - Next to Ready
Actions #3

Updated by okurz 7 months ago

  • Description updated (diff)
Actions #4

Updated by okurz 7 months ago

  • Subject changed from Documentation for OSD worker region, location, datacenter keys in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls to Documentation for OSD worker region, location, datacenter keys in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #5

Updated by okurz 7 months ago

  • Status changed from Workable to Blocked
  • Assignee set to okurz

I would like to clarify as part of #135035 first if we want to combine those concepts.

Actions #6

Updated by livdywan 6 months ago

  • Status changed from Blocked to Workable

This seems to be unblocked now

Actions #7

Updated by okurz 6 months ago

  • Description updated (diff)
  • Assignee deleted (okurz)
Actions #8

Updated by mkittler 6 months ago

  • Status changed from Workable to In Progress
  • Assignee set to mkittler
Actions #9

Updated by mkittler 6 months ago

  • Status changed from In Progress to Feedback

AC1 is already fulfilled (even though the documentation doesn't mention literally "region", "location" and "datacenter").

MR for AC2: https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/779

Actions #10

Updated by okurz 6 months ago

mkittler wrote in #note-9:

[…] the documentation doesn't mention literally "region", "location" and "datacenter"

yes, but shouldn't it?

Actions #11

Updated by mkittler 6 months ago

The MR for the pillars has just been merged.


yes, but shouldn't it?

But then I'd replace the existing "planet-earth,continent-antarctica,location-my_station" example to match what we use on OSD. Having two different examples for this would otherwise be a bit excessive. I tend to just keep the existing example.

Actions #12

Updated by okurz 6 months ago · Edited

Ok, fine. Keep it :)

But please keep in mind how users would find the relevant information. So maybe on the internal openQA wiki page?

Actions #13

Updated by mkittler 6 months ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF