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

@okurz Would you please have a look if this is a proper task for tools team? Or shall I contact other team?

Appreciate if this can be planned with request urgency considered!

okurz wrote in #note-8:

@xlai syncing assets and triggering tests is commonly done using https://github.com/os-autoinst/openqa-trigger-from-obs/ and for OSD https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/ so I suggest you work with the domain experts in those repos to get the necessary assets synced.

@jlausuch Hi Jose, I checked from merged MRs and found that you enabled SLE Micro 6.1 repo initially. Can we ask you for help here? If you are busy, maybe I will work on it. It will be my first time coding for the tool. It may take some time to understand the overall logic firstly.

jlausuch created https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/merge_requests/198 to cover this. Merged and deployed.

I have also created the mediums with empty variables. But there are 2 things to point out:

• it will sync the new images (install.tar) but in the other directory (/var/lib/openqa/factory/other/) instead of hdd directory. If we need them in hdd, then we need to modify this line https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/script/cfg.py#L293 to include tar in the condition.
• it will also trigger tests using those new flavors. Is that desired?

jlausuch wrote in #note-11:

I have also created the mediums with empty variables. But there are 2 things to point out:

• it will sync the new images (install.tar) but in the other directory (/var/lib/openqa/factory/other/) instead of hdd directory. If we need them in hdd, then we need to modify this line https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/script/cfg.py#L293 to include tar in the condition.

@jlausuch Thank you for the help.

Is it possible to UNTAR the synced images to some http links? Sth like
http://10.200.131.12:8666/ipxe/aarch64/SL-Micro.aarch64-6.1-Default-SelfInstall-Build20.3/.

Quote from ticket description:

for each SLM 6.1 build, please **untar** , **x86 and aarch64** , below resources into **http accessible links** from OSD ipmi SUT

BTW, for baremetal, we do not need it in HDD value. But better to have it in some var which we can use in test.

• it will also trigger tests using those new flavors. Is that desired?

It is fine to either trigger, or not trigger. We can just put the jobs under the default-selfinstall flavor.

xlai wrote in #note-12:

Is it possible to UNTAR the synced images to some http links? Sth like
http://10.200.131.12:8666/ipxe/aarch64/SL-Micro.aarch64-6.1-Default-SelfInstall-Build20.3/.

Currently no. That would require some extra code in https://github.com/os-autoinst/openqa-trigger-from-obs/tree/master/script

Hope published files are uncompressed and well structured in folder hierarchy which reflects DISTRI, BUILD, ARCH and etc. By the way, besides the pxe boot files, there are also disk image to be installed via pxe like http://10.200.131.12:8666/ipxe/x86_64/SL-Micro.x86_64-6.1.xz

@jlausuch Hi Jose, this will soon be a blocker for SLM 6.2 OSD openqa test enablement too. It is more needed this time, because the only one pair of machine that can run SLM baremetal test are in NUE2 lab and will not work soon. We have to switch to pxe installation on the other pair of machine in PRG2 lab.

Will it be possible to help coordinate that the one working on 6.2 pipelines help to implement this pxe resource(published as http link)?

If not easy, we can do it by ourselves, but we need to learn first. And maybe the training that you mentioned earlier can be planned at some recent proper time slot?

We probably don't need to do some magic to extract install.tar files. I can see that in the iso directory there are some install.iso. Currently:

SL-Micro.aarch64-6.2-Base-Build1.1.install.iso
SL-Micro.aarch64-6.2-Base-RT-Build1.1.install.iso
SL-Micro.aarch64-6.2-Base-RT-SelfInstall-Build1.1.install.iso
SL-Micro.aarch64-6.2-Base-SelfInstall-Build1.1.install.iso
SL-Micro.aarch64-6.2-Default-Build1.1.install.iso
SL-Micro.aarch64-6.2-Default-SelfInstall-Build1.1.install.iso

SL-Micro.x86_64-6.2-Base-RT-SelfInstall-Build1.1.install.iso
SL-Micro.x86_64-6.2-Base-SelfInstall-Build1.1.install.iso
SL-Micro.x86_64-6.2-Default-SelfInstall-Build1.1.install.iso

SL-Micro.ppc64le-6.2-Base-512-SelfInstall-Build1.1.install.iso
SL-Micro.ppc64le-6.2-Base-4096-SelfInstall-Build1.1.install.iso
SL-Micro.ppc64le-6.2-Default-512-SelfInstall-Build1.1.install.iso
SL-Micro.ppc64le-6.2-Default-4096-SelfInstall-Build1.1.install.iso

Please let me know which ISOs should I sync and will add it to https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/blob/master/xml/SUSE:SLFO:Products:SL-Micro.xml

I replied in slack,but let me also copy it here to be synced in ticket

For pxe installation, we do NOT need install.iso, but need install.tar. The contents of these two are totally different. Also for install.tar, it is needed to untar it into some directory, and http accessible.

@Jose Lausuch
 For SLM6.2  pxe installation, need to untar below "*.install.tar" into a directory separately, and publish them as http accessible link
- https://download.suse.de/ibs/SUSE:/SLFO:/Products:/SL-Micro:/6.2:/ToTest/images/SL-Micro.aarch64-6.2-Default-SelfInstall-Build1.1.install.tar
- https://download.suse.de/ibs/SUSE:/SLFO:/Products:/SL-Micro:/6.2:/ToTest/images/SL-Micro.x86_64-6.2-Default-SelfInstall-Build1.1.install.tar

I spent some time in hackweek on learning the tool. A potential solution is proposed with 2 PRs,

• https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/merge_requests/213
• https://github.com/os-autoinst/openqa-trigger-from-obs/pull/278

Welcome to review!

xlai wrote in #note-27:

I spent some time in hackweek on learning the tool. A potential solution is proposed with 2 PRs,

• https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/merge_requests/213
• https://github.com/os-autoinst/openqa-trigger-from-obs/pull/278

Welcome to review!

The two PRs are merged. Will follow up status.