Conversation
doc/rbd/rados-rbd-cmds.rst
Outdated
| OSD caps (capabilities): | ||
|
|
||
| ceph auth get-or-create client.{ID} mon 'profile rbd' osd 'profile {profile name} [pool={pool-name}][, profile ...]' mgr 'profile rbd [pool={pool-name}]' | ||
| .. prompt:: bash # |
There was a problem hiding this comment.
| .. prompt:: bash # | |
| .. prompt:: bash $ |
There was a problem hiding this comment.
Do we think most people won't be running as root?
There was a problem hiding this comment.
I certainly hope so. And even if they will be we shouldn't be encouraging it with #...
There was a problem hiding this comment.
%s/bash #/bash $/g - this change is in now.
doc/rbd/rados-rbd-cmds.rst
Outdated
|
|
||
| To `create a Ceph user`_, with ``ceph`` specify the ``auth get-or-create`` | ||
| command, user name, monitor caps, and OSD caps:: | ||
| To `create a Ceph user`_, use the ``ceph`` command with the ``auth |
There was a problem hiding this comment.
Nit: I'd just say use "ceph auth get-or-create" command, without splitting "ceph" and "auth get-or-create" parts. It's also how this command is referenced below -- when talking about the output.
There was a problem hiding this comment.
You're right. This change is in.
doc/rbd/rados-rbd-cmds.rst
Outdated
| Unless specified, the ``rbd`` command will access the Ceph cluster using the ID | ||
| ``admin``. This ID allows full administrative access to the cluster. It is | ||
| recommended that you utilize a more restricted user wherever possible. | ||
| Unless otherwise specified, the ``rbd`` command uses the ID ``admin`` to access the Ceph cluster. The ``admin`` ID allows full administrative access to the cluster. We recommend that you acess the Ceph cluster with an ID that has fewer permissions than the ``admin`` ID does. We call this non-``admin`` ID a "block device user" or "Ceph user". |
There was a problem hiding this comment.
Instead of bare "ID", I'd use "user ID" everywhere.
There was a problem hiding this comment.
I might suggest "Ceph user" instead, I think "user ID" is even more likely to be confused with Linux /etc/passwd-type users.
There was a problem hiding this comment.
I'm going to go with "Ceph user ID" for now, for minimum ambiguity.
anthonyeleven
left a comment
There was a problem hiding this comment.
non-blocking suggestions
doc/rbd/rados-rbd-cmds.rst
Outdated
| Unless specified, the ``rbd`` command will access the Ceph cluster using the ID | ||
| ``admin``. This ID allows full administrative access to the cluster. It is | ||
| recommended that you utilize a more restricted user wherever possible. | ||
| Unless otherwise specified, the ``rbd`` command uses the ID ``admin`` to access the Ceph cluster. The ``admin`` ID allows full administrative access to the cluster. We recommend that you acess the Ceph cluster with an ID that has fewer permissions than the ``admin`` ID does. We call this non-``admin`` ID a "block device user" or "Ceph user". |
There was a problem hiding this comment.
I might suggest "Ceph user" instead, I think "user ID" is even more likely to be confused with Linux /etc/passwd-type users.
doc/rbd/rados-rbd-cmds.rst
Outdated
|
|
||
| To `create a Ceph user`_, with ``ceph`` specify the ``auth get-or-create`` | ||
| command, user name, monitor caps, and OSD caps:: | ||
| To `create a Ceph user`_, use the ``ceph`` command with the ``auth |
doc/rbd/rados-rbd-cmds.rst
Outdated
| OSD caps (capabilities): | ||
|
|
||
| ceph auth get-or-create client.{ID} mon 'profile rbd' osd 'profile {profile name} [pool={pool-name}][, profile ...]' mgr 'profile rbd [pool={pool-name}]' | ||
| .. prompt:: bash # |
There was a problem hiding this comment.
Do we think most people won't be running as root?
3410e59 to
7bf0e58
Compare
Refine "Create a Block Device User" in doc/rbd/rados-rbd-cmds.rst. https://tracker.ceph.com/issues/57001 Signed-off-by: Zac Dover <zac.dover@gmail.com>
5b9df7b to
51bc438
Compare
Refine "Create a Block Device User" in doc/rbd/rados-rbd-cmds.rst.
https://tracker.ceph.com/issues/57001
Signed-off-by: Zac Dover zac.dover@gmail.com
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows