[PjM][epic][tools] Share openQA Hardware between SUSE and openSUSE
I discussed that topic shortly with Santi. Good ideas but needs definitely a decision from Coolo & other openSUSe people.
#5 Updated by RBrownSUSE almost 4 years ago
- Assignee changed from RBrownSUSE to szarate
No, I'm really not the right person to assign this to - this is not my job any more, neither as a Linux Distribution Engineer nor as openSUSE chairman
It's a SLE QA Department responsibility to help openSUSE with openQA.
SUSE purchased 3 workers for openSUSE and only gave it 2
SUSE has higher demands for hardware, but openSUSE is struggling now
Marita was driving a solution to managing all of the openQA hardware. Managing two sets of hardware is harder than one.
We have support for shared workers
o3 is already totally isolated from all other openSUSE infrastructure
osd is it's own beast from all SUSE infrastructure
merging the two networks so that o3 and osd can both draw from the same pool seems to be the sensible, logical way of balancing the requirements from both osd and o3
If this approach is not accepted, than as openSUSE Chairman I formally request that openSUSE receive the 'missing' o3 worker that was purchased at the same time as openqaworker1 and openqaworker4, or a suitable alternative.
#6 Updated by okurz almost 4 years ago
- Category set to Infrastructure
IMHO in line with what coolo and rbrown stated: Sponsoring more openSUSE hardware is most likely cheaper and easier for SUSE to do than to combine networks. Having to administer just one network might be easier but the existing two also offer their benefits: Tick-Tock openQA deployments, our kind of A/B testing :) Streamlining the administration, e.g. by saltifying o3 more can be beneficial of course :)
#11 Updated by szarate over 1 year ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html