From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] fix #4808: ceph: use setting names with underscores
Date: Wed, 6 Sep 2023 16:57:32 +0200 [thread overview]
Message-ID: <75631e85-0440-46c7-a359-ab0d9a80209a@proxmox.com> (raw)
In-Reply-To: <20230905085331.541541-1-m.sandoval@proxmox.com>
Am 05/09/2023 um 10:53 schrieb Maximiliano Sandoval:
> As suggested in [1], it is recommended to use `_` in all cases when
> dealing with config files.
>
> [1] https://docs.ceph.com/en/reef/rados/configuration/ceph-conf/#option-names
The first thing I asked myself was "how is the priority though if both exist?"
Then I had to check the code and saw that this is only affecting
MDS creation, where we enforce that the config section doesn't exist,
so it's OK (but still relevant info, so I added it to the commit
message).
Anyhow, it would be still good to know how ceph handles the situation
where both exist, e.g.:
mds standby for name = foo
mds_standby_for_name = bar
# what about mixing them?
mds_standy for name
Also, did you checked for other such occurrences in our API?
Manually tracing all call sites where cfs_write_file('ceph.conf', ..) is
called should allow you to find most potential call sites using
the undesired style.
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> PVE/API2/Ceph/MDS.pm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
applied, thanks!
next prev parent reply other threads:[~2023-09-06 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 8:53 [pve-devel] " Maximiliano Sandoval
2023-09-06 14:57 ` Thomas Lamprecht [this message]
2023-09-07 9:07 ` [pve-devel] applied: " Maximiliano Sandoval
2023-09-07 9:30 ` Maximiliano Sandoval
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=75631e85-0440-46c7-a359-ab0d9a80209a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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