action #157147
closedcoordination #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
0%
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¶
- AC1: http://open.qa/docs/#_assigning_jobs_to_workers suggests the specific concept of "region-…,datacenter-…,location-…"
- AC2: A SUSE specific documentation explains the meaning of "region, datacenter, location" used within https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls
Suggestions¶
Incorporate ideas from #157144-2
- Simply change the lower text in http://open.qa/docs/#_assigning_jobs_to_workers with the specific concept of "region-…,datacenter-…,location-…"
- Add a SUSE specific documentation for the meaning of "region, datacenter, location" used within https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls, possibly in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/README.md itself, maybe referencing that repo in detail on https://wiki.suse.net/index.php/OpenQA and/or https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/README.md
Updated by okurz about 1 month ago
- Related to action #157534: Multi-Machine Job fails in suseconnect_scc due to worker class misconfiguration when we introduced prg2e machines added
Updated by okurz about 1 month ago
- Target version changed from Tools - Next to Ready
Updated by okurz about 1 month 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
Updated by okurz about 1 month 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.
Updated by mkittler 15 days 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
Updated by mkittler 12 days 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.
Updated by mkittler 11 days ago
- Status changed from Feedback to Resolved
Added a link on https://wiki.suse.net/index.php/OpenQA#Administration.