[pve-devel] [PATCH docs v2 2/3] pveceph: add section about ceph configuration

[pve-devel] [PATCH docs v2 2/3] pveceph: add section about ceph configuration

[Alwin Antreich via pve-devel]

[-- 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

[pve-devel] [PATCH docs v2 3/3] pveceph: link ceph configure section

[Alwin Antreich via pve-devel]

[-- Attachment #1: Type: message/rfc822, Size: 4546 bytes --]

From: Alwin Antreich <alwin@antreich.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs v2 3/3] pveceph: link ceph configure section
Date: Wed, 29 Oct 2025 10:18:11 +0100
Message-ID: <20251029091811.2800592-3-alwin@antreich.com>

to follow how ceph configuration is adjusted

Signed-off-by: Alwin Antreich <alwin@antreich.com>
---
 pveceph.adoc | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/pveceph.adoc b/pveceph.adoc
index cefecad..0d6e9ec 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -136,8 +136,9 @@ during critical operations, such as recovery, rebalancing, or backfilling. That
 means you should avoid maxing out your available memory already on regular
 operation, but rather leave some headroom to cope with outages.
 
-The current recommendation is to configure OSDs with at least **8 GiB of
-memory** for good performance. The OSD daemon requires 4 GiB by default.
+The current recommendation is to xref:pve_ceph_configuration[configure] OSDs
+with at least **8 GiB of memory** for good performance. The OSD daemon requires
+4 GiB by default.
 
 NOTE: Total memory consumption is primarily determined by the number of OSD
 daemons. However, for critical operations, all Ceph services may require
-- 
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