From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-kernel-meta/proxmox-ve v3] proxmox-boot: add kernel pinning functionality (#3761)
Date: Wed, 16 Feb 2022 12:29:07 +0100 [thread overview]
Message-ID: <1645010894.tkxg0q0yro.astroid@nora.none> (raw)
In-Reply-To: <20220211151547.181259-1-s.ivanov@proxmox.com>
On February 11, 2022 4:15 pm, Stoiko Ivanov wrote:
> changes v2->v3:
> * incoroporated Fabian's and Thomas' feedback - huge thanks:
> ** changed `p-b-t kernel next-boot <ver>` to `p-b-t kernel pin <ver> --next-boot`
> ** improved usage output
> ** style-fixes to proxmox-ve apt-hook
> ** 'untaint' the fd fetched from the environment in proxmox-ve apt-hook
> * fixed a glitch in the non p-b-t booted case (next-boot pin followed by a
> permanent pin cause the next-boot to be ignored)
> * output of `p-b-t kernel list` now only prints pinned versions if they are set
>
> original cover-letter for v2:
> changes v1->v2:
> * incorporated the feedback on the v1 (by Aaron and Fabian - huge thx!):
> ** a next-boot pin is now handled independently from a pin - i.e. if you
> both pin a kernel and set one for the next-boot - the system afterwards
> keeps the pinned version (instead of the latest)
> ** change from modifying /etc/default/grub to creating a snippet in
> /etc/default/grub.d/proxmox-boot-pin.cfg - I did not see a need for having
> two pinning files there (since they get written both at each relevant
> invocation anyways - thus also no need for prefixing with y_ and z_
> ** the semantics of unpin changed (it now takes an optional argument to
> remove the next-boot-pin only (made the cleanup-service cleaner)
> ** added a check to the apthook in proxmox-ve as Fabian suggested
> * changed the semantics of get_first_line - to check for file existence
> itself, since it makes using it shorter at almost all call-sites
> * fixed two perlcritic warnings in the pve apthook (which is quite
> independent of the series)
>
> again tested on 3 VMs (ext4, zfs+uefi, zfs+legacy) - but would be grateful
> if you find some use-case apart from - pin permanent, pin next-boot, reboot,
> reboot.
for the whole series:
Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
Tested-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
not applying for now in case we want to roll this out together with the
final version of the other series.
>
>
> original cover letter of v1:
> The following series adds:
> * proxmox-boot-tool kernel pin <kabi-version> (to permanently set the
> default entry of the respective bootloader)
> * proxmox-boot-tool kernel unpin (to undo a previous pin)
> * proxmox-boot-tool kernel next-boot (to do a pin+touch a file, which causes
> an unpin on next boot)
>
> This is the first functionality which is available for 'regular grub-setups'
> (i.e. systems setup with lvm-thin with our ISO or systems installed on top
> of plain debian) as well.
>
> The first two patches are cleanup+refactoring (and should not change any
> functionality)
>
> The choices (those I think might benefit from a bit of feedback) for this
> implementation were:
> * for grub - automaticially rewrite '/etc/default/grub' (as this is where
> I'd look to check whether some default is set)
> * for systemd - set the entry in the loader.conf and not in the efivars
> (`bootctl set-default/set-once`) - mostly from my bias towards config
> files instead of UEFI vars (depending on implementation quality of the
> UEFI) - another reason was to keep the implementation close for both
> boot-loaders
> * for p-b-t booted systems the need to run `p-b-t refresh` manually
> afterwards (following the behavior of `p-b-t kernel add/remove`) could
> be changed to invoking the refresh directly (as with non-p-b-t booted
> systems). Especially since it might make sense to 'add' multiple kernels
> and then do the mount+copy+configupdate only once, whereas you can only
> pin on version anyways
>
> Tested on three VMs installed from the 7.1 ISO (UEFI+ZFS, legacy+ZFS,
> UEFI+lvm-thin).
>
> pve-kernel-meta:
> Stoiko Ivanov (4):
> proxmox-boot: return empty if file does not exist in get_first_line
> proxmox-boot: fix #3671 add pin/unpin for kernel-version
> proxmox-boot: add --next-boot option kernel pin command
> proxmox-boot: add pin/unpin functionality for non-p-b-t systems
>
> bin/proxmox-boot-tool | 97 +++++++++++++++++++++++
> debian/pve-kernel-helper.install | 1 +
> debian/rules | 3 +
> proxmox-boot/Makefile | 4 +
> proxmox-boot/functions | 45 +++++++++++
> proxmox-boot/proxmox-boot-cleanup.service | 13 +++
> proxmox-boot/zz-proxmox-boot | 8 ++
> 7 files changed, 171 insertions(+)
> create mode 100644 proxmox-boot/proxmox-boot-cleanup.service
>
> proxmox-ve:
> Stoiko Ivanov (3):
> apt-hook: fix perlcritic warnings
> apt-hook: verify that fd is numeric
> apt-hook: add check preventing the removal of pinned kernels
>
> debian/apthook/pve-apt-hook | 36 +++++++++++++++++++++++++++++++++---
> 1 file changed, 33 insertions(+), 3 deletions(-)
>
> --
> 2.30.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
next prev parent reply other threads:[~2022-02-16 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 15:15 Stoiko Ivanov
2022-02-11 15:15 ` [pve-devel] [PATCH pve-kernel-meta v3 1/4] proxmox-boot: return empty if file does not exist in get_first_line Stoiko Ivanov
2022-02-11 15:15 ` [pve-devel] [PATCH pve-kernel-meta v3 2/4] proxmox-boot: fix #3671 add pin/unpin for kernel-version Stoiko Ivanov
2022-02-16 12:14 ` Oguz Bektas
2022-02-11 15:15 ` [pve-devel] [PATCH pve-kernel-meta v3 3/4] proxmox-boot: add --next-boot option kernel pin command Stoiko Ivanov
2022-02-11 15:15 ` [pve-devel] [PATCH pve-kernel-meta v3 4/4] proxmox-boot: add pin/unpin functionality for non-p-b-t systems Stoiko Ivanov
2022-02-11 15:15 ` [pve-devel] [PATCH proxmox-ve v3 1/3] apt-hook: fix perlcritic warnings Stoiko Ivanov
2022-02-11 15:15 ` [pve-devel] [PATCH proxmox-ve v3 2/3] apt-hook: verify that fd is numeric Stoiko Ivanov
2022-02-11 15:15 ` [pve-devel] [PATCH proxmox-ve v3 3/3] apt-hook: add check preventing the removal of pinned kernels Stoiko Ivanov
2022-02-16 11:29 ` Fabian Grünbichler [this message]
2022-03-04 10:18 ` [pve-devel] applied-series: Re: [PATCH pve-kernel-meta/proxmox-ve v3] proxmox-boot: add kernel pinning functionality (#3761) Thomas Lamprecht
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=1645010894.tkxg0q0yro.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.