xrootd proxy server with disk cache
50K+
You can at the official XrootD documentation for detailed information about the tool:
--nogrid: avoid WLCG CAs installation--health_port: port for healthcheck process listening, type=int, default=80/data/xrd/: saved file location for both cache and std modes/etc/xrootd/: config files dir/var/log/xrootd/cmsd.log: log of cmsd service/var/log/xrootd/cmsd.log: log of xrootd serviceJust put your xrootd config file in $PWD/config:/etc/xrootd
# with your xrd_cache.conf on $PWD/config
sudo docker run --rm --privileged -p 32294:32294 -p 31113:31113 -v $PWD/config:/etc/xrootd cloudpg/xrootd-proxy --config /etc/xrootd/xrd_test.conf
REMEMBER To expose the ports indicated in your config file. In the case of config/xrd_test.conf are: 32294, 31113
File saved will be put on /data/xrd, so you may want to mount your storage backend there
An health check is available on:
# response 0 everything running, response 1 something went wrong
curl <container_ip>/check_health
In case of response 1, with docker logs you can see a log dump of the crashed daemon.
You need to first install docker-compose. Then run use the docker-compose.yml file provided to bring up locally:
The command for bringing the full stack up is:
git clone https://github.com/Cloud-PG/docker-images.git
cd docker-images/xrd-proxy
/usr/local/bin/docker-compose up -d
To shutdown the stack:
/usr/local/bin/docker-compose down
# Put a test file on the remote host
sudo docker exec -ti xrdproxy_origin_1 touch /data/xrd/test.txt
# Request that file from the cache redirector xrootd process
# that is listening on 1094
sudo docker exec -ti xrdproxy_client_1 xrdcp -f root://localhost:1094//test.txt /dev/null
# If you find no error you can now check that the file is correctly cached on cache server
sudo docker exec -ti xrdproxy_cache_1 ls /data/xrd/
# you should see these two files: test.txt test.txt.cinfo
Content type
Image
Digest
Size
248.9 MB
Last updated
over 8 years ago
docker pull cloudpg/xrootd-proxy