[9.0] Support selecting legacy adaptor client #7258
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chrisburr
force-pushed
the
legacy-adaptor-selector
branch
from
96294ad to
0d72a7d
Compare
chrisburr
force-pushed
the
legacy-adaptor-selector
branch
5 times, most recently
from
2e7fbee to
c2f9472
Compare
chrisburr
force-pushed
the
legacy-adaptor-selector
branch
from
c2f9472 to
e18eb7c
Compare
chrisburr
requested review from
fstagni,
andresailer and
atsareg
as code owners
fstagni
reviewed
Nov 2, 2023
|
@fstagni As you marked the conversation as resolved, are you happy to merge? |
fstagni
approved these changes
Nov 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds the ability to enable the DiracX backend for RPC calls in a specific client by setting
/DiracX/LegacyClientEnabled/SYSTEM_NAME/SERVICE_NAMEin the CS. The existing DIPS/Tornado client selector logic is then used to conditionally redirect RPC calls to thediracxClientclass property of the client.This PR also modified the CS to switch from an EnabledVOs list to a DisabledVOs list for specifying which Virtual Organizations (VOs) should not use DiracX via the legacy compatibility mechanism. This better reflects how having DiracX enabled is a temporary thing during the deployment of DIRAC v9.
Closes #7188
Closes DIRACGrid/diracx#154
BEGINRELEASENOTES
*Core
NEW: Support using DiracX as a backend for RPC calls
ENDRELEASENOTES