-
Notifications
You must be signed in to change notification settings - Fork 172
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
[v7r1] FTS3: allow to alter TPC preference list and source SE with plugins #5096
[v7r1] FTS3: allow to alter TPC preference list and source SE with plugins #5096
Conversation
32c0485
to
4b0d4dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for being picky and difficult. :/
I think the plugin needs to be VO-aware.
Ah, this bloody VO parameter... OK, I'll try to cook up something. But that basically means that the initialization done can only be VO agnostic. I'll modify accordingly, thanks for the review |
@andresailer I changed the implementation, it should now propagate the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for incorporating all my suggestions! Some more comments for docstrings and comments
3592e47
to
8dac8ca
Compare
Thanks for the very careful review. I've just squashed all the commit together, and it runs fine in LHCb. Please re-approve, I'll remove the WIP |
Because some links may be special or some sites shitty, this mechanism allows for more flexibility in choosing a third party protocol or a source SE when transferring with FTS.
This comes with a Default plugin which does exactly what the hardcoded behavior was doing, and serves as documentation. It is totally backward compatible.
This is currently tested in LHCb
BEGINRELEASENOTES
*Subsystem
NEW: FTS3 plugins to alter TPC and source SE preferences
ENDRELEASENOTES