This marks version 02 of the patch series "Fix #4759: Configure
Permissions for ceph-crash.service" [0].
Each patch also lists which changes have been made between versions.
Other changes not otherwise mentioned in patches:
v1 --> v2:
* drop patch regarding POSIX compatibility in debian/po
This patch makes it so that `ceph-crash` attempts to use the
non-host-specific keyring before anything else, which avoids
unnecessary error messages landing in the systemd-journal in our case.
Signed-off-by: Max Carrara
---
Changes v1 --> v2:
* new
...h-crash-change-order-of-client-names.patc
Ceph has a postinst hook that sets the ownership of '/var/lib/ceph/*'
to ceph:ceph (in our case), but misses out on '/var/lib/ceph/crash/posted'.
This patch therefore also updates the permissions of '/var/lib/ceph/*/*'.
Signed-off-by: Max Carrara
---
Changes v1 --> v2:
* use `find` instead of
Ceph has a postinst hook that sets the ownership of '/var/lib/ceph/*'
to ceph:ceph (in our case), but misses out on '/var/lib/ceph/crash/posted'.
This patch therefore also updates the permissions of '/var/lib/ceph/*/*'.
Signed-off-by: Max Carrara
---
Changes v1 --> v2:
* use `find` instead of
when creating the cluster's first monitor.
Signed-off-by: Max Carrara
---
Changes v1 --> v2:
* do not enable/restart `ceph-crash` anymore when creating first mon
* drop changes to function `ceph_service_cmd` as they are no longer
needed
* create keyring for `ceph-crash` before modifying
This commit adds the `set_ceph_crash_conf` function, which dynamically
adapts the host's Ceph configuration in order to allow the Ceph crash
module's daemon to run without elevated privileges.
This adaptation is only performed if:
* Ceph is installed
* Ceph is configured ('/etc/pve/ceph.conf' ex
This adds support for writing arbitrary sections to 'ceph.conf' while
ensuring that already written sections are not duplicated.
Sections that are associated with the client, for example
'[client.foo]', are written directly after the '[client]' section.
Signed-off-by: Max Carrara
---
Changes v1
Signed-off-by: Max Carrara
---
Changes v1 --> v2:
* none
PVE/API2/Ceph.pm | 5 +
1 file changed, 5 insertions(+)
diff --git a/PVE/API2/Ceph.pm b/PVE/API2/Ceph.pm
index 81c17d6e..7fedb87a 100644
--- a/PVE/API2/Ceph.pm
+++ b/PVE/API2/Ceph.pm
@@ -192,6 +192,11 @@ __PACKAGE__->register_method
Having a file named e.g. "60" in your current directory will cause it
to be deleted when executing `pveceph purge`. This commit fixes that
by making the config hash differ between which values represent file
paths and which don't.
Signed-off-by: Max Carrara
---
Changes v1 --> v2:as
* use two ha
1. Comments, irrespective of whether they start with '#' or ';' are
now treated the same. Otherwise, sections and key-value pairs with
a trailing comment starting with ';' are still parsed. Consider
this example:
[some.section] # inline comment after section
foo = bar ; in
This patch makes it so that `ceph-crash` attempts to use the
non-host-specific keyring before anything else, which avoids
unnecessary error messages landing in the systemd-journal in our case.
Signed-off-by: Max Carrara
---
Changes v1 --> v2:
* new
...h-crash-change-order-of-client-names.patc
cephconfig: allow writing arbitrary sections
This adds support for writing arbitrary sections to 'ceph.conf' while
ensuring that already written sections are not duplicated.
Sections that are associated with the client, for example
'[client.foo]', are written directly after the '[client]' section
The call to next now does not return an Option, but rahter contains a
dedicated Unknown variant. Therefore the unwrap call can be avoided and
the panic to calls to `pveversion` when /etc/os-release contained
`VERSION_CODENAME=trixie` can be avoided.
Reported in the community forum:
https://forum.p
Am 12.12.23 um 14:42 schrieb Fiona Ebner:
> In many configurations, e.g. multiple vNICs with multiple queues or
> with many Ceph OSDs, the default soft limit of 1024 is not enough.
> QEMU is supposed to work fine with file descriptors >= 1024 and does
> not use select() on POSIX. Bump the soft limi
In many configurations, e.g. multiple vNICs with multiple queues or
with many Ceph OSDs, the default soft limit of 1024 is not enough.
QEMU is supposed to work fine with file descriptors >= 1024 and does
not use select() on POSIX. Bump the soft limit to the allowed hard
limit to avoid issues with t
Am 05.02.24 um 13:38 schrieb Thomas Lamprecht:
> Am 05/02/2024 um 13:28 schrieb Fiona Ebner:
>> Like this, __WARN__ handlers will still be called. In particular,
>> daemons like pvestatd will set a __WARN__ handler and also log
>> warnings to syslog. The intention behind introducing log_warn() was
Am 05.02.24 um 13:39 schrieb Thomas Lamprecht:
> Am 05/02/2024 um 13:28 schrieb Fiona Ebner:
>> So all warnings will be treated consistently inside a worker task. In
>> particular, all warnings will count towards the task warning count and
>> be more visible in the UI. Avoids the need to switch exi
Am 05/02/2024 um 13:28 schrieb Fiona Ebner:
> So all warnings will be treated consistently inside a worker task. In
> particular, all warnings will count towards the task warning count and
> be more visible in the UI. Avoids the need to switch existing warnings
> to log_warn().
>
> When pvedaemon
Am 05/02/2024 um 13:28 schrieb Fiona Ebner:
> Like this, __WARN__ handlers will still be called. In particular,
> daemons like pvestatd will set a __WARN__ handler and also log
> warnings to syslog. The intention behind introducing log_warn() was to
> make warnings more visible, not less, so fix th
So all warnings will be treated consistently inside a worker task. In
particular, all warnings will count towards the task warning count and
be more visible in the UI. Avoids the need to switch existing warnings
to log_warn().
When pvedaemon forked a worker, the worker would inherit its __WARN__
h
Like this, __WARN__ handlers will still be called. In particular,
daemons like pvestatd will set a __WARN__ handler and also log
warnings to syslog. The intention behind introducing log_warn() was to
make warnings more visible, not less, so fix the semantics to make
sure switching from warn to log_
On 1/31/24 14:17, Fabian Grünbichler wrote:
> On January 30, 2024 7:40 pm, Max Carrara wrote:
>> when creating the cluster's first monitor.
>>
>> Signed-off-by: Max Carrara
>> ---
>> PVE/API2/Ceph/MON.pm | 28 +++-
>> PVE/Ceph/Services.pm | 12 ++--
>> PVE/Ceph/Too
On February 2, 2024 7:23 pm, Thomas Lamprecht wrote:
> Am 26/01/2024 um 13:05 schrieb Fabian Grünbichler:
>> installing it at least gives the admin a heads up if our base Debian release
>> is
>> ever faster shipping a newer version of shim or Grub, which would look
>> (something) like this:
>>
>>
Am 02.02.24 um 19:42 schrieb Thomas Lamprecht:
>
> basically applied this, thanks.
>
> Basically, as I went for the v2 [0], as the series file needed some adaption
> due to recent v8.1.5 patch I just made a new commit but kept your message and
> added an Originally-by Trailer, hope that's all ri
Hi,
Here a summary of the weekend.
First, thanks to you guys to be there, it was great to finally meet you
!
users were pretty happy to see finally a proxmox stand at fosdem
- we have seen a llooo of people on the stand with questions. (I
have 10min break on the full weekend).
We alwa
25 matches
Mail list logo
