public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Friedrich Weber <f.weber@proxmox.com>
Subject: Re: [pve-devel] [PATCH ceph master 3/3] buildsys: add check for changed ceph-osd sysctl settings
Date: Thu, 15 Feb 2024 14:20:21 +0100	[thread overview]
Message-ID: <c276a72b-84ff-4616-a110-8724e01fff2c@proxmox.com> (raw)
In-Reply-To: <20240215094056.66233-4-f.weber@proxmox.com>

Am 15/02/2024 um 10:40 schrieb Friedrich Weber:
> If the ceph-osd sysctl settings template (30-ceph-osd.conf.in) shipped
> by upstream changes, our ceph-osd postinst patch will need to be
> adapted to apply the new settings on package upgrade. To make sure we
> do not forget, store the current checksum of that file in our Makefile
> and fail the build early if the checksums do not match.
> 
> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
> ---
> 
> Notes:
>     - failing the build might be a bit drastic, but a simple warning seems
>       too easy to overlook
>     - strictly speaking we'll miss updates of `sysctl_pid_max` [1], but to
>       catch this, we'd need to check the generated 30-ceph-osd.conf
>       (without .in) after it is generated during the build process, and
>       failing then sounds may be too annoying :)
>     
>     [1] https://github.com/ceph/ceph/blob/main/etc/sysctl/90-ceph-osd.conf.in
> 

noticing is one thing, but then having an actual plan what to do is something
else, as most options would again have the possibility to override existing
sysctls. IMO just installing the new file is fine too, and judging from the
past this file won't see that much churn, especially during stable point
releases, so omitting this one for now, maybe checking out the bigger picture
(see reply to patch 1/3) leads to some improvements that make it really
obsolete anyway.




      reply	other threads:[~2024-02-15 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15  9:40 [pve-devel] [PATCH ceph master+quincy-stable-8 0/3] fix #5213: avoid connection freezes when installing/upgrading ceph-osd Friedrich Weber
2024-02-15  9:40 ` [pve-devel] [PATCH ceph master 1/3] fix #5213: ceph-osd postinst: add patch to avoid connection freezes Friedrich Weber
2024-02-15 13:16   ` [pve-devel] applied: " Thomas Lamprecht
2024-02-16 13:54     ` Friedrich Weber
2024-02-15  9:40 ` [pve-devel] [PATCH ceph quincy-stable-8 2/3] " Friedrich Weber
2024-02-15 13:17   ` [pve-devel] applied: " Thomas Lamprecht
2024-02-15  9:40 ` [pve-devel] [PATCH ceph master 3/3] buildsys: add check for changed ceph-osd sysctl settings Friedrich Weber
2024-02-15 13:20   ` Thomas Lamprecht [this message]

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=c276a72b-84ff-4616-a110-8724e01fff2c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.weber@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal