public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev, ross@kallisti.us
Cc: mcgrof@kernel.org
Subject: [PATCH kdevops 0/4] kdevops: make trixie default
Date: Thu, 10 Oct 2024 18:01:07 -0700	[thread overview]
Message-ID: <20241011010111.3543993-1-mcgrof@kernel.org> (raw)

Debian lacks its own directory index which can be used for guestfs. They
should add one, though as support in kdevops shows, only a few minor things
are needed, and since kdevops has figured out what those things are, it should
be easy to use virt-builder on the backend on daily debian images for any
release but in particular for debian 13 (trixie) which kdevops cares about
a lot since we use it heavily for automated tests.

I recently noted also that as we're ramping up kdevops kernel-CI integration
with Meta's kernel-patch-daemon [0] for patchwork, we *want* to really get
a squeeky clean experience for using debian testing. Development on that
front has shown github likes to pretend that Ubuntu is the center of
the Linux testing universe and because that it makes using github actions using
github runners simply useless for kernel hacking [1]. To this end we need to
start drawing up security policies to allow us to use and leverage any Linux
distribution a developer prefers to use, for us to leverage a secure way to use
self-hosted runners.

To reduce bringup make debian trixie the default. This should reduce many
bringup times. Although debian trixie hasn't been default for a while, many
systems we've been testing for XFS testing / sysbench have been leveraging
debian 13 with an upgrade when CONFIG_GUESTFS_COPY_SOURCES_FROM_HOST_TO_GUEST
is enabled (debian host on trixie, /etc/apt/sources.list detected to be a local
mirror, and guest is debian 12), and so in practice we've already have been
testing trixie for a while now.

This just makes bringup faster.

But debian maintainers:  could we please see if perhaps debian can leverage our
findings to host official debian guestfs virt-builder images? kdevops shows
what's needed to be done using existing images.

[0] https://github.com/facebookincubator/kernel-patches-daemon
[1] https://lore.kernel.org/kdevops/CAB=NE6VKWSkv1JZ_Z2LKq4o7+JBkKc6u8Wa1zxxBnGHOG4BgjA@mail.gmail.com/T/#u

Luis Chamberlain (4):
  guestfs: make trixie generic image the default
  guestfs: fix uefi boot for debian trixie
  guestfs: fix trixie bringup
  guestfs: make debian trixie default

 kconfigs/Kconfig.guestfs                      | 16 +++++++++---
 .../gen_nodes/templates/guestfs_q35.j2.xml    |  2 +-
 scripts/bringup_guestfs.sh                    | 25 +++++++++++++++++++
 workflows/linux/Kconfig                       |  2 +-
 4 files changed, 40 insertions(+), 5 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-10-11  1:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  1:01 Luis Chamberlain [this message]
2024-10-11  1:01 ` [PATCH kdevops 1/4] guestfs: make trixie generic image the default Luis Chamberlain
2024-10-11  1:01 ` [PATCH kdevops 2/4] guestfs: fix uefi boot for debian trixie Luis Chamberlain
2024-10-11  1:01 ` [PATCH kdevops 3/4] guestfs: fix trixie bringup Luis Chamberlain
2024-10-11  1:01 ` [PATCH kdevops 4/4] guestfs: make debian trixie default Luis Chamberlain
2024-10-11 19:00 ` [PATCH kdevops 0/4] kdevops: make " Luis Chamberlain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241011010111.3543993-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=kdevops@lists.linux.dev \
    --cc=ross@kallisti.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox