[pve-devel] [PATCH docs] Fix #2015: Improve CephFS docs

[Thomas Lamprecht]

a bit more meaningful title is always nice: 

partially-fix #2015: cephfs: document how a ceph auth key 

On 12/7/18 9:49 AM, Alwin Antreich wrote:
> Signed-off-by: Alwin Antreich <a.antreich at proxmox.com>
> ---
> This does not address the package update yet.
> 
>  pve-storage-cephfs.adoc | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/pve-storage-cephfs.adoc b/pve-storage-cephfs.adoc
> index b7f3f4d..5111ad1 100644
> --- a/pve-storage-cephfs.adoc
> +++ b/pve-storage-cephfs.adoc
> @@ -78,6 +78,13 @@ secret generally requires root privileges. The file must only contain the
>  secret key itself, opposed to the `rbd` backend which also contains a
>  `[client.userid]` section.
>  
> +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 managment see the Ceph docs
> +footnote:[Ceph user management http://docs.ceph.com/docs/luminous/rados/operations/user-management/].
> +
> + ceph auth get-key client.userid > /etc/ceph/cephfs.secret

Sorry if I overlook something, but why do you pipe it to /etc/ceph/cephfs.secret ??

Would it not make more sense to advise something like:

root at cephServer# ceph auth get-key client.USERID > USERID.secret
root at cephServer# scp USERID.secret PVE-HOST:/etc/pve/priv/ceph/SID.secret

As this is what's actually needed?

> +
>  If Ceph is installed locally on the PVE cluster, i.e., setup with `pveceph`,
>  this is done automatically.
>  
>