From: Alwin Antreich via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Alwin Antreich <alwin@antreich.com>
Subject: [pve-devel] [PATCH docs v2 2/3] pveceph: add section about ceph configuration
Date: Wed, 29 Oct 2025 10:18:10 +0100 [thread overview]
Message-ID: <mailman.366.1761730050.362.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20251029091811.2800592-1-alwin@antreich.com>
[-- Attachment #1: Type: message/rfc822, Size: 5269 bytes --]
From: Alwin Antreich <alwin@antreich.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs v2 2/3] pveceph: add section about ceph configuration
Date: Wed, 29 Oct 2025 10:18:10 +0100
Message-ID: <20251029091811.2800592-2-alwin@antreich.com>
to illustrate how to change the configuration in the MON DB.
Signed-off-by: Alwin Antreich <alwin@antreich.com>
---
pveceph.adoc | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/pveceph.adoc b/pveceph.adoc
index 1ed6666..cefecad 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -567,6 +567,36 @@ The CLI command to destroy the OSD is:
pveceph osd destroy <id> [--cleanup]
----
+[[pve_ceph_configuration]]
+Ceph Configuration
+------------------
+
+Ceph daemon and clients pull their configuration from one or more sources
+footnote:[Ceph config sources https://docs.ceph.com/en/latest/rados/configuration/ceph-conf/#config-sources].
+In {PVE}, a minimal ceph.conf file is used to hold bootstrap settings. Most of
+the configuration is held in the central configuration database maintained by
+the MON services.
+
+To persistently change configuration values use the bellow commands
+footnote:[Ceph MON DB commands https://docs.ceph.com/en/latest/rados/configuration/ceph-conf/#commands]:
+
+[frame="none",grid="none", align="left", cols="30%,70%"]
+|===
+|ceph config dump|Show all configuration option(s)
+|ceph config get <who> <name>|Show configuration option(s) for an entity
+|ceph config set <who> <name> <value>|Set a configuration option for one or more entities
+|ceph config rm <who> <name>| Clear a configuration option for one or more entities
+|===
+
+.Example for increasing the osd_memory_target for all OSD daemons
+[source,bash]
+----
+ceph config set osd osd_memory_target 8G
+----
+
+NOTE: If an option exists in a local configuration file, the configuration in
+the MON DB will be ignored because it has a lower precedence.
+
[[pve_ceph_pools]]
Ceph Pools
--
2.39.5
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next parent reply other threads:[~2025-10-29 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251029091811.2800592-1-alwin@antreich.com>
2025-10-29 9:18 ` Alwin Antreich via pve-devel [this message]
2025-10-30 13:29 ` Aaron Lauterer
2025-10-29 9:18 ` [pve-devel] [PATCH docs v2 3/3] pveceph: link ceph configure section Alwin Antreich via pve-devel
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=mailman.366.1761730050.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alwin@antreich.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