> Our next team meeting is scheduled for Wed Dec 10 @ 18:00 UTC. We'll be
> on jitsi, https://jitsi.debian.social/DebianCloudMeeting20251210
This meeting happened as scheduled. Here are my notes:
Attendees: waldi, noahm
Topics:
## mkosi ##
Noah raised the possibility of using mkosi as a replacement for FAI as
the cloud image build tool and described the early results of a
proof-of-concept port of the current image build configuration to it.
The following discussion raised several concerns that need to be
addressed for further consideration, including:
1. Mkosi feels too high-level. Does it provide fine-grained enough
control over the image content to satisfy the needs of a canonical
diѕtribution provided images?
2. Can it build images for all supported architectures? (riscv and
ppc64el bootloader installation are particular concerns)
3. By default, systemd-repart doesn't generate the same filesystem
layout as debian-installer, in particular with regard to /boot and
/boot/efi mountpoints. We would need to address this.
See the following for additional details:
https://salsa.debian.org/cloud-team/debian-cloud-images/-/issues/53
https://salsa.debian.org/noahm/debian-cloud-images/-/commits/mkosi
https://github.com/systemd/mkosi/
## Cloud resources for DSA ##
no updates
## bullseye-backports listing in the Azure Marketplace ##
The bullseye-backports marketplace listing continues to be an issue.
Last month we discussed moving the arm64 images to a different plan (an
Azure Marketplace concept) in order to cope with new restrictions on the
Azure side. We did that, but it turns out to be insufficient, as the
existing plan still expects new arm64 images to be added along when we
publish new releases, and there's no way to modify the plan to remove
arm64. So the remaining options are:
1. Move deprecate the existing plan and create a new amd64 specific
plan to go along with the arm64 plan, or
2. Deprecate the bullseye-backports plan altogether.
Noah will follow up and implement one of these options.
## buster image issues ##
The Azure Marketplace has recently been complaining of outstanding
security isues in the buster images. As these images are EOL from
Debian's perspective, waldi marked them as deprecated in the
Marketplace. This will trigger notifications to users of the images and
will make them unavailable after 180 days.
Noah pointed out that the AWS marketplace configuration should be
checked to ensure that it's consistent with the deprecation in the Azure
marketplace, and will follow up to make sure it is.
## upcoming kernel changes ##
There was a brief discussion of proposed kernel changes that would
impact the cloud images for forky. The plan would eliminate the cloud
variant of the kernel binary packages and would split the main package
into a base kernel image package (maybe with some core modules) and one
or more "extra modules" packages.
