More object store documentation. #15707
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link out to relevant training materials for older documentation and add some documentation for User Selectable Storage (#14073).
The object store sample now includes two smaller use cases around User Selectable Storage - namely details about how to setup scratch storage and how to setup an experimental storage selection (e.g. iRODS). This includes object store tags I would use to communicate this data to the user, a discussion of cleaning up short term storage, and description of private storage and having different storage options using separate quotas.
I've also dumped in the big MSI-based example from #14073 because it demonstrates a bigger example with more factors and richer descriptions.
If anyone, especially admin-focused folx, found #14073 too sprawling to review these examples give admins something small to digest and give indications about how servers will need to be updated to leverage this new functionality.
How to test the changes?
(Select all options that apply)
License