Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc/cephfs: edit front matter in client-auth.rst #57119

Merged
merged 1 commit into from
Apr 29, 2024
Merged

doc/cephfs: edit front matter in client-auth.rst #57119

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 7 additions & 7 deletions doc/cephfs/client-auth.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,15 @@
CephFS Client Capabilities
================================

Use Ceph authentication capabilities to restrict your file system clients
to the lowest possible level of authority needed.
Ceph authentication capabilities are used to restrict CephFS clients to
the lowest level of authority necessary.

.. note:: Path restriction and layout modification restriction are new features
in the Jewel release of Ceph.
.. note:: Path restriction and layout-modification restriction were introduced
in the Jewel release of Ceph.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we don’t care about Infernalis and earlier? Remove?

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 on the fence about removing stuff like this.

The case for removing information about when features were introduced: this is a technical manual, meant to explain how to use Ceph. This is not a historical record of the development of Ceph.

The case against removing information about when features were introduced: It's nice to know when features were introduced, and gives a sense of Ceph as an ongoing concern that responds to the world in which it serves the ends of its users and developers.


.. note:: Using Erasure Coded(EC) pools with CephFS is supported only with the
BlueStore Backend. They cannot be used as metadata pools and overwrites must
be enabled on the data pools.
.. note:: Using Erasure Coded (EC) pools with CephFS is supported only with
:term:`BlueStore`. Erasure-coded pools cannot be used as metadata pools.
Overwrites must be enabled on erasure-coded data pools.


Path restriction
Expand Down