NOT MERGE: temporarily force WMCore services to production Rucio #972
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.
NEVER MERGE IT! It will be needed for a few more weeks until we get some changes applied to the Rucio integration instance.
On the WMAgent side, we need to update the 2 rucio urls under:
and the agent config.py (if running WMAgent >= 1.4.5.pre2), from:
to
FYI @todor-ivanov this should be all the changes we need to enable our private VM services to talk to Rucio production.
NOTE: MSTransferor is fully enabled, so be careful with the workflow you are going to assign and whether input data is already available or not...
NOTE-2: Unrelated to this, but we also disable MSOutput and MSUnmerged microservices for private VM deployment (to avoid MongoDB/Mongo client issues that don't allow the service to run!)