From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [RFC] letting Ceph read its own config as the ceph user
Date: Wed, 14 Oct 2026 18:54:48 +0800 [thread overview]
Message-ID: <20261014105448.2660976-1-k.chai@proxmox.com> (raw)
In-Reply-To: <20261013092516.1596661-1-k.chai@proxmox.com>
Hi all,
Maximiliano kindly went through the ceph.conf part with me off-list,
and I'd like to change a few things from the RFC:
- I'd keep the /etc/ceph/ceph.conf symlink after all. Otherwise edits
made through it would stay on one node and get overwritten, and PVE
itself relies on the symlink in a few places (setup_pve_symlinks(),
check_ceph_enabled()).
- The copy would go to a separate path instead, as root:ceph 0440. I
think its directory should be owned by root, since the mon and OSDs
read the config before dropping privileges. That rules out
/var/lib/ceph and /etc/ceph, which are both owned by ceph. pmxcfs's
own /var/lib/pve-cluster would work, so I'll use
/var/lib/pve-cluster/ceph.conf below, but better ideas are welcome.
- The Ceph services could find the copy through a single drop-in in
ceph-.service.d/:
Environment=CEPH_CONF=/var/lib/pve-cluster/ceph.conf,/etc/ceph/ceph.conf
If the copy is missing, Ceph falls back to the symlink. I tried this
with one mgr: after "ceph mgr fail" it came back as ceph and found
the copy, without systemd having to restart it.
- Sorry, the systemd path unit I suggested as a fallback doesn't work.
It only notices changes made on the local node, not the ones coming
from other nodes.
I haven't figured out yet how to make a failed copy visible. Maybe a
log message, or a health check.
The ceph-crash error at boot had two causes in the end, and I sent a
fix for each:
- ceph-crash wasn't ordered after pve-cluster. The pve-manager patch
[1] replaces the per-unit drop-ins with one for all ceph-* units, so
it now covers ceph-crash and a few other units we had missed.
- Its startup ping ran "ceph -s" as client.admin, whose key ceph-crash
can't read. With the Ceph PR [2], it uses the same keys it posts
crashes with.
The rest of the RFC stays the same. Thanks again, Maximiliano, for
your help!
Cheers,
Kefu
[1] https://lore.proxmox.com/pve-devel/20261014104321.2652781-1-k.chai@proxmox.com/T/#u
[2] https://github.com/ceph/ceph/pull/72674
prev parent reply other threads:[~2026-10-14 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:25 [RFC] letting Ceph read its own config as the ceph user Kefu Chai
2026-10-14 10:54 ` Kefu Chai [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=20261014105448.2660976-1-k.chai@proxmox.com \
--to=k.chai@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.