public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alwin Antreich <a.antreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] update docs link for cephfs
Date: Thu, 24 Sep 2020 09:27:09 +0200	[thread overview]
Message-ID: <20200924072710.2195707-1-a.antreich@proxmox.com> (raw)

* use codname instead of hardcoded release name
* ceph migrated to readthedocs with a minor uri change
https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/AQZJG75IST7HFDW7OB5MNCITQOVAAUR4/

Signed-off-by: Alwin Antreich <a.antreich@proxmox.com>
---
 pve-storage-cephfs.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pve-storage-cephfs.adoc b/pve-storage-cephfs.adoc
index 45933f0..a942709 100644
--- a/pve-storage-cephfs.adoc
+++ b/pve-storage-cephfs.adoc
@@ -90,7 +90,7 @@ secret key itself, opposed to the `rbd` backend which also contains a
 A secret can be received from the ceph cluster (as ceph admin) by issuing the
 following command. Replace the `userid` with the actual client ID configured to
 access the cluster. For further ceph user management see the Ceph docs
-footnote:[Ceph user management http://docs.ceph.com/docs/luminous/rados/operations/user-management/].
+footnote:[Ceph user management http://docs.ceph.com/en/{ceph_codename}/rados/operations/user-management/].
 
  ceph auth get-key client.userid > cephfs.secret
 
-- 
2.27.0





             reply	other threads:[~2020-09-24  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  7:27 Alwin Antreich [this message]
2020-09-24  7:27 ` [pve-devel] [PATCH docs 2/2] update links to docs.ceph.com Alwin Antreich
2020-09-25  7:14   ` 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=20200924072710.2195707-1-a.antreich@proxmox.com \
    --to=a.antreich@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