OEM: Provide STACKIT images

[robinschneider]

Provide oem-stackit images

Add support for STACKIT as a new provider.
The Image has chrony installed and configured, ptp_kvm kernel module loaded.

How to use

This image is configured for STACKIT but it will work on other OpenStack installations as well.
You can use the openstack-packer-plugin to create an OpenStack image from it https://github.com/hashicorp/packer-plugin-openstack.

Testing done

We have tested this image on STACKIT both as a Kubernetes node as well as a standalone VM for arm64 and amd64.

• Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
• Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

CI: http://localhost:8080/job/container/job/packages_all_arches/6241/cldsv/ to produce images

[tormath1]

Thanks, I triggered a CI build to generate images / oems.

[tormath1]

Thanks, I feel we're almost good here. I left a single nit-pick comment. Three additional things:

• the produced images are currently bzipped, similar to OpenStack (or other vendors), the benefit is really small:

$ du --si flatcar_production_stackit_image.img.bz2
566M	flatcar_production_stackit_image.img.bz2
$ du --si flatcar_production_stackit_image.img
567M	flatcar_production_stackit_image.img

If you don't have strong requirements to bzip format, you can set the image compression to none here:

scripts/ci-automation/vms.sh

Line 141 in 1f4794f

elif [[ "${format}" =~ ^(scaleway|kubevirt|proxmoxve)$ ]];then

• A CI build has been restarted, I will ask you to test the produce images: https://bincache.flatcar-linux.net/images/amd64/9999.0.6+tormath1-stackit-oem-image/ when available (currently a 404)
• If you are happy with the current state, we can maybe arrange a bit the commit history (e.g this 792bfa4 is not relevant to keep in the history)

[robinschneider]

Thanks, I feel we're almost good here. I left a single nit-pick comment. Three additional things:

* the produced images are currently `bzipped`, similar to OpenStack (or other vendors), the benefit is really small:

$ du --si flatcar_production_stackit_image.img.bz2
566M	flatcar_production_stackit_image.img.bz2
$ du --si flatcar_production_stackit_image.img
567M	flatcar_production_stackit_image.img

If you don't have strong requirements to bzip format, you can set the image compression to none here:

scripts/ci-automation/vms.sh

Line 141 in 1f4794f

elif [[ "${format}" =~ ^(scaleway|kubevirt|proxmoxve)$ ]];then

* A CI build has been restarted, I will ask you to test the produce images: https://bincache.flatcar-linux.net/images/amd64/9999.0.5+tormath1-stackit-oem-image/ when available (currently a 404)

* If you are happy with the current state, we can maybe arrange a bit the commit history (e.g this [792bfa4](https://github.com/flatcar/scripts/commit/792bfa43014bb6edb4724d5d569232f7709fd38d) is not relevant to keep in the history)

We don't use the bzip format, will adjust it.
Should I squash all commits?
Will adjust it according to your feedback!

[tormath1]

Thanks a lot for this. I will merge the commit and backport it to current Alpha, Beta and Stable. This should be available at next Flatcar releases. In the meantime, nightly builds will be available if you want to run tests again.

[tormath1]

cherry-picked to:

• flatcar-4372
• flatcar-4344
• flatcar-4230

[github-actions]

Build action triggered: https://github.com/flatcar/scripts/actions/runs/15977552362