action #134969
open[qe-core] Require latest released quarterly update images for each product to be available
0%
Description
We recently get a suggestion and agreed in discussions with Heiko Rommel, Jan Stehlik, and Antoine Ginies, that when testing released products, it is better to use latest QU image + scc updates.
For detailed requirements,
- all supported products' latest QU image are needed,
- sle12sp3~sle12sp5 (12sp3 has teradata tests after LTSS ends, 12sp4 seems ending but not final confirmed yet)
- sle15sp2-sle15sp5 (and sle15sp6/7 when they are released)
- available in three locations' mirror server and pxe server so that local openqa servers' jobs can access them-- DE NUE2 lab(OSD), PRG1 lab (http://openqa.qam.suse.cz/ resides in) and BeiJing lab (http://openqa.qa2.suse.asia/ resides in)
- the QU images can be accessible via http(s) in repository way (unpacked from iso), and are put with FIXED names like SLExxSPx-QU-LATEST
- the latest QU for all products are added in pxe server
I am not sure if this ticket's scope can be fully covered by openqa infrastructure (some should). It will help a lot, if anyone familiar with it can help point out which parts should go to which team. We will then split the ticket properly. Thanks in advance!
Updated by Julie_CAO 10 months ago
With the iPXE support, a new setting for the URL of released product is introduced, +MIRROR_HTTP=XXX in test suite level. It is more configurable than previous fixed ones in test scripts.
If we would support iPXE only(as opposed to PXE boot), we can set the value to the latest QU mirror server. We need not sync them on openqa servers at meantime.
Updated by okurz 10 months ago
- Project changed from openQA Infrastructure to openQA Tests
- Subject changed from Require latest released quarterly update images for each product to be available to [qe-core] Require latest released quarterly update images for each product to be available
- Category set to New test
I assume this ticket is better suited for QE-Core within the scope "new product enablemement" hence adjusting the issue tracker accordingly