Skip to content

doc/rbd: refine "Create a Block Device User"#49283

Merged
zdover23 merged 1 commit intoceph:mainfrom
zdover23:wip-doc-2022-12-06-rbd-rados-rbd-cmds-create-a-block-device-user-semantics
Dec 7, 2022
Merged

doc/rbd: refine "Create a Block Device User"#49283
zdover23 merged 1 commit intoceph:mainfrom
zdover23:wip-doc-2022-12-06-rbd-rados-rbd-cmds-create-a-block-device-user-semantics

Conversation

@zdover23
Copy link
Contributor

@zdover23 zdover23 commented Dec 6, 2022

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

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands
  • jenkins retest this please
  • jenkins test classic perf
  • jenkins test crimson perf
  • jenkins test signed
  • jenkins test make check
  • jenkins test make check arm64
  • jenkins test submodules
  • jenkins test dashboard
  • jenkins test dashboard cephadm
  • jenkins test api
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox
  • jenkins test windows

@zdover23 zdover23 requested a review from a team December 6, 2022 14:21
@zdover23 zdover23 requested a review from a team as a code owner December 6, 2022 14:21
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 #
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.. prompt:: bash #
.. prompt:: bash $

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we think most people won't be running as root?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I certainly hope so. And even if they will be we shouldn't be encouraging it with #...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

%s/bash #/bash $/g - this change is in now.


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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. This change is in.

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".
Copy link
Contributor

@idryomov idryomov Dec 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of bare "ID", I'd use "user ID" everywhere.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might suggest "Ceph user" instead, I think "user ID" is even more likely to be confused with Linux /etc/passwd-type users.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to go with "Ceph user ID" for now, for minimum ambiguity.

Copy link
Contributor

@anthonyeleven anthonyeleven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

non-blocking suggestions

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".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might suggest "Ceph user" instead, I think "user ID" is even more likely to be confused with Linux /etc/passwd-type users.


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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree

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 #
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we think most people won't be running as root?

@zdover23 zdover23 force-pushed the wip-doc-2022-12-06-rbd-rados-rbd-cmds-create-a-block-device-user-semantics branch 2 times, most recently from 3410e59 to 7bf0e58 Compare December 6, 2022 19:38
@zdover23 zdover23 requested a review from idryomov December 6, 2022 19:40
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>
@zdover23 zdover23 force-pushed the wip-doc-2022-12-06-rbd-rados-rbd-cmds-create-a-block-device-user-semantics branch from 5b9df7b to 51bc438 Compare December 7, 2022 03:58
@zdover23 zdover23 merged commit b460d28 into ceph:main Dec 7, 2022
@zdover23
Copy link
Contributor Author

zdover23 commented Dec 7, 2022

#49300 - Quincy backport
#49301 - Pacific backport

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants