QA (public) » openQA Project (public) » openQA Infrastructure (public)

It's a valid idea. You have to be aware that this approach reduces redundancy. We don't necessarily ensure that we have redundant machines for every CPU class. I suggest based on the CPU details which you can find on the workers page of openQA as well add specific worker classes for what you need in particular. Settings need to go into the salt pillars in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls

EDIT: Discussed in SUSE QE Tools estimation meeting. Future ideas noted down in #65271#note-90

osukup wrote:

as short term solution we can add this to salt for real workers ... ( it can be added by salt itself ..)

Yes, but as I stated I don't know the specific requirements so I suggest for users to add specific worker classes.

@MDoucha no response by you so closing with our suggestions as resolution.

MDoucha wrote:

And I don't know what hardware we have so I can't give you better requirements than "look at the worker list and figure out what might matter for testing". For x86_64, we need extra worker classes at least for Intel and AMD in general. For PowerPC, it might make sense to create extra classes for Power8 and Power9. Anything else can be added later.

That I can do :)

Hm, I don't know if that makes sense but I created https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/400 which is adding some worker classes. Maybe you mean bare metal machines that use the ipmi backend?

After finally receiving positive feedback in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/400 from at least one person I now merged :)

Xiaojing_liu wrote:

We would like to add CPU info on ipmi backend, such as 64bit-ipmi, intel or 64bit-ipmi,amd. But we don't know get the CPU information of those bare-metal machines.

As written in https://suse.slack.com/archives/C02CANHLANP/p1648108099104639?thread_ts=1648101936.264619&cid=C02CANHLANP racktables should have all necessary information, if it does not then please raise that as a problem to the managers that managed adding the machines into the racks. For most if not all what e.g. Nick does is only help to get the machines connected, not having access to the invoice or vendor details. You might be able to find out relevant information by looking at previous openQA jobs on the machines finding uploaded logs that include machine details, kernel logs, etc. I created #108842 so maybe we will progress that way but that means that I can effectively block this ticket by #108842 unless anyone wants to go with the alternatives I proposed which I don't plan to do.

So we have resolved #108842 and clarified that in general SUSE QE Tools will support engineers to get relevant information into racktables and then from racktables also in salt pillar data where necessary.

@MDoucha with that back to you, all the necessary information should be available for you to gather information from machines or ask teams to provide the data and then put the according information into salt pillars.

OSD worker list now shows 75 qemu_x86_64 worker instances with WORKER_CLASS=intel and 26 with WORKER_CLASS=amd (out of 156 qemu_x86_64 instances in total). That's good enough for now.