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
Include the network domain (wan, lan) in list_replicas #64
Comments
Just to link this to #62 where I layed out the plan for this. In the first iteration I will add empty signatures for domain to all the RSEManager methods. At that point, the list_replicas call can basically already use them. What we said today is, that list_replicas for the client in general should use domain='wan'. If an RSE is found witch matches with the client location, it should query again with domain='lan' for the RSE. |
i will extend it to list_replicas(.. , domain='wan') once the signature for create_protocol is merged. then we can gradually start making the clients domain aware |
…as_domain_aware__Fix__64 core: make list_replicas domain aware; Fix #64
…as_domain_aware__Fix__64 core: make list_replicas domain aware; Fix #64
…ubissue_62 bug: Commented out rsemanager syntax errors #62
Use the dataservice instead of DAS for block replicas
Motivation
For local usage, a combination of wan/lan attributes with rse_expressions will provide the local or remote replicas to a site.
Modification
added lan/wan in list_replicas (clients/rest/server). default wan
The text was updated successfully, but these errors were encountered: