public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 2/4] pve-storage-cephfs: describe CephFS, not RBD, in external cluster setup
Date: Sat, 11 Apr 2026 20:50:34 +0800	[thread overview]
Message-ID: <20260411125036.778122-3-k.chai@proxmox.com> (raw)
In-Reply-To: <20260411125036.778122-1-k.chai@proxmox.com>

The "external Ceph cluster" section of the CephFS chapter describes
configuring "external RBD storage" in both the CLI and the GUI
walk-throughs. Refer to CephFS there instead - this was likely a
copy-paste leftover from the RBD chapter.

Signed-off-by: Kefu Chai <k.chai@proxmox.com>
---
 pve-storage-cephfs.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/pve-storage-cephfs.adoc b/pve-storage-cephfs.adoc
index 8d36246..ab8d850 100644
--- a/pve-storage-cephfs.adoc
+++ b/pve-storage-cephfs.adoc
@@ -91,16 +91,16 @@ copy it to the `/root` directory of the node on which we run it:
 # scp <external cephserver>:/etc/ceph/cephfs.secret /root/cephfs.secret
 ----
 
-Then use the `pvesm` CLI tool to configure the external RBD storage, use the
-`--keyring` parameter, which needs to be a path to the secret file that you
-copied.  For example:
+Then use the `pvesm` CLI tool to configure the external CephFS storage, use
+the `--keyring` parameter, which needs to be a path to the secret file that
+you copied.  For example:
 
 ----
 # pvesm add cephfs <name> --monhost "10.1.1.20 10.1.1.21 10.1.1.22" --content backup --keyring /root/cephfs.secret
 ----
 
-When configuring an external RBD storage via the GUI, you can copy and paste
-the secret into the appropriate field.
+When configuring an external CephFS storage via the GUI, you can copy and
+paste the secret into the appropriate field.
 
 The secret is only the key itself, as opposed to the `rbd` backend which also
 contains a `[client.userid]` section.
-- 
2.47.3





  parent reply	other threads:[~2026-04-11 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11 12:50 [PATCH docs 0/4] ceph: audit of Ceph-related chapters Kefu Chai
2026-04-11 12:50 ` [PATCH docs 1/4] pveceph: fix Ceph Manager abbreviation Kefu Chai
2026-04-11 12:50 ` Kefu Chai [this message]
2026-04-11 12:50 ` [PATCH docs 3/4] pveceph: various small language fixes Kefu Chai
2026-04-11 12:50 ` [PATCH docs 4/4] docs: various small grammar fixes Kefu Chai

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=20260411125036.778122-3-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal