Hi Philip, I spent a bit of time trying to setup an openqa node based on what you did (and others) for openqa and os-autoinst on ppc64el . I had no particular issue with openqa from salsa but os-autoinst seems to be a different version on openqa.debian.net . Especially the isotovideo wrapper that doesn't produce a debug output as is, contrary to openqa.d.n (autoinst-log.txt in Logs & Assets) . Some other little issues I had, were: - some run dependencies missing - apache integration not done (or I missed something) - configuration files taken into account seems to be the ones in /usr rather that /etc I guess a README.Debian would be nice to have if some of those steps should still be done manually, because I more or less randomly fixed issues reported in journalctl -xe :) Once I got the whole thing working, I could change some .pm, needles and template (maybe the more ppc64el specific) to make installation testing work on ppc64el which is nice. For that I just used the qemu backend. Some upstream people have developed an ipmi backend for x86 that could be reused on ppc64el baremetal, but it needs to be tested. Also, for LPAR environments, I guess one would need to write an HMC capable backend. Now, some questions : - I'd be glad to provide some more detailed feedback/patches on the above points but are the git trees on salsa of openqa and os-autoinst the latest ? which I was unsure as I said above. - I wanted to know what was the way to structure the tests of Debian distro and derivatives : upstream seems to suppose that one "openqa-tests-<distro>" / "/var/lib/openqa/share/tests/<distro>" should be done per each <distro> . But I see you integrate kali tests into openqa-tests-debian. Does that mean that you link /var/lib/openqa/share/tests/kali to /var/lib/openqa/share/tests/debian ? F. On Sat, 20 Jul 2019 08:37:31 +0200, Philip Hands <phil@hands.com> wrote: > Frédéric Bonnard <frediz@debian.org> writes: > > > Hi Philip, > > > > I see you work on openqa for debian on x86 and I was wondering what > > needs to be done to have tests being run on ppc64el which I'm interested in. > > Depending on the manpower/hardware it requires, I may help. > > Great :-) > > I am very interested in getting other architectures to work. > > I have tried a couple of times with arm64 (emulated with qemu) but > didn't get it to work because of the way that OpenQA uses the first > serial port combined with features of our d-i arm64 builds and perhaps > what qemu is willing to emulate. > > I don't know enough about arm64 to be certain where to best fix that -- > it's clearly fixable, but I chose to concentrate on other things for the > moment. > > If you're able to provide the knowledge to get ppc64el working, either > emulated under qemu, or probably better by running an OpenQA worker on > real ppc64el, that would be a big step forward. > > The main issue with openqa.debian.net at the moment is that it's a bit > short of disk space, which means that I end up having to juggle the test > jobs, and deleting the artefacts rather too soon -- that might make > things a little annoying (having more architectures means having more > .iso images on the disk, so will make that a bit worse). > > The packages for OpenQA are not currently in Debian (I'm working on it), > but it is installed from packages on openqa.d.n (using a personal repo) > so I guess it shouldn't be too hard to make ppc64el openqa-worker > packages, if you have somewhere to run a ppc64el worker. > > So far, I've only been running the workers on the same machine as the > main software, so I would guess that we may bump into issues with running > external workers, but that's how OpenQA normally runs, so it should be > fine in the end. > > Cheers, Phil. > -- > |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. > |-| http://www.hands.com/ http://ftp.uk.debian.org/ > |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
Attachment:
pgpBOCc0C2svQ.pgp
Description: PGP signature