doc/rados: edit filestore-config-ref.rst #51745
Conversation
Edit doc/rados/configuration/filestore-config-ref.rst. https://tracker.ceph.com/issues/58485 Signed-off-by: Zac Dover <zac.dover@proton.me>
| .. note:: Since the Luminous release of Ceph, Filestore has not been Ceph's | ||
| default storage back end. Since the Luminous release of Ceph, BlueStore has | ||
| been Ceph's default storage back end. However, Filestore OSDs are still | ||
| supported. See :ref:`OSD Back Ends |
There was a problem hiding this comment.
@anthonyeleven: This PR is one is a series that I have labeled "FileStore deprecation". A future pull request (like, a near-future pull request, probably next week if not tomorrow) will hit every place in the documentation suite and communicate the idea that it's time to redeploy OSDs.
There was a problem hiding this comment.
Would that be soon enough that Reef won't release claiming that Filestore is still supported? To be clear, I'm saying that the ONLY thing to be left in this file for Reef and main should be an admonition to redeploy OSDs before upgrading.
There was a problem hiding this comment.
Would that be soon enough that Reef won't release claiming that Filestore is still supported? To be clear, I'm saying that the ONLY thing to be left in this file for Reef and main should be an admonition to redeploy OSDs before upgrading.
Yes, it will be soon enough that Reef will release with documentation that informs readers that Filestore is not supported at all in Reef.
Here's what's going on here: this is (probably) the final commit affecting this file before I have to start keeping two sets of books for (at least) the RADOS docs. One set of future books will be a Reef-(inclusive)-and-future-releases set that mentions Filestore only to warn people away from it and to let them know that Filestore is defunct, and the other set of future books is a Quincy-and-back-in-time-to-possibly-as-far-back-as-Luminous set that still presents Filestore as a supported storage back end. This commit gets the text into good-enough-by-the-standards-of-English grammar shape that I won't have to edit the extant English in both branches of the bifurcation that is about to occur.
There is a similar do-this-here-and-do-that-there issue vis-à-vis cache tiering. Step one: kill as many doubleton birds with one stone as possible. Step two: contend with the surviving singletons.
| performance. To implement such an extrinsic method, refer to the following | ||
| settings. | ||
|
|
||
| If the underlying file system has no size limit, then Ceph XATTRs are stored as |
There was a problem hiding this comment.
I think we can remove this whole section. If not, I think only EXT4 has the XATTRs issue.
There was a problem hiding this comment.
@neha-ojha @jdurgin: What say you?
Edit doc/rados/configuration/filestore-config-ref.rst.
https://tracker.ceph.com/issues/58485
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