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.

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

Update RSE attributes documentation. Resolves #399. #403

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

bjwhite-fnal
Copy link
Member

Here's a first draft of trying to document all of the remaining RSE attributes, and tweaks to the existing documentation.
@bari12 @voetberg I'd value your input on a review of this.

@voetberg
Copy link
Contributor

voetberg commented Dec 2, 2024

All really good additions! I think we can add more though. Would it make sense to group attributes by things specific to tape RSEs, and things controlling transfers? Makes it easier to scan through and find exactly what you're looking for.

I think it would also be very useful to have an example or two for maybe ""typical"" use cases (settings you'd want to set for tape rses, things you're change when you're setting up a non-posix rse?) It's annoying for me not to have an operator's knowledge here, but are there a few clusters of RSE-types that exist? Surely there's a decent bit of commonality

@bjwhite-fnal
Copy link
Member Author

@voetberg I think that's a good idea to give a more comprehensive example. However, I think this page should just list every available option.

Maybe we should instead modify this section of the "configuration" page, which is already sort of trying to do that. The given RSE there already wouldn't work for transfers, since it doesn't have an fts (or some other transfer manager) configured.

@voetberg
Copy link
Contributor

voetberg commented Dec 3, 2024

@voetberg I think that's a good idea to give a more comprehensive example. However, I think this page should just list every available option.

Maybe we should instead modify this section of the "configuration" page, which is already sort of trying to do that. The given RSE there already wouldn't work for transfers, since it doesn't have an fts (or some other transfer manager) configured.

That would be fantastic! The code on that page is quite a bit too generic to really be helpful

@bjwhite-fnal bjwhite-fnal force-pushed the 399-rse-attributes-and-settings branch from 6738224 to 89c859d Compare December 4, 2024 18:15
@@ -119,7 +119,7 @@ Rucio will look for the config in the following locations -
cache provider for auth tokens. If False, use a private in-memory cache.
Default: `False`
#### **common**
- **extract_scope**: _(Optional)_ <!--??--> Default: `atlas`.
- **extract_scope**: _(Optional)_ Default: `atlas`.
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
- **extract_scope**: _(Optional)_ Default: `atlas`.
- **extract_scope**: _(Optional)_ Default: `def`.

This has been changed recently, see: https://github.com/rucio/rucio/blob/3d5cbf5d8c0e37f793bbd6f01d1064e44cfe0b4f/lib/rucio/common/utils.py#L577

@bjwhite-fnal bjwhite-fnal force-pushed the 399-rse-attributes-and-settings branch 2 times, most recently from a23d8c8 to eb2f42c Compare December 19, 2024 16:02
@bjwhite-fnal bjwhite-fnal force-pushed the 399-rse-attributes-and-settings branch from 126812b to 8ead320 Compare December 19, 2024 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants