Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
X
xrootd-softlink-plugin-cluster
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
j.knedlik
xrootd-softlink-plugin-cluster
Commits
f7474a7b
Commit
f7474a7b
authored
7 years ago
by
pkramp
Browse files
Options
Downloads
Patches
Plain Diff
added readme
parent
fab124bc
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
readme.md
+31
-0
31 additions, 0 deletions
readme.md
with
31 additions
and
0 deletions
readme.md
0 → 100644
+
31
−
0
View file @
f7474a7b
# XRootD Disk Cache Local Access
## Description
An XRootD - Vagrant setup using multiple XRootD plug-ins to implement fast access for clients to an XRootD Cache sitting on top of a shared filesystem
##Usage
-git clone https://git.gsi.de/dc/XRootD-Reps/xrootd-disk-cache-local-access.git --recursive
-cd alice-xrootd-builder-docker-container/
-sudo ./start.sh
-cd ..
-vagrant up
-vagrant ssh client
-./proxyprefixtest.sh
##Procedure explanation
###The client wants to copy a file from an external dataserver to the local filesystem:
-The client employs a plug-in, which prepends the address of the redirector/datamanager.
-The client then connects to the redirector, which checks for existence of the searched file on the shared filesystem in the used cms-plugin
-if the file exists, the client gets redirected to the shared filesystem, where it opens the file locally without involvement of any other server
-if the file does not exist, the plug-in redirects the client to the forwardproxy
-the client now connects to the forwardproxy, which opens a connection to the externalDataserver
-the file gets returned to the client and is simultaneously cached by the proxy on the shared filesystem
##Configuration
The forwardproxy needs the cache location:
-oss.localroot /home/vagrant/shfs
The manager/redirector needs the cache location:
-oss.localroot /home/vagrant/shfs
The client plugin for the proxy prefix needs the prefix in XrdProxyDefault.conf
-proxyPrefix=://192.168.1.200:1094///x
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment