Need somewhere to publish "firmwares" that are used in test

[smoser]

stubby's test harness uses some "firmwares" files that come from OVMF and from shim-signed packages.
These can be collected from an ubuntu system using './test/collect-firmwares'.

Using different firmware files over time adds variability to the test harness, and exposes it to bugs like in LP: #1986692.

It would be good to publish the firmware files in one way or another, so that we can use consistent versions.

I've attached

• gen-lxc-firmwares.txt - bash script to use lxc to generate the firmwares files from an ubuntu container
• focal.tar.gz - files from focal up to date as of today
• jammy.tar.gz - files from jammy up to date as of today (they suffer bug 1986692, so they're not really usable).

[hallyn]

What about storing them in oci layers at zothub.io?

[smoser]

I guess i'm not entirely opposed to that, but then i need an oci client to download the thing.
You can call me old, but 'wget' works pretty well.

One thought I had was to create a puzzleos project called 'firmware-bins' and then have releases of it or something like that. that way github would host whatever tarball we put up there.

[hallyn]

One thought I had was to create a puzzleos project called 'firmware-bins' and then have releases of it or something like that. that way github would host whatever tarball we put up there.

Let's do that.

[smoser]

a thought, we are producing these ovmf files in bootkit now: https://github.com/project-machine/bootkit
and bootkit's intent is basically to be a set of bins like that.

[smoser]

Just to mention here. I attempted a bump to jammy in PR #35.
The end result is that it really seems like the jammy firmwares are slower.

The are the 4M variant compared to 2M variant on focal.