-
Notifications
You must be signed in to change notification settings - Fork 107
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
MSTransferor: support input data placement with Rucio #9759
Conversation
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
For some reason, the
it must be missing some subtle detail of the import behavior. @todor-ivanov I believe there will be further changes to this PR. But just in case you can have a look at these changes by tomorrow morning, it would be great! Thanks |
Jenkins results:
|
Jenkins results:
|
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.
Alan, I made few minor comments in the code. Most of them could really be skipped, but one or two may be worth taking care of or at least double checked if not changed.
Todor, thanks for your review. Following your review, I have made further changes in my last commit. Please have another look, and if you agree, mark those conversations as resolved. |
Thanks @amaltaro I took a quick look at your new commit and I think you addressed everything I mentioned. I think the changes are good to go now. |
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
Jenkins results:
|
@nsmith- and @ericvaandering I think I have finally converged on this PR and tested the most common use cases. I might merge it today, but feel free to leave questions/comments at any time and I can follow up on those in a different PR, if needed. |
Jenkins results:
|
Jenkins results:
|
Implement whole logic of input data placement with Rucio fix import from PycurlRucio clean init file minor aesthetic changes import absolute_import one more absolute_import copy cert/ckey methods over to pycurlRucio useRucio flag might not be in the configuration file apply Todors suggestions use getattr for self.phedex set self.phedex instead Rucio initialization message complete RSE limits/usage logic fix key name name -> rse bytes_remaining is always 0, set it to quota fix getRucioToken getdata has no decode parameter fix getPileupDatasetSizesRucio function fix getDatasetBlocksRucio and getPileupSubscriptionsRucio fix getBlockReplicasAndSizeRucio method New pycurl function listReplicationRules fix listReplicationRule fail case API to fetch blocks and their sizes given a container Make the correct calls for PhEDEx and Rucio integrate pickRSE update long=1 to long=True fix logic for renewing the rucio token RequestInfo child class of MSCore; skip some service initialization fix keyword arguments fix MSMonitor NoneType; add debug rule log bugfixes to rule monitoring; rule creation; others support lifetime parameter for rule replicas fix MSOutput initialization more fixes to the pycurl rucio function; print grouping of the rules Make Rucio rule completion consistent with PhEDEx, percentage stuck_at returns a string datetime format minor logging fix
cleanup init.py module more fixes to unit tests unit test for blocks/sizes per container fix unit tests
Jenkins results:
|
All right, it should be tested enough by now... |
Fixes #9725
Fixes #9461
Status
In development
Description
Summary of changes are:
__init__
method to support sub-classes to provide service names that they do not want to be initialized;wmcore_transferor
ask_approval
always False;lifetime
andasynchronous
parameters for replication rule creation;In addition to that, there is:
It depends on the following new configuration parameters:
useRucio
: to enable/disable Rucio as a DM service (if disabled, PhEDEx is used)rulesLifetime
: defines an expiration time for all rules created by MSTransferor. Production rules (against the production Rucio server) have no expiration time.Is it backward compatible (if not, which system it affects?)
yes
Related PRs
none
External dependencies / deployment changes
Deployment changes:
dmwm/deployment#924
dmwm/deployment#942