 |
 |
Hi Andrew,
Sorry, I realize I should be more precise in what I am trying to achieve with this setup. I have multiple locations A, B, C and so on. In each location I want to run a disc-caching-cluster and for each location it is optional whether they have a data cluster. As each location is firewalled and has only a limited amount of public IPs, I want to front each location setup with a direct mode proxy, which is currently not part of the configuration above.
The machines which ultimately access the data should only have access to the local cache cluster, while the cache cluster has access to the local data cluster and to each direct mode proxy of each location, which is why I configured the cache cluster as a forwarding proxy. In the end I thought that I would be able to locate data from different locations for example by using <protocol><ip-of-local-cache-redirector><protocol><dns-of-direct-mode-proxy-of-different-location> or for local access as in my initial post by using <protocol><ip-of-local-cache-redirector><protocol><ip-of-local-data-redirector>.
As I understood from the documentation, each cluster needs a redirector, which is why I configured one redirector for the disc-caching-cluster and one redirector for the data-cluster, as I do not want the accessing machines from location A to utlimately access the disc-caching-cluster from location B and vice versa.
From your answer I gather that locating data (without the usage of further plugins and services) with xrdfs is only possible if the redirector I talk to is the redirector which manages the data-cluster?
Thanks and kind regards,
Ewgenij
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1