From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] ceph: fix two broken lists
Date: Tue, 19 Nov 2024 11:12:25 +0100 [thread overview]
Message-ID: <20241119101225.35659-1-f.weber@proxmox.com> (raw)
The two lists were missing the initial empty line and were
consequently rendered as inline text, which made them hard to read.
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
---
pveceph.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/pveceph.adoc b/pveceph.adoc
index a828834..da39e7f 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -97,6 +97,7 @@ You should test your setup and monitor health and performance continuously.
.CPU
Ceph services can be classified into two categories:
+
* Intensive CPU usage, benefiting from high CPU base frequencies and multiple
cores. Members of that category are:
** Object Storage Daemon (OSD) services
@@ -161,6 +162,7 @@ performance potential of the underlying disks.
If unsure, we recommend using three (physical) separate networks for
high-performance setups:
+
* one very high bandwidth (25+ Gbps) network for Ceph (internal) cluster
traffic.
* one high bandwidth (10+ Gpbs) network for Ceph (public) traffic between the
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-11-19 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 10:12 Friedrich Weber [this message]
2024-11-19 11:06 ` [pve-devel] applied: " Thomas Lamprecht
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=20241119101225.35659-1-f.weber@proxmox.com \
--to=f.weber@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